What an Apparel Purchase Order Should Contain

Purchase orders get treated as administration. In a garment programme they are closer to a control document: they are what production is planned against, what goods are received against, what an invoice is checked against and what everyone refers back to when two people remember an agreement differently.

This guide covers what belongs in one and how it relates to the other documents in an order. It is about operational completeness, not legal completeness. Whether a document creates a binding contract, and what any clause in it means, depends on the contract and its governing law, and those are questions for a lawyer.

Which document is which

Four documents circulate in the same email thread and are routinely used as though they were interchangeable. Keeping them apart makes the rest of this straightforward.

A typical order of events, not a required one. Some transactions merge steps and some add their own; what matters is that each step has a document behind it rather than a recollection.

A purchase order is not a tech pack

This distinction causes expensive confusion. A purchase order saying five hundred hoodies, black, is a complete commercial instruction and a useless manufacturing instruction. It does not say which fabric, at what weight, in which construction, to which measurements, with which decoration, in which sizes, with which labels, packed how.

The two sets should reference each other rather than duplicate each other. A purchase order that reproduces the whole specification will drift out of step with it the first time the specification is revised; a purchase order that names the specification and its revision stays correct.

The fields an apparel purchase order needs

Not every field applies to every order, and no list of fields makes a document legally complete. What follows is what a manufacturer needs in order to plan, produce, pack, ship and invoice an order without going back with questions.

Why a total quantity is not enough

Apparel is the reason purchase orders have matrices. A single style exists in several colours and every colour exists in several sizes, and the factory cannot cut anything from a total. The size breakdown drives the marker, the fabric consumption, the cutting plan and the packing, so a quantity that is not broken down is a quantity that cannot be produced.

Two practical points. Give the matrix per colour rather than per style, because colours are cut separately and a colour with an unusual breakdown affects consumption. And state the size range in the same designations as the approved measurement chart, so nobody has to interpret whether your L is the chart's L. Where those designations come from is covered in size charts for production.

Naming the date properly

A delivery date on a purchase order can mean several different things, and the ambiguity is entirely avoidable. Ex-factory, the date goods are ready and available at the factory, is a different milestone from the date they ship, and both differ from arrival at a destination. Which one your date refers to determines whether transit time sits inside or outside the deadline.

Name the milestone, and make sure it is consistent with the delivery term. It is also the date the whole production calendar is planned backwards from. See time-and-action calendars. It matters twice over, because the milestone the order names is the one any delivery measure should later be calculated against. See building a supplier scorecard. A date described as delivery on a DDP order and on an EXW order refers to two different moments. What controls the production timeline itself is covered in production lead times; the purchase order's job is only to state the agreed milestone without ambiguity.

Referencing rather than restating

Packing is the clearest example. A purchase order should not carry every carton dimension, fold instruction and label placement. It should point at the packing specification by name and revision, and let that document carry the detail. The same applies to artwork, labelling and any compliance requirement. What a packing specification itself contains is covered in pack-out specification.

Quantity variance, and what happens if it moves

Cut quantities and delivered quantities are not always identical. Fabric behaves, cutting produces loss, and pieces are rejected at inspection, so some programmes agree a tolerance and some require exact quantities. What matters is that this is agreed rather than discovered.

• There is no universal tolerance. Any allowable variance above or below the ordered quantity is a commercial term and should be stated in the order if it applies.
• A buyer does not automatically have to accept extra pieces, and a supplier does not automatically have the right to ship them. If overmake is contemplated, say so and say on what basis it is invoiced.
• A buyer does not automatically have to accept a shortage either. Whether a short shipment is acceptable, and what happens if it is not, depends on what was agreed.
• Say it once, in the order. A tolerance discussed verbally and not written down is not a tolerance.

When the order changes

Orders change. Quantities move, a colour is added, a delivery date is pulled forward, a label changes, artwork is revised. The failure mode is not that changes happen; it is that they accumulate across a message thread until nobody can say what the current order is.

A material commercial change should end up in updated order documentation, whether a revised purchase order, a revised confirmation or whatever the two companies use, rather than only in the conversation that produced it. What counts as material is a judgement, but the list below is a reasonable starting point.

• Quantity, or the size and colour breakdown within the same total
• Price, currency, payment terms or delivery term
• The required date or the milestone it refers to
• Material, colour or any change to the specification revision the order points at
• Artwork, decoration method or placement
• Labelling, packing or destination

The same discipline applies on the technical side, where a specification carries its own revision history, which is the reason a purchase order references a revision rather than restating content. Version control in the specification itself is covered in the tech pack guide.

When does production actually start?

There is no single trigger, and pretending otherwise is how programmes end up with a factory waiting on an approval the buyer thought had been given. What starts production is whatever the two sides agreed has to be true first, and that list is worth writing down at the beginning.

The prerequisites usually come from two directions at once.

A commercial order can legitimately exist before every technical detail is closed. That is normal, and it is often how material is booked in time. What should not happen is bulk production running ahead of an unresolved critical approval. Which approvals genuinely gate production is covered in the pre-production sample reference, and what happens when bulk is produced against something unapproved is covered in when bulk differs from the sample.

Before you send the order

None of this is bureaucracy for its own sake. An order that carries these answers is one a factory can plan, cut, make, pack and invoice without a single clarifying email, and the time saved lands directly in the delivery date.