Create a new SKU or revise an existing product?

A stationery and office-supplies chain carries a popular gel-pen blister pack (SKU-PEN-4PK, GTIN 08901112223331, net purchase cost ₹72.00, MRP ₹120.00) with 420 four-packs currently distributed across 18 stores and the ecommerce fulfilment centre (₹30,240 at cost). For the back-to-school season, the manufacturer replaces the 4-pen blister pack with a new '5-Pen Value Pack' (5 pens per pack, new net cost ₹85.00, new MRP ₹140.00). However, on the vendor's commercial price sheet, the supplier keeps its internal vendor item code (VEND-GP-100) unchanged and simply edits the description column from Gel Pen 4-Pack to Gel Pen 5-Pack. If a junior catalogue executive imports that vendor sheet and overwrites SKU-PEN-4PK in place—updating the title to '5-Pen Pack' and the price to ₹140.00 while 420 physical 4-packs still sit in store bins—every ecommerce customer who orders the advertised '5-Pen Pack' receives a 4-pen pack picked from existing bin stock, store shelf labels mismatch the printed ₹120.00 MRP on the 4-pack blister card, and historical margin and return rates across the two packs collapse into one corrupted series.

The operational decision for a product-data steward is how to distinguish a non-identity revision (such as fixing a typo or adding a search synonym) from an identity-breaking product change that requires a new internal SKU, a verified GTIN under global barcode standards, and a formal transition link (GS1 — GTIN Management Standard, GS1 GTIN Management Standard — Rule 270: Pack/case quantity changes). Connecting this workflow to fashion variant catalogue controls and retail product declaration and compliance data ensures that product-data steward teams maintain one auditable position from source record to downstream execution.

When to revise an existing SKU versus creating a new product identity

Retail systems rely on two distinct identifiers that serve different layers of the operation:

• Global Trade Item Number (GTIN / EAN / UPC): The external supply-chain and point-of-sale barcode governed by the GS1 GTIN Management Standard. Under GS1 principles—and specifically GS1 Rule 270 on pack/case quantity changes—any modification to the count of trade items contained in a pack or case, net weight/volume declaration, or primary functional specification requires a new GTIN so scanners, warehouses, and consumers can distinguish the old item from the new item.
• Internal Stock Keeping Unit (SKU): The merchant's internal operational key that binds perpetual inventory balances, weighted-average cost, warehouse bin locations, fashion size/colour variant trees, and product declaration data.

Even when an unsophisticated supplier reuses its own vendor catalogue number or fails to assign a new barcode after changing a pack, the retailer must never overwrite an active SKU that still has on-hand stock, open purchase orders, or open return windows. Quantify the overlap exposure before any product change using these equations:

Active Legacy Stock Exposure (Units) = Store On-Hand Units + Warehouse Available/Reserved Units + Open In-Transit v1 PO Units

Pick-Error Oversell Risk (Units) = Legacy 4-Pack Units in Shared Bins Exposed to Overwritten 5-Pack Ecommerce Listing

Unit Cost Valuation Distortion (₹) = Legacy Units on Hand × (New Pack Unit Cost − Legacy Pack Unit Cost)

Applying this decision table guarantees that no physical change in pack count, weight, or customer promise ever corrupts the inventory ledger or misleads an online shopper.

  <path d="M219 85 L248 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r011)"/>

  <rect x="248" y="40" width="195" height="90" rx="8" fill="#fef9c3" stroke="#ca8a04" stroke-width="1.5"/>
  <text x="262" y="64" font-weight="700" fill="#854d0e">2. Apply Identity Gate</text>
  <text x="262" y="84">GS1 Rule 270: Pack count +25%</text>
  <text x="262" y="102">Legacy stock: 420 u (₹30,240)</text>
  <text x="262" y="118" font-size="11" fill="#475569">Block in-place SKU overwrite</text>

  <path d="M443 85 L472 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r011)"/>

  <rect x="472" y="40" width="195" height="90" rx="8" fill="#ffedd5" stroke="#ea580c" stroke-width="1.5"/>
  <text x="486" y="64" font-weight="700" fill="#9a3412">3. Split Operational IDs</text>
  <text x="486" y="84">Keep SKU-PEN-4PK (Sell-down)</text>
  <text x="486" y="102">Create SKU-PEN-5PK (New GTIN)</text>
  <text x="486" y="118" font-size="11" fill="#475569">Link via Supersession Table</text>

  <path d="M667 85 L696 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r011)"/>

  <rect x="696" y="40" width="200" height="90" rx="8" fill="#dcfce7" stroke="#16a34a" stroke-width="1.5"/>
  <text x="710" y="64" font-weight="700" fill="#166534">4. Execute Clean Cutover</text>
  <text x="710" y="84">Sell down 420 legacy 4-packs</text>
  <text x="710" y="102">Receive 600 new 5-packs cleanly</text>
  <text x="710" y="118" font-size="11" fill="#475569">Preserve 30-day return lookup</text>

  <rect x="24" y="166" width="872" height="164" rx="8" fill="#ffffff" stroke="#cbd5e1" stroke-width="1.2"/>
  <text x="44" y="194" font-weight="700" font-size="13" fill="#0f172a">Governance rule: Never overwrite an active SKU when pack count, net content, or sellable identity changes</text>
  <text x="44" y="220" fill="#334155">• Gate A: Feed validation gate flags any vendor update that alters pack quantity, net weight/volume, or cost/MRP beyond revision rules.</text>
  <text x="44" y="246" fill="#334155">• Gate B: Identity gate creates a new internal SKU (SKU-PEN-5PK) and enforces a distinct GTIN (or DC over-label if vendor reused barcode).</text>
  <text x="44" y="272" fill="#334155">• Gate C: Transition gate maintains both SKUs in parallel until the 420 legacy 4-packs sell through and their customer return window expires.</text>
  <text x="44" y="302" font-weight="600" fill="#0369a1">Outcome: Zero customer pick errors (no 4-packs shipped on 5-pack orders), exact ₹30,240 legacy valuation preserved, and clean return resolution.</text>
</g>
<defs>
  <marker id="arrow-r011" viewBox="0 0 10 10" refX="8" refY="5" markerWidth="6" markerHeight="6" orient="auto-start-reverse">
    <path d="M 0 0 L 10 5 L 0 10 z" fill="#475569"/>
  </marker>
</defs>

Worked illustrative example: transitioning from a 4-pen pack to a 5-pen pack with 420 legacy units in stores

Illustrative example (hypothetical scenario): Examine the stationery chain's transition when the supplier replaces the 4-Pen Gel Pack (SKU-PEN-4PK) with the 5-Pen Gel Pack (SKU-PEN-5PK) under the reused supplier code VEND-GP-100.

Step 1: Establish the baseline operational and commercial parameters

• Legacy Product (SKU-PEN-4PK — Active Phase-Out State):
  • Sellable unit composition: 4 pens per blister pack (GTIN 08901112223331)
  • On-hand stock across 18 stores + DC on Day 1 of transition: 420 four-packs (420 × 4 = 1,680 individual pens)
  • Legacy net purchase cost: ₹72.00 per 4-pack (₹72.00 ÷ 4 = ₹18.00 per pen); total legacy inventory value = 420 × ₹72.00 = ₹30,240
  • Legacy printed MRP / selling price: ₹120.00 per 4-pack (total retail value = 420 × ₹120.00 = ₹50,400; gross margin = ₹120.00 − ₹72.00 = ₹48.00 per pack or 40.00%)
• New Replacement Product (SKU-PEN-5PK — New Launch State):
  • Sellable unit composition: 5 pens per blister pack (+25.0% pack quantity change; new GTIN 08901112223348 assigned per GS1 Rule 270)
  • Initial launch purchase order (PO-9102): 600 five-packs (600 × 5 = 3,000 individual pens)
  • New net purchase cost: ₹85.00 per 5-pack (₹85.00 ÷ 5 = ₹17.00 per pen); initial PO value = 600 × ₹85.00 = ₹51,000
  • New printed MRP / selling price: ₹140.00 per 5-pack (total retail value = 600 × ₹140.00 = ₹84,000; gross margin = ₹140.00 − ₹85.00 = ₹55.00 per pack or 39.29%)

Step 2: Execute deterministic state, threshold, and exception calculations

1. Quantify the operational failure if SKU-PEN-4PK had been overwritten in place:
   • Valuation distortion: Overwriting the standard cost on the single SKU from ₹72.00 to ₹85.00 while 420 legacy packs remain on hand would artificially inflate the book value of the 420 legacy packs by 420 × (₹85.00 − ₹72.00) = 420 × ₹13.00 = ₹5,460 (from ₹30,240 to ₹35,700).
   • MRP and fulfilment violation: Raising the POS and ecommerce price on the single record from ₹120.00 to ₹140.00 would cause stores to scan the 420 legacy packs at ₹140.00 against a printed blister-card MRP of ₹120.00 (+₹20.00 overcharge per pack) and cause warehouse pickers to ship 4-pen packs against ecommerce orders promising 5 pens.
2. Execute the controlled two-SKU supersession transition:
   • The product-data steward holds the vendor import, keeps SKU-PEN-4PK locked at ₹72.00 cost / ₹120.00 MRP (Status = Discontinued — Sell Through Only), creates SKU-PEN-5PK at ₹85.00 cost / ₹140.00 MRP (Status = Active), and links them with Supersession Record SUP-PEN-04-TO-05.
   • Across the 30-day transition window, stores sell 380 of the 420 legacy 4-packs at ₹120.00 (380 × ₹120.00 = ₹45,600, leaving 420 − 380 = 40 legacy packs worth 40 × ₹72.00 = ₹2,880) while receiving and selling 310 of the 600 new 5-packs at ₹140.00 (310 × ₹140.00 = ₹43,400).
   • When a customer returns 3 legacy 4-packs on Day 22, scanning GTIN 08901112223331 resolves deterministically to SKU-PEN-4PK and refunds ₹360.00 (3 × ₹120.00 = ₹360.00), never the ₹420.00 (3 × ₹140.00) price of the 5-pack.

Creating SKU-PEN-5PK instead of overwriting SKU-PEN-4PK protects 420 legacy packs (₹30,240 at cost / ₹50,400 at retail) from a ₹5,460 valuation error, prevents ₹20.00-per-pack POS MRP mismatches, and preserves exact return resolution.

Product-change governance workflow for retail data stewards

To prevent supplier catalogue updates from corrupting active inventory, pricing, and historical reporting, enforce a four-step product-change gate:

1. Classify every incoming product modification against identity-change rules (Owner: Product-Data Steward). Check whether the proposed change alters net content, pack/case quantity (GS1 Rule 270), primary material/ingredient composition (product declaration data), dimensional shipping class, or warranty terms. If any identity attribute changes, reject an in-place overwrite.
2. Quarantine supplier feeds that reuse vendor codes or GTINs for changed packs (Owner: Catalogue Operations / PIM Rule). When a vendor submits a changed pack count, weight, or cost jump on an existing vendor item code (VEND-GP-100), hold the feed record in Pending Steward Review. If the supplier failed to allocate a new GTIN under the GS1 GTIN Management Standard, generate a new internal SKU and require warehouse barcode over-labelling until the vendor remedies its barcode.
3. Create a bidirectional Supersession Record (Old_SKU -> New_SKU) (Owner: Merchandise Planner + Data Steward). Set the legacy SKU to Phase-Out (No New POs; Sell-Through Active) and link it to the new SKU so demand planners can chain historical sales velocity across the transition without merging inventory ledgers.
4. Retain the legacy SKU in POS and OMS lookup tables through the full return window (Owner: Omnichannel Operations). Never delete or deactivate POS barcode scanning on SKU-PEN-4PK the day store stock hits zero; keep the SKU active for returns and service lookups until at least 90 days after the last unit is sold.

Choosing the right governance mechanism: Even without a dedicated Product Information Management (PIM) platform, you can enforce this discipline in your ERP item master by locking Pack Quantity, Net Weight/Volume, Base UOM, and Primary GTIN against edits whenever Cumulative Lifetime Receipts > 0.

Observable acceptance tests for your retail systems

Before relying on this workflow in production, execute three deterministic acceptance tests (ACT-R011-01 to ACT-R011-03) in your staging environment or controlled ledger:

Applying product-identity rules to your catalogue workflow

To stop supplier pack changes and silent specification edits from corrupting store stock and online orders:

1. Lock identity-defining fields (Primary GTIN, Pack/Case Count, Net Weight/Volume, Base UOM) in your ERP or PIM item master so they cannot be overwritten once an item has recorded purchase receipts or sales.
2. Add a Supersedes_SKU and Superseded_By_SKU link field to your item master so merchandising and replenishment reports can chain demand history across old and new packs cleanly.
3. Require warehouse receiving clerks to verify pack count and GTIN on first delivery of any revised vendor line so supplier code reuse (VEND-GP-100) is caught at the dock before mixed packs enter shared bins.
4. Run acceptance tests ACT-R011-01 to ACT-R011-03 with your product-data steward and warehouse receiving lead before your next seasonal assortment update.