fft order
Manage orders
Manage the orders of your tenant.
An order is the demand the platform fulfills: what a consumer asked for, where it goes, and how. It is the object every fulfillment flow starts from — the platform sources and routes an order into the pickjobs, packjobs and handovers that carry it out. You do not create those directly; they arise from the order.
An order moves through OPEN, PROMISED, LOCKED, CANCELLED and OBSOLETE. Reading is cheap; every write is versioned. A mutation reads the order first to learn its current version and sends that version back — the API rejects a write that carries a stale one. Pass --if-version to skip that read when you already know the version: you get a clean 409 instead of a silent overwrite if you were wrong.
<id> is the order's platform id, the one 'fft order list' and 'fft order get' print. There is no tenantFacilityId-style shorthand for orders.
Usage
fft order [flags]Subcommands
- fft order cancel — Cancel an order
- fft order create — Create an order
- fft order get — Show one order
- fft order list — List orders
- fft order search — Search orders (BETA)
- fft order unlock — Unlock a locked order
- fft order update — Update an order (PATCH)
See also
- fft — parent command
This command also accepts the global flags.