Map legacy catalog fields to the AgenticLift schema and import your data.
Prepare your data
Before import, complete the following steps:
- Map legacy field names to the AgenticLift schema (for example:
colour_hextocolor,legacy_skuto product variantsku). - Confirm the following are ready for Agentic Channel configuration:
- The locale for your catalog (for example:
en-US). This value is auto-populated from the Store settings during channel creation. - The Store key created during project settings configuration.
- If Stripe is your payment service provider, the restricted secret key from your Stripe account. This is entered during Agentic Channel setup.
- The locale for your catalog (for example:
- Remove duplicates and consolidate variant SKUs under a shared
item_group_id. - Ensure all required attributes are populated.
Products with missing
gtin, brand, image_link, or description are at high risk of being excluded from AI agent recommendation sets.Import products
Use the Import API for catalogs exceeding 500 SKUs. For smaller catalogs, use the Merchant Center to import from a CSV file.
Link inventory
Tie Inventory entries to the supply Channel to ensure accurate availability in the feed. Out-of-stock items should not have
enable_checkout set to true.Group variants
Use a shared
item_group_id for variants of the same product to prevent fragmented search results. For example, if a shoe comes in 10 sizes, all 10 must be grouped under one item_group_id. Otherwise, the AI agent sees 10 separate products, which reduces recommendation quality.Price configuration
Prices must be embedded at the variant level and, if you use dedicated Channels, scoped to the distribution Channel. Currency must be
USD for the US launch. For real-time price updates, use the Import API. These propagate to the Universal AI Feed within 15 minutes.