A WMS can control packaging versions by treating every operationally distinct box, label, insert, pouch or sticker as an inventory component with its own SKU. The current component SKUs belong in the finished product’s packaging bill of materials. Old versions remain separately identifiable, while effective dates, inventory status, location rules and scan validation determine which version can enter an order.
The important distinction is that the WMS should not attempt to manage packaging from filenames such as insert-final-v7.pdf. Artwork files control what gets printed. Component SKUs control what gets received, stored, picked, consumed and retired. A reliable system connects the two without treating them as interchangeable.
Give each meaningful packaging version a component SKU
Start with a stable SKU convention for physical packaging components. Shopify similarly describes SKUs as internal codes used for inventory tracking, reporting, fulfillment and third-party integrations. It recommends unique, simple and consistent values and notes that matching across connected systems is case-sensitive. Shopify’s SKU guidance
A packaging SKU might combine component type, product family and revision without trying to encode every specification. Examples include BOX-CANDLE-R03, LABEL-VANILLA-R05 and INSERT-SUBSCRIBE-R02. Keep the detailed dimensions, material, finish, supplier item number and approved artwork reference in associated records rather than creating an unreadable SKU.
Create a new component SKU when warehouse staff must distinguish the new item from inventory already on hand. That usually includes changes to required copy, language, barcode, dimensions, product compatibility, regulatory information or pack-out instructions. A minor production correction that remains fully interchangeable may only require an artwork revision, provided the business has documented that decision.
This component-level approach complements a broader packaging artwork version-control workflow. The artwork system identifies the approved production file; the WMS identifies the physical stock produced from that file.
Separate internal packaging SKUs from customer-facing identifiers
An internal component SKU is not automatically a GTIN. GS1 rules address when a trade item needs a new GTIN, including certain changes to predefined assortments, declared net weight and major packaging dimensions. Review the GS1 GTIN Management Standard when packaging changes affect the identity of a trade item rather than merely an internal warehouse component.
This separation prevents two common mistakes. The first is changing a retail identifier for every internal print run. The second is assuming that an unchanged sellable-product identifier means the warehouse can mix old and new packaging freely. Your internal SKU policy should reflect operational interchangeability even when the customer-facing product identifier stays the same.
Build a packaging bill of materials for each sellable SKU
For every sellable product or kit, define the packaging components required to ship one unit. A simple packaging bill of materials might specify one carton, one product label, one instruction card and one promotional insert. Store the required quantity and, where the system permits, the applicable channel, market or order condition.
| Record | Example | Operational purpose | Primary owner |
|---|---|---|---|
| Sellable SKU | CANDLE-VANILLA-8OZ | Identifies what the customer ordered | Ecommerce or product team |
| Packaging component SKU | LABEL-VANILLA-R05 | Identifies the exact physical packaging revision | Packaging operations |
| Packaging BOM line | 1 × LABEL-VANILLA-R05 | Connects the sellable SKU to its required component | Operations or master-data team |
| Artwork reference | VANILLA-LABEL-R05.pdf | Connects received stock to the approved print file | Creative or packaging team |
| Inventory status | Approved, hold or obsolete | Controls whether stock can enter fulfillment | Warehouse or quality team |
Do not overwrite the old component SKU on historical receipts or completed work orders. Update the active BOM for future work while preserving the earlier relationship for traceability. This makes it possible to investigate a packing complaint, inventory variance or recall without reconstructing the packaging state from email and filenames.
If you are moving from informal packing instructions to structured production, the related guide to ecommerce kitting models explains when pre-kitting can remove repeated component picks from the packing station.
Use controlled status changes instead of deleting old versions
A useful packaging lifecycle has at least four states: pending approval, active, depletion-only and blocked. The exact names can vary, but each state needs a defined effect on purchasing, receiving, allocation and picking.
- Pending approval: The component SKU and expected receipt can exist, but the material cannot be allocated to customer orders.
- Active: The component is approved for the relevant packaging BOMs and can be replenished, allocated and picked.
- Depletion-only: Existing stock may be used under defined rules, but purchasing is disabled and no new production should be ordered.
- Blocked or obsolete: The component cannot be allocated or picked. Remaining units move to quarantine, rework, return or disposal.
Status control is safer than deleting a discontinued item. Deletion removes context precisely when operations may need to reconcile residual stock, open purchase orders, pending kits and historical shipments.
Choose a cutover rule before the new stock arrives
Every packaging change needs an explicit cutover rule. Otherwise, the warehouse will improvise based on which pallet is easiest to reach.
- Hard cutover: Block the old version at a specified time or order number. Use this when old copy, barcodes or compatibility information must not ship.
- Deplete then switch: Consume approved old stock before allocating the new version. Use this only when both versions are acceptable to customers and other stakeholders.
- Channel-specific cutover: Use different versions for retail, wholesale, marketplace or direct orders when requirements differ.
- Market-specific cutover: Assign language, regulatory or regional versions according to the destination or selling entity.
- Campaign window: Activate an insert or promotional component for qualifying orders between controlled start and end conditions.
Record the cutover rule in system data, not only in a launch spreadsheet. Shopify metafields can store specialized information on products, variants and other records, and metafield definitions can apply validation rules. They can therefore hold packaging attributes that need to move from the commerce layer into an integration, although the WMS remains responsible for enforcing warehouse execution. Shopify’s metafield documentation
Control physical inventory by location and status
New and obsolete versions should not share an undifferentiated pick face. Give each component SKU a scannable label and defined storage location. Put unapproved receipts and retired stock in non-pickable locations so a visual resemblance cannot bypass the system.
Inventory vocabulary also needs to be precise. Shopify, for example, distinguishes on-hand, available, committed, unavailable and incoming quantities and can display bin-location information. Those distinctions matter during a revision because stock can physically exist without being eligible for new orders.
For sticker and label components, customstickers.com can serve as a production source, but the warehouse record should still identify the exact component SKU, approved artwork reference and receipt status. Supplier names and purchase-order descriptions are not substitutes for internal version control.
Validate the version at receiving, kitting and packing
Control points should follow the component through the operation. At receiving, compare the purchase order, component SKU, shipment label and approved sample before releasing stock. During kitting, scan each component against the kit BOM. At packing, validate either the packaging component itself or the completed kit assigned to the order.
A practical exception workflow should stop rather than silently substitute. If the required component is unavailable or the scanned SKU does not match, route the order to an exception queue. Shopify Flow supports actions such as adding order tags and placing fulfillment orders on hold, which can help pass ecommerce exceptions into a connected operational process.
Scanning every low-risk component may add more labor than it prevents. Use the strongest controls for versions with regulatory, compatibility, barcode, language or customer-promise consequences. For simple decorative extras, location control and periodic verification may be sufficient.
Account for bundles and kits in the system design
Bundles introduce another layer because customer-facing availability depends on component inventory. Shopify states that the component supporting the fewest complete bundles limits bundle availability after required quantities are considered. It also notes that changing a component SKU in a Shopify bundle requires deleting and recreating the bundle.
That constraint makes packaging architecture important. If packaging is modeled as a commerce bundle component, routine packaging revisions may create unnecessary storefront maintenance. In many operations, it is cleaner to keep the sellable bundle stable in ecommerce and manage packaging components through a WMS or production BOM. Confirm that the resulting integration still reserves enough packaging inventory and blocks fulfillment when a required component is unavailable.
Shopify also states that fixed bundles can contain up to 30 components and that bundle inventory is tracked overall rather than by location. Those limits may matter for complex subscription kits or multi-location fulfillment.
Run a controlled packaging-version change
A packaging revision should move through a repeatable release sequence rather than a one-time scramble.
- Create the new component SKU without changing historical records for the old version.
- Attach the approved specifications, artwork reference, supplier item number and inspection criteria.
- Define which sellable SKUs, kits, channels and markets require the new component.
- Select a hard cutover, depletion or conditional-use rule and name the person authorized to release it.
- Receive new stock into a hold location and verify identity, quantity and print version.
- Update the packaging BOM and any integration mappings in a controlled release.
- Move approved stock to the correct pick face and remove or block the previous version as required.
- Test representative orders, including bundles, subscriptions, international orders and expedited workflows.
- Reconcile residual old stock, open purchase orders and prebuilt kits before closing the change.
The same discipline should extend across the full ecommerce packaging system, especially when cartons, labels, inserts and protective materials change on different schedules.
Audit the system with a small set of operational reports
The most useful reports are exceptions, not design histories. Monitor active BOMs that reference blocked components, inventory in the wrong status or location, open purchase orders for depletion-only SKUs, orders held for missing packaging and obsolete stock with positive on-hand quantity.
Also reconcile expected component consumption against shipped units. If 5,000 qualifying orders shipped but only 3,900 inserts were consumed, the problem may be an incorrect BOM quantity, an unrecorded substitution, a scanning bypass or a packing-compliance issue. The variance is a prompt to investigate, not proof of a single cause.
The practical takeaway
WMS packaging version control works when packaging becomes controlled inventory rather than packing-station decoration. Assign a new component SKU whenever versions cannot safely be mixed, connect that SKU to sellable products through a packaging BOM, isolate stock by status and location, and make every cutover rule explicit.
For the next packaging change, start with one finished product. List every physical component used to ship it, identify which versions are currently in the building, and verify that the WMS can block the wrong one. That single exercise will expose most version-control gaps before they become customer orders.