Can the Salesforce Commerce Cloud adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Salesforce Commerce Cloud tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
How long does the Salesforce Commerce Cloud integration take to ship?
Our standard window is thirty days from signed scope to live Salesforce Commerce Cloud adapter in production, plus a one-week monitored stabilization phase. For Glendale, Arizona, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
What happens if Salesforce Commerce Cloud changes their API after we go live?
Our SRE team monitors Salesforce Commerce Cloud change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
Does it work with our existing Salesforce Commerce Cloud licenses?
Yes — the adapter rides on top of your existing Salesforce Commerce Cloud subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
Do we own the integration code at the end?
Yes. The Connectify Salesforce Commerce Cloud adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.
Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the Salesforce Commerce Cloud surface.