Mercado Libre Marketplace Connector

The problem

Selling on Mercado Libre while running NetSuite usually means someone opens the seller back office every morning, exports orders to a spreadsheet, and keys them into NetSuite as Sales Orders. By the afternoon the stock figures in NetSuite and the published quantities on the marketplace no longer agree, oversells start, and the finance team is left reconciling a single monthly payout against hundreds of individual orders, commissions, shipping charges and refunds that were never recorded as separate transactions.

The connectors that do exist were designed for North American marketplaces first. They assume one selling account, one currency, one tax model and a shipping flow that Mercado Envios does not follow. Fulfilled-by-marketplace inventory sitting in a Mercado Libre warehouse has no home in the NetSuite item location model, and the settlement report never maps cleanly onto a Deposit.

What ECOSIRE builds

This is a build-to-order engagement. We build a Mercado Libre connector as a native NetSuite customization inside your account — not a hosted middleware product you rent. Everything runs on your SuiteCloud licence, inside your governance limits, against your record model.

Order ingestion

A Scheduled script polls the Mercado Libre orders API on the interval you choose, and a Map/Reduce script processes each page so a large backlog never exceeds script governance. Each marketplace order becomes a NetSuite Sales Order against the customer record we resolve or create from the buyer nickname and document identifier. Buyer detail lands on a custom record so repeat buyers do not spawn duplicate Customers. Marketplace order ID, pack ID, listing ID and shipping ID are stored in custom body and line fields so every NetSuite transaction is traceable back to the marketplace.

Listings, items and inventory

We map your NetSuite Inventory Items, Assembly Items, Kit/Package Items and matrix parents to marketplace listings using a custom record that holds the listing ID, variation ID and the location or location group whose availability feeds it. A User Event script on Item Fulfillment, Item Receipt and Inventory Adjustment marks affected items dirty; a Map/Reduce pushes the recalculated available quantity to the marketplace. A saved search drives the available-to-sell figure, so you control whether committed, on-order or a reserved buffer is deducted — the rule is yours, not ours.

Mercado Envios and fulfilment

For seller-fulfilled orders we retrieve the shipping label and tracking number and write them back onto the Item Fulfillment, then confirm dispatch to the marketplace. For fulfilled-by-marketplace orders we treat the marketplace warehouse as its own NetSuite Location, so stock transfers, receipts and consumption are visible in your inventory valuation instead of vanishing. Cancellations and returns come back as Return Authorizations and Credit Memos rather than manual journals.

Settlements and reconciliation

The payout file is parsed into its component lines — order payments, commissions, shipping charges, financing costs, refunds and adjustments — and posted to the accounts and departments you nominate. The result is a NetSuite deposit that balances to the payout amount, with each fee on its own line, so month-end is a match rather than an investigation.

OneWorld, currency and tax

If you run OneWorld, each selling account is bound to a subsidiary, so Brazilian, Mexican, Argentine and Colombian operations post to the right books with the right base currency. We set the transaction currency and exchange rate on inbound orders, apply your tax codes or tax groups by nexus, and populate the custom segments your reporting relies on. Where local fiscal documents are produced by a separate system, we write the document number and status back onto the NetSuite transaction so the two stay linked.

Integration surface

All marketplace calls run through the SuiteScript N/https module with OAuth token handling in a secure custom record and NetSuite's secrets support, so no credential is stored in plain text. Where you need to push events from outside NetSuite, we expose a RESTlet with a dedicated integration role holding only the permissions it needs. SuiteFlow handles the approval and exception paths your team wants to control by hand, and a custom record captures every request, response and error for support.

Who this is for

Brands and distributors selling across one or more Mercado Libre sites who have outgrown manual entry; operations teams tired of overselling; and finance teams who need the payout to reconcile without a spreadsheet. It suits companies running NetSuite OneWorld with Latin American subsidiaries as well as single-subsidiary sellers exporting into the region.

How delivery works

1. Scoping call. We walk your NetSuite account, your marketplace accounts, your item and location model, and the exact fee and tax treatment you need. We agree the availability rule, the customer strategy and the settlement mapping. 2. Fixed quote. You receive a written scope and a fixed price before any code is written. Nothing starts until you approve it. 3. Build. We develop in a Sandbox or Release Preview account as an SDF project under source control, typically two to four weeks depending on the number of sites and the fee mapping. 4. Install in test. The bundle is installed in your Sandbox and tested against real listings and real order data with you present. Mapping, governance and error handling are tuned there. 5. Production. Once you sign off, the same SDF project is deployed to production, script deployments are enabled on the schedule agreed, and we monitor the first live cycles. 6. Support. A post-go-live support window is included, covering defects and marketplace API changes encountered during that period.

You own the resulting SDF project and source. Nothing is obfuscated, nothing phones home, and there is no per-order fee.