By the Onsites AI team · Last updated · 4-minute read
The three sales documents get confused most often by teams small enough to write them casually — the quote that quietly became a contract, the "order confirmation" sent before anything was ordered, the invoice sent with the order ("pay when we ship"), terms tangled into statuses nobody meant. The distinctions are not bureaucratic; they are what each document does in the relationship's timeline: the quote exists before commitment and expires by design; the order exists after acceptance and binds both sides to the same line items; the invoice exists after delivery and demands the money the other two promised. This guide gives each its exact job, the transitions between them, and the two or three mix-ups that cause most real disputes — with the desk's shared catalog keeping every version's numbers honest.
A quote is an offer — the full anatomy from the quote-writing guide — and its defining property is boundedness: specific items at specific prices, valid until a specific date, with the terms (payment window, delivery basis) stated exactly once in the money sentence. Quotes are not contracts; nothing binding exists until the buyer accepts, which is precisely why the validity window matters so much that deliberate quotes announce it: "valid until August 15" teaches the buyer what to decide by when, and re-opens the lane honestly if the date passes. The common mix-up: sending what is functionally a contract ("we hereby commit to supplying...") labeled as a quote — you have committed without a buyer signature, at your side a document that reads like an obligation and expires like an offer. Quote like an offer; the acceptance does the binding, visibly.
An order is what the deal becomes the moment the buyer accepts — same items, same prices, now a binding commitment on both sides, and a fact the desk can point at: who owes which production, which carrier, which delivery. In Onsites Mail the transition is deliberate (quote → accepted → order, same lineage), and its meaning is operational: the order drives fulfillment, the tracking pattern reads its state, and the buyer's "did we ship it?" resolves to the order's record rather than a memory. The common mix-up is the confirmation that precedes acceptance — a "thank you for your order" sent to a buyer who has not ordered yet reads as binding (and in strict contract terms may be one), which is why the acceptance line deserves the same visual deliberateness as the money sentence: "this quote — these items, these prices, these terms — is now confirmed as your order #1042, effective today." The order is where the documents stop describing and start committing; it deserves its own document.
Years of small-business invoices reduce to two recurring confusions, worth naming precisely. The contract-shaped quote: drafted with "we hereby commit to supplying..." in the quote template — a document that binds its sender while reading to the buyer like an offer; the discipline is the anatomy (the quote guide): offers propose, acceptances bind, and "valid until [date]" is stated rather than implied. The premature invoice: sent at order or before milestone because the template said so — in strict terms it may even create obligations the buyer never accepted, and in practical terms it converts the delivery conversation into a collection pressure; the honest sequence is delivery (or the milestone terms state it), then the money sentence, then the due date. The proforma variant deserves its own memory: international buyers pay against the proforma, the tax invoice comes after delivery, and the desk that sends the right document first-time never has to explain the difference under deadline pressure — which is when it is most expensive to explain.
The invoice is the oldest document in the family and the one with the strictest etiquette: it exists after delivery (or per milestone terms), it demands money (amount, method, due date — the money sentence, exact), and its statuses (sent → seen → paid, or overdue) drive the chase ladder. Two mix-ups deserve their warnings from the guides. The proforma confusion: international buyers pay against a proforma — the quote in invoice shape, not a VAT invoice — and the desk that sends the real invoice before or instead of the proforma confuses both payment and compliance (the full distinction in the proforma guide). The premature invoice: invoicing before delivery (or milestone) turns a demand into pressure and often breaches the terms the buyer signed — the desk's status trail exists precisely so "when deliverable → when invoice → when due" is a readable chain, not a negotiation. The invoice is where the relationship's money becomes formal; the two habits — money sentence exactness and honest statuses — are what keep it a document instead of a dispute.
Every document in the family quotes from one shared product catalog — the same items, names, and prices whether drafted as quote, confirmed as order, or invoiced — and everything the sequence does for trust reduces to that principle. The mix-ups the sequence exists to prevent are all variations of the divergent number: the €12,400 quote that invoices at €12,800 (re-typed between windows), the discount agreed in a chat that never reached the document, the annual order carrying last year's spreadsheet prices, the invoice that preceded delivery because a template said so. Onsites Mail's shared lineage makes each document inherit from the one before it: the quote carries the catalog's real names, the acceptance binds the quote's prices into an order, the invoice states the order's delivered amount — and if a price must change, it changes in catalog-land, once, and every downstream document quotes it from there. The result is less a feature than a promise: the buyer who reads your quote, confirms your order and receives your invoice is reading one story with one set of numbers — which is what "documents that agree with each other" always meant before the tools fragmented them.
What is the real difference between a quote, an order and an invoice?
Timeline and commitment. A quote is the offer — specific items, prices, terms, valid until a stated date, nothing binding until accepted. An order comes into existence on acceptance and binds both sides to the same line items. An invoice exists after delivery and demands the money those documents promised. Quote = offer, order = commitment, invoice = demand.
When does a quote legally stop being just a quote?
When it is accepted: the buyer's acceptance turns the offer into the order — same line items, same money sentence, now binding on both sides. A quote drafted like a contract ("we hereby commit to supply...") binds its sender even before that, which is deliberate quotes state their boundedness instead.
What is a proforma invoice, and how is it different from an invoice?
The quote in invoice form: international buyers pay against a proforma — it has the invoice's shape (items, amount, payment details) but isn't a tax document and doesn't demand post-delivery; it IS the payment instrument for the order being confirmed. A real invoice exists after delivery and settles what the proforma promised.
What statuses should each document carry?
Quotes: draft → sent → accepted or expired. Orders: confirmed → fulfilled (driving tracking and delivery). Invoices: sent → seen → paid, or overdue once past due — all of it on one trail the account view reads honestly.
What single principle keeps the document family honest?
One shared product catalog: items and prices drafted once in the catalog, inherited by every quote, bound by every order and stated by every invoice — so no number re-types and none drifts between sales, fulfillment and finance.