HEADLESS
Solution · Composable Salesforce

Salesforce Headless 360.

CRMPRACTICE decouples the experience layer from the Salesforce core — Commerce, Service, Experience, Data Cloud, Agentforce and MuleSoft delivered as composable APIs behind any front end, on any channel.

Book a Headless 360 workshopSee our methodology
(01) What it is

A composable operating model for Salesforce.

Headless 360 is Salesforce delivered as a set of first-class APIs — Shopper (SCAPI), Connect REST, Bulk 2.0, Pub/Sub, Data Cloud and the Agentforce Agent API — orchestrated through MuleSoft and consumed by whichever channel your customers actually use.

The Salesforce core (Sales, Service, Commerce, Experience, Data, Agentforce) remains the system of record and system of intelligence. What changes is the presentation layer: PWA Kit, native mobile, in-app messaging, kiosks, voice and partner portals all consume the same governed API surface.

(02) Reference architecture

The four-tier Headless 360 stack.

01 · Experience LayerChannels & touchpoints
PWA KitNative iOS / AndroidIn-App MessagingKioskVoiceConnected TV
GraphQL / REST · WebSocket / SSE · Native SDK
02 · BFF / EdgeBackend-for-frontend per channel
SSR & streamingPersonalizationEdge cachingPII maskingAuth exchange
Signed service-to-service · mTLS · Circuit breakers
03 · MuleSoft API LayerExperience → Process → System APIs
OAuth 2.0 / OIDCRate limits & quotasObservabilityContract testsSchema registry
Event mesh · Async choreography · Idempotency keys
04 · Salesforce CoreSystems of record & intelligence
Commerce (SCAPI)Service (Connect REST)Experience (LWR)Agentforce (Agent API)Data Cloud (Ingest / Query / Segment)Sales · Identity · Shield · Pub/Sub · CDC · Bulk 2.0
(03) The four pillars

Commerce · Service · Experience · Data & Identity.

01

Headless Commerce

Salesforce Composable Storefront (PWA Kit + Managed Runtime) on top of the Shopper API family — SCAPI for products, cart, checkout, promotions, orders and Einstein recommendations.

02

Headless Service

Service Cloud, Messaging for In-App & Web, Voice and Agentforce exposed through the Salesforce Messaging APIs, Chat/Voice SDKs and Connect REST for cases, knowledge and interactions.

03

Headless Experience

Experience Cloud Lightning Web Runtime (LWR) sites, Connect API, and Experience Cloud for Developers to deliver community, portal and partner UX on any front end.

04

Headless Data & Identity

Data Cloud Ingest, Query, Profile and Segmentation APIs unified with Salesforce Identity, OAuth 2.0 and JWT bearer flows for a single, consented customer graph.

(04) Implementation patterns

Six patterns we deploy on every Headless 360 build.

Named, versioned patterns with reference code, contract tests and observability defaults — not slideware.

P-01

BFF per experience

One Backend-for-Frontend service per channel (web, mobile, kiosk, in-vehicle). Each BFF composes SCAPI, Connect REST, Data Cloud and third-party APIs into channel-shaped payloads — never call Salesforce directly from the browser.

P-02

MuleSoft as the API façade

MuleSoft Anypoint publishes a System → Process → Experience API layer. Salesforce APIs sit behind System APIs; SLAs, rate-limits, caching, PII masking and observability are enforced at the Experience tier.

P-03

Composable Storefront reference build

PWA Kit + Managed Runtime with Server-Side Rendering, ISR-style cache tags on SCAPI, edge personalization via Data Cloud segments and Einstein product recommendations invoked server-side.

P-04

Agentforce as a headless agent

Agentforce Agent API embedded in any UI via the Messaging for In-App SDK or a lightweight Web Component — reasoning, tool-use and grounding still governed by Salesforce Trust Layer.

P-05

Event-driven sync

Platform Events, Change Data Capture and Data Cloud Data Actions push state changes to Kafka / EventBridge. Front ends subscribe via WebSocket / SSE gateways for realtime UX.

P-06

Zero-trust identity

Salesforce Identity as the OIDC provider, OAuth 2.0 Web Server + PKCE for user flows, JWT Bearer for service-to-service, Named Credentials for outbound, and Shield-encrypted PII end to end.

(05) Implementation method

How CRMPRACTICE delivers Headless 360.

01

Discover — Headless readiness diagnostic

Two-week assessment of channels, journeys, current Salesforce estate, API maturity, latency budgets and org-splitting decisions. Output: composability score, target reference architecture and phased roadmap.

02

Design — Reference architecture & API contracts

System / Process / Experience API design in MuleSoft, SCAPI + Connect REST usage map, Data Cloud data model, identity flows, edge/caching strategy and non-functional targets (RPO/RTO, p95 latency, cost per session).

03

Deliver — Composable storefront + BFF pods

Parallel pods: (1) PWA Kit / Composable Storefront, (2) BFF & MuleSoft APIs, (3) Data Cloud + Agentforce, (4) Identity & Trust. Trunk-based delivery, contract tests, feature flags and blue/green releases.

04

Evolve — Managed platform & experimentation

SRE-style ownership of Managed Runtime, API observability, evals for Agentforce, personalization experiments on Data Cloud segments and quarterly value reviews against the original business case.

(06) Technology stack

What sits under the hood.

Salesforce Commerce Cloud (B2C & B2B) — SCAPI, PWA Kit, Managed RuntimeService Cloud + Messaging for In-App & Web, Service Cloud VoiceExperience Cloud — LWR sites, Connect REST APIAgentforce — Agent API, Atlas reasoning engine, Trust LayerData Cloud — Ingest, Query, Profile & Segmentation APIsMuleSoft Anypoint Platform — API Manager, Flex Gateway, DataWeaveSalesforce Identity — OAuth 2.0, OIDC, JWT Bearer, SSOHeroku / Hyperforce / AWS / Cloudflare edge
(07) Anti-patterns

What we refuse to ship.

  • 01Calling SCAPI or Connect REST directly from the browser with a long-lived token.
  • 02Treating the composable storefront as a static site — losing SSR, personalization and SEO.
  • 03Bypassing MuleSoft and hard-coding Salesforce endpoints into every channel.
  • 04Duplicating the customer profile in a bespoke store instead of using Data Cloud as the graph.
  • 05Embedding Agentforce via iframe hacks that break the Trust Layer and audit trail.
  • 06Ignoring API rate limits, bulk vs streaming choices and org-split cost modelling.
3.2x
faster time to new channel
48%
storefront p95 latency reduction
60%
less duplicate integration code

Ready to make Salesforce composable?

Two-week Headless 360 readiness diagnostic led by a Principal Architect — reference architecture, API contracts and a phased roadmap before any build begins.

Book a Headless 360 workshop