Order arrives
Email, PDF, phone, spreadsheet, portal or API. AI drafts it; a person confirms it. Nothing commits itself.
Specified and in build · taking design partners
Orders turn up however your customers feel like sending them. boXe turns them into work — prepare, schedule, route, deliver, prove, invoice — for businesses that run their own delivery vehicles.
Animated illustration of a delivery depot: orders arriving from vendor portals, staff picking and packing, eight trucks delivering across a town, stock being received and put away, and a returns van collecting from a customer.
Does this sound like your Tuesday?
One delivery, start to finish
Most software owns one piece of this and hands you a spreadsheet at the seam. In boXe the order, the pick, the run, the proof and the invoice are the same thing, seen from different ends.
Email, PDF, phone, spreadsheet, portal or API. AI drafts it; a person confirms it. Nothing commits itself.
Picked, packed and staged against the delivery. Ticked off by hand in Release 1; driven by Inventory when you turn it on.
Manual in Release 1. The Inventory module raises the same "prepared" event with a scanner.
Confirmed orders become deliveries; deliveries land on runs built from templates. Tomorrow is done this afternoon.
No password. The next stop, front and centre. Works in the basement and the back paddock, syncs from the street.
Next stop
The Corner Deli
12 Marine Pde · back door · by 07:00
Signed in by a device link. No password at five in the morning.
Photo, signature, time, place. Shorts and rejects recorded at the door. Crates out and back on the ledger.
The proof becomes the bill, on delivery or accumulated weekly, and posts to Xero without a re-key.
Try it, right here
These are prototypes with invented data. The rules underneath come from the specifications, and they are what the demo shows.
Unread 3
Pick one, then watch it become an order.
Draft order
The draft appears here. A person confirms it; nothing commits itself.
What is built in
A delivery does not need an order behind it. Collections, returns, transfers and pickup-and-drop each have their own kind of delivery and proof steps.
Crates, kegs, cylinders, linen bags. Signed movements, derived balance, visible to the customer.
The same six trays every Tuesday without anyone remembering. Variations are exceptions, not re-keys.
It reads the email, the PDF and the spreadsheet, and proposes. A person or a rule commits. Always.
Own vehicles and regular contract drivers on one board. No gig marketplace, no strangers.
Each business on boXe is separated in the architecture itself, and tests that fail the build keep it that way.
Who it is for
The vehicles, the customers and the returnables change. The shape of the day does not.
Bakeries, meat, produce, dairy, beverage, catering supply
See your day 02Packaging, cleaning, hospitality supplies
See your day 03Bottles, cylinders, containers, recurring runs
See your day 04Hotel linen, uniforms, collection and return
See your day 05Timber, landscaping, plumbing, electrical
See your day 06Clinics, aged care, pharmacies
See your day 07Equipment, crates, kegs, pallets
See your day 08Warehouse plus delivery for clients
See your dayPricing
Every plan includes unlimited office users, unlimited portal logins and every driver on your fleet. Adding a person to the office never costs you a licence.
What separates the three is being set with the first cohort rather than guessed now and walked back later. Over thirty vehicles is a conversation.
Where we are
boXe is specified end to end, every module and every rule, and in build. The prototypes on this site are clickable today. There are no customers yet. We are taking design partners.
Become a design partnerThe demo
Your orders, your customers and your runs, walked through end to end on a call.