When the eBay shop logs in separately, everything works fine, but frequent CAPTCHAs, orders being written to the wrong country sites, and already-departed colleagues still being able to change prices only start after integrating Mercado Libre and the ERP. These situations are common, and the reason is usually not insufficient tool functionality. What is truly missing is four layers of correspondence: account entity, Seller Hub role, login environment, and tool write scope. Misalignment in any layer will manifest in these forms.
It is recommended to fix the decision order: first determine the expansion form, then solidify the eBay baseline, then separately verify Mercado Libre localization items, integrate tools in three phases (read-only, controlled writing, batch operations), and finally discuss whether to split into multiple accounts. Skipping any step will mix the problems, making it impossible to distinguish whether they are caused by platform rules, permission settings, or tool configuration.
First Determine the Expansion Form: Adding Sites Under the Same Entity or Opening New Accounts Under a New Entity
This step determines how all subsequent permissions are sliced; first distinguish between the three forms.
- Opening Mercado Libre country sites under the same entityShared payment and customer service teams, with permissions divided by site, is the path most eBay sellers try first.
- Establishing a new entity to open a new account for tax purposes, local payment collection, or brand isolation. Registration details, payment accounts, and contact information must all be independent and cannot reuse the same information as existing accounts.
- Managed customer stores permissions are derived from the client's authorization; the tool must allow revocation at any time, and customer stores must not be placed under the same administrator identity as your own account.
Whether multiple accounts are permissible depends on platform rules, not on "convenience of management." A useful reference is Amazon's statement on multiple seller accounts: generally, one account per regional marketplace; multiple accounts are only allowed with a reasonable business need, and policy issues with one account can affect related accounts (Amazon's multi-seller account health advisory). For Mercado Libre, registration details and review criteria must be verified in the official seller hub before expansion; do not treat "multiple accounts" as the default approach.
Deconstruct the seller hub, store tools, and multi-account setup using a four-layer mapping
Each of the four layers has a distinct meaning; conflating them leads to situations where tools appear capable, but operations remain chaotic on the ground.
- Account entity determines who legally owns the store and who handles payments, dictating whether it can be opened and funds can be collected.
- Seller hub role determines who in the backend can change prices, process refunds, or view data only.
- Login Environment: Who logs in from which device, network egress, and browser identity, and who safeguards the credentials.
- Tool Write Scope: Which fields on which stores the ERP can modify, and whether they are read-only or writable.
When all four layers align one-to-one, scaling is simply a matter of replicating the process; if any layer is misaligned, issues will surface in the form of CAPTCHAs, orders written to the wrong site, inventory altered on the wrong store, or lingering permissions after an employee leaves. It is worth noting that the triggers for CAPTCHAs are not unique; changes in login location, device swaps, or tool invocation frequency may all be related. Please refer to account notifications and official policies for specifics, as no single signal can be asserted to definitely cause association or bans. The troubleshooting sequence can be found inPermission and store management troubleshooting for multi-account operations on eBay, Walmart, and Etsy.

Three Baselines to Fix in eBay Seller Center
Before onboarding to Mercado Libre, first document the established processes on the eBay side as handover rules; otherwise, the new platform will duplicate the poorly defined workflows twice.
- Account Security and Recovery Paths: Identify who holds the main email, secondary verification method, and recovery contact. Document this on a handover card to ensure that login access is not limited to a single individual.
- Order, message, and post-sales permissions: Split “can reply,” “can change prices,” and “can issue refunds” into distinct roles. Do not place return and refund permissions in the same account used for routine customer service.
- Tool Authorization Checklist: In the eBay Seller Center, verify authorized third-party applications, revoke any that are no longer in use, and record what each app can read and write.
Once these three items are standardized, the eBay side will have a comparable reference version. If issues arise during Mercado Libre integration, you can quickly determine whether the cause is platform differences or that the process was never defined.
Localization items to check separately in the Mercado Libre seller center
Latin American sites cannot simply apply eBay operational rules. The following items must be confirmed individually in the seller center, rather than assumed based on experience.
- Correspondence between country sites and warehouses: The same SKU may correspond to different warehouses and prices on the Mexico and Brazil sites.
- Customer service language and online hours: Responsibilities for replying in Spanish and Portuguese, along with shift schedules, must be arranged separately from eBay English customer service.
- Fulfillment method and delivery time commitments: Whether shipping from your own warehouse or a local warehouse, and how delivery time promises should be set.
- Tax and invoice requirements: Determined by the entity's location and site rules; confirm with official sources or local service providers.
- After-sales disputes and reputation metrics: The handling paths and evaluation criteria differ from eBay's; they cannot be directly copied.
The direct requirements for tools are: the ability to distinguish products, prices, inventory, and warehouses by site. If site-level distinction is not possible, “orders written to the wrong site” and “inventory modified for the wrong store” are not operational errors but inevitable configuration outcomes. For troubleshooting approaches due to platform structural differences, refer to the extended reading.Multi-platform seller account and store management tools troubleshooting guide, including Mercado Libre..
Store management tools are integrated in the order of "read-only sync → controlled write → batch operations".
An ERP's support for a specific platform does not mean all permissions can be opened at once. A sensible integration sequence is to gradually expand the write scope, ensuring you can pause at each step.
- Read-only syncFirst, fetch orders, inventory, and product status, then verify them item by item against the Seller Center, without writing any fields. The goal at this stage is to confirm whether the mappings are correct, not to improve efficiency.
- Controlled writeSelect a small number of SKUs, limit it to a single site, open inventory writing first, then open price writing, while retaining manual review. Price errors directly lead to loss orders, so they are placed after inventory.
- Batch OperationsPricing updates, customer service templates, and bulk listing operations require thresholds, stop conditions, and designated rollback owners, with logs traceable to specific individuals, timestamps, and data fields.
Do not grant batch access to systems that lack audit logging. Compare the capability differences between eBay and Mercado Libre tools witheBay Seller Center and multi-account tool selection principlesfor context.

Multi-Account Coordination: When to Separate and When to Isolate
Multi-account setups are not a default solution. First, determine if they are truly necessary; different entities, country-specific sites, or distinct team responsibilities justify splitting accounts; splitting accounts within the same team, entity, and site typically only increases management overhead.
When separation is necessary, the following items must be strictly isolated rather than merely observed:
- Login environments: Use dedicated devices and network egress points, with credentials secured by assigned owners; do not share primary account passwords.
- Payment and tax records: Keep records independent for each entity; do not mix them across entities.
- Customer service identity and scripts: Use the corresponding identity for each site and brand to avoid sending buyers responses from the wrong site.
- Tool authorization: Each account is authorized individually; account-level full permissions are granted only to a limited number of managers.
- Offboarding and role transfer: Deactivate seller center roles and tool authorizations on the same day, and check for any unexpired API tokens.
Do not use multi-browser instances, proxies, or shared credentials to bypass platform reviews. Such practices do not solve permission issues; the risk falls on the account, and they also violate the rules of most platforms.
Use a single acceptance form to decide whether to expand to more platforms.
Whether a single Mercado Libre site is stable is judged by checkable criteria, not by the feeling that it is 'roughly fine'.
| Checklist item | Pass criteria (based on team-defined thresholds) | When not passed |
|---|---|---|
| Account health | No unhandled policy notifications; performance metrics are within the site's required range | Pause onboarding new sites and address notifications first |
| Order Errors | A consecutive period with no orders for incorrect sites or incorrect warehouses | Revoke bulk write permissions and switch to manual review |
| Inventory Accuracy | Tool inventory matches seller center sampling results | Revert to read-only synchronization |
| Customer Service Response | Clear responsibility and time slots for each site | Do not open bulk sending of customer service templates |
| Permission Revocation | Complete deactivation on the day of resignation or transfer | Pause the creation of new accounts |
| Tool Log | Every write is traceable to the person, time, and field | Bulk operations are not supported |
Once this table passes completely, we can then consider connecting to more platforms such as Shopee, Lazada, and Temu; if any item fails, continue expanding sites, as the same issues will simply repeat on more shops. For the overall approach to site expansion sequence and tool selection, refer toMulti-platform seller tool selection and multi-account operational strategy.
FAQ
I already have an eBay shop. Do I need to set up a separate company entity for Mercado Libre?
First, check the requirements for payment, taxation, and site audits regarding the entity, and then decide whether to set up a new one. It is not a valid reason to create a separate entity just to 'facilitate opening more shops.' The specific conditions should be based on the Mercado Libre official seller center. In most cases, you can start by using country-specific sites under the same entity.
What should I pay attention to when logging into the seller centers of both eBay and Mercado Libre on the same computer?
Use fixed devices and network egresses, do not share login credentials, and use separate environments for shops with different entities. If you see a CAPTCHA, first check account notifications and login records instead of immediately attributing it to a specific signal.
The ERP already supports eBay. When integrating Mercado Libre, should we sync inventory first or orders first?
First, pull orders and inventory in read-only mode for reconciliation, with no writes to either. After moving to the write stage, open up inventory first, then prices, because an incorrect price write would directly result in losing orders.
Should Mercado Libre multi-country sites authorize store management tools by account or by site?
Site-level authorization is more granular, so the tools should support site-level read/write. Account-level full permissions should be reserved for a small number of owners, with operational roles granted site-level permissions to facilitate revocation and accountability.

