MARKETPLACE EDI CONNECTION

Connect to MercadoLibre EDI with EDIXT

MercadoLibre Electronic Data Interchange (EDI) marketplace profile built around purchase order, advance ship notice, invoice, and inventory advice, transport design, and downstream handoff into Commerce platforms, ERP, and Warehouse management.

This page uses the current EDIXT rollout profile for MercadoLibre, covering X12 850, 856, 810, 846 for rollout planning, validation, and downstream handoff before partner-specific exceptions are added.

Marketplace Partner layer
US Coverage
4 flows Message scope
Marketplace the United States X12 850, 856, 810, 846
Partner overview

How to use this partner profile

MercadoLibre is currently mapped as a marketplace partner in the United States. The current EDIXT Electronic Data Interchange (EDI) profile for this route is built around purchase order, advance ship notice, invoice, and inventory advice, because those messages usually define the first operational checkpoints teams need to stabilise.

Use this profile to plan transport over API, SFTP, and AS2, validation checkpoints, and downstream handoff into Commerce platforms, ERP, Warehouse management, and Finance while partner-specific identifiers, exceptions, and timing rules are being confirmed.

EDIXT is currently using the marketplace rollout profile for MercadoLibre, based on purchase order, advance ship notice, invoice, and inventory advice. Confirm the final document mix, identifiers, transport rules, and timing windows during onboarding.
EDI capabilities

Transactions and message scope

Below is the current Electronic Data Interchange (EDI) document profile used to plan connectivity for MercadoLibre, based on the document mix teams usually need first in this marketplace workflow.

850

Purchase order

Core order instructions that trigger validation, routing, and downstream fulfilment.

856

Advance ship notice

Shipment structure and carton detail passed into warehouse, carrier, and customer systems.

810

Invoice

Structured billing data passed to finance and reconciliation workflows.

846

Inventory advice

Inventory position or availability signals synced into planning and commerce systems.

Onboarding flow

Typical rollout sequence for MercadoLibre

A typical Electronic Data Interchange (EDI) rollout starts by teams agreeing how to define marketplace order scope and ends with the controls needed to monitor fulfilment and exceptions.

1

Define marketplace order scope

Agree which order, inventory, shipment, settlement, and return messages need to be supported.

2

Normalize channel data

Map marketplace-specific fields into a consistent order and finance model.

3

Route validated events downstream

Send clean marketplace data into ERP, warehouse, and reporting systems without channel-specific rework.

4

Monitor fulfilment and exceptions

Keep stock issues, shipment misses, and settlement anomalies visible across the operation.

Validation focus

Common issues teams need to catch early

The main Electronic Data Interchange (EDI) risk areas for MercadoLibre usually show up around inventory feed drift and settlement disconnected from fulfilment.

FAQ

Questions teams often ask before they connect MercadoLibre

These answers cover the document mix, transport methods, validation checks, and downstream handoff patterns currently used to plan connectivity for MercadoLibre.

What transaction scope is usually relevant for MercadoLibre?

MercadoLibre is currently profiled around purchase order, advance ship notice, and invoice, which gives teams the practical document scope to map, validate, acknowledge, and route into live operations.

Is this based on exact partner coverage or a common rollout pattern?

This profile is based on the current EDIXT rollout pattern for MercadoLibre, using the marketplace message mix and downstream handoff patterns teams most often need first.

Which systems usually need to receive MercadoLibre data?

For this profile, the downstream handoff usually touches Commerce platforms, ERP, Warehouse management, and Finance, so the integration design needs to keep both partner rules and internal system constraints in view.

Next step

Turn this partner profile into a live rollout plan

Use this profile to confirm the document scope, transport rules, validation ownership, and downstream routing needed for MercadoLibre, then move the rollout into mapping, testing, and cutover.

Document scope X12 850, 856, 810, 846
Transport API / SFTP / AS2
Landing systems Commerce platforms / ERP / Warehouse management