eCommerce
eCommerce EDI and API Integration for Marketplaces, Drop-Ship and 3PLs
Grow online channels without growing manual work
Online sellers juggle marketplaces, storefronts, retailer drop-ship programs and 3PLs. ECOM connects them all to your ERP and inventory, so orders flow automatically and every channel shows accurate availability.
At a glance
Key documents
- 850 Purchase Orders
- 855 Order Acknowledgments
- 856 Ship Notices (ASN)
- 810 Invoices
- 846 Inventory Reports
- 945 Warehouse Shipping Advice
Systems we integrate
- Storefront and marketplaces
- ERP or order management
- Warehouse or 3PL
- Retailer drop-ship programs
- Who we help
- Online sellers and brands, from storefront-only businesses adding marketplaces to sellers in retailers’ drop-ship programs, and the operations teams behind them.
- What we connect
- Your storefront, marketplaces, retailer drop-ship programs, ERP and 3PLs, so orders, inventory, tracking and invoices share one flow.
- Problems we solve
- Overselling, orders keyed by hand, tracking that reaches the channel late, and a different format at every partner.
- Even without EDI
- Marketplaces and storefronts mostly use APIs rather than EDI. ECOM works with APIs, EDI, files and portals, so the channel does not have to use EDI.

What is eCommerce integration for sellers?
For online sellers, integration means connecting sales channels such as marketplaces and storefronts with back-office systems like ERP, inventory and fulfillment. It also often includes retailer drop-ship programs that use EDI, and 3PL warehouses that ship orders. The goal is one accurate flow of orders, inventory and shipment data across every channel.
Who you connect with
Who an online seller exchanges data with
The same inventory and orders feed every channel; the partners decide the format.
-
Marketplaces
Orders, listings, inventory
Marketplace APIs -
Retailer drop-ship programs
Orders, tracking, invoices
X12 EDI -
Your storefront
Orders, stock, shipping
Platform APIs -
Warehouses and 3PLs
Ship requests, confirmations
EDI, API or files -
Carriers
Labels, tracking events
Carrier APIs
How you sell online
Marketplaces, retailer drop-ship, your own storefront and fulfillment each need a different connection
The four below are the common ways an online seller connects. Most sellers run more than one.
-
Marketplace selling
Sellers listing products on one or more marketplaces.
- How it runs
- Orders are pulled by API, acknowledged, shipped with tracking and settled. Inventory and prices go back on the marketplace’s schedule.
- Systems
- Marketplace seller interfaces, ERP, warehouse.
- Typical problem
- Update limits and late-shipment metrics make accuracy and timing the main risks.
-
Retailer drop-ship programs
Sellers shipping direct to customers for a retailer’s website.
- How it runs
- The retailer sends an order, you acknowledge, ship, return tracking and invoice, and keep inventory current.
- Documents
- Systems
- ERP, warehouse or 3PL, retailer drop-ship portal.
- Typical problem
- Acknowledgment and tracking deadlines are measured, so manual handling does not keep up.
-
Home goods and specialty marketplaces
Suppliers selling through marketplaces that ship from supplier warehouses.
- How it runs
- Orders, ship confirmations with tracking and invoices are exchanged under the marketplace’s supplier program.
- Systems
- ERP, warehouse, marketplace supplier portal.
- Typical problem
- Large, bulky items add carrier and delivery-window rules to the order data.
-
Warehouse and 3PL fulfillment
Sellers who store and ship inventory through a fulfillment partner.
- How it runs
- Ship requests go to the partner, which confirms shipments and returns, and sends inventory adjustments back.
- Systems
- ERP, 3PL warehouse system, carriers.
- Typical problem
- The seller’s available quantity depends on the partner’s confirmations arriving on time.
How to read this page: a standard or system named here shows where a requirement is published or what ECOM can connect. It does not mean ECOM has a verified partnership with any named company, and your own contracts and partners define the final requirements.
Who it's for
Different roles, different workflows
-
Brands and sellers on marketplaces
Orders arrive from marketplace interfaces, and inventory, shipment tracking and returns must go back in each marketplace’s required form and timing.
-
Sellers in retailer drop-ship programs
A retailer’s website takes the order and you ship direct to its customer. Orders, shipment confirmation, tracking and invoices follow the retailer’s drop-ship guide, usually over EDI.
-
Online sellers with warehouses and 3PLs
Orders, inventory and shipment confirmations pass between the storefront, the ERP and one or more fulfillment partners, and must reconcile across all of them.
How the workflow runs
One retailer drop-ship order, from the retailer’s website to the invoice
Marketplaces mostly use APIs. Retailer drop-ship programs mostly use EDI. A seller that has both needs one order and inventory flow behind them.
- Seller→Retailer 846 Inventory feed Available quantity per item, on the retailer’s schedule.
- Retailer→Seller 850 Drop-ship order The retailer’s customer is the ship-to.
- Seller→Retailer 855 Order acknowledgment Accepts or rejects; flags backorders.
- Seller→Warehouse or 3PL 940 Ship request Pick, pack and ship to the end customer.
- Warehouse or 3PL→Seller 945 Shipped confirmation Carrier, tracking number and quantities.
- Seller→Retailer 856 Shipment notice and tracking Lets the retailer tell its customer.
- Seller→Retailer 810 Invoice Against the order the retailer sent.
- 01
Publish inventory you can honor
Send availability by the retailer’s schedule. Counts that run ahead of the warehouse become cancelled orders.
- 02
Receive and acknowledge orders quickly
Many programs measure acknowledgment time and cancellation rate. Validation up front keeps bad orders out of fulfillment.
- 03
Release to fulfillment
The order goes to your warehouse or 3PL, or to your supplier if the product ships from a vendor.
- 04
Return tracking and confirm shipment
The tracking number and carrier must reach the retailer within its window, or it cannot update its customer.
- 05
Invoice, then handle returns
Invoice against the retailer’s order, and process return authorizations where the program uses them.
Beyond EDI
Every way an online order or inventory change can arrive
One seller may receive an order by API from a marketplace, by EDI from a retailer and by file from a 3PL. ECOM prepares each for the same systems.
How it arrives
- APIMarketplace and storefront orders
- EDI850 drop-ship orders, 856, 810, 846
- Flat file3PL and warehouse files
- PortalRetailer vendor portals
- SpreadsheetInventory and price uploads
- PDF or emailCustomer orders by email
ECOM
- Validate every file or message
- Map to each partner's rules
- Deliver, acknowledge and monitor
Where it goes
- ERP orders
- 3PL ship requests
- Tracking updates
- Invoices out
Challenges
Integration challenges in ecommerce
Overselling risk
Inventory spread across channels must stay accurate to avoid cancellations.
Manual order handling
Downloading and uploading orders does not scale with volume.
Mixed EDI and API partners
Marketplaces use APIs while retailers often require EDI.
How we help
How ECOM supports ecommerce companies
-
Marketplace integration
Connect marketplaces through the interfaces each one publishes, scoped during discovery.
-
Retail drop-ship EDI
Exchange drop-ship orders, inventory and confirmations with retailers.
-
Channel unification
Normalize orders and inventory across channels with UniChannel.
-
3PL connectivity
Send orders to 3PLs and receive confirmations.
-
Exception visibility
Monitor orders and inventory feeds in PRISM-SCV.
Systems integration
The systems an online seller connects
Online selling touches more systems than a wholesale account, and each uses a different way of exchanging data.
From
- Marketplace orders
- Drop-ship orders
- Inventory feeds
- 3PL confirmations
ECOM · eCommerce exchange
- Validate each order
- Map per channel
- Secure delivery
To
- ERP orders
- 3PL ship requests
- Tracking updates
- Invoices out
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| System | What flows | What to plan for |
|---|---|---|
| Storefront and marketplaces | Orders in; listings, inventory, tracking and returns out. | Marketplaces publish their own interfaces and limits. Support for a given one is scoped during discovery. |
| ERP or order management | Orders from every channel, stock levels and invoices. | A single order record per channel prevents the same stock being sold twice. |
| Warehouse or 3PL | Ship requests out; shipped confirmations, tracking and returns back. | Confirmation timing drives how fast tracking can be sent to a channel. |
| Retailer drop-ship programs | EDI orders, acknowledgments, shipment notices and invoices. | Programs differ by retailer, so each is mapped and tested on its own. |
eCommerce and retail
Online channels here, retailer supplier programs on the retail page
-
Storefront and marketplace orders
Orders, listings, inventory and tracking with your own storefront and the marketplaces you sell on, covered on this page.
-
Retail supplier compliance
Selling to retailers' stores and warehouses under their vendor guides, with ship notices, labels and chargebacks.
Retail supplier compliance in detail -
Marketplace guides
Integration guides for marketplaces such as Amazon, Walmart Marketplace and Wayfair.
Marketplace guides in detail
Channel rules
The same order, three different sets of rules
A marketplace, a retailer drop-ship program and your own storefront each treat the same sale differently. The data work is in keeping them consistent.
-
Marketplaces
Interfaces and limits set by the marketplace. Updates are throttled, and late shipment or cancellation rates affect the seller.
Marketplaces in detail -
Retailer drop-ship
EDI documents under the retailer’s drop-ship guide, with acknowledgment and tracking deadlines.
Retailer drop-ship in detail -
Your own storefront
The storefront platform’s order and inventory interfaces, connected to your ERP.
Your own storefront in detail -
Retail supplier programs
Selling to retailers’ stores and warehouses is a separate set of rules, covered on the retail page.
Retail supplier programs in detail
Inventory and returns
Where online sellers lose money in the data
Two issues recur: stock counts that do not reflect reality, and returns that are handled outside the system.
-
Oversell
The same unit is promised to two channels. A shared available-to-sell figure and a sensible buffer prevent it.
-
Late tracking
A marketplace or retailer cannot tell the buyer where the order is, which drives support contacts and defects.
-
Returns
Return authorizations, receipts and refunds are matched back to the original order across channels.
-
Mixed formats
One partner sends API calls, another EDI and another a spreadsheet. Normalizing them early keeps the back office simple.
Documents and standards
Common transactions
Common X12 documents in retailer drop-ship and fulfillment programs. Marketplaces mostly use APIs instead.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Code | Document | What it does |
|---|---|---|
| 850 | Purchase Orders | The retailer sends a drop-ship order for its customer. |
| 855 | Order AcknowledgmentsX12 name: Purchase Order Acknowledgment | Accepts, changes or rejects the order. |
| 856 | Ship Notices (ASN)X12 name: Advance Ship Notice | Returns the carrier and tracking number. |
| 810 | Invoices | Bills the retailer for the order. |
| 846 | Inventory ReportsX12 name: Inventory Inquiry/Advice | Shares available quantity by item. |
| 945 | Warehouse Shipping Advice | A warehouse or 3PL confirms what shipped. |
Scenarios
Typical integration scenarios
Digital-native brands
Add marketplaces and retail drop-ship programs to a direct store.
Retailers selling online
Integrate marketplace sales and vendor drop-ship.
Trading partners
eCommerce partners we connect with
Examples of ecommerce platforms, marketplaces and retailers trading partners ECOM can connect your business with.
Logos are trademarks of their respective owners. Their display does not imply endorsement of ECOM Specialist.
Frequently asked questions
Can I connect Amazon and retail EDI customers on one platform?
Yes. PRISM supports marketplace APIs and retail EDI, so both channels can share inventory and fulfillment processes.
How often can inventory be updated across channels?
Update frequency depends on channel rules and API limits. ECOM designs schedules that balance accuracy and limits.
Do you integrate with 3PLs?
Yes. ECOM connects sellers to 3PL warehouses using EDI, APIs or files.
Is a marketplace integration the same as retail EDI?
No. Marketplaces mostly publish APIs and set their own limits, while retailer drop-ship programs usually use X12 EDI. The same seller often needs both, and they share inventory and order data behind the scenes.
What causes cancelled marketplace and drop-ship orders?
Mostly inventory that is out of date by the time the order arrives, or an acknowledgment that does not reach the retailer in time. A shared inventory view and faster order validation address both.
Who sends the tracking number in a drop-ship program?
The seller, usually as a ship notice or tracking update on the retailer’s schedule. If a 3PL ships the order, its shipped confirmation is the source for that data.
Can a small seller start with only one channel?
Yes. Starting with one marketplace or one retailer and designing the order and inventory flow so more can be added is a common way to begin.
How to get started
Tell us who you trade with and what you run
- Send the basics. Your trading partners, the documents they require, your ERP or other systems, and any deadline.
- We review the requirements. An ECOM specialist looks at the partner programs, document formats and connections involved.
- You decide how to proceed. We outline the options, including managed services or software, for you to compare.
Helpful to share, but not required
You do not need an implementation guide or a finished requirements list to contact us. If you have these, they speed things up:
- The channels you sell on and any retailer drop-ship programs you are in or joining.
- Your ERP, storefront platform and fulfillment partners.
- How inventory is counted and shared today.
- The problem you most want gone, such as overselling or manual orders.
See how ECOM works with customers: case studies ERP integrations compare delivery options (software, managed or team-based)
Talk to an EDI/API expert
Tell us about your partners, systems and goals. We will show you how PRISM and our team can help.















