Salesforce Commerce Cloud Development
Senior engineers working across Salesforce B2C Commerce (SFCC) — SFRA cartridges, OCAPI/SCAPI integrations, and custom controllers — and the honest SFCC → Shopify Plus migration when the licence and agency overhead no longer pay off. We tell you which side of that line your store is on before any code is written.
Our SFCC engagement process
- Audit. We read the existing SFCC codebase — cartridge path, SFRA overrides, custom controllers and ISML, the OCAPI/SCAPI surface, and the job framework — and produce a written assessment of technical debt, upgrade exposure, and whether continued SFCC investment or a Shopify Plus replatform is the more honest call for your GMV and team.
- Engineer. On SFCC: cartridge development against the SFRA base, dw.* script API work, OCAPI/SCAPI integration endpoints, hook-based cart and checkout logic, and Page Designer components. On migration: data-model mapping from SFCC catalogue and customer objects into Shopify, with a 301 plan that protects organic rankings.
- QA + UAT. Regression on a representative sample of orders and integration flows, OCAPI/SCAPI contract verification, and — for migrations — a side-by-side parity pass on catalogue, pricing, promotions, and customer records before any DNS cutover.
- Launch + support. Cutover during low-traffic hours, a monitoring window, and a scoped post-launch support period agreed in writing. For teams staying on SFCC, an optional retainer for ongoing cartridge, integration, and seasonal-readiness work.
What's included
- A senior engineer who actually reads dw.* script API and SFRA cartridge code — not a generalist guessing at Demandware internals
- An honest stay-vs-migrate recommendation grounded in your licence cost, agency overhead, and catalogue complexity — not a default sales pitch in either direction
- SFCC cartridge, OCAPI/SCAPI integration, and Page Designer work, or a full SFCC → Shopify Plus replatform — picked to the brief
- Written architecture briefs, risk registers, and rollback plans you own and can re-read
- Cross-platform fluency: Shopify Plus, BigCommerce, SFCC, and NetSuite in one team — useful when an integration bridges two of them
Project timeline
Scoped per project
A single cartridge or OCAPI integration lands in 2-4 weeks; a substantial SFCC build in 8-16 weeks; an SFCC → Shopify Plus replatform typically 12-24 weeks depending on catalogue size, custom cartridge depth, and integration count. We confirm a window in writing once the audit surfaces the real shape of the work — quoting a fixed day-count beforehand is how scope creep starts.
FAQ
- Do you build on Salesforce Commerce Cloud, or only migrate off it?
- Both. About half of SFCC enquiries want engineering on the existing platform — SFRA cartridge work, OCAPI/SCAPI integrations, custom controllers, Page Designer components — and we do that. The other half are weighing a move to Shopify Plus because the SFCC licence plus mandatory agency overhead has outgrown the revenue. We start every SFCC engagement with an audit precisely so we can give an honest read rather than defaulting to "rebuild it" or "migrate it".
- When does it make sense to migrate from SFCC to Shopify Plus?
- In our experience the trigger is rarely technical capability — SFCC is a capable enterprise platform — it is total cost of ownership. When the SFCC revenue-share licence, the SI/agency retainer needed to ship even small changes, and the cartridge maintenance burden together exceed what an equivalent Shopify Plus build plus our retainer would cost, the maths favours a move. We model that explicitly during the audit. Stores doing very high GMV with deep B2B or complex promotions sometimes still belong on SFCC; we will say so.
- What SFCC work can you actually do?
- SFRA-based cartridge development, dw.* script API work, custom controllers and ISML templates, OCAPI and SCAPI (B2C Commerce API) integration endpoints, hook-based cart/checkout/tax logic, Page Designer components, and the job framework for scheduled imports/exports. We work to the cartridge-path override model rather than forking the base, so upgrades stay tractable.
- How do you protect SEO during an SFCC to Shopify migration?
- A full URL inventory from the SFCC storefront and Search Console, mapped to a 301 redirect plan before cutover, plus parity checks on canonical tags, structured data, and meta. The legacy SFCC URL structure (locale and catalogue path) rarely maps one-to-one onto Shopify, so the redirect map is engineered, not auto-generated — getting it wrong is the single biggest cause of post-migration organic loss.
- What does an SFCC engagement cost?
- A single cartridge or integration typically £6K-£25K. A substantial SFCC build or a full SFCC → Shopify Plus replatform typically £40K-£200K depending on catalogue size, custom cartridge depth, and integration count. We share firm pricing in writing once the audit is complete — quoting before we have read the codebase is unfair to both sides.
- Where are you based?
- London-based (Covent Garden), remote-first across UK + EU + US Eastern overlap. Most of our merchants are UK and EU, with a meaningful slice on US Eastern. We schedule across these zones; deeper APAC coverage is engagement-specific.