Smart. Logistics.

Upload a sample file and talk it through with the AI. Core fields, custom fields, whatever your operation actually tracks. It becomes your canonical booking schema — versioned, confirmed, done.

Each customer's own spreadsheet gets its own mapping, learned once and reused automatically. Nobody on your team re-teaches the same columns twice.

Manual upload for the operators who need it. A documented API for the ones who don't. Both normalise against your schema and hit the dispatch board the same way.

A conversational flow that turns a sample file into a confirmed booking schema — no rigid template your customers have to conform to.

Every customer keeps their own file format. The platform remembers how to read it, so onboarding a new one takes minutes, not integration work.

A real vehicle-routing solve — Google OR-Tools assigns orders to vehicles by weight capacity and sequences each route for minimum distance, not nearest-neighbour guesswork.

A running stock balance per depot location, reconciled by scheduled cycle counts. Every movement logged — receiving, picking, adjustments — so a shortage shows up before a customer does.

Branded portals where your customers' customers book a return and track it — booked, collected, arrived at depot — no phone call needed.

Drivers see today's stops. Warehouse staff scan orders onto and off vehicles and confirm picks. Same app, same backend, access shaped by who's signed in.

Generated per order, ready to print, tied back to the schema so nothing needs re-keying at the label stage.

Barcode scan-in the moment an order reaches a depot, with a live warning on the routes board if a stop hasn't been confirmed there yet.

Customers who want to send data programmatically get a real, OpenAPI-documented endpoint and their own key — not a workaround.