> For the complete documentation index, see [llms.txt](https://fundpop-crowdfunding.gitbook.io/fundpop-crowdfunding-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fundpop-crowdfunding.gitbook.io/fundpop-crowdfunding-docs/faqs/orders-and-statuses.md).

# Orders and Statuses

## How do order statuses change for mixed pre-order campaigns?

When an order contains multiple pre-order products from different campaigns, the order status will change throughout the lifecycle of the campaigns. Here's how it works:

**Initial Status After Checkout**

* If the order only contains pre-order items, the status will be **Pending**
* If the order includes a pledge fee or regular (non-pre-order) products, the status will be **Partially Paid**

**When First Campaign Ends**

* When the first campaign reaches its end date, the status changes to **Paid**
* At this point, ALL pre-order items in the order are charged (not just items from the first campaign)
* This happens because Shopify processes all deferred payments in an order based on the earliest due date

**If Later Campaigns Fail**

* If a later (All-or-nothing) campaign fails, we automatically initiate a refund for items from that campaign only
* The order status changes to **Partially Refunded**
* Items from successful campaigns remain paid and are not affected

For example: An order contains pre-order Product A (Campaign 1) and pre-order Product B (Campaign 2):

1. Initial status: **Pending**
2. Campaign 1 succeeds and reaches end date: Status becomes **Paid** (both A and B are charged)
3. Campaign 2 fails: Status becomes **Partially Refunded** (refund issued for Product B only)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fundpop-crowdfunding.gitbook.io/fundpop-crowdfunding-docs/faqs/orders-and-statuses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.