> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/orders.md). # Rmfg Orders Blocks that track paid RMFG orders through production and shipping. ## RMFG Get Order ### What it is Fetches an RMFG order's status and shipment tracking ### How it works Fetches `/v1/orders/{id}`: the status (`received`, `in_production`, `ready_for_pickup`, `shipped`, `delivered`, `cancelled` or `refunded`), estimated ship date, line items, a status history, and carrier tracking once shipped. An unknown ID is reported as `RMFG not_found_error: `. `tracking_url`, `tracking_number` and `estimated_ship_date` are emitted only when RMFG has them, so a graph can branch on their presence; `amount_total_cents` is `0` until the order carries a total. ### Inputs | Input | Description | Type | Required | | --------- | -------------------------------------------------------- | ---- | -------- | | order\_id | Order ID from Pay Cart or an order.status\_changed event | str | Yes | ### Outputs | Output | Description | Type | | --------------------- | --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | error | Error message if the request failed | str | | order | The full order | Order | | order\_id | Order ID | str | | status | received, in\_production, ready\_for\_pickup, shipped, delivered, cancelled or refunded | "received" \| "in\_production" \| "ready\_for\_pickup" \| "shipped" \| "delivered" \| "cancelled" \| "refunded" | | tracking | Carrier, number and link once shipped | OrderTracking | | tracking\_url | Carrier tracking link, once shipped | str | | tracking\_number | Carrier tracking number, once shipped | str | | estimated\_ship\_date | Planned ship date, when known | str | | amount\_total\_cents | Amount charged, USD cents | int | ### Possible use case **Shipping Notification**: When an `order.status_changed` event arrives, load the order and message the customer with the tracking link. **Delivery Confirmation**: Check for `delivered` status before closing a support ticket. **Cancellation Handling**: Detect `cancelled` or `refunded` orders and update the internal record. *** ## RMFG List Orders ### What it is Lists the RMFG account's manufacturing orders ### How it works Reads one page of `/v1/orders`, newest first, with `limit` between 1 and 100, and returns `next_cursor` when there are more. Feed the cursor back in to page; an empty `next_cursor` means the last page. An invalid cursor is rejected by RMFG and surfaced as `RMFG : `. An account with no orders yields an empty `orders` list, no `order` items and an empty cursor. ### Inputs | Input | Description | Type | Required | | ------ | ------------------------------------------------------------ | ---- | -------- | | limit | Orders per page. | int | No | | cursor | next\_cursor from a previous page; empty for the first page. | str | No | ### Outputs | Output | Description | Type | | ------------ | ------------------------------------------------------------------ | ------------ | | error | Error message if the request failed | str | | orders | This page of orders | List\[Order] | | order | One order at a time | Order | | order\_ids | IDs in the same order | List\[str] | | next\_cursor | Pass back as cursor to fetch the next page; empty on the last page | str | ### Possible use case **Weekly Production Report**: Page through all orders and summarise what is in production versus shipped. **Open Order Dashboard**: List recent orders and filter to those not yet `delivered`. **Reconciliation**: Match order totals against the accounting system's records. *** --- # 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://agpt.co/docs/integrations/block-integrations/orders.md?ask=&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.