How to add WhatsApp to proALPHA
Short answer
proALPHA has no native WhatsApp channel, so the usual path is a small middleware service between the WhatsApp Business Platform (Cloud API or a BSP) and proALPHA's web service layer or OpenEdge database. The middleware sends approved templates on ERP events and turns inbound replies into controlled transactions or tasks. Keep writes behind a review step and keep the middleware inside your network.
Many proALPHA customers are German-speaking and international mid-market manufacturers and machine builders, with a mix of on-premise installations and hosted ones. Their suppliers, drivers and service technicians already live on WhatsApp, while the ERP is reached through the rich client or a browser. The gap shows up as phone calls and e-mails to confirm delivery dates.
WhatsApp is attractive because delivery rates and read rates are far higher than e-mail for short, time-critical messages. The constraint is that Meta controls the channel: business-initiated messages need pre-approved templates and recorded opt-in, and the number you use must be registered to a WhatsApp Business account.
This page describes a realistic build against proALPHA, which sits on a Progress OpenEdge database. Exact interface names and module licences differ by proALPHA version and by what your partner enabled, so confirm them in your own installation before committing to a design.
What teams use it for
Delivery date confirmation from suppliers
When a purchase order is released, send the supplier a template message with the order number and requested date. A reply of Confirm or a new date is parsed and stored as a proposed change for the buyer, not written straight into the order.
Shipment and pickup notices to customers
After a delivery note is posted, send the carrier, planned arrival and tracking link to the customer contact. Useful for machine builders shipping long-lead assemblies where the receiving dock needs notice.
Service technician dispatch
Push a service order summary with address and contact to a field technician, and accept a reply with arrival, completion and a photo that is attached to the service order as a document.
Approval nudges for purchase requisitions
Notify an approver on mobile with Approve and Reject quick-reply buttons. The reply creates an approval record that a second system check validates against the approver's ERP authority.
Overdue payment reminders
Send a polite reminder with the invoice number and a payment link for open items past due, only to contacts who have opted in and only inside agreed hours.
proALPHA integration surface
- proALPHA web service interfaces (SOAP and REST style, exposed through the proALPHA application server in current releases; the exact service catalogue depends on version and licensed modules).
- Direct read access to the Progress OpenEdge database through SQL-92 over JDBC or ODBC, useful for status lookups. Use a read-only database user and never write to base tables directly.
- proALPHA workflow and event mechanisms for triggering on status changes (for example order release or delivery note posting); availability and naming vary by version.
- Standard export and import interfaces and scheduled jobs for batch exchange where no event hook exists.
- Document management in proALPHA for storing inbound photos and PDFs against the right business object.
How it works
- 1
Register the WhatsApp Business Platform account
Create a Meta business account, verify the business, and either use the Cloud API directly or choose a business solution provider. Register a dedicated number that is not used in the personal app.
- 2
Define and submit message templates
Write templates for each flow (confirmation request, shipment notice, approval request) with variable slots. Submit for approval in the languages you need, such as German and English, and keep them short.
- 3
Capture opt-in and map contacts
Store opt-in evidence and the mobile number per contact, in a proALPHA contact field or an external table keyed by contact ID. Normalise numbers to E.164.
- 4
Build the event-to-message service
A middleware reads trigger events (via workflow hook, polling a status table, or a scheduled export), looks up the data over the web service or SQL, fills the template and calls the Cloud API.
- 5
Handle webhooks for replies and delivery status
Expose an HTTPS endpoint for Meta's webhook, verify the signature, deduplicate by message ID, and classify replies as structured buttons, free text or media.
- 6
Write back through a review queue
Post replies into proALPHA through the supported web service as a proposed change, a task, or a document attachment. A buyer or planner accepts it. Log the full exchange.
Example flows
Supplier confirms a purchase order line
Trigger: A purchase order is released with a requested delivery date.
- Middleware reads the order header and lines via web service.
- A confirmation template goes to the supplier contact with order number and date.
- Supplier taps Confirm or sends a new date as text.
- Middleware parses the date, checks it is plausible, and creates a proposed change for the buyer.
- Buyer accepts in a review screen and the confirmation date is stored.
Result: Confirmations arrive the same day without phone calls, and every date change has a reviewer.
Technician reports job completion
Trigger: A service order is assigned to a technician.
- Dispatch message with customer address and fault description.
- Technician replies Done with a photo of the signed report.
- Middleware stores the photo as a document on the service order.
- A task is created for the service coordinator to close the order and trigger invoicing.
Result: Closed-out jobs reach back office faster and the evidence is attached to the order.
Keeping data on-prem
WhatsApp itself is a cloud channel, so message content passes through Meta's infrastructure; that cannot be avoided. What you can keep on-premise is everything around it: the middleware, the ERP credentials, and any AI that classifies replies. Run the middleware in your DMZ or private network, expose only the webhook endpoint through a reverse proxy, and call proALPHA from inside. If replies contain free text that must not leave your environment for further processing, classify them with a locally hosted open-weight model rather than a public API. Limit what goes into outbound templates to non-sensitive references such as order numbers, not prices or drawings.
Security checklist
- Verify the webhook signature on every inbound call and reject unsigned traffic.
- Use a dedicated proALPHA integration user with the minimum authorisations, not a named employee account.
- Keep outbound templates free of prices, drawing content and personal data beyond what is needed.
- Store opt-in evidence and honour opt-out keywords immediately to stay inside GDPR and WhatsApp policy.
- Log message ID, contact, template and resulting ERP object for audit.
Ways to get it done
Off-the-shelf BSP with a generic ERP connector
Effort: Days to a few weeks, plus per-conversation fees.
Works for notifications only when a connector to proALPHA exists or a CSV or webhook bridge is acceptable. Check coverage before buying.
Build in-house middleware
Effort: Typically several weeks for two or three flows, plus template approval time.
Fits teams with OpenEdge or proALPHA web service skills who want full control over data flow.
Work with a partner such as Netray
Effort: A scoped pilot of one flow first, then extend.
Best when you also want AI to read free-text replies, keep the ERP side on-premise and add approvals around write-back.
Pitfalls
- !Using a number that is also active in the personal WhatsApp app, which blocks Cloud API registration.
- !Sending free-form messages outside the 24-hour customer service window; only approved templates are allowed then.
- !Letting a reply update a delivery date directly in the ERP without a review step.
- !Storing phone numbers in unstructured contact notes so opt-in cannot be proven.
- !Assuming a web service name from another release; check what your version actually exposes.
Frequently asked questions
Does proALPHA have a built-in WhatsApp function?
Not as a standard channel in the versions we know of, though your partner may offer an add-on. Most teams add a middleware service that talks to the WhatsApp Business Platform on one side and proALPHA's web services or database on the other. Verify with your proALPHA partner what your release supports.
Can we send order confirmations to customers on WhatsApp?
Yes, as approved template messages to contacts who opted in. Keep the content to references and status, and send the full document by link or e-mail. Free-form messages are only possible inside the 24-hour window after the customer writes first.
Is it safe to let suppliers reply and change ERP data?
Only through a review step. Parse the reply, show it to a buyer as a proposed change, and post it after acceptance. Direct write-back from an external chat opens risk for spoofing and typos, especially on dates and quantities.
Can this run on-premise?
The middleware and ERP access can, and should. WhatsApp message content still travels through Meta. If you add AI to interpret replies, a local open-weight model keeps that text inside your network.
Which languages can templates use?
Templates are submitted per language and approved separately. German and English are common for proALPHA customers. Pick the language per contact record and keep a fallback so no recipient gets an unreadable message.
Want WhatsApp working on your proALPHA?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment