still, items, things, footwear, shoes, brogues, men, brown, shoelaces, catalog, white
Photo by StockSnap on Pixabay

Supply Chain

Part of Retail advertising technology infrastructure

Connecting product catalogues to sponsored listing systems

Plan item IDs, feed mappings, stock updates and checks for a retailer sponsored listing integration.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Supply Chain Desk.

undefined

Connect a product catalogue by defining what one advertised item represents: keep its ID stable across systems, map fields for selection and display, and set rules for price and stock changes.

Check that the ad, landing page and any purchase record refer to the intended item or variant. A successful feed upload alone does not establish that a listing is accurate when shown.

Sponsored-listing systems each define their own catalogue contract. Criteo's retailer-integration feed (Criteo), Kevel's catalogue for sponsored listings (Kevel) and Epsilon Retail Media's filter mappings (Epsilon Retail Media) require different fields and different delivery routes.

Sponsored Listing System Requirements for Product Catalogue Integration

  • PlatformCriteo
  • PlatformKevel
  • PlatformEpsilon Retail Media
  • Required Unique IDMust be unique and consistent per variant; changes break attribution (Criteo)
  • Required Unique IDSet at catalogue creation; cannot be changed later (Kevel)
  • Required Unique IDNot specified directly, but relies on API mappings (Epsilon Retail Media)
  • Key Fieldsid, title, description, link (Criteo)
  • Key FieldsUnique item ID, with aliases for attribute keys and search keys (Kevel)
  • Key FieldsCategory cross-sell mappings via API or TSV file in Google Cloud Storage (Epsilon Retail Media)
  • Update MethodFile-based feed upload; store ID passed in ad request for availability (Criteo)
  • Update MethodFeed-based catalogue update; use of aliases and search keys for filtering (Kevel)
  • Update MethodFilter mapping updates via filterMapping API or TSV file (Epsilon Retail Media)

Choose the sponsored-listing item level

A retailer may have a parent product, several saleable variants and offers from different sellers. Decide which is the advertising item. Store parent, brand, category and seller relationships separately, and make the landing page resolve to the advertised offer.

Criteo’s current feed documentation requires a unique, consistent ID for each product variant. It says changes to IDs break attribution and reporting (Criteo).

Kevel requires an item ID key when a catalogue is created. It says the key cannot later be changed (Kevel).

These are provider-specific requirements, but both make identifier design an early integration decision.

For Criteo, map the variant ID to id, the product name to title, and the product detail-page URL to link (Criteo).

Criteo's feed documentation sets requirements for catalogue fields; check its specification when mapping a catalogue (Criteo).

Integration Steps for Product Catalogue to Sponsored Listing Systems

  1. Define Item LevelDecide whether the advertising item is a parent product, variant, or seller-specific offer. Store relationships separately.
  2. Assign Stable IDsUse a consistent, unique ID per variant—do not change after integration (Criteo) or during catalogue creation (Kevel).
  3. Map Key AttributesMap variant ID to id, name to title, and detail page URL to link (Criteo); use aliases and search keys (Kevel).
  4. Validate Landing PagesEnsure the landing page resolves to the advertised offer and matches the advertised content.
  5. Test with Representative RecordsTrace normal items, variants, unavailable stock, and invalid seller offers through ingestion to purchase feed.

Map the catalogue feed's uses

Campaign users need to find eligible products. The decision system needs attributes for page context and shopper-selected filters. The page or app needs approved content to render the listing.

Kevel separates product data into campaign management, targeting and rendering. Use aliases to correlate your attribute keys with reserved keys, and search keys to filter the data (Kevel).

Some integrations use SKU and lookup details in their own systems after winning ads are returned; others want ad responses to match organic listings. Kevel's catalogue guidance identifies campaign management, targeting and rendering as uses for product data (Kevel).

Kevel builds a catalogue from a feed of products and requires only a unique identifier for items, with aliases correlating your attribute keys to its reserved keys and search keys to filter the data (Kevel). Epsilon Retail Media maps category IDs to human-readable values and says there is no file-based method to synchronise this information: it must be done through the filterMapping API (Epsilon Retail Media).

The Criteo retailer-integration feed specification lists id, title, description and link among its fields. It defines id as a unique identifier for a single product variant and says it must be unique and consistent; the link must go to the product detail page whose information matches the catalogue. Use the chosen platform’s schema, not one provider’s fields as a universal standard (Criteo).

Epsilon Retail Media accepts category cross-sell mappings through its crossSellCategory API or as a TSV file in a Google Cloud Storage bucket it hosts, one file per catalogue (Epsilon Retail Media). Each row maps a category to a category it can target, each mapping is single-directional, and the TSV should be UTF-8 encoded (Epsilon Retail Media). It advises synchronising cross-sell mappings to automate approval and reduce campaign management load (Epsilon Retail Media).

Make freshness part of eligibility

Identify the source of stock, price and destination data, how each change reaches the ad system, and what happens while an update is pending. For store-specific availability, Criteo recommends passing the selected store ID in the ad request; when a shopper selects a filter, Criteo says to make a new API call including that filter (Criteo). Keep the request’s store and filter values aligned with current retailer data.

Set a retailer rule for stale or unknown items, such as withholding paid eligibility until the source and ad system agree. Check that the chosen platform can enforce the rule, then apply the same eligibility decision before the listing is served; do not assume it happens automatically.

Category data drifts as the site changes. Epsilon Retail Media says that as you create additional categories on your site, the filterMapping API must be used to update categories (Epsilon Retail Media).

Handling Stock, Price, and Freshness in Sponsored Listings

  1. Identify Data SourcesDetermine origin of stock, price, and destination data (e.g., ERP, POS, inventory system).
  2. Set Update RulesDefine how updates propagate: e.g., real-time sync, batch feeds, or API calls. Use store ID in ad requests for location-specific availability (Criteo).
  3. Enforce EligibilityImplement rule to withhold paid eligibility if stock or price is stale or unknown. Confirm platform supports this enforcement.
  4. Monitor DriftUpdate category mappings via filterMapping API when new categories are added (Epsilon Retail Media).

Trace representative records

With authorised test data, trace a normal item, a variant, an unavailable item and an offer from a seller the advertiser cannot use. Follow each record through ingestion, the campaign picker, ad decision, rendered placement and proposed purchase feed.

Change one price or stock value and record when the advertising view updates. Run the check before release and compare the observed update with the retailer's intended rule.

When a tile is wrong, identify the first stage where the item diverges. When the tile is correct but a sale cannot match it, inspect the item ID and parent relationship before changing attribution settings.

Pre-Release Validation Checklist for Sponsored Listing Integration

  • Test normal product listingVerify correct ID, title, image, price, and link are displayed.
  • Test variant displayConfirm variant-specific details (e.g., size, colour) match the advertised offer.
  • Test out-of-stock itemCheck that it's excluded from eligible listings and does not appear in ads.
  • Test seller restrictionEnsure offers from restricted sellers do not appear in sponsored listings.
  • Test price updateChange one price and confirm the ad view updates within expected timeframe.
  • Validate purchase trackingEnsure proposed purchase feed matches the item ID and parent relationship used in ad.

Further reading: Product Feed Parameters (developers.criteo.com).

More from Supply Chain

Supply Chain

Ad servers and creative delivery

Understand publisher and advertiser ad-server handoffs, creative delivery, counting differences and checks before a tag goes live.