24 June 2026SKUWorks Team

10 Purchase Order Mistakes That Cause Supplier Delays and Warehouse Problems

Purchase Orders
Operations
purchase orders
supplier management
sku data
carton configuration
packaging
warehouse operations

Why purchase order mistakes cost product brands so much

Purchase orders are often treated like admin paperwork. For product brands, that is where things start to go wrong.

A purchase order is part of the production and fulfilment instruction set. If key fields are vague, missing, or inconsistent, the supplier has to guess, pause, or proceed on the wrong assumption.

That is how small PO mistakes turn into operational failures:

  • factories produce the right item in the wrong variant
  • suppliers pack units into the wrong inner packs or master cartons
  • warehouses receive stock that does not match the expected carton configuration
  • retailers reject deliveries because carton labels or pallet rules were missed
  • invoices do not match expectations because the unit of measure was unclear
  • teams waste days reconciling email edits against outdated PO versions

These are the purchase order mistakes that create delays, rework, chargebacks, and avoidable supplier friction.

What a supplier-ready purchase order needs to do

A supplier-ready PO should let the supplier execute without chasing basic clarifications.

At minimum, it should clearly show:

  • what product is being ordered
  • which exact SKU or variant applies
  • quantity and unit of measure
  • pack structure and carton configuration
  • label and packaging requirements
  • ship-to details and delivery terms
  • the approved version of the order

If your PO cannot answer those questions quickly, it is not ready.

For a fuller reference, see How to Write a Supplier-Ready Purchase Order.

Mistake 1: Missing or unclear SKU references

SKU ambiguity is one of the most common PO mistakes, especially for brands with multiple colours, sizes, finishes, bundles, or regional packaging variants.

Typical failure points include:

  • using a product name but no SKU
  • using an internal SKU the supplier does not recognise
  • using a supplier item code without the brand SKU reference
  • combining multiple variants under one vague line item
  • relying on colour names like "blue" or "large" without a precise variant code

How it breaks supplier execution

A PO might say:

  • "Water bottle, 1,000 units"

But which one?

  • 500ml or 750ml
  • matte black or gloss black
  • EU barcode or US barcode
  • single unit or gift set

If a supplier has to work it out from an old email thread or attachment name, the risk of error is high.

How to prevent it

Use line items that include:

  • brand SKU
  • supplier item code if applicable
  • full variant description
  • size, colour, and finish attributes
  • barcode or GTIN where relevant

A simple rule: if a warehouse receiver or factory planner cannot identify the exact item from the PO line alone, the reference is too weak.

This is much easier when your SKU structure is consistent. See How to Structure SKUs Properly (Before You Print Anything).

Mistake 2: Not specifying pack quantities and inner pack logic

Many purchase order errors happen after the product itself has been identified correctly.

The supplier knows what to make, but not how to pack it.

Common missing fields include:

  • units per inner pack
  • inner packs per carton
  • units per master carton
  • whether cartons must be mixed or single-SKU
  • whether retail packs, display packs, or bundles apply

Real example

A wholesale order lists 8 SKUs and total units for each. The PO does not state that each SKU must be packed in inner packs of 6, with 4 inners per carton. The supplier ships loose units in mixed cartons to hit the total quantity.

The products are technically correct. The shipment is operationally wrong.

Now the brand has:

  • longer warehouse receiving time
  • relabelling or repacking costs
  • possible retailer non-compliance
  • confusion in inventory counts

How to prevent it

Be explicit about pack logic on every PO where it matters:

  • ordered quantity in selling units
  • units-per-pack structure
  • inner pack quantity
  • master carton quantity
  • whether split cartons are allowed
  • carton assortment rules if mixed cartons are required

This is where many PO templates fail. They leave space for quantity and price, but not for the operational fields that actually drive packing.

Mistake 3: Using the wrong unit of measure

A PO that says "1,000 units" may look clear internally and still be unusable for a supplier.

Does 1,000 mean:

  • eaches
  • pairs
  • sets
  • cartons
  • kilos
  • metres
  • pallets

This is one of the most damaging common PO mistakes because it affects production, invoicing, receiving, and stock booking.

Typical unit of measure conflicts

PO wording

1,000 units

Supplier interpretation

1,000 sets

Brand expectation

1,000 individual pieces

Result

quantity shortfall dispute

PO wording

200 cartons

Supplier interpretation

200 master cartons

Brand expectation

200 inner packs

Result

overproduction or overshipment

PO wording

500

Supplier interpretation

billed as pairs

Brand expectation

counted as eaches

Result

invoice mismatch

How to prevent it

Always define the unit of measure on PO lines using a controlled field, not a vague description.

For each line item, specify:

  • order quantity
  • unit of measure
  • conversion logic if needed
  • carton or pack equivalent if relevant

For example:

  • 1,000 eaches
  • packed 10 eaches per inner
  • 5 inners per carton
  • total expected cartons: 20

This avoids a common scenario where a factory invoices on carton quantities while the brand expected unit quantities.

Mistake 4: Leaving carton counts and carton configuration vague

Carton details matter well before shipping day.

Suppliers need carton count clarity for:

  • packing line setup
  • carton purchasing
  • pallet planning
  • container loading
  • warehouse receiving
  • retailer routing compliance

Yet many POs never state the expected carton structure clearly.

What gets missed

  • expected total carton count
  • units per carton
  • carton dimensions or max weight constraints
  • single-SKU vs mixed-SKU cartons
  • palletisation rules

A PO may include total unit quantity but no carton detail. That forces the supplier to choose a packing method, which may not match downstream warehouse or retail requirements.

How to prevent it

Add carton configuration fields to the PO or to the referenced packing instructions:

  • units per carton
  • target total carton count
  • mixed carton rules if applicable
  • max carton weight
  • pallet configuration if required

This is particularly important for wholesale, retail compliance, and 3PL receiving. If you are preparing stock for external warehousing, How to Prepare Product Data for 3PL Onboarding is a useful companion.

Mistake 5: Shipping instructions are incomplete or buried

A supplier can finish production on time and still miss the shipment because the shipping instructions were unclear.

Common gaps include:

  • missing ship-to address
  • missing requested ship date or delivery window
  • no incoterms
  • no carrier or forwarder details
  • no booking contact
  • no pallet requirements
  • special routing instructions hidden in email rather than on the PO

How it usually fails

The supplier asks:

  • Which warehouse should this go to?
  • Is this FOB or DDP?
  • Do we book with your forwarder or use ours?
  • Are floor-loaded cartons acceptable?
  • Does delivery need an appointment?

Every unanswered question adds delay.

How to prevent it

Shipping instructions should be explicit and easy to find, not buried in free-text notes.

Include:

  • full ship-to name and address
  • requested ship date and required delivery window
  • incoterms
  • carrier or freight forwarder details
  • booking instructions and contact details
  • pallet, labelling, or ASN requirements if applicable

If shipment rules differ by warehouse, retailer, or market, standardise those rules in your operational data instead of relying on memory.

Mistake 6: Failing to include label and packaging requirements

This is where many POs stop too early.

The supplier may know what to make and where to send it, but still not know:

  • which packaging artwork version to use
  • which barcode must appear on unit packaging
  • where labels should be placed
  • which carton label format is required
  • whether retailer-specific labels are needed

Real example

A shipment arrives with the correct product and correct quantities, but the cartons are rejected because the required carton labels were never included or referenced in the approved PO package.

That can mean:

  • relabelling cost
  • delayed delivery
  • retailer chargebacks
  • urgent manual correction work

How to prevent it

Your PO should either contain packaging and label requirements directly or clearly reference the approved files and specifications.

That usually includes:

  • packaging file version
  • barcode or GTIN requirement
  • unit label requirement
  • carton label template or specification
  • placement instructions
  • any retailer- or channel-specific requirements

To reduce artwork and packaging confusion, see How to Hand Off Packaging Files to Suppliers Without Version Chaos. If carton labels are part of the issue, Master Carton Labelling Guide (Retail + 3PL + Warehouse) is also worth reviewing.

Mistake 7: No version control or approval trail

Some of the worst supplier PO errors happen after the PO is first sent.

The team changes quantity, packaging, or ship date by email. The supplier acknowledges one change but misses another. Production starts against an outdated version.

Real example

A brand sends a PO for 5,000 units. Later, the buyer emails: "Please reduce black to 4,000 and increase white to 6,000." The factory updates its planning sheet but the approved PO version never changes. Finance, logistics, and the warehouse all keep working from the old numbers.

Now nobody agrees on what was ordered.

How to prevent it

A strong PO approval workflow should include:

  • version number or revision date
  • named approver
  • change log
  • one approved source of truth
  • a clear rule that email comments do not override the PO unless the PO is reissued

This matters just as much as the PO content itself. A perfect PO in version 1 does not help if production follows an unapproved version 3 from an email chain.

For a broader control layer before production begins, see Supplier Production Approval Checklist.

Mistake 8: Not checking order quantities against MOQ, pack multiples, and production constraints

A line item quantity can be internally sensible and still operationally impossible.

Common examples:

  • ordering below MOQ
  • ordering quantities that break carton multiples
  • ordering colours in ratios the supplier cannot run efficiently
  • ordering labels or packaging in quantities that force overage
  • ignoring minimum print runs or die-cut constraints

How it creates avoidable friction

The supplier comes back with one of three outcomes:

  1. request to change the order
  2. produce overage and invoice accordingly
  3. part-complete the order in a way that creates downstream stock imbalance

How to prevent it

Before approval, check each line against:

  • MOQ
  • order multiple
  • inner pack multiple
  • carton multiple
  • production run constraints
  • packaging print constraints

This is one of the clearest purchase order best practices: make sure ordered quantity matches supplier reality before the PO is issued, not after.

Mistake 9: Forgetting supplier-specific requirements

Not every supplier works the same way.

One supplier may need:

  • their own item code on each line
  • a factory site reference
  • a separate packaging instructions attachment
  • carton breakdown in a specific format
  • booking references for their freight team

Another may refuse to process a PO without an incoterm, payment term, or destination code.

Why one-size-fits-all POs fail

Brands often build one generic PO and assume every vendor can work from it. In practice, some suppliers need specific fields, naming conventions, or file formats to process orders correctly.

When those requirements are missed, the supplier delays acceptance, rekeys information manually, or executes against assumptions.

How to prevent it

Maintain supplier-specific rules such as:

  • mandatory PO fields
  • accepted file format
  • supplier item reference requirements
  • packaging or carton data requirements
  • booking and logistics contacts

A standard PO format is useful, but it still needs room for supplier-specific operational fields.

Mistake 10: Treating the PO like a document instead of structured operational data

This is the root cause behind many purchase order formatting issues.

When a PO is assembled manually from spreadsheets, old PDFs, and email threads, teams end up copying inconsistent data into a static document. That is how errors creep in across:

  • SKU references
  • unit of measure
  • pack details
  • carton counts
  • ship-to locations
  • file versions
  • approvals

A better approach is to build supplier-ready purchase orders from structured, reusable product and supplier data.

That means your PO fields are not invented from scratch every time. They are pulled from a controlled source:

  • product master data
  • approved pack configurations
  • supplier references
  • warehouse addresses
  • label requirements
  • revision-controlled workflow steps

If your product data itself is inconsistent, fix that first. Product Master Data Sheet: Fields Every Brand Should Include is a good place to start.

A simple checklist for reducing PO mistakes

Before sending a PO to a supplier, review this checklist.

PO review checklist

  • Every line has a clear brand SKU
  • Supplier item code is included where needed
  • Variant details are explicit: size, colour, finish, region, bundle type
  • Quantity is stated with the correct unit of measure
  • Pack quantities are defined: units per inner, inners per carton, units per carton
  • Carton configuration is clear, including mixed-carton rules if relevant
  • Expected carton count is stated or can be calculated from the PO
  • Packaging and label requirements are attached or referenced with version control
  • Ship-to address is complete and correct
  • Ship date, delivery window, and incoterms are stated
  • Booking instructions, carrier details, or forwarder contact are included if required
  • Quantities have been checked against MOQ, order multiples, and production constraints
  • Supplier-specific required fields are present
  • The PO has a version number or revision date
  • The approved version is the only version sent for execution

How a structured PO process prevents repeat errors

Most brands do not have repeated PO issues because their team is careless. They have repeated issues because the process allows inconsistency.

A structured PO process usually includes:

  • standard fields for SKUs, quantities, units, pack structure, labels, and shipping
  • controlled templates by supplier type or order type
  • product data pulled from a maintained source rather than retyped manually
  • approval steps before release
  • clear revision control after release
  • linked packaging files and operational attachments

The benefit is not just cleaner paperwork. It is fewer clarification cycles, fewer supplier assumptions, and fewer downstream errors in warehousing and fulfilment.

If your team is still building POs from ad hoc documents and email chains, standardising the workflow is usually the fastest way to reduce recurring errors. SKUWorks is designed to support that kind of operational control with structured product data, consistent PO fields, and approved versions in one workflow.

FAQ

What should always be included on a supplier-ready purchase order?

At minimum:

  • clear SKU references
  • variant details
  • quantity and unit of measure
  • pack and carton configuration
  • ship-to details
  • delivery terms
  • packaging and label requirements
  • approved version or revision information

What is the most common mistake brands make on purchase orders?

The most common mistake is assuming a PO is clear because it makes sense internally. Suppliers need execution detail, not internal shorthand. Unclear SKUs, vague quantities, and missing pack instructions are especially common.

Why do suppliers reject or query purchase orders?

Usually because something important is missing or ambiguous, such as:

  • unit of measure
  • carton configuration
  • shipping instructions
  • item references
  • approval status
  • packaging file version

Suppliers query POs when they cannot execute confidently without risk.

Should a purchase order include carton counts and pack quantities?

Yes, if carton and pack structure matters to production, shipping, receiving, wholesale, retail compliance, or 3PL handling. For many product brands, that detail is essential, not optional.

How do I avoid version control issues with purchase orders?

Use one approved PO version, add revision numbers or dates, record changes formally, and do not rely on scattered email edits as the source of truth.

What is the difference between a purchase order and a production instruction?

A PO authorises the order commercially and operationally. A production instruction may go deeper into manufacturing details. In practice, many brands need the PO to carry enough operational detail to avoid execution mistakes even if separate production documents also exist.

How detailed should shipping instructions be on a PO?

Detailed enough that the supplier knows exactly where to send the goods, when they need to move, under which incoterms, and whether booking, pallet, or carrier rules apply.

Final takeaway

The biggest purchase order mistakes are rarely dramatic. They are small gaps in SKU references, units, pack structure, carton counts, shipping instructions, or approvals.

Those small gaps are exactly what cause production delays, receiving problems, rework, and disputes.

A good PO does not just confirm that you are buying something. It tells the supplier how to execute the order correctly, with no guesswork.

Related posts