Trading partner network

eCommerce Platforms, Marketplaces and Retailers EDI and API integration

Selling through platforms, marketplaces and online retailers means exchanging orders, inventory, shipments and invoices over APIs and EDI. ECOM connects your business with ecommerce platforms, marketplaces and online retailers through EDI, APIs, managed file transfer and portal automation, integrated with your ERP.

Trading partner network

eCommerce platforms, marketplaces and online retailers we connect with

Through its network, ECOM can connect your business with 3.1M+ trading partners. The 129 ecommerce platforms, marketplaces and online retailers below are highlights, by name and business segment. Companies with an integration guide link to it, and each guide says whether it rests on the company’s own documents or on typical industry practice.

Commerce platforms

Software that merchants use to build and run an online store. Connected mainly through APIs and apps.

Online retailers and brands

Retailers and direct-to-consumer brands that sell online and send purchase orders, receive shipment notices and pay invoices.

Fulfillment services

Providers that print, pack or ship on behalf of sellers.

Historical guides (closed, acquired or renamed)

Guides kept for teams that still hold documents, claims or invoices. Each page says what happened to the company; confirm before investing in a new integration.

How the exchange works

How ecommerce platforms, marketplaces and online retailers exchange business documents

Marketplaces and storefront platforms mostly exchange orders, inventory and tracking through their own published APIs, while online retailers that use drop-ship suppliers often use EDI. Timing matters most: if stock levels or shipment status fall behind, the channel oversells, cancels orders or penalizes the seller.

Common documents with ecommerce platforms, marketplaces and online retailers
DocumentWhat it does in this relationship
APIs Listings, orders, inventory and fulfilment updates through the platform’s own REST API.
EDI 850Purchase Order A drop-ship order from an online retailer, with the end customer’s ship-to address.
EDI 856Advance Ship Notice Shipment confirmation with carrier and tracking number, so the customer can follow the delivery.
EDI 846Inventory Inquiry/Advice Inventory feed that keeps the online offer in line with what you can actually ship.
EDI 810Invoice The invoice to the online retailer for each drop-shipped order.

What onboarding a new ecommerce platforms, marketplaces and retailers partner usually involves

  1. Set up API access from your seller or vendor account and agree the SKU and listing mapping.
  2. Decide how often inventory and prices are sent, and how cancellations and returns flow back.
  3. Test orders end to end, including split shipments and tracking updates, before opening the channel.

Integration guides

eCommerce Platforms, Marketplaces and Retailers integration guides

Detailed guides covering documents, workflows, connectivity and ERP options for specific companies. A selection is shown here; search all 122 ecommerce platforms, marketplaces and online retailers guides in the directory above.

1-800-Flowers.com EDI integration

How EDI and API integration with 1-800-Flowers.com typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with 1-800-Flowers.com.

Read the guide

1A Auto EDI integration

How EDI and API integration with 1A Auto typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with 1A Auto.

Read the guide

1stDibs EDI integration

How EDI and API integration with 1stDibs typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with 1stDibs.

Read the guide

Adorama EDI integration

How EDI and API integration with Adorama typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Adorama.

Read the guide

Amazon EDI integration

A guide to connecting with Amazon as a first-party vendor through EDI or vendor APIs, and as a marketplace seller through the Selling Partner API.

Read the guide

AutoTrader EDI integration

How EDI and API integration with AutoTrader typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with AutoTrader.

Read the guide

Back Market EDI integration

How EDI and API integration with Back Market typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Back Market.

Read the guide

BARK EDI integration

How EDI and API integration with BARK typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with BARK.

Read the guide

BigCommerce EDI integration

How EDI and API integration with BigCommerce typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with BigCommerce.

Read the guide

Boll & Branch EDI integration

How EDI and API integration with Boll & Branch typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Boll & Branch.

Read the guide

Bombas EDI integration

How EDI and API integration with Bombas typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Bombas.

Read the guide

Brooklinen EDI integration

How EDI and API integration with Brooklinen typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Brooklinen.

Read the guide

General EDI flow

How EDI with your trading partner typically works

Many trading partners do not publish their EDI or API specifications. This is the general sequence most programs of this kind follow.

  1. 850 Purchase order

    From your trading partner

    The buyer sends the order: items, quantities, prices, ship-to and requested dates.

  2. 855 Order acknowledgment

    From you to your trading partner

    You confirm, change or reject the order, where the partner asks for it.

  3. 856 Advance ship notice

    From you to your trading partner

    You tell the buyer what is on the shipment, with the carton and label details the buyer needs to receive it.

  4. 810 Invoice

    From you to your trading partner

    You bill for what shipped, in the format the buyer's payables system expects.

  5. 997 Functional acknowledgment

    Both directions

    Each side confirms that every file it received was readable. A rejected file is corrected and resent.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Connecting with an ecommerce platforms, marketplaces and retailers partner not listed here?

ECOM connects businesses with partners of every size using their published EDI, API or file requirements.