Skip to main content

Salesforce Commerce Cloud

Pinch supports Salesforce Commerce Cloud (SFCC) — both B2C Commerce and B2B Commerce — through a managed install handled by the Pinch team.

How the integration works​

DirectionWhat flows
From SFCC → PinchOrder events (placed, paid, fulfilled), return events, customer profile updates
From Pinch → SFCCDecision tags written to the order record (e.g. Pinch - Review : Suspect Abuse), readable by your existing returns flow
From your warehouse → PinchDisposition data — same API as any other warehouse integration

The exchange uses SFCC's standard order-extension hooks. Your storefront code keeps running as-is; Pinch reads and writes via the SFCC OCAPI surface.

Setup​

SFCC isn't a self-serve install (unlike Shopify). The flow is:

  1. Email support@pinch.ai with your SFCC realm and instance type.
  2. Pinch provisions a service account and grants the OCAPI scopes needed.
  3. A solution engineer schedules a 30-minute kickoff and runs through deployment of the Pinch order extension.
  4. You connect your RMS (Loop, Aftership, etc.) and send disposition data — the same final two steps as the Shopify install.

Most SFCC merchants are live within 2 weeks of kickoff.

What's the same as Shopify​

  • The Pinch team configures your workflows, decisions, and variables during onboarding.
  • Decisions arrive at your RMS via the same customer-tag mechanism.
  • Your customer success manager walks you through the dashboard once data starts flowing.

What's different from Shopify​

  • No App Store install button — everything is provisioned by the Pinch team.
  • Initial sync takes longer (typically 2–4 days vs 1–24 hours on Shopify) because SFCC's bulk OCAPI export is slower.
  • For B2B Commerce instances, additional fields are captured (account-level signals, multi-buyer purchasing patterns) that don't apply to B2C.

See also​