How to add WhatsApp to Epicor Vantage and Epicor 9
Short answer
Epicor Vantage and Epicor 9 have no native WhatsApp feature, so you add one with a small middle service. The service reads events from Epicor (BPM directives or Service Connect workflows), sends approved template messages through the WhatsApp Business Platform, and writes replies back through the Epicor business object web services.
Most shops still on Vantage 8.x or Epicor 9 are mid-sized job shops and make-to-order manufacturers whose buyers, suppliers and drivers live on WhatsApp. Order acknowledgements, ship dates and supplier confirmations are chased by phone and personal chat, and none of it is recorded against the PO or the sales order.
The ERP itself is stable and often heavily customised, so replacing it is not the goal. The goal is to push a few high-value messages out of Epicor and pull a few structured answers back in, without touching the core application more than necessary.
Because Epicor 9 is an older platform, the integration surface is narrower than on Kinetic. The approach below sticks to what Epicor 9 reliably offers: Service Connect, BPM method directives, the business object web services and, as a last resort, read-only SQL access.
What teams use it for
Supplier PO confirmations
Send a template message to the buyer contact on a released PO and capture a Confirm or Change reply that updates the promise date on the PO release.
Customer shipment alerts
When a packing slip is shipped, send tracking and expected delivery to the customer contact held on the ship-to, instead of an email that lands in spam.
Late job escalation to the planner
Notify the production planner when a job operation slips past its scheduled finish, with a quick reply to log a new date as a job note.
Quote follow-up
Ping the customer contact three days after a quote is issued and write the reply text to the quote comments for the salesperson.
Driver and field delivery proof
Ask delivery drivers to reply with a photo of the signed delivery note, stored against the shipment record.
Epicor Vantage / Epicor 9 integration surface
- BPM method directives on business objects such as the shipment, PO release and job operation update methods, used to fire a call to your middle service after a successful commit. Exact object names vary by 9.0x release.
- Service Connect workflows (the Epicor 9 integration engine) for scheduled or event-driven flows, including HTTP and file connectors, when you prefer not to use BPM code.
- Business object web services (SOAP, for example the sales order, PO and job services) for writing replies back with the same validation the client applies.
- Business Activity Queries and the Epicor Data Discovery layer for building the read-only recipient and status lookups.
- The underlying database, Progress OpenEdge on older Vantage and Epicor 9 releases (some 9.0x installs use SQL Server), reachable through ODBC for read-only polling if events are not available.
How it works
- 1
Register WhatsApp Business Platform access
Use a verified Meta business account with the Cloud API directly, or a business solution provider if you want hosted inbox tools. Create and submit your message templates up front.
- 2
Capture opt-in per contact
Store a WhatsApp number and opt-in date on the customer, vendor or contact record, using a user-defined field. Do not message contacts without recorded consent.
- 3
Emit events from Epicor
Add a post-processing BPM directive or Service Connect workflow on the events you care about. It posts a small JSON payload with the record keys to your service and returns quickly.
- 4
Build the middle service
A small service queues events, looks up the contact and opt-in, picks a template, sends the message and logs the message ID. It runs on a server that can reach both Epicor and the internet.
- 5
Handle inbound webhooks
Meta posts replies to a webhook. Parse button replies and short text, match them to the open conversation, and call the Epicor business object service to apply the change.
- 6
Add approval for anything that writes
Date changes and quantity changes should create a pending item for a buyer to approve, not post straight to the PO.
- 7
Monitor and retry
Track delivery status callbacks, retry transient failures and alert when the Epicor service endpoint is down.
Example flows
PO release confirmation
Trigger: A buyer releases a PO and the PO release is committed.
- BPM directive posts the PO number and vendor to the middle service.
- Service finds the vendor contact with a recorded WhatsApp opt-in.
- A template with Confirm and Change date buttons is sent.
- On Confirm, the promise date is stamped via the PO web service.
- On Change date, the supplier is asked for a new date and a pending review is created for the buyer.
Result: Supplier answers sit next to the PO instead of in personal chats, and exceptions reach the buyer the same day.
Shipment notice with delivery photo
Trigger: A shipment is marked shipped in Customer Shipment Entry.
- Event carries packing slip, customer and carrier reference.
- Service sends a utility template with the tracking reference.
- The customer or driver replies with a photo.
- Service stores the image as an attachment against the shipment and notes receipt time.
Result: Proof of delivery is attached to the shipment record without anyone re-keying it.
Keeping data on-prem
WhatsApp itself is always a cloud service, so the message content leaves your network. What you control is what you put in it. Keep the Epicor database, the middle service and any AI that interprets free-text replies on-prem, and send only template variables such as a PO number and a date. If you want a free-text reply understood, run an open-weight model locally on the customer's GPUs to classify the reply into confirm, change or question, so the supplier text does not go to a third-party model. The middle service needs outbound HTTPS and an inbound webhook endpoint, which usually means a reverse proxy in a DMZ rather than exposing Epicor.
Security checklist
- Never expose the Epicor application server directly to the internet. Put the webhook receiver in a DMZ and call Epicor from there over the internal network.
- Use a dedicated Epicor user for the integration with only the business object rights it needs, not a shared admin login.
- Verify the Meta webhook signature on every inbound call and reject anything unsigned.
- Keep opt-in records and message logs for audit, and limit template variables to non-sensitive fields.
- Require human approval before any reply changes a date, quantity or price.
Ways to get it done
Build in-house with Service Connect or BPM plus a small web service
Effort: About 3 to 6 weeks for a first set of templates, longer if replies write back.
You have a developer who knows Epicor customisation and wants full control of the flows.
Use a WhatsApp business solution provider with a generic webhook connector
Effort: Roughly 2 to 4 weeks, plus the provider's per-conversation fees.
You want a hosted inbox and templates, and are happy to build only the Epicor side.
Work with a partner such as Netray
Effort: Scoped per project, typically a short pilot on one or two flows first.
You want reply interpretation, approvals and an on-prem option without building the plumbing.
Pitfalls
- !Putting HTTP calls inside a synchronous BPM directive can slow or fail user transactions. Queue the event and return immediately.
- !Templates must be approved before use, and business-initiated messages outside the customer care window need a template. Plan lead time.
- !Phone numbers stored free-form on contacts break matching. Normalise to international format.
- !Writing back through the database instead of the business objects bypasses validation and can corrupt the Progress data.
- !Epicor 9 customisations differ widely between sites, so confirm event names and object methods against your own release.
Frequently asked questions
Does Epicor Vantage or Epicor 9 have a built-in WhatsApp connector?
No. There is no native WhatsApp feature in those releases. You connect them through Service Connect or BPM directives that call a middle service, which talks to the WhatsApp Business Platform. Some third-party add-ons exist, but check they support your exact version.
Can replies from WhatsApp update Epicor automatically?
Yes, through the Epicor business object web services, so validation still runs. For anything that changes dates, quantities or prices, route it through an approval step rather than posting directly.
Do I need the cloud WhatsApp API or a provider?
Either works. The Cloud API gives you direct control and low cost. A business solution provider adds inbox tooling and support. Both need approved templates and recorded opt-in for business-initiated messages.
Is it safe to connect an older Epicor 9 server?
Yes if you keep Epicor off the public internet. Run the middle service and webhook receiver in a DMZ, call Epicor over the internal network with a restricted user, and avoid exposing the application server or database.
Can this run without sending ERP data to a public AI?
Yes. Send only template variables, and if you need to understand free-text replies, classify them with an open-weight model hosted on your own hardware so supplier text stays on-prem.
Want WhatsApp working on your Epicor Vantage / Epicor 9?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment