Workflow · order to invoice
The chain every load follows in Logis. Nothing below is typed twice: each record is born from the one before it, and the invoice reads the numbers everyone already agreed on.
01 · Order
Typed, started from a template, or received over the network from a client on Logis. Drafted by Logis AI from an email or a PDF Soon. Price, references, dates, requirements. Approving it makes it real.
Who: dispatcher, or the clientWrites: orders
02 · Cargo
One consignment: sender, consignee, loading place, unloading place, quantities, temperature, ADR. An order can hold several. Cargo waits in the pool until it is put on a carriage — and that is the month it counts for your plan.
Who: dispatcher (falls out of the order)Writes: cargo, cargo legs
18 plt · 11,400 kg · ambient
Seven records, one chain, two keyboards fewer. — the Logis team
03 · Carriage
Your own truck and driver, a private carrier you send a transport order to, or a network partner who gets it as a real order in their Logis. Dispatching sends it; the driver accepts on the phone. One carriage can hold many cargos and stay open for weeks.
Who: dispatcherWrites: carriages, dispatch
Carrier: choose
↳ Fork · network handoff
No free truck? Send it to a partner.
The carriage arrives as an order in their Logis with a transfer number. They accept, counter or decline on the record. Their driver’s stops show in your thread; their invoice to you reads the agreed price. Each company sees one level each way, and nothing further down the chain.
↳ Fork · recall
Changed your mind? Take it back.
Until the first cargo is loaded a dispatched trip can be recalled. The driver gets a card — quiet before they answered, loud if they are already moving. After the first load, the door is closed.
04 · Route
Generated from the cargo: load here, unload there, via a depot if the cargo has legs. Time windows, what to count and what to photograph. The driver sees today’s stops as a list.
Who: Logis, from the cargo; dispatcher adjustsWrites: route stops, tasks
05 · Stop & report
On site, loaded, counts differ, late, problem, delivered — each a card in the Inbox with a photo or a count. The dispatcher answers on the card. The office can report a stop for a driver too; the card is the same.
Who: driver, then dispatcherWrites: stop reports, Inbox cards
06 · Documents
CMR photographed at the ramp, POD, delivery notes, the carrier’s invoice — attached to the carriage and the cargo, shared with the partner for their leg. Logis AI reading and e-CMR signing Soon.
Who: driver, partnerWrites: documents
07 · Invoice
The agreed price, the waiting time the driver reported, the ferry surcharge allocated to the cargo — on your template, in the client’s language, with your numbering. The carrier’s bill to you reads the same number. Margin per route, live.
Who: accountant or dispatcher, one clickWrites: invoices, ledger entries
