A second marketplace, same workbench
Alongside Amazon, the workbench connects to Mercado Libre Global Selling (CBT): the same product data is used to authorise a store, publish items, pause or reactivate them, reprice and update stock. The capability is implemented and enabled as a beta channel.
Reuse your assets across marketplace workflows
The expensive part of running two marketplaces is not writing another title — it is re-entering the title, the images, the cost sheet and the stock figures into yet another tool.
Competitor research, listing copy, main and secondary images, landed-cost modelling — all of it already lives in the same task. The Mercado Libre channel reuses those outputs: another submission, not another data entry pass, and the same cost model behind it.
Running both channels does not tangle the workflow: each channel is authorised separately, configured with its own sites, and reports its own per-SKU results. When an item is rejected, you can see which attribute caused it.
Shared and separate
| Shared | Listing copy, image assets, cost and stock conclusions, task history |
|---|---|
| Separate | Authorisation tokens, site configuration, item model, per-SKU results |
| Never done | Data is not copied between channels automatically; every write needs your confirmation |
Authorise, publish, control — through the official APIs
The capabilities below exist in the implementation layer; the in-app operation panel is provided according to your enablement status, and we assist with configuration otherwise.
Store authorisation (OAuth)
App ID and secret key stay on your machine. You authorise once on Mercado Libre; the workbench receives a scoped, expiring token. The refresh token is single-use, so each renewal is written straight back to local encrypted storage.
Publishing to CBT
Items are submitted through the Global Selling API: category, currency, price, available quantity, SKU, brand, GTIN, model, package dimensions and weight, pictures, description, variations and warranty terms — to the sites you select.
Two item models
Standard sellers use the legacy item API; sellers tagged user_product_seller use the User Products model. With the channel set to auto, the workbench reads the account tags and picks the model for you.
Status, price and stock
Pause, reactivate, delete, reprice and update stock from one place. Deletion follows the platform's semantics — the global item is paused first, then marked deleted site by site, so no half-deleted site item is left behind.
Per-SKU results
Every SKU reports back individually: accepted, rejected, the reason, and whether it can be retried. One rejected row in a batch does not swallow the rest of the run.
Rate limits and retries
Request frequency follows the platform's current limits and account conditions. HTTP 429 responses trigger backoff as instructed, and token errors are handled according to the platform's authorisation rules.
Availability and service boundaries
Status: Mercado Libre listings are in beta, enabled on request, and not yet open to all customers — the same status as Amazon listings. The in-app operation panel is provided according to enablement. This page does not describe beta capability as generally available.
- Publishing, repricing, stock updates and deletion are submitted only after you confirm them; nothing is written to your store silently.
- Only the scopes needed to publish items are requested. Order and buyer personal data (name, phone, address) are not accessed.
- Your credentials are never handled: authorisation happens on Mercado Libre, and only a revocable token is stored locally.
- No managed operations, no store registration on your behalf, no payment collection.
- No promises of impressions, ranking, sales or advertising outcome; compliance findings are advisory and need human review before publishing.
- Sites are not "publish to every Latin American marketplace at once": the selectable sites are those already enabled on your CBT account.
Two channels in parallel, Amazon remains the primary one
The product is designed around Amazon sellers. Mercado Libre is an extension of the same workflow, not a replacement.
| Item | Amazon channel | Mercado Libre channel |
|---|---|---|
| Authorisation | Selling Partner API (LWA) with an expiring access token | OAuth (app ID / secret key + redirect), single-use refresh token renewed automatically |
| Operations | Publish, activate, pause, delete, reprice, update stock, query | Publish, pause, reactivate, delete, reprice, update stock |
| Sites | 11 Amazon marketplaces (AU / US / UK / DE / FR / IT / ES / CA / JP / MX / AE) | Sites already enabled on your CBT account |
| Item model | Amazon product type definitions | Legacy and User Products, detected automatically |
| Status | API layer complete, in beta | API layer complete, in beta, enabled on request |
| Shared assets | Listing copy, image assets, cost and stock conclusions live in one task and are used by both channels | |
Amazon scopes and data use are documented in the Amazon integration page; Mercado Libre authorisation and credential storage are covered in security.
Run it on your own store first
Send us a product and its target Mercado Libre site. We verify authorisation and connectivity first, then enable write operations at your pace.
Request a trial