eCommerce Platforms, Marketplaces and Retailers integration

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.

At a glance

1stDibs integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific 1stDibs program or a customer relationship.

Illustration of a laptop with a shopping cart and stacked parcels, representing the ecommerce platforms, marketplaces and retailers industry that 1stDibs operates in.
Industry. eCommerce Platforms, Marketplaces and Retailers: where 1stDibs operates.
Workflow diagram: your ERP and warehouse systems exchange documents with 1stDibs through ECOM. You send 855, 856, 810, 846; you receive 850; 997 acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor 1stDibs 855 856 810 846 855 856 810 846 850 850 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about 1stDibs

Tell us which documents you exchange with 1stDibs, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with 1stDibs.

  • Review of 1stDibs' requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
1stDibs

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How 1stDibs integration fits your systems

Your systemsERP, order management and accounting
ECOMMapping, validation, connectivity and monitoringAS2 or SFTP · EDI network (VAN) · API or web portal
1stDibsIts program, documents and requirements
  1. ConfirmConfirm your 1stDibs program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding 1stDibs integration

Who this is for: Brands, sellers, wholesalers and suppliers that sell through 1stDibs, and the teams that manage listings, orders and fulfillment.

Scope: This guide describes typical practice for this kind of trading relationship; 1stDibs's own program details are confirmed during onboarding.

1stDibs is an online marketplace for antiques, vintage design and luxury goods. ECOM's directory lists it under luxury marketplace. Sellers and suppliers on marketplaces typically deal with order feeds, inventory and price feeds, shipment confirmations and settlement reports, through APIs, file feeds or EDI depending on the program.

What matters most with a marketplace is that one source of inventory and order truth reaches every channel. 1stDibs' own EDI or API specification is not part of this guide and no 1stDibs document was read: treat what follows as typical practice for a marketplace, and confirm the documents, X12 version, delivery method and testing steps with 1stDibs.

ECOM maps the documents to your order management, ERP and warehouse systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where 1stDibs integration gets complicated

Typical requirements—confirm with your trading partner.

Listings and inventory accuracy

Marketplaces rely on current stock and price feeds. Stale data leads to cancellations and poor seller metrics.

How ECOM helps: ECOM maps inventory and stock data (846) between your systems and 1stDibs, so one position reaches every system, with differences listed for review.

What you gain: Stock positions stay consistent, and mismatches are visible early.

Orders from many channels

A seller usually receives orders from several channels. They all have to reach the same warehouse and ERP without double counting.

How ECOM helps: ECOM maps the documents to your systems and monitors every exchange, as software, as a managed service or both, so your team handles exceptions instead of re-keying.

What you gain: Less manual work and fewer surprises after go-live.

High-value goods

High-value goods raise the importance of exact quantities, serial or item identification and insured, tracked shipping. Documents have to reconcile line by line.

How ECOM helps: ECOM maps invoice, payment and remittance data to your ERP or finance system and matches each document to the order or shipment it relates to, with differences listed for review.

What you gain: Faster reconciliation and cash application, and a clear trail for audit.

Settlement and returns

Fees, refunds and returns reconcile against payouts. Clear settlement data reduces manual accounting.

How ECOM helps: ECOM monitors each document and acknowledgment, flags rejected, late or mismatched ones and routes each exception to a named owner with the document history attached.

What you gain: Problems are corrected before they turn into deductions, write-offs or delayed payment.

Workflows

Typical 1stDibs business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not 1stDibs' published process.

Marketplace order to cash

  1. 1Receive order
  2. 2Confirm and allocate stock
  3. 3Ship the order
  4. 4Send shipment confirmation
  5. 5Reconcile payment

Inventory and price feed

  1. 1Prepare stock and price data
  2. 2Send 846 or feed update
  3. 3Receive acknowledgment
  4. 4Fix rejected items

Documents and APIs

1stDibs documents by program

General guidance. We could not verify 1stDibs' EDI requirements from a published source, so these are documents commonly exchanged in this industry, not 1stDibs' confirmed requirements. Confirm the list, versions and programs with 1stDibs.

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order From 1stDibs Not stated General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment To 1stDibs Not stated General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest To 1stDibs Not stated General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice To 1stDibs Not stated General guidance Typically bills for what shipped, matched against the order.
846 Inventory Inquiry/Advice To 1stDibs Not stated General guidance Typically shares inventory positions or availability between the two sides.
832 Price/Sales Catalog To 1stDibs Not stated General guidance Typically shares item, price and catalog updates.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • AS2 or SFTP

    Many companies exchange EDI files directly over AS2 or SFTP.

    General guidance

  • EDI network (VAN)

    Many suppliers connect through a value-added network that delivers files to and from the partner and keeps an audit trail.

    General guidance

  • API or web portal

    Some programs use REST or SOAP APIs, a supplier portal or a cloud EDI service for some documents. A login is usually required for portals.

    General guidance

Challenges

Common integration challenges

  • Inventory accuracy

    Out-of-date inventory leads to oversells and cancellations.

  • Order volume and speed

    Marketplace order windows are short and delays affect seller ratings.

  • Feeds that change

    APIs and file formats change, and each marketplace has its own rules.

  • Settlement reconciliation

    Payouts need to match orders, fees and returns.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by 1stDibs. ECOM works from them during mapping and testing.

Automation options for 1stDibs suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet 1stDibs' labeling and ship notice requirements, and see what needs action. 1stDibs sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect 1stDibs documents to your ERP

ECOM connects the documents you exchange with 1stDibs to your ERP and warehouse systems, so orders post without re-keying and ship notices and invoices come from the data you already hold.

Solution

eCommerce Integration

Connect storefronts, marketplaces, your ERP and your warehouse in one flow.

Solution

Drop-Ship Automation

Automate drop-ship orders, tracking and invoices end to end.

Service

Fully Managed EDI

Have ECOM run your EDI connections, monitoring and partner changes.

General EDI flow

How EDI with 1stDibs typically works

The documents, their order and the timing are 1stDibs' to set; this is the general sequence most programs of this kind follow.

  1. 850 Purchase Order

    From 1stDibs to you

    Typically carries the order: items, quantities, prices, ship-to locations and requested dates.

  2. 855 Purchase Order Acknowledgment

    From you to 1stDibs

    Typically confirms an order, or reports changes to quantities, prices or dates.

  3. 856 Ship Notice/Manifest

    From you to 1stDibs

    Typically tells the receiver what is on each shipment, often with carton or pallet label details.

  4. 810 Invoice

    From you to 1stDibs

    Typically bills for what shipped, matched against the order.

  5. 846 Inventory Inquiry/Advice

    From you to 1stDibs

    Typically shares inventory positions or availability between the two sides.

  6. 832 Price/Sales Catalog

    From you to 1stDibs

    Typically shares item, price and catalog updates.

  7. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

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.

Next step

Get help with your 1stDibs program

Each request goes to an ECOM EDI specialist with 1stDibs' name attached, so the reply starts from your program.

  • Review 1stDibs' requirements

    Send us 1stDibs' guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect 1stDibs to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each 1stDibs document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match 1stDibs' rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

1stDibs integration FAQs

Does 1stDibs use EDI?

Marketplaces and online retailers use a mix of APIs, file feeds and, in some programs, EDI. This page does not describe 1stDibs' program.

Can ECOM connect marketplace orders to my ERP?

ECOM connects orders, inventory, shipment and invoice data between marketplaces, APIs, EDI and your ERP or warehouse system. This page does not indicate a relationship with 1stDibs.

Which EDI documents are typical for a marketplace?

Typical documents are 850, 855, 856, 810, 846, 832, 997. That is general practice, not 1stDibs' published list.

How does onboarding with 1stDibs usually work?

Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on 1stDibs' requirements, test cycles and your ERP.

Does this guide mean 1stDibs endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by 1stDibs.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. 1stDibs sets its own requirements and can change them at any time; your 1stDibs implementation guide, supplier portal or account contact is the authoritative source for your program.

  • ASC X12: transaction set reference (standards body) Standards reference
  • 1stDibs: company description Background, not checked against a company source The one-sentence description of 1stDibs comes from general public knowledge and was not checked against 1stDibs' own website for this page.
  • 1stDibs: no company document read Background, not checked against a company source No 1stDibs supplier, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request 1stDibs integration assistance

Tell us about your 1stDibs program, documents and ERP. We will outline the connection, mapping and testing plan.