Make the update trustworthy before making it automatic
A vendor email, a tracking number and a delivery appointment describe different events. Combining them into one order status can create a reassuring dashboard that hides what the studio still needs to do. AI is most useful when it gathers evidence and highlights the next decision.
At Marais Home, our own retail and design business, we built an order tracker that brings together order information and updates from connected sources. Its working rules include preserving human corrections, keeping snapshots and recording unresolved matches. This guide draws on those patterns; it does not promise unattended reliability or describe a finished product available to every studio.
Begin with a tracker your team can review. Automated updates should make an existing operating process easier to follow, with a named person responsible for exceptions and stale information.
Track individual items and preserve the source
Use stable references for project, vendor order, purchase order and line item. Keep ordered quantity, shipped quantity and received quantity separate. A single order may include furniture still in production, an accessory already received and a damaged item awaiting resolution.
For each update, store the evidence link or document reference, source date and time the tracker checked it. An estimated ship date belongs in a different field from an actual shipment date. Receiving at a warehouse is different from delivery to the client.
Define statuses in ordinary language before connecting sources. For example, confirmed means the vendor acknowledged the order; shipped means there is evidence the relevant goods shipped; received means the relevant destination acknowledged receipt. Your business may use other stages, but everyone should understand what qualifies an item to move forward.
A worked example: one order, two different outcomes
Fictional example: purchase order PO-104 contains a sofa and two lamps. A vendor email says the lamps have shipped and gives a tracking number. The sofa remains in production. The proposed update should mark two lamps as shipped, attach the evidence and leave the sofa unchanged.
A later carrier update says delivered. Before recording the lamps as received, confirm the destination and the shipment match. Delivery to a receiver does not mean installation at the client’s home. If the source only says your order has shipped without identifying items, put the update in a review queue.
If one lamp arrives damaged, keep its physical receipt and its open claim as separate facts. Overwriting everything with received would hide the follow-up; replacing everything with damaged would hide that the other lamp is ready. A good tracker preserves both the logistics and the unresolved work.
Keep corrections and uncertainty visible
When someone corrects a status after speaking with a vendor, the next refresh should not overwrite that decision from an older email. Marais’s tracker includes a status lock for this reason. A practical adaptation also records who made the correction, when and why, with an explicit way to release the lock.
Give uncertain updates a home: unmatched order references, conflicting dates, missing documents and quantities that do not reconcile. An ambiguous match should remain a candidate. It should not become a confirmed update merely because a model can write a convincing explanation.
Keep a history of changes and summarize what actually changed on each refresh. Preserve the previous state so a mistaken update can be inspected and reversed. Avoid forwarding generated client updates automatically until a person has checked that the underlying evidence supports them.
Monitor the process as well as the orders
A scheduled task can stop when a connection expires or a machine becomes unavailable. Show the last successful check for each source and make a failed or overdue refresh visible. A current-looking dashboard should never conceal that it has not received new information.
Start with one active project and a manual review of proposed changes. Test a partial shipment, a duplicate message, an unclear reference and a human correction. Measure whether the tracker makes review easier and whether its exceptions are useful before increasing its authority or adding more projects.
- Agree on item identifiers, status definitions and acceptable evidence.
- Connect a limited set of relevant sources and preview proposed changes.
- Review uncertain matches and verify that human corrections survive refreshes.
- Add visible freshness checks, change history and an owner for follow-up.