Salesforce Commerce Cloud Platform

Salesforce Commerce Cloud catalogs are typically large, structured, and spread across multiple sites, locales, and price books, which makes manually preparing product data for shopping channels, marketplaces, and ad platforms slow and error-prone. Connecting your Commerce Cloud storefront to Feedance lets you turn that catalog into clean, channel-ready product feeds without custom exports or scripts.

Because Feedance reads product, inventory, and order data directly from your store, feed updates reflect what shoppers actually see and buy, rather than a stale or manually maintained spreadsheet. This is particularly valuable on an enterprise platform like Commerce Cloud, where catalogs change frequently through promotions, price books, and inventory reservations.

Feedance connects to Salesforce Commerce Cloud using secure, permissioned API access, the same type of connection Salesforce provides for approved integrations. You authorize Feedance to read the specific data it needs, and Feedance uses that authorization to pull product, inventory, and order information on an ongoing basis so your feeds and dashboards stay in sync with your live store.

No code, custom middleware, or developer resources are required on your side to maintain the connection. Once access is granted, Feedance handles scheduling, data retrieval, and formatting automatically.

Feedance works with exactly three data entities on every platform it supports, including Salesforce Commerce Cloud:

Feedance does not access customer records, coupons or gift cards, shipping or tax configuration, or any other store data beyond these three entities.

• Two generations of API coexist. Commerce Cloud stores can be integrated through the newer SCAPI (Shopper and Admin APIs, OAuth 2.0, OpenAPI-based) or the older OCAPI, which Salesforce has marked deprecated in favor of SCAPI for new integrations. Which one a given store uses can affect available data and setup details.
• Enterprise access controls. API access to Commerce Cloud is managed through Salesforce's Account Manager, which issues client credentials scoped to specific permissions. Your Commerce Cloud administrator will typically need to authorize and configure this access before a connection can be established.
• Multi-site and multi-locale catalogs. Larger Commerce Cloud implementations often run multiple storefronts, locales, and price books from a single instance, so it is worth confirming which site and locale your feed should draw from.
• Rollout can involve IT or an implementation partner. Because Commerce Cloud is an enterprise platform, connecting a new external tool often goes through a partner agency or internal IT team rather than a single store owner, so plan for that step in your timeline.

1. Sign in to your Feedance account and choose Salesforce Commerce Cloud as your platform.
2. Provide your Commerce Cloud store details and the credentials Feedance requests to establish a secure API connection.
3. Confirm the requested access, which is limited to products, inventory, and orders.
4. Let Feedance run its initial sync to import your catalog, stock levels, and order history.
5. Review your data in Feedance and set up your feed rules, mappings, and destinations.

Feedance keeps your product, inventory, and order data synced with Salesforce Commerce Cloud on a regular, automated schedule so your feeds reflect current catalog and stock conditions without manual re-exports. Exact sync frequency can vary based on your plan and store size, and you can trigger a manual refresh when you need the latest data immediately.

1. Keep product titles and descriptions complete and accurate in Commerce Cloud, since Feedance builds feeds directly from that source data.
2. Make sure variant and pricing data is consistent across the catalog so downstream channels display the correct options and prices.
3. Confirm inventory data is accurate and up to date so your feeds do not advertise out-of-stock items.
4. If you run multiple sites or locales, double-check which one Feedance is reading from before publishing feeds to a new channel.
5. Review your feed in Feedance after major catalog changes, such as a new season launch or bulk price update, to confirm everything synced as expected.