THE SHORT ANSWER
An item identifier should follow the same purchasable item through ordinary updates. A group identifier connects related variants, while an offer identifier represents a seller’s offer where the destination uses one. Changing price or wording should not create a new product identity.
Start with the purchasable selection
Write down exactly what the shopper can buy. A shoe in black, size 42, is a different selection from the same shoe in size 43. A parent model number can connect them, but it should not erase the distinction between their stock, price and landing-page selections.
Keep the internal SKU and destination identifier relationship documented. They may be identical, but that is a design choice. If you transform identifiers, preserve a reversible mapping so support teams can trace a destination issue back to the correct source row.
Keep commercial changes out of identity
A price is a changing fact about an offer. Adding it to an identifier can make a discount look like a new item and obscure history. The same problem occurs when a title rewrite is used to regenerate IDs.
Choose an immutable identifier from the system that owns the item. Treat it as text across CSV, JSON and spreadsheet work. Leading zeros, long digit strings and case can carry meaning even when a tool tries to interpret them as numbers.
Model groups without collisions
A parent group should identify the family, while each child keeps its own ID. Check that option names are consistent and that two rows do not describe the same combination of options within the same group. A group label alone does not establish that its members are valid variants of one product.
Review identity reuse carefully. If a retired SKU is assigned to an unrelated new item, old approvals and historical measurements may attach to the wrong product. Your process needs a deliberate rule for that situation rather than assuming that an identical string always means an identical item.
Test identity across refreshes
Compare two snapshots in which only price and stock change. The set of item IDs should remain stable. Then test a genuinely new variant and a removed variant. Those changes should be visible as additions and removals with a clear explanation.
Use the variant group checker on a small sample to find duplicate IDs and option collisions. Keep longer-term identity decisions in your source system and review workflow. A checksum or a unique-looking string is not enough to prove that history remains attached to the right item.
ILLUSTRATIVE WORKED EXAMPLE
Make it concrete.
Illustrative family: group TRAIL has items TRAIL-BLK-42 and TRAIL-BLK-43. A sale changes their prices but not their IDs. Introducing a white size 42 variant creates TRAIL-WHT-42; it should not overwrite either black variant or inherit unsupported descriptive decisions.
Your practical checklist
- Identify the exact purchasable selection.
- Keep price and title out of IDs.
- Store identifiers as text.
- Check unique option combinations within groups.
- Define a policy for retired or reused SKUs.
Common questions
Can the group ID equal a child item ID?
Avoid that collision. Follow the target’s grouping requirements and keep the parent identity distinct from its children.
Should IDs change when stock reaches zero?
An availability change is normally an update to the existing item, not a reason to invent a replacement identity.
Sources & scope
Official references checked 29 October 2026. Examples are illustrative, not customer results. Platform requirements can change; use current destination documentation for implementation decisions.
Our editorial method & corrections ↗