Fulfilling a delivery request - Pacten Guides
Once a request is in the queue and has any approval it needs, fulfilment is tracked on the shipment rather than on the request. That distinction matters: one order can go out in more than one shipment, and each is at its own point.
The queue is under Delivery → Delivery Requests. The flat list of everything in flight sits in your Work index, which is named for your sector — Shipments for a logistics workspace, and something else for others.
A shipment is not given a status. Its state falls out of two facts — whether it has left, and whether it has arrived — so the operator view and the page your client sees cannot disagree with each other.
An order can hold as many shipments as it needs — three pallets leaving on three days is three shipments against one request. Each carries its own carrier, tracking reference and dates, and each moves through the four states independently.
The order-level state is always the least advanced of its shipments. An order showing Preparing when two of its three shipments have arrived is correct: something is still outstanding.
Someone assigned to a delivery gets a schedule of their own runs, grouped as Today and Tomorrow, with one button per shipment — Mark picked up, Mark delivered, or the pickup wording where that applies.
- They see only shipments they are actually assigned to, not the whole queue.
- The buttons advance the same two facts the desk view reads, so marking a run delivered updates the order and the client’s status page at the same moment.
- A run with no agreed date is shown separately rather than being dropped from the schedule.