Quotations live in inboxes
A quote sent from someone’s mail client is invisible to everyone else. Nobody can say what was offered, at what price, or whether it still stands.
Sales
Sales runs on the same customer, item and stock records as everything downstream. A price agreed on a quotation is the price on the order, on the dispatch note and on the invoice, because all four are reading one record.
The problem
None of these are dramatic failures. They are the small, daily leaks of running sales in a tool that knows nothing about the rest of the business.
A quote sent from someone’s mail client is invisible to everyone else. Nobody can say what was offered, at what price, or whether it still stands.
Customer-specific rates and agreed discounts sit in people’s heads. The wrong one gets applied and nobody notices until the invoice is queried.
What was quoted is re-keyed into an order, then into a dispatch note. Each retype is a chance for a quantity or a rate to change without anyone deciding it should.
Three orders commit the same pallet because the person taking the fourth had no way to see what was already spoken for.
Capabilities
Five groups, all reading the customers, items and price lists already held in the Core OS.
From first enquiry to a document the customer can act on.
The rate that applies, applied without anyone looking it up.
The record everything downstream reads from.
What this customer is allowed, held on the customer.
What is open, what is late and what it is worth.
Workflow
The same reference runs through all six. Nothing is re-entered on the way.
A sales order moves through six stages: enquiry, quotation, approval, confirmed order, stock reservation and invoice.
01 Enquiry
SO-2026-0148
Logged
02 Quotation
SO-2026-0148
Sent
03 Approval
SO-2026-0148
Approved
04 Sales order
SO-2026-0148
Confirmed
05 Stock
SO-2026-0148
Reserved
06 Invoice
SO-2026-0148
Raised
Use cases
Different rates by territory and by customer, applied automatically rather than looked up in a rate sheet that three people maintain differently.
A quotation raised against an incoming consignment, so what is promised is tied to what is actually arriving and when.
Two branches selling to the same customer see one credit limit, one order history and one set of agreed terms.
Works with
These read and write the same Core OS records, so a handover between them passes a reference rather than a retyped copy.
Real-time stock across warehouses, batches and serial numbers.
Planning, picking, loading and proof of what actually left.
Import and export orders with their documentation and landed cost.
Invoicing, receivables and reporting off operational records.
FAQ
Yes. Price lists and per-customer rates live on the customer record in the Core OS, so the right rate is applied wherever that customer is used — quotation, order, invoice — without anyone having to look it up.
If Inventory is active, yes. The quotation reads available stock at the moment it is prepared, so you are not promising what is already reserved against another order.
The order stays open for the balance. Partial dispatch, backorder and amendment are ordinary states on the order itself, not a second document someone has to remember to raise.
Yes. Approval rules are Core OS workflow, so sign-off can be required by value, by discount level or by customer, and the record of who approved what is kept with the quotation.
Have a different question? Talk to us.
Bring a quotation you sent last week. We will show what the same one looks like when the order, the stock and the invoice are reading it.