> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/referral-program/management/orders.md).

# Orders

Most referral orders need nothing from you — Bloop records, checks, and rewards automatically. This view is for the few that need a decision: an order on hold, one flagged as suspicious, or a referral that happened off-platform.

> **Best practice:** Review held orders weekly, not as a fire drill. A flagged order sits on a 14-day hold and follows your normal rules if you do nothing — a quick weekly pass clears legitimate referrers before they wait too long and catches abuse before a reward is paid. Pair this view with the [Fraud center](/referral-program/management/fraud-center.md).

### Order status

| Status            | What it means                                  | Reward paid? |
| ----------------- | ---------------------------------------------- | ------------ |
| Unused (internal) | Referee claimed a discount, hasn't ordered yet | No           |
| Pending           | Order recorded, reward on hold                 | No           |
| Approved          | Passed all checks, reward issued               | Yes          |
| Rejected          | You declined it                                | No           |

An order moves Unused → Pending → Approved or Rejected. **Pending costs you nothing** — it's your only cheap window to catch a problem before the reward exists. Even after Approved, Bloop can **revoke** a reward if the order is later cancelled or fully refunded — see [reward revocation](/referral-program/rewards.md#revoking-a-reward).

### Why an order is held

* **Review period** — your campaign's configured delay (in hours) before a reward approves. `0` means instant.
* **14-day fraud hold** — Bloop flagged the order as suspicious. This overrides your review period.

A short review period (a day or two) suits most stores; go longer if your return rate is high or order values are large.

### Which orders need you

| What you see                                                  | What to do                                                                                                           |
| ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Pending, no flag                                              | Nothing — it approves itself                                                                                         |
| Pending, fraud-flagged                                        | Check the [Fraud center](/referral-program/management/fraud-center.md); approve or reject before the 14 days run out |
| Referee cancelled or refunded during the hold                 | Reject — there's no sale to reward                                                                                   |
| A referral that never appeared (phone order, uncaptured code) | Add it manually                                                                                                      |

When evidence is ambiguous, approving is usually the gentler default — a rejected genuine advocate often stops sharing. Reserve rejection for a clear, repeated abuse pattern.

### Approve or reject an order

1. Open **Referral orders** and find the order.
2. Review the referee, referrer, order value, and any fraud flags.
3. **Approve** to issue the reward, or **Reject** to decline it.

Approving a flagged order clears its fraud case; rejecting marks it disqualified and notifies the referrer.

### Manually add a referral order

1. In **Referral orders**, add an order.
2. Enter the Shopify order number, amount, and customer.
3. Choose the referrer to credit and the campaign (active campaigns only).
4. Optionally issue the reward immediately.

Bloop blocks duplicates — an order already linked to a referral, or a customer already tied to one, can't be added again. A manual order is recorded as **Approved**, except for a **custom reward**, which stays **Pending** for you to fulfil by hand.

### Common mistakes to avoid

* **Chasing unflagged pending orders.** They approve themselves — spend your attention on flagged ones instead.
* **Ignoring the held queue for weeks.** Past the 14-day window, a fraud flag's protection lapses.
* **Rejecting a genuine order to be safe.** A denied real advocate often stops sharing.

### Next steps

* Investigate flagged orders in the [Fraud center](/referral-program/management/fraud-center.md).
* Learn how rewards are calculated in [Referrer and referee rewards](/referral-program/rewards.md).


---

# 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://docs.bloop.plus/referral-program/management/orders.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.