What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Arlington, Texas. After go-live, the Salesforce Commerce Cloud adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
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.
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 Arlington, Texas, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
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.
Is this a packaged Salesforce Commerce Cloud connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
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.