Features

Everything between the order and the invoice.

Not a suite. A short list of things a delivery business does every single day, done properly.

Intake

Getting the order in

The order arrives in whatever form the customer felt like sending. It should still land as clean data.

Email and paste: Forward or paste an order email and it comes back as a structured draft — customer matched, lines matched, quantities read.
Photograph a list: A phone photo of a handwritten or printed order gets read and turned into lines you can correct before approving.
History-aware suggestions: Line matching leans on what this customer actually buys, so ambiguous descriptions resolve to the right product.
Approve, then it is an order: Intake produces a draft, and a draft is not on the board. A person approves it and it lands in Ready.

Board

Six states, one board, one truth. Everyone from the office to the loading bay is reading the same row.

Ready → Run → Out → Review → Capture → Done: A state only exists where real work happens. Capture is the one people forget to build: delivered, but not yet invoiced. It gets flagged after two days so nothing is quietly given away.
Customer-specific pricing: Lines price against that customer's own list, with per-line discounts and manual overrides when the deal is the deal.
Quotes: Quote a customer, keep the number and the PDF, then turn the accepted quote into an order without retyping it.
Full trail: Who changed what, when, and what the order looked like before. Cancellations and collections included.

Delivery

The run is the unit of work for the yard. Build it once, print it once, load it once.

Areas and vehicles: Define delivery areas and the vehicles that serve them, with capacity so you can see a run filling up.
Stops in order: Set the stop sequence for the run, move orders between runs, and print the route the driver actually drives.
Pick sheets and pick lists: A pick sheet per order for accuracy, one consolidated pick list per run for speed. Both from the same data.
Delivery notes and POD packs: Batch-print the paperwork for a whole run so nothing leaves without its documents.

Return

Most of the money leaks after the truck comes back. This is the part everyone skips.

Per-line review: Log short, damaged, wrong or refused against the line it happened to, while the driver is still standing there.
Credit, replace or back order: Each discrepancy gets an outcome. Back orders are new orders that stay linked to the one they came from.
Document mailroom: Scanned and emailed invoices and PODs are read, matched to the order and customer, reviewed, then sent on in bulk.
Export for capture: The priced order goes to your accounting system for invoicing, and the invoice number comes back onto the order.

Buying

Ships free with the product today. Built on the data the connector already syncs.

Buying runs: Stock on hand, open orders and recent sales in one view, so the reorder decision has numbers behind it.
Shortfall visibility: See where committed orders outrun available stock before a customer finds out for you.
Supplier view: Group what needs buying by supplier and export the list.
Purchase orders: Today the buy list exports for capture in your accounting system, which raises the POs and keeps owning stock. A purchase-order flow inside Marula Flow is on the roadmap.

Portal

A big enough part of the product to have its own page.

Their catalogue, their prices: Each customer logs in to their own products at their own prices, on your own domain.
A cart that waits: One persistent draft they build across the week and send when it is complete.
Quotes end to end: They request, you price, they accept — and the accepted quote becomes an order in Ready.
Invoices, PODs and their own PO number: Documents sit on the order, and the customer's purchase order comes in with it.
Document library: Spec sheets, SDS and certificates linked to products, shown to the customers who buy them — plus public share links that need no login at all.

The customer portal has more to it than fits here.