Commercial Availability
Human approval: Not Required
Dependency: None

Salesforce OMS Marketplace Architecture for Amazon, Flipkart and Myntra

Technical architecture reference for Commerce Pipe: how marketplace orders, inventory, listings and financial events connect Amazon, Flipkart and Myntra with Salesforce Order Management and Omnichannel Inventory.

Architecture overview

Commerce Pipe connects Amazon, Flipkart and Myntra marketplace operations with Salesforce Order Management (OMS) and Omnichannel Inventory (OCI). The architecture preserves two invariants:

  1. Marketplace orders enter Salesforce OMS directly. They do not pass through SFCC checkout or get recreated as storefront orders.
  2. OCI remains the availability and reservation authority. Commerce Pipe exchanges marketplace inventory events with OCI. Physical stock execution stays with the merchant's WMS or DMS.

Data flow

Marketplace channels
Amazon (SP-API)
Flipkart (Seller API v3 + v2 returns)
Myntra (PRETR V4)
→
Commerce Pipe
Durable outbox
Deduplication
Channel adapters
→
Salesforce
Order Management (OMS)
Omnichannel Inventory (OCI)

Your D2C storefront (SFCC or headless) continues sending orders into Salesforce OMS through its standard integration. Commerce Pipe handles the marketplace channel. Both converge on the same OMS.

Durable outbox pattern

Commerce Pipe uses a two-transaction pattern to separate Salesforce DML from marketplace API callouts:

  1. Transaction 1: Persist the marketplace operation as an outbox record inside Salesforce. This commits within Salesforce governor limits.
  2. Transaction 2: An async process reads outbox records and attempts the marketplace API call. Success marks the record complete. Failure routes it to a dead-letter queue with error context.

This means a marketplace API timeout or error cannot roll back Salesforce data. The business event is never silently lost.

Channel adapters

Commerce Pipe is structured as four SFDX packages:

Technical Evidence Block

Commerce Pipe Package Architecture

Verified Capabilities & Contracts

  • ✓ marketplace-core: shared framework, outbox, dedup, error handling
  • ✓ amazon: SP-API adapter (depends on marketplace-core)
  • ✓ flipkart: Seller API adapter (depends on marketplace-core)
  • ✓ myntra: PRETR adapter (depends on marketplace-core)

Operational Boundaries & Limitations

  • ⚠ Each channel adapter requires its own marketplace API credentials
  • ⚠ Channel-specific API rate limits apply independently
Last verified: September 2026
Reviewed by: tailoredd Platform Engineering

Each adapter handles the marketplace-specific API contracts, authentication, and data mapping while the core package provides shared outbox, deduplication, error handling, and the LWC Operations Console.

API surface per channel

  • Amazon: SP-API — Orders, Listings Items, Finances. Authentication via LWA (Login with Amazon) through Named Credentials.
  • Flipkart: Seller API v3 for orders, listings, dispatch. Returns still include v2 endpoints. Authentication via External Credentials.
  • Myntra: PRETR V4 for orders, catalogue/inventory, returns.

Capability and boundary matrix

Commerce Pipe Operational Boundaries

CapabilityOwnerIntegrationAuthorityNotes
Marketplace Order Ingestion Commerce Pipe SP-API / Seller API / PRETR Salesforce OMS Marketplace orders enter OMS directly as OrderSummary records. External order IDs retained for deduplication.
ATP & Inventory Reservations Salesforce OCI OCI APIs OCI Omnichannel Inventory remains the availability authority. Commerce Pipe syncs marketplace stock levels.
Listing & Price Sync Commerce Pipe Channel-specific APIs Marketplace Product data mapped from merchant SKU to marketplace-specific identifiers.
Dispatch & Label Generation Commerce Pipe Channel fulfilment APIs Marketplace + OMS Dispatch events update both marketplace and Salesforce order lifecycle states.
Return Processing Commerce Pipe Channel return APIs Marketplace + OMS Return events surfaced in Salesforce. Physical return handling stays with WMS.
Financial Event Capture Commerce Pipe Settlement/finance APIs Operational record Auditable transaction data preserved for ERP handoff. Commerce Pipe does not execute payouts.
WMS/DMS Physical Execution Out of scope Not managed Merchant WMS/DMS Picking, packing, QC and physical stock management remain with the merchant.

What Commerce Pipe does not do

  • Does not replace Salesforce OMS — it feeds marketplace orders into it.
  • Does not replace OCI — OCI remains the reservation authority.
  • Does not replace your WMS or DMS — physical warehouse execution remains there.
  • Does not operate as a consumer marketplace — that is Emporio.
  • Does not claim universal marketplace coverage — current scope is Amazon, Flipkart and Myntra.
  • Does not calculate commissions or execute seller payouts.

Failure modes and operational visibility

Fault Tolerance

Known Failure Modes & Degradation Behaviors

Marketplace API timeout during order pull

Behavior during fault:

Outbound request records failure in the durable outbox. The operation persists in Salesforce before the external call is attempted.

Fallback / Degradation:

Dead-letter queue captures the failed event. Retry logic re-attempts delivery. No order data is silently lost.

Operator Visibility:

LWC Operations Console surfaces failed operations with marketplace error codes and retry history.

Duplicate marketplace order event received

Behavior during fault:

Exactly-once deduplication matches the external marketplace order identifier against existing OrderSummary records.

Fallback / Degradation:

Duplicate event is acknowledged but not processed. No duplicate OrderSummary is created.

Operator Visibility:

Dedup match logged in the Commerce Pipe operational log with the matched external ID.

OCI inventory reservation failure

Behavior during fault:

If OCI cannot reserve inventory for a marketplace order, Commerce Pipe records the reservation failure against the order.

Fallback / Degradation:

Order enters an exception state in OMS. Operator reviews and decides next action (manual reserve, cancel, etc).

Operator Visibility:

Exception visible in Salesforce OMS and the Commerce Pipe Operations Console.

Marketplace settlement data delayed

Behavior during fault:

Financial event sync runs on marketplace-defined settlement cycles. Delays reflect marketplace processing, not Commerce Pipe failures.

Fallback / Degradation:

Financial data arrives when the marketplace settles. No data is fabricated or estimated.

Operator Visibility:

Settlement sync status visible in Operations Console with last-successful-sync timestamps.

Commerce Pipe vs Emporio

Commerce Pipe connects a merchant selling on external marketplaces (Amazon, Flipkart, Myntra) to Salesforce OMS/OCI. The marketplace already exists. Commerce Pipe is the connectivity layer.

Emporio is for businesses building and operating their own multi-vendor marketplace. It handles seller onboarding, catalog moderation, buy-box logic, split cart routing, and financial data handoff to ERP.

One connects your company to external marketplaces. The other helps your company operate a marketplace of its own.

Sources and references

Primary Documentation & Verified Sources