Selling on WhatsApp with your ERP's inventory and prices:what connects and how
An AI agent selling on WhatsApp is only as reliable as the data it checks. If it reads a price PDF or last week's inventory spreadsheet, it promises things you do not have. Connected to your ERP, it answers with each customer's inventory, price list and account balance, and leaves the order entered. Here is what data flows, how it connects and which mistakes to avoid.
How do you integrate WhatsApp with your ERP to sell?
To integrate WhatsApp with your ERP, you connect an AI agent to the official WhatsApp Business API and to the ERP, through the system's API, a connector or your company's integration layer. In every conversation, the agent reads inventory, price lists and account balance for the customer writing in and writes the sales order back, with nobody retyping it.
WhatsApp does not connect to an ERP on its own: the app and Meta's API move messages, not orders. What joins the two is the layer in between, which understands what the customer is asking for, queries the system with the permissions you grant and records the result. Sellium plays that role with SAP, Oracle, Tango, Odoo, NetSuite and other ERPs, and logs every conversation in Salesforce.
What happens when WhatsApp sells without checking the ERP
At many companies, WhatsApp is the channel where the most selling happens and the only one connected to nothing. The customer asks about price and stock, someone opens the ERP on another screen, copies the figure into the chat and, if there is an order, types it in again. When a bot with no integration takes over that step, the problem changes shape but does not go away: it answers with data that is not the system's.
It is a connection problem, not a channel problem. In MuleSoft's connectivity report, the companies surveyed use 897 applications on average and only 29% of them are integrated with each other (MuleSoft, 2025). The sales chat each rep handles from their own phone does not even make that count.
- Stock that is not there: the customer confirms, the warehouse is out and the shortage shows up when the truck arrives.
- A price from another list: someone quotes the general price list to a customer who has their own, or the one from two weeks ago.
- Credit nobody checked: an order is taken from an account with an overdue balance or no credit left, and accounting finds the problem.
- Retyping: the order closed in the chat is entered by hand in the ERP, late and with errors.
- Repeat questions: the status of each order is answered by searching the system, over and over.
What data the agent reads and writes in your ERP
Integration is not all or nothing. To sell on WhatsApp you need a limited set of data, almost all of it read-only, and one write that matters: the sales order. This is the typical map, adjusted during discovery to fit your system.
With that data, the agent quotes and takes orders the way a rep would with the ERP open. The full order flow is in WhatsApp order taking, and how the price is built from your lists and discounts is in automated WhatsApp quotes.
| ERP data | Read or write | What the agent uses it for |
|---|---|---|
| Catalog, codes and units | Read | Understanding what the customer wants even when they name it their own way, with cross-references, pack sizes and selling unit |
| Inventory by warehouse | Read | Confirming availability before promising anything and offering an equivalent if something is out |
| Price lists and promotions | Read | Applying that customer's or channel's list, with volume tiers and current promotions |
| Account balance and credit | Read | Knowing whether the account has an overdue balance or available credit before confirming the order |
| Customer terms | Read | That account's payment terms, zone, delivery days and minimum order |
| Sales order | Write | Creating the confirmed order, ready to pick and invoice through your usual process |
| Order status | Read | Answering what stage an order is at without anyone having to look it up |
The exact scope (which objects, which fields and with what permissions) is defined during discovery and depends on your ERP and its version.
And in the CRM: the conversation, the quote and the order are logged on the customer's record in Salesforce. The ERP remains the source of truth for inventory, prices and balances; the CRM, for the business relationship.
Three ways to connect WhatsApp to the ERP: API, connector or middleware
How it connects depends on what your ERP exposes, not on where it is installed. The rule of thumb is simple: if the system has an API, the agent works through it. If it does not, there are other routes, and they are chosen during discovery, before we quote.
| Route | When it is used | What to keep in mind |
|---|---|---|
| ERP API | The ERP publishes an API (REST, OData, SOAP or another) to query and create records | It is the preferred route: the data is current and every call uses an integration user with narrow permissions |
| Existing connector | There is already a connector between your ERP and Salesforce, or a standard one for your system | You build on what already works; check which data it syncs and how often |
| Middleware or integration layer | Your company already runs an integration bus or platform, or the ERP is on-premise and exposes no API | The agent queries that layer or, on local installs, the ERP database with read-only access; the order goes in through whatever mechanism the system supports |
Exported spreadsheets and price PDFs are left out on purpose: they are a copy that goes stale, and the agent ends up promising what is not there.
WhatsApp with SAP, Oracle, Tango, Odoo or NetSuite
The most common ERPs among companies that sell on WhatsApp in Latin America expose an API, each with its own quirks. The table sums up where each one connects; the technical details are covered system by system during discovery.
| ERP | Where it connects | Worth knowing |
|---|---|---|
| SAP | Native API integration with the SAP product suite | In SAP Business One, the Service Layer (REST/OData) is the recommended route for a new integration |
| Oracle | The native APIs of Oracle ERP Cloud and Oracle Database, over standard protocols | If your implementation mixes cloud and on-premise modules, the work is defined by the available APIs |
| Tango Gestión | The REST APIs of the Tango ecosystem, with token authentication | It usually requires the system installed and connectivity to your company's environment |
| Odoo | The external API (XML-RPC and JSON-RPC), in both Community and Enterprise | Webhook triggers depend on the edition; in Community they are handled with server actions or periodic queries |
| NetSuite | SuiteTalk REST and SuiteQL, with OAuth 2.0 | It has no native outbound webhooks: events are handled with scripts or periodic queries |
Sellium also integrates with other ERPs; if yours is not listed, it is assessed during discovery.
Six mistakes when connecting WhatsApp to the ERP
Projects that fail almost never fail because of the API. They fail because the agent checks data that is no use for selling, or because nobody defined what happens when something does not add up.
- Copying instead of querying: uploading an inventory spreadsheet or a price PDF to the bot. It works on day one; a week later, the agent is selling with stale data.
- No cross-references: the ERP has internal codes and the customer orders by brand, size or nickname. Without a cross-reference table, the agent asks too many questions or picks the wrong product.
- Ignoring the account balance: confirming orders without checking balance or credit. The order goes in and accounting stops it, with the customer waiting.
- Too many permissions: connecting with an admin user to get it working fast. The agent needs to read a few things and write one; those are the permissions it should have.
- No plan for downtime: if the ERP does not respond, the agent cannot make up the inventory. You have to define what it does: take the order as pending confirmation or hand it to a person.
- Integrating everything at once: trying to connect invoicing, logistics and collections in the first month. Start with inventory, prices and order entry, measure, and then add more, like WhatsApp payments or quote follow-up.
What happens to your ERP data
The question IT always asks is where the data ends up. The short answer: in your systems. Sellium runs inside your Salesforce org and queries the ERP at the moment of the conversation, with an integration user and the permissions you grant. There is no Vantegrate-operated middle layer keeping a copy of your database.
What travels over WhatsApp is the conversation with the customer: the price that applies to them, their available stock, their order. Nothing that customer would not see if their rep sent it. The details on architecture, encryption and auditing are on our security page.
- Least privilege: the integration user reads what the agent needs and writes only the sales order.
- Traceability: every query and every new record is logged, and the order keeps the conversation that created it.
- Own data only: the agent identifies who is writing before showing prices, balances or orders, and never shows another account's data.
How to tell whether the ERP integration is working
Measure before you connect: a few weeks of baseline are enough to compare with numbers instead of impressions afterward. These six metrics show whether the agent sells with real data and where to adjust.
| Metric | What it measures | How it is calculated |
|---|---|---|
| Questions answered with ERP data | How many price and stock questions are answered without a person | Questions resolved by the agent over all price and stock questions |
| Orders with no retyping | How much of the channel goes straight into the system | Orders created by the agent over all WhatsApp orders |
| Shortages after confirmation | Whether the stock being promised is real | Confirmed orders with out-of-stock items at picking time, per week |
| Pricing errors | Whether the right list was applied | Credit notes or re-invoicing caused by a wrong price on WhatsApp orders |
| Orders held for credit | Whether the account balance is checked before confirming | Orders stopped by accounting after being confirmed to the customer |
| Response time | The speed the customer experiences | Minutes between the question and the answer with price and availability |
Pull the data from the ERP and Salesforce, not from an estimate, and compare the same customers before and after.
How a WhatsApp sale connected to the ERP works
What used to go through the chat, an ERP screen and manual entry, the agent handles in a single conversation, at any hour.
The customer writes in
By text, voice note or a photo of a list: they ask for a price, check stock or send the order straight away.
The agent identifies them
By their number, against the CRM and the ERP, and pulls their price list, their terms and their account balance.
It queries the ERP on the spot
Inventory by warehouse, the price from their list with tiers and promotions, and the balance or credit available.
It answers and confirms
It gives real price and availability in the chat; if something is out, it offers an equivalent. Before entering the order, it repeats the summary and waits for a yes.
It writes the order to the ERP
The order goes in as a sales order, ready for your picking and invoicing process, and the conversation is logged in Salesforce.
It reports status or hands off
It answers about order status when the customer asks and passes anything outside the rules to a person, with the full context.
Integration, buyers and selling time, in numbers
Third-party figures with a published source, to size the problem. None of them is a Sellium result: every implementation is measured against the company's own baseline.
29%
Of a company's applications are integrated with each other, on average, out of 897 in use
95%
Of IT leaders say integration is a hurdle to implementing AI effectively
61%
Of B2B buyers prefer, in general, a buying experience without a sales rep involved
70%
Of sales reps' time goes to tasks that are not selling, by their own account
Caveats: the MuleSoft report comes from interviews with 1,050 IT leaders worldwide and measures integration between applications in general, not WhatsApp in particular. The Gartner survey covered 632 B2B buyers, who still prefer to talk to a rep for decisions that need context; that is why the agent hands those cases off. The Salesforce figure is based on what reps report themselves.
Sellium: the agent that sells with your ERP data
Sellium is delivered configured and connected: our team does the discovery, the ERP integration and the training on your catalog. It sells on WhatsApp with your real inventory and price lists, checks the account balance and leaves every order in the ERP and every conversation in Salesforce. That is how it works in Wholesale Distribution and Construction Materials.
Sellium
AI sales agent for WhatsApp
Sellium is Vantegrate's AI sales agent for WhatsApp: it runs on the official API, runs inside Salesforce, integrates with your ERP for inventory, prices and account balances, quotes, takes the order and enters it, around the clock.
Explore SelliumSecure AI agents
Sellium runs 100% on Salesforce and Oracle Cloud infrastructure, certified SOC 2 Type II and ISO 27001. Vantegrate enables, the customer operates and certifies.
See the security modelISV and Consulting PartnerRuns inside your Salesforce
Sellium reads and writes your objects, respects your profiles and permissions, and works alongside Agentforce and your existing flows.
Vantegrate and SalesforceFrequently asked questions about integrating WhatsApp with your ERP
What sales and IT teams ask before connecting the sales channel to the ERP.
Can you integrate WhatsApp with an ERP?
Can you integrate WhatsApp with an ERP?
Yes, but not directly: WhatsApp moves messages and the ERP records transactions, so you need a layer in between that understands the conversation and operates the system. That layer is an agent connected to the official WhatsApp Business API and to the ERP's API, which reads inventory and prices and creates the order.
Which ERPs does Sellium integrate with?
Which ERPs does Sellium integrate with?
SAP, Oracle, Tango, Odoo, NetSuite and other ERPs, to read inventory, prices and account balances and to create the sales order. If your system is not on the list, how to connect it is worked out during discovery, before we quote.
What if my ERP has no API?
What if my ERP has no API?
There are other routes: a connector that already exists between your ERP and Salesforce, your company's integration layer or, on local installs, a connection to the system's database with limited access. What we do not recommend is working from exported spreadsheets, because the agent would end up selling with stale data.
Are the inventory and prices it gives real time?
Are the inventory and prices it gives real time?
Yes: the agent queries the ERP at the moment of the conversation, so it reports the stock and price the system has when the customer asks. If your ERP updates inventory with a lag, for example when each delivery note is closed, the agent reflects that same lag: accuracy depends on how up to date the system is.
Does my ERP data leave my company?
Does my ERP data leave my company?
No. Sellium runs inside your Salesforce org and queries the ERP with an integration user, with the permissions you grant, and does not keep a copy of your database on Vantegrate infrastructure. Only what the customer needs to see about their own account travels over WhatsApp. The details are on our security page.
How much does it cost to connect WhatsApp to the ERP with Sellium?
How much does it cost to connect WhatsApp to the ERP with Sellium?
Sellium is priced in two parts: an initial implementation quoted for each company, which includes the ERP integration, and a monthly subscription with AI credits that scale up, with no lock-in. You pay for WhatsApp messages directly to Meta, on your own account and with no markup from us. For your number, request a quote with your ERP and your inquiry volume.
Let WhatsApp sell with your ERP's data
Tell us which ERP you use, how inquiries come in and what you want the agent to read and enter. We will show you, with your catalog and your price lists, how Sellium would answer and leave the order in your system.