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

# Managing Release Orders

Once a release is published, CrushSuite builds one release order per member and tracks it through billing. This article covers where those orders live, what each status means, and what you can do befo

***

#### How orders are created, and where to find them

Members who customize get a release order the moment they confirm; everyone else is picked up in a bulk pass shortly after the **Customization Deadline**, with the release's default products.

Day to day those orders live on the release itself, in the **Member orders** card — there's no separate Orders tab. To open the full orders screen, use **Review N orders** on the red attention banner at the top of the release, or **View all** under the billing table on a shipped release. The rest of this article describes that screen.

#### The four statuses

Each order carries one of four statuses, each with a matching filter chip:

| Status              | Meaning                                                                                       |
| ------------------- | --------------------------------------------------------------------------------------------- |
| **Default**         | No order yet, or one with the release's default products and no billing problem.              |
| **Customized**      | The member confirmed their own product selection.                                             |
| **Skipped**         | The member (or you) skipped this release for them.                                            |
| **Needs attention** | A billing attempt failed, or the order has a pre-processing data error, and it isn't skipped. |

Filter with **All**, **Customized**, **Skipped**, **Default**, and **Needs Attention**, or search by name or email. One quirk: the skipped badge here reads **Orders Skipped**, while the filter chip and order detail page say **Skipped**. Same status.

***

#### Highlighted Issues

When a release has problem orders, a **Highlighted Issues** section appears above the order table, collecting them in one place. It's hidden when there's nothing to show.

Each row carries a **Category** — **Payment**, **Compliance**, **Shipping**, **Contract**, or **Billing** — and a **Severity** of **Critical**, **Warning**, or **Info**. Failed billing and pre-processing checks are critical; a failed compliance check is a warning. Narrow the list with the **Category** and **Issue state** dropdowns. Each row's state is **Open** or **Resolved**, set from its own dropdown — CrushSuite never resolves one itself. Marking a highlighted issue **Resolved** and clearing the order's own error flag are separate controls: if an order still won't process after you've resolved the highlighted issue, check the order itself and clear its error flag too.

{% hint style="warning" %}
A failed compliance check is recorded as a note on the release order. It does not stop the order from being created or billed. If you need shipments hard-blocked on compliance, configure that in CrushSuite Compliance's pre-checkout requirements. See [Clubs and CrushSuite Compliance](https://crushsuite.gitbook.io/docs/clubs/reference/clubs-and-crushsuite-compliance).
{% endhint %}

***

#### Taking action on an order

Open an order's detail page and use its **More actions** menu for **Skip release** / **Unskip release**, **Send payment update email**, **Clear error flag** (shown when a pre-processing error is present), and **Retry billing** (shown once a billing attempt exists but no Shopify order does). **Retry billing** creates the subscription contract first if the order never got one, then starts a new attempt against the same contract and payment method — it won't succeed if the payment problem hasn't changed. Send a payment update email first. If that menu item is greyed out, the member has no saved payment method at all; send them their portal link instead.

The page has four editable cards: **Order summary** (**Edit items**), **Notes & gift** (customer note and gift message together), **Payment**, and **Delivery**. **Payment** shows its **Edit** only when the member has a saved payment method to switch to.

All of this disappears once the order exists in Shopify — it's a live Shopify order at that point, and changes belong in **Shopify Admin**.

> 📸 **Screenshot:** The release orders screen: filter chips, the Highlighted Issues table, and a row badged **Needs attention**.

***

#### Late signups and migrated members

Members who joined after the **Signup Cutoff Date** are excluded from the bulk pass and listed above the main order table under **Late Signups**. Click **Process** to create their order, generate a contract, and attempt billing in one pass. Each step runs independently, so a partial result still leaves a usable, retriable order. Migrated members left without an order get their own section just below, with the same **Process** action.

{% hint style="info" %}
If orders in this release aren't billing the way you expect, see [Release Orders Didn't Bill](https://crushsuite.gitbook.io/docs/clubs/troubleshooting/release-orders-didnt-bill).
{% endhint %}