Logistics and supply
Logistics intelligence from order to reconciliation
A load that runs late touches the order, the truck, the receiving site and the tank forecast. One late load, followed to its receiving record, shows what has to hold when a record is late, missing or wrong.
A delivery crosses several systems before it becomes an accepted business record. Supply orders the product and plans the load. The supplier confirms a loading time. Logistics follows the truck through stage updates. The receiving site records what arrived and the tank readings around it, and Forecast counts the load in its estimate of when each tank runs out. Each team can finish its own task while the delivery as a whole still carries an open question.
This article follows one constructed example, a late load and its receiving record, through Ancilor. The site, quantities and times are illustrative. The platform page follows a late delivery across the modules.
A load that misses its window
The supply planner orders a tanker load of 30,000 litres for Site B in Ancilor Supply, due between 14:00 and 16:00. The supplier confirms loading at 08:00. Stage updates come in from the driver: loaded at 08:40, on the motorway at 11:15. Then nothing. At 16:00 the window has closed, Site B has no receipt, and its run-out estimate still counts the load.
The truck arrives at 19:40, after the site manager has handed over to the night attendant, who supervises the unloading and takes tank readings before and after. The receipt is completed the next morning: 29,640 litres measured in the tank against 30,000 on the supplier's delivery document.
| Record | Comes from | What it establishes |
|---|---|---|
| Order and planned load | Ancilor Supply | What was ordered, for which site and window |
| Stage updates | The driver or forwarder | That a stage was reported, and when |
| Delivery document | The supplier | What the supplier says it loaded |
| Receipt and tank readings | The receiving site | What arrived and what the tank measured |
| Run-out estimate | Ancilor Forecast | When the tank runs out on current assumptions |
Keep commitments, reports and confirmations apart
An order is an intention. A planned load is a commitment with a window. A stage update is a report from the road: it records that someone said the truck was on the motorway at 11:15, not where the truck is now. A receipt is a confirmation from the destination, and the tank readings around it are measurements. Fold all of these into one delivery status and the late load looks either fine or lost, when the honest answer is "reported on the motorway at 11:15, nothing since".
When a supplier revises an arrival time, Ancilor Logistics keeps the original commitment beside the revised one. The planner can see that the window moved, who recorded the change and when.
Match the receipt to the right load
Identifiers come from different places. Supply has its own order and load numbers, the supplier prints its own document number, and the site enters what it reads off the paperwork at the gate. Two suppliers can issue the same document number, so a receipt matched on that number alone can attach to the wrong load.
The receipt should carry the document number together with its issuer, and the match should use both, along with the site and the expected window. The same rule holds for electronic freight documents, the subject of Regulation (EU) 2020/1056 on electronic freight transport information: keep each document's own identifier and issuer.
Ancilor is designed to make the link where the records point to one load, and to log who confirmed it. Where two open loads for the same site overlap in time, the receipt is designed to stay unmatched and go to the dispatcher with both candidates side by side. A tidy guess is worse than an open question with an owner. And a receipt sent twice from a phone with a weak signal must still count once.
Know how old each figure is
At 16:00, the latest stage update is almost five hours old. Shown without its age, "on the motorway" reads like a current position. Every figure on the dispatcher's screen needs its time and its source: the last stage update, the tank reading behind the forecast, the supplier's confirmation.
Freshness also limits what other parts of the system may do. Ancilor Forecast stops a run when its tank readings are too old, rather than publishing a run-out date built on stale inputs. When Ancilor Supply cannot reach the operations records, it shows its last copy and the time it was taken, rather than an empty list. Both choices give up a confident-looking answer for an honest one.
Forecasting, planning and AI answer different questions
| Function | Question | What it needs |
|---|---|---|
| Forecasting | When does this tank run out if nothing changes? | Dated tank readings, sales history and the age of each input |
| Planning | Which load goes where, and when? | Open orders, vehicle capacity, delivery windows and what each site can receive |
| AI assistance | What happened to this load, and what should we ask? | The records the user may see, and a person to review the answer |
In the example, Site B's forecast should show that it still includes a load that has not arrived. Moving the next load is the supply planner's decision. AI can summarise the load's history and draft the question to the supplier. It does not change the delivery, the stock or the order.
When the site cannot take the load
Change one detail. Site B's receiving bay has an open repair: an inspection found a leaking valve at the fill point, the repair is under way, and the bay is on hold until the technician finishes the next morning. The late truck is now the smaller problem. The questions are whether anyone can receive the load when it arrives, and whether the tank lasts until then. The dispatcher sees the truck, the site manager sees the repair and the planner sees the run-out estimate, a range rather than a single date. None of them sees the conflict alone.
Ancilor is designed so that a hold on a receiving bay appears beside the deliveries due there, with the job, its owner and the expected finish, and so that the run-out estimate is read against it. The options are the ones the records allow: keep the revised arrival if the repair can be finished first, reschedule the load for after the repair, or agree another receiving plan with the site manager. The planner chooses one and records why. A rescheduled delivery is designed to count as confirmed only when the supplier confirms the new time, and to show as requested until then, beside the original window. Only the person responsible for the repair should lift the hold, and never to make a delivery plan work. The article on AI-assisted decisions follows this case from the planner's side, and the article on maintenance explains the hold.
Who confirms, who acts
The dispatcher follows up the silent truck and records the revised arrival. The night attendant records the tank readings, and the site manager completes the receipt and explains or flags the 360-litre difference. The supply planner decides whether the next load for Site B moves.
In Ancilor, these steps are actions with a named owner, logged with who took them and when, rather than side effects of another record changing. Payment stays where it belongs: finance pays the supplier from the accounting system, against the received quantity, once the difference is explained.
What Ancilor reads, and what it leaves alone
Stage updates come from the driver or forwarder, and receipts and tank readings from the site. Ancilor reads from the systems a business already runs, such as accounting and bank files, and does not write into them, or into a supplier's or forwarder's systems. Matches and corrections are made in Ancilor and logged with who made them and when. When two systems disagree, each keeps its own record, and the difference is visible in one place.
Test the awkward cases first
Start with one route and one product, and test the cases that break things: a receipt that arrives after a newer status update, a receipt sent twice, a partial delivery that must leave the remainder open, a receipt that could belong to two loads, a source that stops answering, a dispatcher trying to approve a stock adjustment. Each should end in a state someone can explain, with a named owner for whatever is still open. Then add the next route.
References
- Regulation (EU) 2020/1056 on electronic freight transport informationEuropean Parliament and Council of the European Union, 2020. eur-lex.europa.eu/eli/reg/2020/1056/oj
Start with one workflow.
Bring one process, the systems it already runs on and the decision your team needs to make.