All integrations
Enterprise commerce · import Salesforce B2C Commerce
Connect Salesforce B2C Commerce with fashion content
Import product data, attributes, and media from Salesforce B2C Commerce.
- Available after intake
- Read only
Salesforce B2C Commerce
This is the route
- You create an API client for OCAPI or SCAPI.
- Photopilot imports products with their custom attributes.
- Image and content tasks are ready for each item and variant.
- Approved images and copy are sent to your PIM or catalog import via FTP, the Webshop Excel, or the API.
Salesforce B2C Commerce at a glance
- What is exchanged
- Through OCAPI or SCAPI, Photopilot reads products, custom attributes, and EAN or UPC. Photopilot does not write to Salesforce B2C Commerce.
- How often
- Every two hours by default, with only the products updated in the catalog since the previous run.
- What you provide
- The OCAPI or SCAPI URL of your environment and an API client with client ID and secret, plus read permissions for the catalog.
- Good to know
- The integration is built on the official Salesforce APIs. We define locales, channels, and custom attributes together before it runs on the fixed schedule.
Then in Photopilot
Reliably linked
Let source data flow through to sales-ready product pages
300.000+ articles processed
9,5M+ supplier images indexed
~3.200 photos automatically edited per day
Frequently Asked Questions
How often does Photopilot read from Salesforce B2C Commerce?
Every two hours by default, with only the updated products from the catalog.
What does Photopilot need to connect Salesforce B2C Commerce?
The OCAPI or SCAPI URL and an API client with client ID and secret, plus read permissions for the catalog.
What needs to be clear up front for this integration?
Locales, channels, rights, and custom attributes. The connection imports; approved images and texts are sent via FTP/SFTP, the Webshop Excel, or the API.
How to start
First the trial route, then the technique
The integration is the starting point. After that, Photopilot keeps linking, editing, writing, checking, and publishing together.
What is the source of truth?
Which fields, images, and barcodes define the item.
What can be automated?
Link, crop, and text, or show an exception first.
Where should it go?
Webshop, FTP, Azure, or API, before anything is built.









