No. 19Operations systems3 min readOCTYN
Tracking a trade order from quote to delivery without losing status midway.
Tracking a trade order from quote to delivery without losing status means keeping one record per order that every step writes into, from the supplier checks through payment, shipping and claims. The record says which step the order waits on and who it waits for, and a person still closes anything that moves money or commits the company.
Ask a trading company where one of its orders stands and somebody goes to find the latest message about it. Whichever party wrote last is the status. It stays the status until somebody else writes in and says something slightly different. For an order that is moving, it hardly matters. When a shipment stalls, though, the first sign is usually the buyer asking where it is.
Where the status of an order lives today
A cross border order passes through a lot of hands before anyone is paid. A buyer asks for a price and a supplier quotes it. After that the bank needs documents for the letter of credit and the forwarder needs a booking, with an insurer behind them in case the goods turn up short or broken. Each party knows its own part well. Inside the trading company, the only place all the parts meet is somebody's inbox, read by whoever remembers what the earlier messages meant.
Years of supplier and buyer relationships sit in chat threads that only the people who wrote them know how to read. That works for a long time. Then one of those people is away in the same week a supplier's certificate goes missing.
One record per order, written into by every step
The order desk OCTYN designed for a trading company starts from the other end. A buyer's request becomes one order record, and every step after intake writes into that same record instead of opening another thread. Moving an order from one step to the next is what the glossary calls orchestration.
| Step | What lands on the order record |
|---|---|
| Intake | product, quantity, terms and destination |
| Supplier checks | certificates, inspection and supplier documents, checked against the order |
| Payment | what the bank asks for escrow or a letter of credit |
| Shipping | the booking and shipping papers, and each milestone as it happens |
| Claims | the evidence, already attached when a delivery is short or damaged |
Then the status question has a plain answer. The operations view is drawn to show each open order with the step it is waiting on and who it is waiting for. First thing in the morning, the team sees the orders at risk, with the reason written next to each one. The thread with the buyer carries on, and anyone who wants the whole conversation can read it, but what is true about the order now lives in the record.
The steps a person still closes
In the design, accepting a supplier waits for a person on the team, and so does confirming an order to a buyer. Anything that moves money waits for a person too. The system gathers the documents and prepares the step, then stops there until somebody closes it.
A drawing, so far
The trade order desk has been mapped and drawn, and that is all. OCTYN mapped the order path with the company across every workflow an order touches and drew the system and where it stops. It was not built for them. It is not running, and the demo on the case page runs on synthetic orders.
What the mapping did settle is mostly ownership. The order record replaces the message chain as the place an order's state lives, and which steps a person closes and which the system prepares and carries got decided one at a time. That split is the one worth arguing over inside your own operation, before anything gets built.
Buyers will still write in to ask where their goods are, and whoever answers will have the order open in front of them.
Bring the version of this that is about your company.
The first conversation is with the people who would build it. If there is a fit, the Consult comes next.