Stable item IDs in a product feed

A stable item ID is the durable identifier for a product or sellable variant. It should stay the same when a title, description, photo or price changes. That continuity lets a receiving system recognise that it is looking at the same item with updated facts rather than a new product appearing from nowhere.

Why this matters now

Titles change for good reasons: a merchant adds a material, corrects a spelling mistake or updates a seasonal name. If the ID changes too, historical associations and routine refreshes become needlessly fragile. Stable IDs are quiet infrastructure. Customers rarely see them, but feeds rely on them to make sense of change.

What to check first

A practical way to do it

1. Find the existing internal product or variant identifier in the source shop.
2. Choose the level of identity that matches the sellable row, especially for variants.
3. Keep the value as text so leading zeros do not disappear in exports.
4. Reject duplicates before publishing a refreshed feed.
5. Document any migration where an old ID must deliberately be retired.

Common mistakes

• Generating IDs from product titles or URLs.
• Sharing one item_id across variations that can have different stock or prices.
• Replacing all IDs during a platform migration without retaining a mapping.

What this does not mean

A clean product feed makes your catalogue understandable to a receiving platform. It does not guarantee approval, inclusion, ranking, sales or a particular checkout experience. Those decisions and customer-facing flows remain with the platform and the merchant.

The useful habit is simple: correct the source data, then validate the exported feed. Do not patch a one-off file and assume the next shop sync will remember your fix. That is how a tidy launch turns into a slow drift a fortnight later.