Your customers and suppliers already have WhatsApp open. WhatsApp commerce lets them transact there — against live SAP Business One data, with permissions and a logged trail — instead of behind a portal login they will not remember.
It is a portal alternative, not a notification add-on. That is the distinction worth holding on to, because most "WhatsApp for ERP" offerings are the second thing.
A notification integration pushes information out: a payment reminder, a dispatch alert, a daily digest. Useful, one-way, and the recipient can do nothing except read it. WhatsApp commerce runs the other direction as well — the customer or supplier asks for something, or does something, and SAP Business One responds.
Compare it against the thing it actually replaces. A customer portal means a login, a password reset nobody completes, an app or a bookmark, and a support call when it does not work. Adoption is the problem portals never solve. WhatsApp has no adoption problem: the install base is already there, the interface is already familiar, and the message thread is its own history.
Underneath, this is still your ERP. Orders land in SAP Business One as documents, against the right business partner, at the right price list, inside the same approval rules your staff work within. The channel changes; the controls do not.
Six things, each completed end to end in the chat — no phone call, no portal login.
That set is the test of whether a channel replaces a portal or merely decorates one: every item is something a customer would otherwise phone your team to ask.
Seven, including one most ERP-to-WhatsApp offerings do not attempt: full item-by-item quoting inside the chat.
The supplier side matters more than it first looks. Purchase-order acknowledgement and delivery confirmation are where most of the chasing happens in a distribution or manufacturing business, and they are the calls nobody wants to make twice.
The automation starts inside SAP Business One, not in the chat.
Creating or releasing a purchase order triggers an outbound WhatsApp PDF with Confirm and Reject buttons to the supplier. Publishing an RFQ pushes the line items to every matching vendor. When a supplier bids or confirms dispatch in the chat, the connector writes back through the SAP Business One Service Layer — a draft quotation or an updated delivery log, in real time. Delivery delays trigger alerts to purchasing or the customer automatically.
The flows run fully automated on menus and buttons; unrecognised text gets a structured redirect back to the menu. The conversation trees, validations and fields extend to your own SAP Business One user-defined fields.
The outbound half of this already runs in production: the daily receivables digest at Him Electronics in Kathmandu lands on WhatsApp before the morning meeting (how that was built). Commerce adds the return path — the supplier or customer acting in the same thread.
Yes. The WhatsApp Business Platform is Meta’s official channel for businesses to message customers, and commerce use of it is what the platform exists for. Messaging rules apply — opt-in is required before you message someone, and template approval governs business-initiated messages outside an open conversation window.
Yes. The consumer app and the free WhatsApp Business app cannot connect to an ERP. This runs on the WhatsApp Business Platform (the API), which is what allows a verified business number, message templates, and an integration that reads and writes to SAP Business One.
Yes — on SQL Server or SAP HANA, cloud or on-premise, on the installation you already run. Nothing in the SAP Business One configuration is replaced. The integration reads and writes through the same permission model your users already work within.
No, and the difference matters commercially. Alerts push information out — a receivables digest, a stock warning. WhatsApp commerce lets the other party act: place an order, request a statement, check a delivery. Alerts are one-way; this is a transaction channel.
No. That is the reason this replaces a portal. Customers and suppliers use the WhatsApp already on their phone, with no app to download, no account to create and no password to reset — which is exactly where customer portals lose people.
WhatsApp integration is scoped to your flows and priced on the demo call. Meta charges separately for conversations on the WhatsApp Business Platform, billed by conversation category and destination country, so that portion depends on your message volume rather than on the integration.
WhatsApp integration is scoped to your flows and priced on the demo call.
Bring one process your customers currently phone about. That is the fastest way to judge whether this replaces the portal you were about to build.