The agent-first command center for ecommercewithout fake autonomy.
Zeler.ai is building an operational layer for ecommerce modules, agents, and integrations with one clear rule: every capability shows whether it is available, in construction, or vision.
✓ Transparency first: agents in design, modules in construction, and visible scope before autonomy claims.
Agent-first operating system
Zeler Command Center
ZelerAI's primary layer: an agent-first operating system for signals, status, and decisions. ERP-like modules are the secondary layer that structures inventory, catalog, reporting, and support.
Built for operators living across marketplaces, stores, and chats
The problem
Operations grow faster than clarity.
Ecommerce teams do not need another magic promise. They need to know what to review, what to automate gradually, and what still requires human judgment.
Scattered signals
Sales, catalog, support, stock, and reputation are split across dashboards and spreadsheets.
Opaque automation
Tools promise to operate alone, but do not explain limits, permissions, or review points.
Reactive decisions
Teams detect fires late because there is no prioritized view of operational pain.
Operating model
Clarity first. Assistance second. Responsible automation after that.
Zeler.ai does not jump straight into autonomous agents. It builds a foundation where every step has status, limits, and explicit review.
Unify signals
Map modules and integrations to understand what is happening before taking action.
Assist with context
Design agents that suggest, explain, and prepare decisions without hiding human review.
Automate by scope
Activate flows gradually when permissions, data, and limits are defined.
Command Center
A view for prioritizing operations, not another inflated dashboard.
The Command Center organizes signals and states so operators know what to review first. Today it is communicated as product direction in construction, not a complete production feature.
Zeler Command Center
In constructionZelerAI's primary layer: an agent-first operating system for signals, status, and decisions. ERP-like modules are the secondary layer that structures inventory, catalog, reporting, and support.
View modules →Modules
Operational blocks with visible limits
Each module explains the problem it addresses, its state, and what it does not promise yet.
ZelerData
AvailableZelerData connects Mercado Libre data with Google Sheets to sync sales, orders, listings, and stock into customizable reports. Teams can work with updated metrics, multiple accounts, role-based permissions, and ready-to-use templates for operational analysis.
Request demo →ZelerPricing
Controlled visionPricing module direction for signal reading, supervised rules, and margin analysis. It is not presented as production-ready autonomous repricing.
Follow roadmap →ZelerStock
In operational designSecondary ERP module for structuring inventory and logistics as operational signals, not as a full physical automation promise.
Request beta →ZelerSupport
Assistive visionAssisted support module for preparing replies and escalation criteria. It is not positioned as a production autonomous chatbot.
Suggest a pain →ZelerListings
Assistive visionCatalog module for preparing content, attribute, and pre-review suggestions. It does not promise autonomous publishing.
View agents →Agents
Agents in design, with supervision as a principle
Agents appear as copilots or product vision. They are not presented as available production autonomy.
No agent shown on this home operates alone in production; every card displays its real state.
Assisted analysis
Zeler Analyst
Agent in design for summarizing operational signals and proposing reviewable hypotheses. It is not production available and does not make autonomous decisions.
Actively being built; may require support from the Zeler team.
View roadmap →Catalog with human review
Zeler Catalog
Agent vision for preparing catalog improvements and detecting missing data before publishing or syncing changes.
Product direction, not a promise of immediate availability.
Follow progress →Assisted support
Zeler Support
Agent vision for preparing replies, escalation criteria, and context. It is not an autonomous customer support agent.
Product direction, not a promise of immediate availability.
Suggest a pain →Integrations
Connectable channels depending on scope and permissions
Availability is declared per integration; WhatsApp contact is available, conversational automation is not.
LATAM marketplace
Mercado Libre
Catalog, questions, stock, and reputation live in separate flows.
Actively being built; may require support from the Zeler team.
Ask about scope →Owned store
Shopify
The owned store is often disconnected from marketplace operations.
Product direction, not a promise of immediate availability.
View roadmap →Contact and support
Commercial contact and support can lose context when they sit outside the operating system.
Functional foundation or operational service with explicit scope.
Contact →Marketplace
Amazon
Operating Amazon alongside LATAM channels requires normalizing reports and decisions.
Product direction, not a promise of immediate availability.
Follow progress →Build in public
Follow what is being built, what is missing, and what is still vision.
Roadmap and changelog act as a transparency contract so vision does not blur into available capability.
Open roadmap
User validation flow for modules
We updated the validation and permission flow so accounts can access modules inside app.zeler.ai in a clearer and more controlled way.
Zeler module naming alignment
We aligned how modules are named and presented so the experience is clearer and more consistent across the Zeler ecosystem.
ZelerData beta flow validation
We are validating the core ZelerData flow with connected accounts, saved information, and operational synchronization before expanding usage.
Latest updates
Webhook-driven data freshness in ZelerData
We improved ZelerData data freshness so formulas query read models updated from Mercado Libre webhooks, including production validation for recent listings and orders.
Data parity between ZelerData and Mercado Libre
We improved ZelerData consistency against the Mercado Libre UI by fixing and validating listings, dashboard, and order data, including fees, costs, promotions, stock, status, logistics, and authorized shipping and buyer fields when applicable.
ZelerData token settings
We simplified the ZelerData settings experience in app.zeler.ai so users can copy their token when needed and remove revoked tokens, with updated backend support to handle these changes safely.
If you operate ecommerce and want to shape this with us, join early.
The beta starts with real conversations about operational pain. No total automation promises; just scope, priorities, and public learning.