Workflow recipes
Use these end-to-end playbooks when you have a result in mind and need the shortest path through Orderly. Each recipe combines setup, validation, launch checks, and the signals to monitor afterward.
| If you want to… | Start here | Typical outcome |
|---|---|---|
| Move store orders into a shipping system | Route Shopify orders to ShipStation | A tested order flow with a narrow routing rule and rollback plan |
| Check whether carrier invoices match negotiated rates | Audit a carrier invoice | A repeatable cost review with discrepancies prioritized |
| Act on shipments before delivery risk becomes a late delivery | Intervene before a shipment is late | A daily alert-triage and escalation workflow |
A safe way to use any recipe
- Define one test case. Use a test order, a small invoice sample, or one tracking number before expanding the workflow.
- Record the starting state. Capture the source record, current status, and expected result so the test is easy to evaluate.
- Change one thing at a time. Narrow filters and rules make failures easier to diagnose.
- Confirm the downstream result. A successful action in Orderly is only complete when the destination system reflects the expected state.
- Assign an owner and rollback. Decide who watches the first production run and how they will pause or reverse it.
Need a different path?
- Start with account setup if your organization or platform connections are not ready.
- Use troubleshooting when a sync, rate, webhook, or API workflow is already failing.
- Follow production readiness before an API integration begins handling live traffic.