Existing B2C Commerce foundation
The landscape included SFRA cartridges, Worldline payment, delivery/pickup slot logic, OCI reservations, SAP CDC/SLAS identity flows, loyalty logic, GTM tracking, and hybrid PWA redirects.
Success Story
Order Management introduced into an existing Salesforce B2C Commerce setup
For a large omnichannel retailer, Salesforce Order Management was integrated into a productive B2C Commerce environment to stabilize and scale post-purchase operations.
The baseline was an established Salesforce B2C Commerce landscape with SFRA storefront flows, payment integration, slot management, inventory reservation, loyalty, identity, tracking, and PWA touchpoints. Salesforce Order Management (SOM) was then introduced as the execution layer for post-order processes and connected to storefront and API channels.
OMS introduction context
Environment and delivery scope
SOM-based order history and order details
Order history and detail views were sourced from SOM, including aggregation of order summary, fulfillment orders, payments, and shipments.
Cancel and modify process rollout
Cancel/modify actions were implemented in SOM, including release of reserved delivery slots and controlled transfer into a follow-up basket.
SOM service layer and object mapping
A dedicated layer handled composite/API integration, SOM-to-SFCC mapping, response normalization, and consistent error handling.
OCAPI extensions for app and API channels
OCAPI actions (`cancel`, `modify`, `confirm`) plus enriched responses (`c_somOrder`, `c_newBasketUUID`) enabled channel-consistent behavior.
Return management logic
A configurable return-by-date logic (for example 14 days) was introduced to align post-purchase and service operations.
Initial project situation
Strong checkout, but fragmented post-purchase flows
Commerce checkout quality was high, but post-order operations lacked an integrated execution model.
Cross-system dependencies for slot, stock, and payment states
Cancel/modify scenarios required consistent orchestration across reservations, slot release, and order status transitions.
Multiple touchpoints across storefront, app, and APIs
Order operations needed the same behavior quality in web UI and API-driven channels.
High stability requirements in a live environment
Commerce, OMS, and third-party integrations required explicit service contracts, fallbacks, and observability.
Activities for OMS introduction
Step 1
Post-purchase target model definition
End-to-end flows for history, details, cancel, modify, and returns were modeled and prioritized with business and technical teams.
Step 2
Integration and service-layer implementation
SOM APIs, mapping rules, error classes, and response contracts were implemented as reusable integration building blocks.
Step 3
Storefront and OCAPI alignment
Account UI, checkout-adjacent flows, and API endpoints were aligned to the new OMS process behavior.
Step 4
Operational hardening and rollout readiness
Logging, monitoring, edge-case handling, and release safeguards enabled a controlled production rollout.
Planning OMS in your Salesforce B2C Commerce setup?
We support target architecture, integration design, API modeling, and stable introduction of order-management capabilities in live commerce environments.
Discuss this story