Does Esetrix work with Salesforce Storefront Reference Architecture (SFRA)?

Yes. Esetrix is fully compatible with SFRA. The integration operates at the API and data layer, so your SFRA templates, controllers, and front-end customisations remain untouched.

How are SFCC orders split across multiple suppliers?

When an SFCC order contains items from different suppliers, Esetrix splits the order into supplier-specific purchase orders automatically. Each supplier receives only their line items, fulfils directly, and confirmation flows back into the original SFCC order as shipment events.

How long does the Salesforce Commerce Cloud integration take to go live?

Typical go-live is 6 to 8 weeks from contract. This includes API authentication, catalogue and commission mapping, supplier onboarding, UAT, and launch. No systems integrator is required.

Can Esetrix run multiple SFCC sites as a single marketplace?

Yes. Esetrix supports multi-site configurations natively. Supplier catalogues, pricing, and inventory can be scoped per site and locale while commission and settlement operate at the marketplace level.

Does Esetrix support mixed carts with first-party and third-party products on SFCC?

Yes. Buyers can add both operator-owned and supplier-owned products to the same basket. Checkout retrieves live availability, pricing, and shipping for all items. After purchase, Esetrix splits the order and routes each portion to the correct fulfilment source.

How does Esetrix handle internationalisation on Salesforce Commerce Cloud?

Esetrix synchronises product data with locale-specific content across all configured SFCC sites. Pricing, descriptions, and custom attributes can be localised per market while the marketplace logic operates centrally.

What is the best multi-vendor marketplace solution for Salesforce Commerce Cloud?

For enterprise retailers on Salesforce Commerce Cloud, Esetrix is purpose-built marketplace infrastructure that integrates natively via OCAPI and Shopper API. It supports SFRA, multi-site configurations, mixed carts, and internationalisation. Implementation is 6 to 8 weeks with no replatforming and no systems integrator required.

How is Esetrix different from Mirakl for Salesforce Commerce Cloud?

Esetrix is agentic marketplace infrastructure purpose-built for mid-market and enterprise retailers. Unlike Mirakl, Esetrix is operational in 6 to 8 weeks without a systems integrator, includes AI-driven supplier orchestration, and manages the complete supplier lifecycle from onboarding to settlement within a single platform.

Does Esetrix support headless Salesforce Commerce Cloud deployments?

Yes. Because Esetrix operates against the OCAPI and Shopper API layer, it works identically whether the retailer runs SFRA, a composable storefront, or a fully headless front end. The storefront technology is independent of the marketplace logic.

Salesforce Commerce Cloud integration

Turn Salesforce Commerce Cloud into a multi-vendor marketplace. Without replatforming.

Esetrix plugs into your existing SFCC instance through native OCAPI and Shopper API integration. Add suppliers, automate fulfilment, and operate a curated marketplace in 6 to 8 weeks, without replacing the storefront your team already knows.

Request a Commerce Cloud briefing See the architecture →

What the integration delivers

Native

OCAPI + Shopper API (SCAPI)

6–8 wks

From contract to go-live

2-way

Product, inventory & order sync

Zero

Storefront changes required

Capabilities

Everything a marketplace on SFCC needs. Nothing your dev team has to rebuild.

Product sync, order routing, supplier settlement, and agentic operations, delivered through Salesforce Commerce Cloud's native APIs rather than stitched on top of them.

Bidirectional product sync

Products, variants, pricing, images, and custom attributes flow both ways between Esetrix and Salesforce Commerce Cloud. Supplier catalogues publish directly to the correct catalogue assignments and sites.

Real-time inventory

Supplier stock updates propagate to SFCC in seconds. Inventory lists per supplier, with allocation rules and safety thresholds across all sites and locales.

Order routing & split fulfilment

Multi-supplier orders split automatically into supplier-specific purchase orders. Line items route by SKU ownership; fulfilment events return to the original SFCC order with shipment tracking.

Commission & settlement

Commission per supplier, category, or product rule. Automated reconciliation, supplier payout runs, and settlement statements generated from SFCC order data.

Jobs-based orchestration

Asynchronous sync managed through the native SFCC jobs framework. Order, fulfilment, refund, and inventory events processed without polling or custom middleware.

Agentic supplier orchestration

Esetrix agents handle supplier onboarding, catalogue QA, image normalisation, and order exception handling without manual ops for each SKU or order.

Architecture

How data flows between Salesforce Commerce Cloud and Esetrix.

Bidirectional synchronisation via OCAPI and Shopper API, with asynchronous jobs managing each sync. Event-driven, with an immutable audit log on the Esetrix side.

Esetrix→SFCC

Products & variants
Stock levels (inventory lists)
Images & assets
Custom attributes
Catalogue assignments & sites
Order status including tracking details

SFCC→Esetrix

Orders
Customers
Fulfilment events
Refunds & cancellations
Shipment tracking
Buyer messages

Jobs-native by design. Esetrix leverages the native SFCC jobs framework for all asynchronous synchronisations. No custom middleware, no external schedulers, immediate propagation.

Setup

Four steps from contract to live marketplace.

The Esetrix implementation team owns setup end to end. No systems integrator, no outsourced development.

Connect Esetrix to your SFCC instance

Esetrix connects via OCAPI client credentials with scoped access to products, inventory, orders, and customers. No cartridge code modifications required.

Map catalogue, attributes, and commission rules

Map SFCC catalogues, product attributes, and site assignments to the Esetrix marketplace data model. Configure commission rules per supplier, category, or site.

Onboard suppliers and run UAT

Esetrix onboards suppliers in parallel with technical setup. Validate end-to-end flows including order routing, split fulfilment, and settlement.

Activate marketplace

Launch supplier-attributed listings and operate bidirectional sync in production across all configured sites and locales.

Frequently asked

Questions Commerce Cloud teams usually ask.

No. Esetrix integrates at the OCAPI and Shopper API layer. Your SFRA storefront, checkout, and customer experience remain unchanged. Product data, inventory, and orders flow between Esetrix and SFCC through standard API endpoints and the native jobs framework.

Ready to run a marketplace on the Commerce Cloud you already have?

A technical briefing with the Esetrix team covering your SFCC setup, supplier model, and a 6 to 8 week implementation plan.

Request a Commerce Cloud briefing