PRODUCT Β· ORDERS Β· LIFECYCLE

Every state change. Who, when, why.

An order isn't a row in a database. It's a six-month relationship with a manufacturer, a freight forwarder, and a buyer who all need different things from the same record at different times. TradeOS treats lifecycle as the discipline that holds it together β€” every transition logged, every approval traced, every exception handled cleanly.

Book a demoSee pricing β†’

TradeOS
HomeTasksOrders
⌘K SearchSC
RD-2026-077Brevin Health EU$560,000
In productionHigh priority

Production

LotPL-2026-0138ManufacturerSapphire Mfg.AQL1.5Units8,000,000
62%

Commercial

IncotermCIF HamburgCurrencyUSDTerms30/70 LCMargin21.2%
Deposit received$168,000

THE PROBLEM

Most order systems treat lifecycle as "created" and "closed."

QuickBooks has Open / Paid / Closed. Flexport tracks logistics states. Cin7 models warehouse fulfillment. None of them model the multi-month commercial relationship trade actually requires β€” proforma sign-off, deposit gates, manager approval thresholds, partial fulfillment, mid-production amendments, exceptions caught and recorded. Trade operators end up running half their lifecycle in spreadsheets and email threads. The audit trail lives in someone's inbox.

13 STATES, ONE TIMELINE

Six visible milestones. Thirteen operational states underneath.

Operators see a clean six-step rail on every order β€” Order Created, Confirmed, Production, QC, Shipped, Delivered. The platform tracks a richer underlying state machine that includes approval gates, deposit waiting, and exception terminals. The two views serve different purposes: the rail is for daily operations, the state machine is for compliance and audit.

APPROVAL GATES3 optional Β· configurable per tenantDraftConfirmedIn productionQC completeReady to shipShippedDeliveredClosedFROM ANY ACTIVE STATE:CancelledOn hold
Active stateTerminal Β· successTerminal Β· cancelledPause Β· resumable

APPROVAL GATES

Three gates between draft and shipped.

Approval gates pause an order in a holding state until the right person signs off. Three types, all configurable per tenant.

CLIENT APPROVAL

Send. Sign. Advance.

Send the proforma. Client signs off in their portal. State advances automatically. Used when the client requires formal sign-off before production starts.

MANAGER APPROVAL

Rule triggers, manager approves.

Triggered by configurable rules β€” order value above threshold, new manufacturer, rush priority, sanctioned-risk destination. Routes to manager queue with full context. Approving advances; declining sends back.

DEPOSIT GATE

Production paused, deposit pending.

Production paused until deposit received. Visible blocker on the order detail with a "Mark deposit received" affordance for the operator.

WHEN THINGS CHANGE

Cancellation and on-hold, with the impact on record.

Trade orders run for months. Things change. EDMA handles cancellation and on-hold as first-class state transitions, not afterthoughts. Cancellation requires a reason and an impact assessment showing what gets affected β€” open invoices, in-progress lots, booked shipments. On-hold pauses everything with a resume affordance and a reason on file. Both write to the audit trail like any other transition.

EVERY TRANSITION ON RECORD

Who. When. Why.

Every state transition writes to an immutable audit log: timestamp, actor, from-state, to-state, reason if provided, originating task if triggered by one. Useful for compliance audits, dispute resolution, and "wait, who approved that?" moments. Operators can filter by transition type, actor, or date range. The audit trail is read-only β€” even admins can't edit it.

Audit Β· RD-2026-077
AllStatus changesApprovalsDocumentsComments
Mar 1, 09:14
Order created
Sarah ChenSales
Mar 4, 14:22
Draft β†’ Pending manager approval

Trigger: order value > $250K threshold.

Sarah ChenSales
Mar 4, 16:08
Pending manager β†’ Confirmed

Approved as standard terms.

Marcus PatelManager
Apr 1, 10:30
Confirmed β†’ In production

Lot PL-2026-0138 started.

Liam OkaforOperations
Apr 18, 09:55
Note added

Sapphire delayed 4 days.

Liam OkaforOperations
May 2, 13:11
In production β†’ Shipped

Shipment SHP-2026-088 departed Port Klang.

SystemAuto

RULES YOUR BUSINESS NEEDS

Approval rules you configure, enforced consistently.

Set up approval rules once in Settings; they apply to every order automatically. Common rules: orders above $X require manager approval, orders to a new manufacturer require quality manager sign-off, rush priority requires director approval, orders to sanctioned-risk countries require compliance review. Rules are evaluated on transition attempt; matching rules route the order to the approver's queue instead of advancing.

VS. THE TOOLS YOU MIGHT BE USING

Lifecycle is what other tools don't have.

CapabilityQuickBooksFlexportCin7TradeOS
Order states38 (logistics)513
Configurable approval gatesβ€”β€”β€”βœ“
Immutable audit trailpartialpartialpartialβœ“
Configurable rules engineβ€”β€”β€”βœ“
Mid-flight cancellation w/ impactβ€”β€”β€”βœ“
On-hold with resumeβ€”β€”β€”βœ“

Most order tools weren't designed for trade. They were designed for warehouse fulfillment, accounting, or logistics β€” and bolted onto trade after the fact. EDMA models trade from the start.

FREQUENTLY ASKED

Frequently asked

Five questions about the lifecycle.

No β€” the 13 states are fixed for data integrity. But which transitions trigger approvals, notifications, and downstream actions are fully configurable per tenant.

See lifecycle running on your real workflow.

Book a 30-min demo and we'll set up your tenant with your approval rules, your products, and walk through a real order from draft to delivered.

Book a demoOr book a demo β†’

Order lifecycle Β· State machine, approvals, audit trail | TradeOS