Skip to main content
Marketplace channel operations for Salesforce

Connect Amazon, Flipkart and Myntra directly to Salesforce OMS.

Commerce Pipe connects marketplace orders, inventory, listings and fulfilment events with the Salesforce commerce stack you already operate. Marketplace orders enter Salesforce Order Management directly. Omnichannel Inventory remains responsible for availability and reservations. Your WMS or DMS continues doing the physical warehouse work.

Amazon Flipkart Myntra
commerce pipe — architecture
Commerce Pipe architecture: Amazon, Flipkart and Myntra connected to Salesforce OMS and OCI

What is Commerce Pipe?

Commerce Pipe is an India marketplace operations integration for brands using Salesforce Order Management and Omnichannel Inventory.

It connects Amazon, Flipkart and Myntra marketplace operations with Salesforce so that marketplace orders can enter the same OMS used by the rest of the business, inventory can remain governed through OCI, and channel events can be processed without placing another OMS between the marketplaces and Salesforce.

Commerce Pipe is not a new consumer marketplace. It is not a seller-recruitment platform. And it does not replace your warehouse management system. Its job is narrower: connect marketplace operations to the Salesforce operating model.

Amazon · Flipkart · Myntra
↕
Commerce Pipe
↕
Salesforce Order Management
↕
Salesforce Omnichannel Inventory
WMS / DMS — Physical Fulfilment

You already have an OMS. The marketplace should not create another one.

A common marketplace architecture introduces another operational platform between Amazon, Flipkart or Myntra and the systems a brand already uses. That can leave teams deciding which system owns the order, available-to-sell inventory, reservation state, dispatch status, returns, marketplace exceptions, and financial events.

Salesforce OMS
remains the order lifecycle system
Salesforce OCI
remains the availability and reservation authority
Your WMS/DMS
remains responsible for warehouse execution
Commerce Pipe
handles the marketplace connection between them

What Commerce Pipe handles

01

Marketplace orders directly into Salesforce OMS

Bring supported marketplace orders into Salesforce Order Management rather than recreating them through the storefront checkout. External marketplace identifiers are retained so replayed events can be recognised without producing duplicate order summaries.

02

Inventory governed through Salesforce OCI

Use Salesforce Omnichannel Inventory as the availability and reservation layer across supported channels. Commerce Pipe exchanges marketplace inventory events with that model while the physical stock system continues feeding and executing warehouse inventory.

03

Listings, price and inventory updates

Manage channel-specific product operations required by Amazon, Flipkart and Myntra, including supported listing, price and inventory update workflows. Marketplace-specific identifiers remain mapped to the corresponding merchant SKU.

04

Dispatch, labels, manifests and returns

Commerce Pipe supports the channel workflows required to move supported marketplace orders through dispatch and return states while retaining the Salesforce order lifecycle as the operational view.

05

Retries without losing the business event

Commerce Pipe uses a durable outbox pattern so marketplace operations can be persisted before external calls are attempted. Failed operations can be retried and operational exceptions surfaced instead of silently disappearing between systems.

06

Marketplace financial events

Capture supported marketplace financial information and preserve an auditable operational record for downstream processing. Commerce Pipe does not replace your ERP, accounting system or merchant finance controls.

Supported channels

Amazon, Flipkart and Myntra.

Current scope is these three channels. We do not currently describe Commerce Pipe as supporting every marketplace, every geography or every marketplace fulfilment model.

Amazon — SP-API for orders, listings and financial workflows
Flipkart — Seller APIs for listing, shipment/order, dispatch and returns
Myntra — PRETR V4 for orders, catalogue/inventory and returns
commerce pipe
# Deploy Marketplace Core first
sf project deploy start \
  -d packages/marketplace-core \
  -o my-sandbox

# Then deploy channel adapters
sf project deploy start \
  -d packages/amazon -o my-sandbox
sf project deploy start \
  -d packages/flipkart -o my-sandbox
sf project deploy start \
  -d packages/myntra -o my-sandbox

What Commerce Pipe does not replace

This is as important as the feature list.

Does not replace
Salesforce OMS
It feeds marketplace commerce into it.
Does not replace
Salesforce OCI
OCI remains the availability and reservation layer.
Does not replace
Your WMS or DMS
Warehouse picking, packing, QC and physical execution remain there.
Not the same as
Emporio
Emporio is for operating your own multi-vendor marketplace with 3P sellers.
Not positioned as
Universal aggregator
Current scope is Amazon, Flipkart and Myntra.
Compare

Commerce Pipe or a marketplace aggregator?

Platforms such as Unicommerce, Vinculum and Increff are built for broad multichannel operations with extensive connector ecosystems. Commerce Pipe is designed for a different situation: you already use Salesforce OMS and OCI and do not want another OMS between the marketplaces and Salesforce.

Consider Commerce Pipe when
Consider a broader suite when
Salesforce OMS is already strategic
You need dozens of marketplace connectors
OCI already governs availability
Salesforce is not your central platform
Amazon, Flipkart, Myntra are priority
You require a standalone OMS/WMS stack
You want marketplace exceptions in Salesforce
You span many non-Salesforce ERPs

Commerce Pipe and Emporio solve different marketplace problems

Commerce Pipe

Your brand sells on Amazon, Flipkart and Myntra. Commerce Pipe connects those marketplace channels into Salesforce OMS and OCI.

Emporio

Your brand operates its own multi-vendor marketplace. Emporio handles seller onboarding, offers, buy-box logic and sub-order workflows.

Explore Emporio →

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

Questions about Commerce Pipe

Commerce Pipe is Tailoredd's Salesforce-focused marketplace integration for Amazon, Flipkart and Myntra. It connects marketplace operations with Salesforce Order Management and Omnichannel Inventory.

No. Commerce Pipe is designed to bring marketplace orders and events into Salesforce OMS rather than replace it.

No. Marketplace orders are ingested as marketplace orders into the Salesforce order-management architecture. They are not recreated as SFCC storefront checkouts.

The current documented scope is Amazon, Flipkart and Myntra. Tailoredd does not currently claim universal marketplace coverage.

No. A merchant WMS or DMS continues to own physical warehouse operations such as receiving, picking, packing and QC.

Commerce Pipe's architecture does not require a marketplace aggregator between the supported marketplace APIs and Salesforce. Your wider enterprise architecture may still use other systems for other requirements.

Salesforce Omnichannel Inventory acts as the availability and reservation authority. Physical stock execution remains with the merchant's WMS/DMS.

Commerce Pipe connects a merchant selling on external marketplaces to Salesforce OMS/OCI. Emporio is for businesses building and operating their own multi-vendor marketplace.

The currently documented commercial release covers those three channels. Other marketplace support should not be assumed until implemented and verified.

Keep marketplace operations inside the Salesforce architecture you already chose.

If Salesforce OMS and OCI already sit at the centre of your commerce operation, we can review how Amazon, Flipkart and Myntra would fit around them.