Orders from anywhere
However the order arrives, it enters the same way.
Email, a PDF from the customer's own system, a phone call typed by the office, a spreadsheet, the portal, the API or a standing order: every source dispatches one create-order command. Prices, GST and the delivery day are snapshotted there and never re-resolved.
Unread 3
Pick one, then watch it become an order.
Draft order
The draft appears here. A person confirms it; nothing commits itself.
Capture from email, PDF and text
Inbound messages land in an artifact store. Extraction reads them into a draft order with provenance, so every line points back to the words it came from. A person confirms; nothing commits itself.
Draft orders and promotion
Drafts hold anything uncertain: an unmatched product, an ambiguous quantity, a customer we cannot resolve. Promotion to an order happens once, through the one write path, with the same snapshots as a typed order.
Cutoff and delivery-day resolution
Each customer has delivery days, windows and a cutoff. Orders resolve to a valid delivery day with a reason attached ("after 2pm cutoff, next Tuesday") instead of being silently bumped.
Standing orders, generated
Recurring orders are a schedule, not a reminder. A fleet-wide sweep generates occurrences per tenant; variations and week-pauses are exceptions the office sees, not re-keys.
Spreadsheets and CSV
Onboarding reads the spreadsheet you have kept since 2011 and proposes customers, products and prices. CSV import runs through the same validation as everything else.
Where this matters most
The same module, in your trade.
See how order intake shows up on a normal morning in the trades boXe is built for.