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.
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 Mount Vernon, New York, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Mount Vernon, New York. 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.
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.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Salesforce Commerce Cloud adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.