Agentic Commerce
Catalog & Inventory Orchestration
enable agentic commerce by synchronizing your existing product data with the global ai ecosystem to sell products via agentic platforms (such as chatgpt, gemini, and perplexity), your product data must be "agent ready " this means it is not only structured for machine readability but also synchronized in real time to prevent over selling and ensure accurate attribute discovery forter agentic orchestration acts as the orchestration layer between your backend (shopify, google merchant center, salesforce commerce cloud, sfcc) and the various ai model context windows and tool calling apis catalog orchestration overview 1\ integration methods forter agentic orchestration supports three integration methods based on your e commerce setup choose the method that matches your platform a custom integration for merchants who build their own commerce backend you host a product feed at a stable url, and forter fetches it periodically what you provide feed url + webhook endpoint for orders supported formats google merchant center xml, shopify csv, or json how it works you host your feed file at a stable url, and forter fetches it on a configured schedule (hourly, daily, or custom) order delivery completed orders sent to your webhook endpoint with hmac signature verification best for custom built backends managing their own inventory and order processing setup see docid uapnsg c5fkunlagkpqr b salesforce commerce cloud (sfcc) integration direct api integration—no feed hosting needed forter pulls your catalog directly from sfcc via ocapi what you provide ocapi client id and secret how it works forter continuously syncs your catalog via sfcc's ocapi shop api catalog pulling automatic sync of all products and inventory order creation orders created directly via ocapi basket/order apis setup see docid\ tehbhsbzfwvyfo7xd2esl c shopify integration direct api integration—no feed hosting needed forter pulls your catalog directly from shopify via the admin api what you provide shopify admin api access token how it works forter continuously syncs your catalog via shopify's admin api catalog pulling automatic sync of all products, variants, and inventory order creation orders created as draft orders in shopify setup see docid\ rybnwqwu3cm15ccqbvgkm 2\ automated catalog enrichment a primary challenge of agentic commerce is that standard product descriptions are often written for human eyes or legacy search engines, lacking the structured "intent data" agents need once your catalog is connected, forter automatically processes and enhances your data semantic optimization forter rewrites and augments product descriptions to be more discoverable by llms we add missing context that agents frequently look for, such as specific use cases, compatibility notes, and material nuances category normalization we normalize your internal categories into a universal schema, ensuring your products are correctly categorized and discoverable across all ai platforms attribute extraction forter identifies and labels attributes buried in your text (e g , "bpa free," "tsa approved") so agents can answer specific user constraints without hallucinating 3\ inventory heartbeat & reliability to prevent agents from attempting to purchase out of stock items—which creates a poor user experience and potential api errors—forter maintains a high frequency inventory heartbeat real time synchronization forter utilizes webhooks from your e commerce platform to update stock levels the moment a sale occurs on any channel the safety buffer within the forter dashboard, it is possible to set inventory thresholds for example, you can instruct forter to mark an item as "unavailable" to agents when your physical stock hits 3 units, mitigating the risk of race conditions between human shoppers and high speed agents 4\ platform distribution once your catalog is ingested and enriched by forter, it is automatically formatted and exposed to the following agentic interfaces openai (gpts/chatgpt) exposed via structured json schemas for tool calling google gemini integrated via google merchant center synchronization perplexity optimized for citation based discovery and "pro" shopping actions individual/private agents made available through universal commerce protocol (google ucp) 5\ portal configuration to enable catalog synchronization, configure the following in the forter portal based on your integration method shopify integration configure these fields in the integrations > shopify section field description example required platform select platform type "shopify" yes shop domain your myshopify com domain "yourstore myshopify com" yes admin api access token shopify admin api token "shpat " (encrypted) yes api version shopify api version "2024 01" yes steps create shopify admin api access token (see docid\ rybnwqwu3cm15ccqbvgkm ) configure the fields above in the forter portal forter automatically begins syncing your catalog via shopify admin api products appear in the portal within minutes sfcc integration configure these fields in the integrations > sfcc section field description example required platform select platform type "sfcc" yes sfcc instance url your sfcc instance "https //dev01 yoursite demandware net" yes site id your site identifier "sitegenesis" yes ocapi client id ocapi client identifier "forter agentic commerce" yes ocapi client secret ocapi client secret •••••••• (encrypted) yes ocapi version api version "v23 1" yes steps configure ocapi credentials in sfcc business manager (see docid\ tehbhsbzfwvyfo7xd2esl ) configure the fields above in the forter portal forter automatically begins syncing your catalog via ocapi products appear in the portal within minutes custom integration configure these fields in the integrations > custom section field description example required feed url url to your hosted product feed "https //yourstore com/feed xml" yes feed format format of your feed file "google" , "shopify" , or "json" yes update frequency how often forter fetches your feed every 24 hours yes feed active enable/disable automatic fetching true yes feed username http basic auth username (if required) "api user" optional feed password http basic auth password (if required) •••••••• (encrypted) optional note for authentication methods beyond http basic auth (e g , bearer token, api key header), contact your forter representative to configure custom authentication steps host your product feed at a stable url configure the fields above in the forter portal set feed active to true forter automatically fetches and processes your feed on the configured schedule 6\ implementation workflow portal configuration configure your feed or platform credentials in the forter portal (see section 5 above) automated enrichment forter begins the ingestion process, cleaning your data and generating semantic tags deployment once the initial sync is complete, your products are live across the agentic network performance monitoring use the forter portal to monitor semantic hits—instances where an agent successfully identified and considered your product for a user query