Barcode and SKU Systems for Custom Products

2026-09-28 00:49:34

POD Business & Ecommerce

A SKU system for custom products has to survive personalisation, because one design sold in six sizes with three name colours is eighteen sellable units, not one. Build the code from fixed attributes in a fixed order, keep the logic short enough to read, and treat product identifiers as a separate layer from your internal code. A SKU system that mixes the two creates work every time a marketplace asks for a barcode.

Custom apparel gets complicated fast. Variants multiply through size, colourway, print placement, and personalisation, and every combination needs to be identifiable in the warehouse, in the listing, and in the accounts. Sellers who improvise a code at launch spend the next two years untangling it.

Design the Format Before the Catalogue Grows

Use four segments: category, product, variant, and option. A code such as AP-TEE-BLK-L-NAME reads in one glance, sorts correctly in a spreadsheet, and tells a picker what to look for. The order never changes, which is what makes the SKU system usable at volume.

Keep codes to a fixed length where possible. Ragged lengths break sorting and make column formatting unreliable in exports, and they also hide mistakes because a missing segment is harder to spot than a wrong one. Set a length and enforce it from the first product.

Reserve space for growth. Two digits for a product family and two for a variant hold hundreds of combinations, which is enough for most stores for several years. Widening the format later means rewriting every existing code and every listing that references it.

Separate Internal Codes From Product Identifiers

Barcodes and marketplace identifiers are not your internal SKU system. Retail channels often require a GTIN or a platform assigned identifier, and those come from the listing platform rather than from your own naming logic. Treat them as a second field that maps to your code, never as a replacement for it.

Print quality matters for the physical barcode as much as the number itself. A dense code needs enough white space around it and enough contrast to scan on the first attempt, and the same principle that governs color management for print on demand production applies to label printing schedules.

Where a marketplace asks for an identifier, keep the mapping in one table. A single source for barcode to SKU lookups prevents the duplicate listings and mismatched shipments that appear when the same product is set up twice with different numbers.

Handling Personalisation in the Code

Personalised items need a way to distinguish a coded variant from a one-off. Add a suffix that signals a custom order, then let the order management layer hold the name, date, or text as data rather than as part of the code. The SKU system stays stable while the personalisation content changes with every sale.

Keep the fields a buyer chooses separate from the fields you control. Size and colourway are yours to define, while a name or a monogram belongs to the order. Mixing them into one long code makes reporting impossible because every order generates a new identifier.

Watch for products where the personalisation changes production. Printing a name onto a standard blank behaves differently from printing a full panel, and the effect on output is described in puff print effects: production requirements. The code should make that difference visible before the work reaches the press.

Colourways, Size Runs, and Naming Discipline

Name colours from a controlled list rather than inventing a description per product. Two stores calling the same garment navy and midnight blue create returns and spreadsheet pain, and a colour authority keeps the naming consistent across every SKU system entry.

Keep colour codes aligned with what production uses. Matching a house colour to a supplier reference is a technical task, and the mechanics are described in color management: Pantone matching in POD production. The code on your sheet should point to the same reference the printer reads.

Handle size runs explicitly. Kids, unisex, and womens cuts do not map neatly onto each other, so each range needs its own prefix or suffix rather than a shared letter. Buyers notice when a size chart mixes systems, and returns follow.

Use the SKU System to Run the Business

A clean code makes reporting possible. Sales by family, by colourway, and by size become a pivot instead of a manual exercise, and that view tells you which products deserve more space in the catalogue. The range decisions this supports are explored in a related breakdown of accessible and extended sizing across inclusive and adaptive apparel products.

Consistent codes also speed up fulfilment. A picker who reads the label once and finds the item without checking a screen handles more orders per hour, and error rates fall because the code carries the same meaning every time.

Then connect codes to the sales side. Products with clear attribute data rank better in marketplace search, and the broader selection logic is described in best print on demand products to sell in 2026. A tidy SKU system is a prerequisite for that comparison rather than a separate project.

Start Small and Document the Rules

Write the format on one page and put it where new team members will find it. Every attribute list, the separator, the length, and the rule for custom suffixes belong there, along with three worked examples. Undocumented conventions drift within months.

Audit the catalogue twice a year. Duplicate codes, orphaned variants, and products that no longer exist all accumulate, and each one costs a few minutes in every future export. Cleaning them takes an afternoon and prevents months of small errors.

Keep naming conventions applied across niche ranges too. A themed line benefits from the same discipline, and the structure used for narrower catalogues is described in hobby niche products for print on demand.

A working SKU system is boring on purpose: fixed segments, stable length, separate identifiers, and documented rules. CatKissFish produces 500+ custom products with US warehouse shipping and 2-3 day production on 90% of orders, so browse the custom product catalogue and tag every item before you scale. Start your custom order today and let the first hundred SKUs prove the format holds.

Common SKU System Errors

The most common SKU system error is letting personalisation leak into the code. When a buyer name sits inside the product code, every order creates a new identifier and reporting collapses.

The second is inconsistent colour naming. A SKU system that allows midnight blue and navy to describe the same garment creates returns, duplicate listings, and stock counts that nobody trusts.

The third is skipping the audit. Codes with no mapping to existing products accumulate quietly, and each orphan costs time in every export. A check twice a year is enough.

Fix those three and your SKU system becomes an asset. A stable code makes picking faster, marketplace setup simpler, and reporting possible, which is a SKU system doing the job it was meant to do from the start.