WhatsApp agent connected to your ERP: orders without manual entry
A WhatsApp agent connected to your ERP takes a customer's order, checks stock and price in the system and loads it as an order, without anyone typing it. We build it on the official WhatsApp API, with a one-week discovery and go-live in 2 to 3 weeks; the code and infrastructure stay in your account.
Updated on October 16, 2026
The problem: orders arrive on WhatsApp and are typed in by hand
In distributors, wholesalers and shops with field salespeople, the order arrives as a voice note, a photo of a list or a long message. Someone reads it, interprets it and enters it in the ERP. It is slow, information gets lost and mistakes only show up when the customer complains.
What the agent does inside tu ERP
All our agents talk to the system through a connector with the same interface. For tu ERP it is set up once and the agent always uses the same five operations.
| Operation | Example in a conversation | Read or write |
|---|---|---|
| Identify customer | Recognizes the buyer by their WhatsApp number and account. | Read |
| Search products | “Send me 20 boxes of yerba” is matched against your catalog, with codes and pack sizes. | Read |
| Check stock | Warns whether it is available before confirming and suggests alternatives. | Read |
| Check prices | Applies that customer's price list and terms, not a generic price. | Read |
| Create order | Builds the order from what was confirmed in the conversation and loads it into the system. | Write |
Which ERPs and systems we work with
The connector adapts to what each system offers: its API, an accessible database, scheduled exports or an intermediate layer for systems with no API. We confirm it in discovery, before committing to scope.
- Tango Gestión: see the Tango integration page.
- öppen: see the öppen integration page.
- Odoo and other ERPs with an API.
- Google Sheets or Excel spreadsheets when there is no ERP yet.
- In-house or legacy systems (Java, VB6, Access, old PHP).
How it writes to el ERP without breaking anything
Reading is easy. Writing is the delicate part. That's why the agent never loads data blindly:
- Order pending approval: it reaches the system as a draft and a person confirms it. Once the team trusts it, you switch to direct loading by customer type or amount.
- No duplicates: every order carries a unique key from the conversation; if the customer repeats the message or WhatsApp retries delivery, it is not loaded twice.
- Audit trail: what the customer said, what the agent understood and what was written are all logged, so any order can be reviewed.
- Handoff: if an order is unusual (out-of-stock item, customer with a balance due, an amount outside the norm), it goes to a person with full context.
Timeline
An agent connected to tu ERP goes live in stages. Timelines depend on the available API and on how many products and pricing rules need to be covered.
| Stage | What happens | Time |
|---|---|---|
| Discovery | We review how tu ERP connects, the ordering flows and pricing rules. By the end you know scope and risks. | 1 week |
| Go-live | Agent running on your number, with orders pending approval and the team reviewing conversations. | 2 to 3 weeks |
| Tuning | With real conversations we tune products, synonyms and rules, and enable direct loading where appropriate. | Ongoing |
What sets us apart from a module or a platform
- The code stays in your account: repository, database and deployment are yours. No subscription to an intermediary platform and no lock-in.
- Direct official WhatsApp API (Meta Cloud API), on your number and your Meta account: you pay Meta what Meta charges, with no intermediary markup.
- Several systems at once: besides tu ERP, the same agent can query a spreadsheet, a CRM or an in-house system.
- Business-specific rules and orders by voice note, photo or PDF, not just text.
- If the system is old, we modernize what surrounds it without stopping operations.
- A studio based in Neuquén and Rada Tilly: you talk to us, not to a call center.
Frequently asked questions
- Does my ERP need an API to connect it to WhatsApp?
- Not always. If it has an API, we use it. If not, we can read its database, work with scheduled exports or add an intermediate layer. We assess it in discovery and tell you what is and isn't possible before quoting.
- Can the agent get an order wrong?
- It can misread a message, like any person. That's why orders start pending approval, with an audit trail for every step, and the agent reads the order back to the customer to confirm before loading it.
- How much does it cost?
- It is quoted after the one-week discovery, because it depends on the ERP, the number of products and the pricing rules. On top of that comes what Meta charges per message, which we explain in our WhatsApp API cost guide.
- What if I want to change provider tomorrow?
- You take everything. The code, database and deployment are in your account, so another team can pick up the work without asking us for anything.
Related guides
Related service
AI agents on WhatsApp that answer, book and load orders into your ERP or system (Tango, öppen, Odoo). One-week discovery. The code stays yours.
Other integrations
Shall we talk?
Tell us what you want to solve. We reply within one business day.