Set Up New SKU Data Before the Product Starts Moving

Before the first unit of a new product reaches the warehouse, somebody must decide exactly what that product is. A new SKU is not simply a memorable code or an appealing name on a website. It is the internal reference that connects a particular sellable configuration to purchasing, receiving, storage, pricing, customer promises and returns. A missing case-pack conversion can distort an order by a factor of twelve; an incorrectly inherited weight can produce a carrier problem; an apparently correct barcode can point at the wrong colour. A careful new-SKU checklist catches these mismatches while they are inexpensive to correct.

The following method is for small UK product traders introducing new lines or variants. It distinguishes the business's own stock-keeping unit from globally managed product identifiers and from batch or serial traceability. The specific fields depend on what is sold and how it moves. The objective is not to populate every available software property. It is to establish a verifiable minimum record that supports the actual journey from approved supplier product to customer delivery.

Give the sellable configuration a stable identity

Define exactly what one SKU represents. A product sold individually in three colours may need three different internal sellable references; a sealed multipack may need another. Where the company also sells individual components, identify whether a kit is preassembled stock or a bundle assembled against orders. Do not use the same code for physically different configurations that receiving staff need to distinguish.

Record the supplier's catalogue number alongside the company's own SKU, not as a replacement for it. Several suppliers can use different references for the same approved item, whilst one supplier code may cover multiple manufacturing revisions. Preserve the mapping and the evidence used to regard products as interchangeable. For an unresolved match, retain the uncertainty until an authorised reviewer confirms it.

Where a product uses a GS1 Global Trade Item Number, check whether the trade item has the appropriate GTIN and the barcode encodes the intended number. GS1 explains that its trade-item identifiers distinguish products and that changes meaningful to buyers or supply-chain handling can require a new GTIN. An internal SKU may be freely designed for an organisation's stock system; it should not be misrepresented as a GTIN assigned under GS1 rules.

Separate a product fact from its sales description

Create a source-backed specification record: manufacturer or approved supplier, model, material, finish, dimensions with units, weight where needed, included items and relevant operating conditions. Each factual field needs a definition and source revision. A website headline may be rewritten for readability, but it should not alter the length, connector type or actual contents of the goods offered.

Determine which attributes belong to the whole product family and which apply only to particular variants. A common parent description can be useful, but inheriting one colour's photographs or dimensions across an entire range may produce inaccurate listings. For a technical item, record compatible models and limitations with evidence rather than using a broad 'fits most' statement.

If a value remains unknown, state that explicitly instead of entering a guess to satisfy a mandatory field. Some properties may be optional at the enquiry stage but necessary before a product can be sold, transported or safely installed. Define the business stage at which each fact must be verified. A property filled with a plausible-looking default is not the same as reliable product data.

Define purchasing units and conversion factors before ordering

Record supplier order unit, case quantity, minimum order quantity where applicable, lead-time definition and the product specification revision to be purchased. If the supplier sells cartons whilst the business counts individual units, confirm the case-to-piece conversion and which quantity the purchase-order screen expects. Test a sample order and the planned goods-received entry before submitting a substantial first purchase.

Include variant restrictions. A supplier may impose minimum quantities by colour rather than by product family. The record must distinguish an order for mixed cases from an order for equal quantities of every variation. Store any approved substitution separately from the default product definition: a buyer should not silently change what customers receive because purchasing found an alternative with a similar code.

Clarify when a quoted lead time begins and ends. Production after deposit, dispatch from the supplier and arrival at the receiving warehouse are different events. Keep estimates distinct from confirmed delivery commitments so a planning value cannot accidentally become an unqualified promise on a customer-facing page.

Prepare the warehouse record for actual stock movements

Give receiving teams the identifying attributes they can inspect: printed model reference, packaging configuration, expected labels, unit size and any relevant batch or serial reference. Record appropriate storage and handling requirements, including conditions for fragile, temperature-sensitive or battery-containing items when relevant. Avoid assuming every product requires the same handling information; obtain the correct requirements for the actual goods.

Set stock status and storage location rules before delivery. A unit may be physically on hand but unavailable because it is reserved, damaged or awaiting a product review. Do not populate saleable stock from a purchase order alone. Actual receipt and appropriate release should control availability. If a kit contains several components, decide how reservations and assembly will reduce component balances without double counting.

Test returns and replacements too. Employees should be able to scan or search for the SKU and retrieve the description, actual model, supplier reference and applicable instructions. Where an older revision remains in the market, preserve history rather than rewriting every previous sale to the new specification.

Keep product traceability separate from internal naming

Some products require information supporting traceability to manufacturers, importers or production batches. The Office for Product Safety and Standards guidance describes applicable manufacturer and importer responsibilities, including identification and documentation. Exact obligations depend on the product category, market and economic-operator role. A convenient SKU code alone does not satisfy every relevant duty.

Link the appropriate approved documents and product versions without pretending that every low-risk item requires a statutory certificate. An importer may need evidence unavailable to the online marketing team; a distributor may need to identify the affected products if a later complaint arises. Keep enough relationship between the internal SKU, supplier product and actual received batches for staff to investigate legitimately.

Protect access to confidential supplier documents. A product listing can accurately describe contents without publicly exposing private drawings or commercial arrangements. Make the verified public claims available whilst retaining technical and restricted source material under appropriate business controls.

Test channel prices, images and descriptions before release

Create representative test orders through the sales paths that will actually use the new SKU. Check variant selection, price, tax configuration where relevant, delivery options, product images, included accessories and the correct stock deduction. Review quotations and marketplace feeds separately: a successful integration may still send the wrong variant attributes if its field mapping is incorrect.

Product imagery must depict the item or configuration buyers will receive. If the hero image includes optional accessories, describe that fact clearly. The Advertising Standards Authority's guidance on misleading imagery explains how the overall impression created by a picture matters. A legally reusable photograph is not automatically an accurate representation of the SKU being sold.

Inspect a test shipment or pick instruction. Can the warehouse identify the same product the customer selected? Can a salesperson distinguish a small variant from a visually similar alternative? A record that passes a software form's validation may still be operationally unusable if the human receiving the goods cannot understand it.

Release the SKU only after named checks, then govern changes

Give data ownership to a designated product role and technical implementation to an authorised maintainer. Purchasing verifies suppliers and packs, the product owner verifies commercial descriptions, and operations tests receiving and fulfilment. In a small company one employee may cover several roles, but the underlying decisions should remain distinct. Record which checks passed, which were inapplicable and which uncertainties still prevent release.

After launch, supplier substitutions, revised packaging, new accessories and barcode changes should trigger an appropriate version review. The GS1 GTIN-management guidance is a useful reference for deciding whether material trade-item changes require a new GTIN; apply it to actual products within GS1's scope rather than indiscriminately changing every internal SKU for a cosmetic correction.

Audit the first receipt and a representative customer order. If quantities, identity, images or accounting associations were wrong, repair the authoritative data and affected records, not only the immediate task. A new-SKU checklist succeeds when purchasing, warehouse and sales can all describe one identical product using their own systems and recover the evidence if a later question arises.