Automation · Marketplaces
Publish your WooCommerce catalog on Mercado Libre without risking the account
How an AI agent publishes your store products on Mercado Libre: account census, compliance, category, required attributes and a post-publish audit.
How do I upload my WooCommerce catalog to Mercado Libre without getting listings rejected?
The procedure starts where nobody expects it to: with a read-only census of the Mercado Libre account that classifies every listing by status and by origin. Without that census you work blind, and you risk editing a listing under review (which restarts its moderation) or touching listings you uploaded yourself. Then comes the requirements filter: compliance, category, required attributes. The listing is created paused and only goes live once the post-publish audit confirms it came out clean. The goal is not to publish fast. The goal is not to put the account at risk.
Where it applies: Colombia. The automation is built on Mercado Libre Colombia (MCO): the category dictionary and the ICA check are Colombian.
What starts it
When someone asks for it
You ask the Met for it when you want to publish: in chat, or with the button that runs the task. Publishing on a marketplace is a commercial decision with consequences for the reputation of the account, and it should not happen while nobody is looking.
A manual task: someone on the team runs it with a button, or asks the Met for it in chat.
Who runs it
Igor, Warehouse manager
Igor is the Met seeded for this, and his prompt carries the full playbook with the census as step zero. He is an internal Met: he does not talk to buyers, he works for whoever runs the catalog.
What you need connected
- Mercado Libre E-commerce and marketplaces
- WooCommerce E-commerce and marketplaces
6 steps · 12 tools
The procedure, step by step
Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.
- 1
Census the account before touching anything
The census walks every listing and classifies it by status (active, paused, under review, closed) and by origin: the ones we manage, which carry your SKU, and the outside ones you uploaded yourself. Listings under review are left alone, because editing them restarts moderation, and outside listings are never altered. It is read-only, and it is the step that prevents the most expensive damage.
- 2
Know what can be published today and what cannot
The publishability report classifies the whole publishable catalog of the store against the same filter that would be applied when publishing, and returns the reason product by product. It answers in one pass the question that normally costs an afternoon: which ones can I upload now, and why not the rest.
- 3
Pass the requirements filter
Before any listing is created, the compliance check verifies that the product meets Mercado Libre's requirements. It is not a formality: publishing a prohibited item puts the whole account at risk. In Colombia, veterinary products are additionally checked against the official ICA registry: current means it can be sold, cancelled means it is never published.
- 4
Resolve category and required attributes
Mercado Libre demands a category and the required attributes of that category (brand, model and whichever apply) or it rejects the listing. Prediction suggests the category from the title, the attribute query says which ones are mandatory, and catalog search verifies that the barcode really belongs to that product and not to another one with a similar GTIN.
- 5
Publish paused, not live
The publishing sequence chains everything above and leaves the listing created but paused. Being born paused is deliberate: it gives you a window to review title, photos and price before a buyer can purchase something with a wrong detail on it.
- 6
Audit first, activate second
The post-publish audit reads the real status of each listing on Mercado Libre and catches what the filter cannot anticipate: wrong category, photos pending, listings flagged as prohibited. Only what passes the audit and has stock gets activated, and activation runs through the requirements filter again before turning anything on.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
A connected Mercado Libre seller account
You authorize it from Meteor with the seller account. It is worth checking with the account info query that the authenticated seller is the right one before publishing anything.
-
WooCommerce connected as the source store
With the WooCommerce REST API keys. The source store is where the true price and stock come from; Mercado Libre is a destination, never a source.
-
Your own SKU on every product
The SKU is what marks a listing as managed by us, and what makes it possible to leave the outside ones alone. A catalog with no SKUs forces you to work without that protection.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not touch the listings you uploaded yourself. Without our SKU a listing counts as outside, and it stays out of the whole procedure.
-
It does not edit listings under review. Doing that restarts Mercado Libre's moderation and delays the launch instead of speeding it up.
-
It does not invent required attributes. If one is missing it reports it and stops; completing the product record is still work for whoever knows the product.
-
It does not decide the price. The price comes from the source store; what it does is translate it to the channel with the category commission, not set a commercial strategy.
FAQ
Questions about this automation
Because a Mercado Libre account is almost never empty. Without knowing what is already published, what is under review and what was uploaded by hand, any action can duplicate a listing or restart a moderation in progress. The census is read-only and costs minutes; the mistake it prevents costs weeks.
They are checked against the official ICA registry. If the registration is current they can be sold; if it is cancelled, they are never published under any circumstances. It is a Colombia specific check and it is built into the filter, not left to judgment in the moment.
You can, but the publishability report almost always shows that part of the catalog does not pass the filter. The sensible path is to start with what does pass, and use the reasons in the report as the to-do list for the rest.
That is what the post-publish audit is for: it reads the real status of each listing and catches whatever came out wrong. The compliance check also works to repair a rejected listing, not only to prevent one.
Keep going
Other automations built on the same tools
Marketplaces
Keep price and stock current between your store and Mercado Libre
How do I stop selling something on Mercado Libre that already sold out in my store?
- Starts:
- at a set time
- Steps:
- 5, with 11 real tools
- Needs:
- Mercado Libre · WooCommerce
Customer service and scheduling
Answer "where is my order?" for Mercado Libre sales over WhatsApp
How do I answer the status of a Mercado Libre order without opening the seller panel?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 10 real tools
- Needs:
- Mercado Libre · Meteor CRM
Orders and fulfillment
From a WooCommerce order to an Aveonline shipping label
How do I move orders from my store into Aveonline without retyping them one by one?
- Starts:
- at a set time
- Steps:
- 6, with 13 real tools
- Needs:
- WooCommerce · Aveonline
Collections and receivables
Recover the WooCommerce orders that were left unpaid
How do I recover the orders in my store that were left pending payment?
Sales
- Starts:
- at a set time
- Steps:
- 6, with 12 real tools
- Needs:
- WooCommerce · Mercado Pago · Meteor CRM
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.