What Is SKU Management and Why Does It Matter in Fulfilment?

An order for a medium black T-shirt should never leave the warehouse as a large navy one. Yet similar products, inconsistent codes and duplicate stock records can make that mistake surprisingly easy. Good sku management gives every product variation a clear identity, so your sales channels and fulfilment team agree on exactly what has been ordered, what is available and what should be dispatched.

For a growing eCommerce business, this is not just catalogue housekeeping. It affects picking accuracy, stock availability, replenishment and returns. This guide explains how to build a practical system without making your product codes unnecessarily complicated.

Category: Order Fulfilment

What does an SKU identify?

SKU stands for stock keeping unit. It is an internal identifier that a business assigns to a particular product or product variation.

If you sell the same T-shirt in two colours and three sizes, you normally need six SKUs. Each combination is a distinct item that customers can order and your warehouse must identify separately.

Here is an illustrative structure:

Effective sku management means maintaining the information behind these codes, not simply inventing labels. That information includes the product description, selling unit, stock status and any relevant handling requirements.

A warehouse location is separate. Moving TSH-BLK-M from one shelf to another changes its location, not its product identity.

How SKUs differ from barcodes, batches and serial numbers

An SKU is your internal product reference. A barcode is a machine-readable representation of an identifier, which could be your SKU or another code.

A Global Trade Item Number, or GTIN, identifies a trade item within the GS1 identification system. You should not assume that an internally created SKU replaces a GTIN required by a retailer or marketplace.

Batch numbers identify groups of products, often linked to a production run. Serial numbers identify individual units. Several batches or individually serialised items can therefore share one SKU.

For example, ten identical devices may have the same product code but ten different serial numbers. Businesses that need unit-level traceability should also understand how serial number tracking works in warehousing and fulfilment.

Why sku management matters in fulfilment

Product records connect a customer's order to the physical item on a shelf. If those records are wrong, even a well-organised warehouse can receive unclear or misleading instructions.

It makes stock availability meaningful

Knowing that you have 100 units in the building does not necessarily mean you can sell all 100.

Suppose those 100 units include 20 already allocated to orders and five damaged units held separately. Assuming the remaining stock is unrestricted, only 75 units are available for new orders.

Your system needs to distinguish physical stock from available stock. It also needs consistent product references across your website, marketplaces and warehouse records, whether through matching codes or a reliable mapping between them.

Without that link, the same item can appear under different references and its stock position becomes harder to reconcile. Reliable sku management helps prevent one sales channel from treating unavailable stock as ready to sell.

It reduces ambiguity during picking and returns

A product description such as “black shirt” is not enough when the warehouse holds several sizes, styles and pack formats. A unique code gives the picking team a precise reference to check against the order.

Barcode checks can support that process where suitable scanning controls are in place, but they cannot correct a barcode attached to the wrong product record.

The same principle applies to returns. The returned item must be identified and its condition checked before it goes back into available stock. A returned large shirt should not increase the stock balance for medium shirts simply because both look similar.

How to create a workable SKU structure

Start with a consistent rule that your team can apply to new products. Codes should be unique, stable and compatible with the systems that need to exchange them.

A readable structure such as TSH-BLK-M can help staff recognise a variation. However, sequential codes can also work well when the supporting product data is clear. There is no single format every business must use.

The aim of sku management is reliable identification, not squeezing every product attribute into one code.

Avoid including details that change frequently, such as a selling price, supplier lead time or shelf location. Keep those in separate fields so that routine updates do not force you to rename products.

Check character restrictions and code lengths before agreeing a format with your fulfilment provider. Spaces, punctuation and inconsistent capitalisation can cause problems in some systems or integrations.

Most importantly, do not reuse a retired code for an unrelated product. Historical orders, returns and reports may still reference it.

Give packs and bundles clear rules

A single item and a carton of six are different selling units. Your records should make it clear whether an order quantity of “1” means one product or one whole carton.

Bundles need an equally clear approach. A pre-packed gift set may be held as its own stock item. A bundle assembled after an order arrives needs a defined list of components and quantities.

For example, a gift set containing one candle and two soaps needs instructions that connect the bundle order to those three items. Decide whether stock is held against finished sets or deducted from components, then ensure your systems and warehouse process follow that decision.

A new SKU alone does not establish this relationship. The pack quantity or bundle contents must also be recorded and shared with the fulfilment team.

Keep the product record accurate, not just the code

Good sku management depends on a trusted product record that remains accurate as your range changes. This could start as a controlled spreadsheet, provided it is kept current and agreed with everyone using it.

Useful fields include the SKU, product name, variant details, barcode where applicable, selling unit and pack quantity. Add dimensions, weight and handling requirements when they affect storage, packing or delivery.

Record batch, serial number or best-before tracking requirements separately. These describe how stock needs to be controlled and should not be left buried in a product name.

Choose one person or team to approve new records and changes. That avoids a supplier, marketing colleague and warehouse contact each creating a different code for the same item.

Review exceptions and record changes

Focus routine checks on problems that interrupt orders: unidentified deliveries, duplicate codes, missing variants, unclear pack quantities and differences between recorded stock and physical counts.

When a discrepancy appears, investigate the cause rather than simply changing the balance. A wrong carton quantity at receipt, an unrecorded bundle assembly and a picking error require different fixes.

Keep a change log showing what was amended, when it changed and which systems were updated. Before launching a new variation, check a sample order through to its warehouse record. This is especially useful when two products have nearly identical descriptions or packaging.

What to prepare before outsourcing fulfilment

Moving stock to a 3PL is a useful opportunity to clean up product information, but it should happen before goods arrive at the warehouse.

For sku management to work across your business and fulfilment provider, both sides need an agreed product list and clear rules for identifying each selling unit.

Prepare the following before the first stock delivery:

• A current product file: Include active SKUs, descriptions, variants, barcodes where used and selling units.
• Pack and bundle instructions: Explain carton quantities, pre-packed sets and any assembly requirements.
• Sales channel references: Identify codes that differ between your website, marketplaces and warehouse records.
• Stock-control requirements: Confirm whether products need batch, serial number or best-before tracking.
• Returns instructions: Define which condition checks must happen before an item becomes available again.

Agree how deliveries will be identified and how discrepancies will be reported. Sending mixed, unlabelled variants with an incomplete stock list creates avoidable uncertainty at goods-in.

When comparing order fulfilment services, ask how product records are created, how channel references are connected and who authorises changes. For warehousing and storage, establish how product identity, location and stock status remain visible as goods move through the operation.

Frequently asked questions

Is SKU management the same as inventory management? No. Inventory management covers stock quantities, availability, replenishment and movement. Product identification and the records behind each SKU form part of that wider process. Accurate quantities are only useful when they are attached to the correct item.

Does a small business need an SKU for every product? Unique identifiers are useful even with a small range. Separate codes become particularly important when you introduce sizes, colours, pack quantities or additional sales channels. You do not need an elaborate coding structure to make sku management worthwhile.

Can the same product use different SKUs on different sales channels? It can, provided there is a reliable mapping back to the correct warehouse product record. Where possible, consistent references reduce complexity. If channel-specific codes are necessary, document and test the mapping before accepting live orders.

Should I change an SKU when packaging changes? Not automatically. A minor artwork change may not alter the item customers order. A different quantity, size or separately sold version may need a new record. Consider whether the warehouse or customer must distinguish the old and new versions before deciding.

Get your product records ready for reliable fulfilment

Gus Logistics supports eCommerce brands and product businesses from Nantwich, Cheshire, with order fulfilment and warehousing. Its fulfilment service integrates with more than 60 platforms, including Shopify, Amazon, eBay, WooCommerce and Magento. Warehouse stock is tracked through a real-time WMS client portal, with batch, serial number and best-before tracking available.

If inconsistent product codes or stock records are complicating your operation, discuss your catalogue, selling units and handling requirements before moving stock. Call Gus Logistics on 01270 335014 to talk through your fulfilment and storage needs.