Organisation Map
The highest view in the registry: every documented automation, what it runs on, and where its work ends up — laid out in the order an order actually moves through them.
Like everything else on this page and the one below it, the diagram is generated from the entries each time the site is built. It cannot show something the registry does not contain, and it cannot contradict an entry, because it is made from them.
Start here to get oriented. Go to the Integration Map when you need the detail — which rule touches which system, and which fields two integrations both write.
How to read the diagram
The page reads in journey order, not in folder order. The chevron band across the top is the sequence the business actually moves through, from what we choose to stock to what comes back — an order has to be placed before anything can ship or deliver it — and every entry sits under the stage it belongs to. Click a chevron to jump to its stage. That is what makes the map navigable: you can find where in an order's life a thing happens without already knowing which integration owns it. A stage with nothing documented at it stays on the band, greyed, because an empty stage is worth seeing.
| Stage | Covers |
|---|---|
| 1 · Buying | What Buying & Merchandising commit to — what we choose to stock, and the purchase orders raised with suppliers |
| 2 · Supply | Getting the stock into a warehouse and knowing when it will land: arrival dates, movements between warehouses, and the lead time a shopper reads |
| 3 · Order | The order itself — what is stamped onto it at the moment of sale, and what is written back onto its lines while it waits |
| 4 · Pre-Delivery | The run-up to a delivery: picking the courier and the day, and agreeing that day with the customer. Nothing has moved yet |
| 5 · Delivery | The consignment on its way, and what is known about where it has got to |
| 6 · Post-Delivery | Once the goods are with the customer — returns, claims, and anything that follows |
Two of the six read as more obvious than they are. Buying is the Buying & Merchandising team's own work, not the shopper's — the lead time a customer sees on a product page is Supply, because it is supply information the shopper happens to be shown. And an automation that writes onto an order that already exists is Order, wherever the information it writes came from.
Within a stage, entries are grouped by business area. Each row is one documented entry, read left to right:
| Position | Means |
|---|---|
| Left | The source of truth — the system whose value wins when they disagree |
| Middle | The automation itself. Click it to open the entry |
| Right | The other systems it touches — where the work lands |
Rule IDs are not on this page. They are on the entry and on the
Integration Map, which is where you go when you need them. This map answers what
exists and in what order; a column of LI-BL-… codes under every box answered a question nobody
was asking here and buried the one thing the box is for — its name.
Two kinds of dependency, drawn differently
The difference matters, and the map keeps them apart on purpose:
| On the map | Means | Front-matter |
|---|---|---|
| An arrow labelled then starts | One automation starts the other when it finishes. A real trigger | runs_after |
| A Needs first line under a box | This has to have run already for the box above it to be reading the right thing — but nothing chains them | depends_on |
A Needs first with no arrow is the shape worth stopping on. It means two automations that
depend on each other run on separate schedules: the second can read yesterday's answer, finish
cleanly, and look like it worked. That is not a hypothetical — it is LT3-D2, and it is why the
distinction is drawn rather than collapsed into one arrow.
An entry with neither runs on its own and depends on nothing documented. If that is wrong, the fix is on the entry, not here — the map cannot show a dependency nobody recorded.
Hover any box and its plain-language explanation appears beside it; click to pin it.
The order journey
7 business areas · 10 entries (5 draft · 5 active) · 53 rules
1 · Buying
What Buying & Merchandising commit to — what we choose to stock, and the purchase orders raised with suppliers. Every promise made further down the journey inherits these decisions.
Nothing documented at this stage yet — a gap in the registry, not necessarily a gap in the business.
2 · Supply
Getting the stock into a warehouse and knowing when it will land: arrival dates, movements between warehouses, and the lead time a shopper reads on the product page.
Lead Time
Transfer Order Automation
3 · Order
The order itself — what is stamped onto it at the moment of sale, and what is written back onto its lines while it waits.
Delay Comms
Lead Time
Supply Chain
4 · Pre-Delivery
The run-up to a delivery: picking the courier and the day, and agreeing that day with the customer. Nothing has moved yet.
Delivery Date Confirmation
Shipping Automation
5 · Delivery
The consignment on its way, and what is known about where it has got to.
Courier Tracking
6 · Post-Delivery
Once the goods are with the customer — returns, claims, and anything that follows.
Nothing documented at this stage yet — a gap in the registry, not necessarily a gap in the business.
Where to go next
Integration Map — the detail beneath this picture: every rule and the systems it touches, and every field with the rules that read or write it, flagging any field written from more than one entry.