How Do You Keep SKUs and Packing Slips Correct?

SKU accuracy is a chain, not a single check. A correct barcode on the picking label only helps if the master data behind it matches the print file, the blank and the variant the buyer ordered. Packing slip errors appear when one link in that chain is skipped, and the parcel still looks right from the outside. This guide sets out where SKU mistakes start, the checkpoints that stop them, and the cases where controls cost more than the errors they prevent.

The cost is easy to underestimate. A wrong SKU ships a correct-looking parcel to the wrong buyer, so the seller pays for the return, the replacement and the customer conversation at the same time. Repeat errors in the same variant also damage the trust that a made-to-order shop depends on.

Most of the fix is administrative work done before a single garment is printed, which is why it is often postponed and rarely budgeted.

Where SKU and Packing Slip Errors Start

Errors rarely begin at the packing bench. They begin in master data, where a colour name, a size run or a print file is mapped to a code that nobody validates. By the time the parcel is packed, the mistake is several steps old and fully invisible.

The table below groups the common sources by where they surface. Each one needs a different control, which is why a single final check cannot cover them all.

Read the table from the middle column. The failures that reach the buyer are the ones with no control on the right, and they are almost always the ones that involve two systems disagreeing.

Checkpoint One: Master Data Before the Print File

Every SKU should answer four questions without ambiguity: which blank, which colour, which size and which print file. If any answer lives in a screenshot or a chat thread, the code is not yet safe to sell.

Build the master list once and treat it as the source of truth. Store variants are then mapped to it rather than being the place where product identity is invented. Barcode and SKU systems for custom products covers the naming patterns that survive a growing catalogue.

SKU uniqueness is the rule that pays for itself. Two codes that differ by one character will eventually be read as one code by a human under time pressure, and no scanner will warn anyone.

On our production floor, the most common cause of a mis-print is not a bad file but a file attached to the wrong variant row. The print team sees a technically valid design, so nothing looks wrong until the size or colour is checked against the order.

Checkpoint Two: Barcode Verification at Picking

A barcode scan is only an SKU control if it blocks progress. If a mismatch produces a warning that staff can dismiss, the check becomes a formality within a week.

The picking step should confirm three things: the code matches the order line, the physical item matches the code, and the quantity matches what will be packed. Each of those is a separate failure mode and each deserves its own confirmation.

Where a full warehouse system is out of reach, a printed picking sheet with one scan field per line still works. The point is the block, not the software.

Fulfillment labelling and packing standards sets out how the label, the slip and the parcel should agree, which is the practical version of the same rule.

Checkpoint Three: The Packing Slip Match

The packing slip is the document the buyer keeps, so a wrong slip turns a correct parcel into a support ticket. It should be generated from the same order record that produced the barcode, never from a separate export.

Three fields carry most of the value: the SKU code, the variant description in plain language, and the quantity per line. A buyer who ordered two sizes reads the description first, so matching only the code is not enough.

For multi-item orders, the slip should be checked against the finished parcel rather than against the picking list. The picking list records intent; the parcel records what will be shipped.

Technical accuracy upstream supports this step directly. Technical files and mockup accuracy explains why a mockup that disagrees with the print file produces a slip that looks correct and describes the wrong item.

What a Packing Slip Should Carry

A slip does not need to be elaborate. It needs to be unambiguous for a buyer who has never seen the catalogue and for a support agent reading it weeks later.

Include the order reference, the SKU per line, a plain-language variant description, the quantity, and a short note on the return window. Anything that changes how the buyer should treat the parcel belongs on the slip, not only in an email.

Marketplace sellers should check the platform's own rules before adding fields. Etsy made-to-order policies is a useful reference for what a made-to-order listing is expected to state, and the same logic applies to the document inside the parcel.

Where SKU Controls Fail

Controls fail most often in small catalogues, not large ones. A shop with twelve variants assumes everyone remembers them, so the scan step is dropped and the code lives in memory until someone new joins the team.

They also fail during a blank substitution. When a supplier swaps a blank, the old code may be reused because it is already in the store. That decision needs an explicit approval and a note, or the same code will describe two different garments.

Peak periods expose the third SKU weakness. When order volume rises, the step that gets skipped is the one that feels redundant, and that is usually the packing slip match.

Finally, controls fail when nobody owns the master list. If product data is edited by anyone who needs a quick fix, the list drifts and every downstream check inherits the drift.

A fourth failure is cultural rather than technical. Teams stop reporting near misses once a fix is easy, so the same error returns in a different order and nobody connects the two events. A simple error log, even a shared sheet, keeps that memory alive.

Our QC team reviews recurring mis-ships by code rather than by order, which is what makes the pattern visible. One code appearing three times is a data problem, while three different codes appearing once each is usually a process problem at the bench.

A Practical Rollout for Small Teams

Start with the SKU codes that ship most often. Rebuilding the whole catalogue at once produces a long project and no visible benefit for weeks.

For those codes, write the four answers down, confirm the print file against the store listing, and add one blocking scan at picking. Run it for two weeks and count mis-ships before and after.

Then extend the same pattern to the next group. A narrow, working control beats a broad, ignored one, and the first group usually contains most of the risk.

If a workflow change is needed to support the scan, print on demand proofing workflows describes a review step that catches variant mistakes before production, and catalogue curation explains why a shorter variant list reduces the number of codes that can be confused.

Frequently Asked Questions

How many characters should an SKU have?

There is no universal length. The practical constraint is that it stays readable on a picking sheet and a packing slip, and that it carries the blank, colour, size and design reference in a fixed order so anyone can parse it.

Should the packing slip show the SKU or a readable description?

Show both. The code supports returns and inventory, while the description is what the buyer verifies on opening the parcel. A slip with only a code creates avoidable support questions.

Do barcode checks work for low-volume shops?

They do, though the form can be simple. A phone camera and a printed picking sheet with one scan field per line is enough to create a block, and the block is what prevents the error rather than the sophistication of the tool.

What should happen when a blank is substituted?

The substitution should be recorded against the existing code with a date and a reason, and the print area should be re-checked. Reusing the code silently means the same identifier describes two garments in the same quarter.

Where should the error log live?

Anywhere the team already opens daily. The value comes from grouping entries by code, so a short column for the code and a short note for the cause is enough to reveal a pattern within a few weeks.

The Minimum Viable Control Set

Three controls carry most of the benefit: a validated master list, one blocking scan at picking, and a packing slip built from the same record. Everything else improves speed or reporting rather than accuracy.

Together they protect the two things a buyer checks on arrival, which are the garment and the document inside the parcel. A seller who gets those two right rarely needs to discuss a return.

SKU accuracy then becomes a maintenance habit rather than a project, and the error log turns into the shortest route to the next improvement.

If a supplier ships from a US warehouse, the same discipline travels with the order. A barcode that matches the picking label and a packing slip that matches the parcel keep sku accuracy intact across the handover, which is the point where most accuracy claims are made and most are lost.

Related Articles

How Does Print on Demand Work, Order to Doorstep?

Hangtag, Barcode and GS1 Setup Basics

Lead Time Breakdown: Printing, Curing and Packing