> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-oms-overview/shipping/order-weight-cap.md).

# Order Weight Cap

The Order Weight Cap holds unusually heavy orders for a quick review instead of letting them ship automatically. Chord simply puts the order on hold, tags it over-weight, and (optionally) emails your team so someone can decide how to handle it.

Typical use: catch a bulk order (e.g. 200 books) that's too heavy to ship as normal parcels before it goes out.

## How It Works

```mermaid
flowchart LR
    A[Customer checks out] -->|Order completes| B{Weight ≥ cap?}
    B -->|No| C[Ships normally]
    B -->|Yes| D[Held for review + tagged 'over-weight' + team emailed]
    D -->|Approve| C
    D -->|Cancel| E[Doesn't ship]
```

At completion, Chord adds up the order's shippable weight. If it's **at or above the cap**, the order is held (left unapproved, so it stays out of fulfillment), tagged over-weight, and your notification recipients are emailed. A held order will not ship until someone approves it.

## Getting Started

Go to **Settings → Shipping → Weight Cap**.

1. Set a **Weight cap (lb)** — orders at or above this weight are held (default 50).
2. Optionally add **Notification emails** — who gets the internal heads-up.
3. Click **Save & Enable**.

The cap is configured per store. Turn it off any time with **Disable** — your cap and emails are kept.

## Settings

* **Weight cap (lb)** — Orders whose shippable weight is at or above this are held. Must be greater than 0 to enable.
* **Notification emails** — *Optional.* Internal recipients emailed when an order is held. Separate multiple addresses with commas. This goes to **your team, not the customer**. Leave blank to skip the email (orders are still held and tagged).

## Reviewing held orders

A held order is complete and paid, but sits **unapproved** and won't ship until reviewed.

* **Find them:** **Orders → Over-weight** (a filtered list with an "Awaiting review" view), or filter the Orders list by the over-weight tag.
* **On the order:** a banner explains why it's held, and the order carries the over-weight tag.
* **Decide:** click **Approve** to release it for normal fulfillment, or **Cancel** if it shouldn't ship. What you do beyond that — ship it, contact the customer, arrange another carrier — is your team's process, handled outside Chord.

## FAQ

**Does this reject or cancel the customer's order?**

No. The order completes and the customer is charged/confirmed normally. It's only held internally for review before it ships.

**Who gets the notification email?**

Your internal team — never the customer. Add multiple recipients separated by commas. It's optional; without it, orders are still held and tagged.

**A held order isn't shipping — why?**

That's expected. Held orders stay out of fulfillment until approved. Open the order and click **Approve** to release it.

**We have a channel that auto-approves orders. Are heavy orders still held?**

Yes. The weight cap takes priority over auto-approval, so over-cap orders are always reviewed.

**Can different stores use different caps?**

Yes — the cap and recipients are per store.

**How do I turn it off?** **Settings → Shipping → Weight Cap → Disable.**

Your saved settings are kept for next time.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/chord-oms/chord-oms-overview/shipping/order-weight-cap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.