Order-to-fulfillment sync for a small e-commerce shop
An internal build showing how a store, a spreadsheet and a courier can be wired together so stock and status never drift out of sync.
0
manual re-keying between systems
Internal build — observed in our own system, not a client deployment
Same day
tracking sent automatically on dispatch
Internal build — observed in our own system, not a client deployment
Exceptions
surfaced, not hunted for
Internal build — observed in our own system, not a client deployment
Problem
A growing shop tracks stock in a spreadsheet, takes orders on a storefront, and books couriers by hand. The three never quite agree. Oversells happen, customers ask "where is my order?", and someone reconciles it all every evening.
Before — the manual workflow
- 01
Order placed on the storefront
- 02
Stock spreadsheet updated manually (when remembered)
- 03
Courier booked by copying the address by hand
- 04
Tracking number emailed to the customer manually
- 05
Evening spent reconciling mismatches
Intervention
A sync layer that treats the order as the single event: it decrements stock, books the courier, writes the tracking number back, and notifies the customer — with a daily exception report for anything that does not match, instead of a nightly manual reconciliation.
An internal build, not a client story
This is a system we built and run ourselves rather than a paid client engagement, and it is labeled that way. The figures come from our own deployment; when we run this for a customer, the results section will cite measured client outcomes instead.
The idea
Make the order the single source of truth. Everything downstream — stock, courier, customer notification — reacts to it. Reconciliation becomes an exception report, not a nightly chore.