Delivery days are derived from real cut-off times, and loading is executed against pallets and orders that have already passed their checks.
Dispatch is where every earlier mistake becomes a customer phone call. Linari plans from what is real — cut-offs, checked orders, confirmed pallets.
An order that misses today’s cut-off is planned for the day it can genuinely leave. Cut-off times differ per warehouse — 15:00 in one live site, 12:45 in another.
Live · per warehousePallets are built, confirmed and manifested as tracked objects, not as a note on a printout.
Live · always onWaybill documents are generated and held against the shipment record.
Live · always onInvoice and dispatch data flow back into the ERP through the same interface layer that brings orders in.
Live · always onCut-off times are per warehouse, because trucks do not leave every building at the same hour.
| Operating rule | Ambient DC | Fresh produce | Third site |
|---|---|---|---|
| Pick-plan cut-off time | 15:00 | not used | 12:45 |
In the demo, ask us to open two live warehouse configurations side by side and change one rule while you watch. That is the difference between configuration and a promise.
It is planned for the day it can genuinely leave — not squeezed into a plan the floor cannot execute. Cut-offs are real, and they are per warehouse.
Loading is executed against pallets and orders that have already passed their checks, and pallets are tracked objects with confirmation — not a note on a printout.
Yes. Invoice and dispatch data flow back through the same interface layer that brings orders in — with failures visible and replayable, not silent.
From released order to confirmed pallet to waybill — live in the system, with your cut-offs.