Plenty of importers have a well-drafted supply agreement in a folder and order against a one-page document listing a product name, a quantity and a price. When a dispute arrives, the framework contract says how disputes are resolved and which law applies — which is valuable — but it does not say what was ordered. Only the purchase order says that, which is why it is the document that actually decides.
Why this document, and not the contract above it
A framework contract sets the rules of the relationship. The purchase order applies them to one specific production run, on one date, at one price, for one revision of the product. Everything that changes from run to run lives in the order, and everything that changes is what people later disagree about.
There is a second reason, less legal and more practical. Inside the factory, the framework contract sits with management. The purchase order goes to the people who plan, buy materials and run the line. If a requirement is not on the order, it is not in front of the person who will decide whether to follow it at two in the morning on the last day of the run.
What a purchase order has to contain to be worth something
| Section | What it must say | What goes wrong when it is vague |
|---|---|---|
| Product and revision | Your own part number, the product name, and the revision of the specification or drawing that applies | Goods made to an earlier revision arrive, and both sides are convinced they were right |
| Quantity and tolerance | The quantity ordered, and whether an over- or under-delivery is accepted and within what limit | A partial delivery is invoiced in full, or a surplus arrives unordered and unpaid for |
| Price and currency | The unit price, the currency, what is included, and how long the price holds | Tooling, testing or packaging turn out to be extra, discovered on the invoice |
| Incoterm and place | The rule, the named place, and the version of the rules used — an Incoterm without a place says nothing | Nobody knows who pays which freight and where the risk transfers, which surfaces only after a loss |
| Dates | The date the goods must be ready, distinguished from the shipping date, plus what the supplier owes if it slips | « Ready soon » becomes a season, and the delay is announced when it is too late to react |
| Acceptance criteria | What is inspected, against which reference, by whom, where, and what happens to a rejected lot | Quality becomes a matter of opinion, argued after the goods have left China |
| Packing and marking | Inner and outer packaging, quantity per carton, labels, markings required at destination | Goods arrive sound and unsellable, or blocked because a required marking is missing |
| Payment terms | The split, what triggers each instalment, and the account the money goes to | The balance is claimed before the goods are acceptable, and your only leverage is spent |
The three lines people leave vague
Quantity tolerance comes first, because it looks pedantic and is not. Many production processes do not land exactly on a number, and a factory that has committed to an exact figure will either make extra and invoice it, or fall short and deliver anyway. Say in one sentence what deviation you accept, in which direction, and whether you pay for the difference. That sentence costs nothing and removes an entire category of argument.
Dates come second, and the problem is never the date itself: it is what happens when it slips. Distinguish the date the goods are ready from the date they ship, because the first is the factory's responsibility and the second often is not. Then write the consequence — notification within a stated time, a revised date agreed in writing, and what you may do if the second date slips too. A consequence nobody wrote is a consequence nobody owes.
Acceptance criteria come third, and they are the ones that decide who pays for a bad lot. « Good quality » is not a criterion. A named reference sample kept on both sides, a written inspection standard, the place where inspection happens and the rule for a failed lot — rework, discount, replacement or refusal — is a criterion. Write it while everyone is optimistic, because it can only be written then.
How the order and the framework contract fit together
The two documents are not rivals; they answer different questions. The contract says how the relationship works: confidentiality, ownership of tooling and designs, liability, applicable law, how a dispute is settled. The order says what is being made this time. The clause that keeps them from fighting is one line in the contract stating which prevails if they disagree — and in practice, the order should govern the commercial terms of that run while the contract governs everything structural.
Watch for the reverse trap as well: the supplier's own confirmation. Many factories reply with a sales confirmation carrying their own terms on the back, sometimes different from yours. If you sign it without reading it, you may have accepted a different agreement from the one you sent. Compare the confirmation with your order line by line, and raise any difference before payment rather than after delivery.
A useful test before sending: could someone who has never spoken to this supplier, holding only this order, tell whether the delivered goods conform? If not, the missing information is exactly what you will be arguing about later — and adding it now takes minutes.
A purchase order written this way is longer than a price and a quantity, and shorter than a contract. It takes an afternoon to build the first time and is then reused for every run, with three or four lines changing. That afternoon is the cheapest insurance in the whole purchasing process, and the only one that also makes the factory's job easier.