Route, and the floor

20 September 2026. The sixth release of the 1.0 programme covers the half of an order that happens after it is confirmed, and the half of a job that happens on the floor. An order that is confirmed is not an order that has arrived: between the two sit picking, packing, a label or a van, a window you promised, a signature at a door and a cost nobody was booking against the job. Route is all of that. Machinist already gave the operator a screen at the machine; now there is one job behind every nest and every run, and the minutes come from the scans rather than from a form filled in afterwards.

The order reaches the door

• A delivery is one consignment: the address, the window you promised, the packages, the tracking and the proof. An order can have several, and several deliveries to one site on one van are grouped by the stop.
• The order now carries the address it is delivered to, frozen onto the delivery. A later edit to the customer's address never rewrites a note that has already been printed.
• A second axis beside the commercial status, from pending through to delivered, worked out by one function in the same breath as every delivery write, so the two can never disagree. No screen types over it.
• Proof of delivery is a signature, photographs, the printed name, the time and the place, recorded as a scan event on the delivery's own code. It is a trail, not a status flag. A failed delivery keeps its reason and can be rebooked as a new one: a failed delivery is never edited into a success.
• Delivery notes, packing lists, collection notes and the load manifest are real documents, branded like the rest.

Couriers, honestly

• One generic labels and tracking connector is native: point it at your own carrier account or aggregator.
• Every named carrier works today as a record you keep by hand, with its own label printed and its tracking address pasted once.
• Kabaido ships no tracking address prefilled, for any carrier, because an invented tracking link is an invented fact. A test fails the build if one ever appears.
• First party carrier connections are on the roadmap with no date, and the product, the integrations list and the docs all say the same thing.

Your own vans

• Territories, vehicles, runs and stops. A customer with a Tuesday keeps their Tuesday: the planner opens the territory's next matching day and their stop is already on it.
• Road order sequencing with a map, a drag that always wins, and a distance labelled as planned and straight line every time it appears. Actual kilometres come from the odometer when the run closes.
• A stop with no pin sorts last and asks to be pinned. It is never guessed.
• Loading is built for a scanner: packages in reverse stop order, a missing count that stays red until it is zero, and a departure that asks why if the van leaves short. A parcel that is not yours joins the manifest with a label, so the manifest is complete even when the goods are not.
• Closing a run asks for the odometer, works out what the run cost from your own rates and shares it across the deliveries on it. A cost worked out from a planned distance is shown as planned, never as actual.

The driver's screen

• Today's run, the next stop as one large card, and three things to do at the door: delivered, collected or failed. Navigate hands the stop to Google Maps or Waze.
• It works with the network off. Every action is saved on the device and sends itself when the signal comes back, in order, exactly once. Photographs queue too, and the screen says when there are too many to hold.
• A scan made in a blackspot is recorded at the time it happened, on the trail and in the stock ledger alike, so a day out of signal does not move the goods to the moment the van found a bar.

With Kabaido Stock on

• A van is a location, a load is a transfer onto it, and closing the run reconciles it to zero.
• Without Kabaido Stock nothing is lost: the same issue and the same return are written at your one default location and every figure stays true. What Stock adds is the place to see them together.

The floor, above the machines

• One job behind every nest and every run, carrying its own code through every station. Nothing on the machine screens moved: a machinist who used Arcline yesterday uses it the same way today.
• Machines are stations, each with its own screen at the machine, its own hourly rate and its own device key. That screen can move its jobs and reach nothing else.
• Operators, with what each is certified to run and what an hour of their time costs.
• A day and week board per machine, sized by standard minutes, with a late marker. The same jobs give the same board, and a drag writes the order and nothing else. No solver and no AI decide what you make next.
• Costs per job, machine, operator and month, standard against actual. Actual minutes come from the scans, and a typed correction is stored with the reason for it. Where a rate is missing the screen says so rather than showing a zero.
• Your customer can see the status of their own production order, and nothing else.

Built to order

• Five design modules are listed as built to order with the work each would need first: solid round tools, machine knives, superabrasive wheels, woodworking cutter heads, and coating racks and jigs. Ask for one from the same card.