Skip to content
oBizee / FIELDNOTES
GUIDE 335 / Search, data and automation

Keep catalogue-feed identifiers stable across product changes

A product feed needs a reliable way to identify the item it describes. Treat identifiers as a data contract rather than rebuilding them from whatever title happens to be visible today.

3 min read · estimatePublished by oBizee · Editorial approach

Turn social interest into a workable order process →

A product feed needs a reliable way to identify the item it describes. Treat identifiers as a data contract rather than rebuilding them from whatever title happens to be visible today.

Distinguish a product family from a sellable option

A parent product and a particular size or colour can require different representations. Decide how the feed, storefront and marketing events refer to the same sellable item.

Do not assume that matching display names establish identity. Names can change, and two products can share similar wording.

Record the mapping explicitly

Keep the internal product reference, any variant reference, destination URL and external feed identifier together. Write down what happens when a product is renamed, removed or replaced.

Google Merchant Center's product data specification defines identifiers and product attributes for its feeds. Check the current rules for the destination you use rather than transferring one platform's format to another. Merchant Center specification

Test a rename and a variant

Use a controlled sample to see whether a title change accidentally creates a new item. Check that a selected variant opens the relevant buying choice and reports the appropriate price and availability.

A feed accepted without errors can still point to the wrong option. Inspect the actual destination page, not only the ingestion status.

Keep retired items intentional

Decide how discontinued products leave the feed and what their links show. Do not reuse an old identifier for an unrelated new item solely to save setup work.

Preserve enough history to investigate a campaign or customer question about an earlier product. The mapping should explain the transition rather than conceal it.

Connect the feed to the operating routine

Identify who updates the feed and how failures become visible. A manually refreshed feed should not be described as real-time synchronisation.

This is a preparation guide, not a claim that every feed destination is natively integrated with oBizee. Use the catalogue and stock hub to make the underlying records consistent before using them in another system.

Illustrative case to check

A blue medium shirt is renamed for a new collection. Its sellable identity should not accidentally become a different feed item solely because the title changed. Separately, a redesigned shirt with different construction should not inherit the old reference without a deliberate rule. Keep both decisions in the mapping so campaigns and product pages remain understandable.

Use this guide, then test your own workflow.

Examples are illustrative. Confirm current features, charges and suitability before making a business decision.

Explore this topic → · Find an oBizee setup guide · Ask about your store