How to add WhatsApp to abas ERP
Short answer
abas ERP has no native WhatsApp channel, so you build a small relay: read order, shipment and purchasing records through the EDP interface or the REST API, send approved template messages through the WhatsApp Business Platform, and push replies back as controlled updates. The ERP stays the system of record and the relay only moves messages.
abas ERP is common in German-speaking mid-sized manufacturing, often installed on-prem on Linux or Windows servers and customised heavily over the years with scripts and infosystems. Sales, purchasing and shipping staff already live in the ERP, but customers and suppliers live on phones. Chasing a delivery date or an order confirmation by email is slow, and in many markets a supplier answers WhatsApp in minutes and email in days.
The goal is narrow: send the right status message from abas to the right contact, and let a short reply (confirm, reject, new date) land back in the ERP with a trace. You are not replacing the abas client, you are adding a channel next to it.
Because the ERP is often behind a firewall, the design question is less about WhatsApp and more about where the relay runs and which direction connections are opened. This page walks through that path for a typical abas installation.
What teams use it for
Delivery notification to customers
When a delivery note is posted or a shipment is handed to the carrier, send a template message with the order reference, parcel count and tracking link from the shipping data in abas.
Supplier order confirmation
After a purchase order is released, message the supplier contact and ask for a confirm or a revised date. A reply of 'confirm' updates a confirmation field or a user-defined note on the purchase order line.
Overdue purchase order nudges
A nightly job reads open purchase order lines past their delivery date and sends a polite reminder per supplier, grouped so one supplier gets one message, not twenty.
Sales rep quote follow-up
Notify the rep on their own phone when a customer opens or answers a quote, and let them reply with a short status that is logged against the customer record.
Internal approvals on the move
Send a purchase requisition or discount approval request to a manager, with approve and reject quick-reply buttons, then write the decision back through the same controlled path as any other update.
abas ERP integration surface
- EDP (Enterprise Data Processing) interface: abas's long-standing programmatic access to records, typically reached over a TCP session from Java, .NET or scripting clients; exact client libraries and versions vary by abas release.
- REST API: newer abas releases expose HTTP endpoints for master and transaction data; availability and the exact resource names depend on version and licensing, so confirm in your installation.
- Infosystems and scripts: custom queries and batch lists that can be exposed as a read model for 'open POs' or 'orders shipped today' without touching core tables.
- Event hooks: abas supports triggering your own logic on certain record changes through scripts; where that is not enabled, polling a change timestamp every minute or two is the fallback.
- Contacts live in the customer and vendor records and their contact persons; mobile numbers are often missing or unformatted, which matters because WhatsApp needs E.164 numbers.
How it works
- 1
Pick the delivery path
Use the WhatsApp Business Platform Cloud API directly, or a Business Solution Provider if you want a managed inbox. Register the business number and verify the business with Meta first, since approval can take days.
- 2
Build a read model in abas
Create or reuse an infosystem or REST query that returns just the fields needed for each message: document number, partner, contact mobile, dates, status. Keep it read-only.
- 3
Stand up the relay
A small service (Node, Python or Java) polls the read model or receives a script trigger, builds the template payload and calls the Cloud API. Run it inside your network if abas is not exposed, and open only outbound HTTPS to Meta.
- 4
Register templates
Submit utility templates for order status, delivery and reminders with named placeholders. Marketing-style wording gets classified differently and costs more, so keep the wording transactional.
- 5
Handle inbound replies
Meta calls a webhook on your relay. Match the sender number to a known contact, parse buttons or short keywords, and write only to a staging field or user-defined note, never directly to posted quantities or prices.
- 6
Log and monitor
Store message id, template, abas record reference and status in the relay's own table so support can answer 'was this sent' without opening WhatsApp.
Example flows
Shipment notice
Trigger: A delivery note is posted in abas for a customer with a stored mobile number.
- The relay picks up the new delivery note from the read model.
- It resolves the contact and checks opt-in status in its own table.
- It sends the 'shipment_dispatched' template with order number and tracking link.
- Delivery and read receipts update the relay log.
Result: The customer gets the notice in seconds and the order desk sees fewer 'where is my order' calls.
Supplier confirms or reschedules
Trigger: A purchase order is released and the supplier has an opted-in WhatsApp contact.
- Relay sends the order summary with Confirm and New date buttons.
- Supplier taps Confirm, or replies with a date.
- Relay validates the date format and writes it to a review field on the PO line.
- A buyer sees changed dates in an infosystem list and accepts or rejects them.
Result: Confirmations arrive the same day, and the buyer stays in control of the actual delivery date.
Keeping data on-prem
A typical on-prem abas server is not reachable from the internet and should not be. Run the relay on a host in the same network segment as abas, give it a service account with read-only EDP or REST rights plus a narrow write path for the staging fields, and let it initiate outbound HTTPS connections to the WhatsApp Cloud API. For inbound webhooks, put a thin receiver in a DMZ or a cloud function that queues messages, and let the internal relay pull them, so no inbound port to the ERP network is opened. WhatsApp itself is a cloud service, so message content leaves your premises by design: keep templates free of prices, drawings and personal data beyond what is needed.
Security checklist
- Use a dedicated abas service user with the minimum read rights and a separate narrow write right, not a named employee account.
- Store Meta access tokens in a secrets manager, rotate them, and never place them in abas scripts.
- Record explicit opt-in per contact and honour opt-out keywords; WhatsApp enforces this and can restrict a number that ignores it.
- Verify the webhook signature from Meta on every inbound call and reject unsigned traffic.
- Keep personal data in the message minimal, and review GDPR obligations including the data processing agreement with the platform provider.
Ways to get it done
Build a relay in-house
Effort: Roughly 3 to 6 weeks including Meta onboarding and templates.
Teams with a Java or .NET developer who already knows EDP or the abas REST API and want full control over wording and flow.
Use a BSP or no-code automation tool with a generic connector
Effort: Days to a couple of weeks, but limited two-way logic.
Low volume notifications where a database export or CSV drop from abas is enough.
Work with a partner such as Netray
Effort: A scoped pilot of a few weeks, then extend flow by flow.
You want the ERP-side read model, the relay, replies and an optional AI layer for free-text replies built and documented together.
Pitfalls
- !Missing or messy mobile numbers in contact records: clean and normalise to E.164 before launch.
- !Sending free-form messages outside the 24-hour window, which WhatsApp blocks; use approved templates.
- !Letting inbound replies write straight into posted documents; route them through a review field.
- !Polling the ERP too aggressively and loading the application server during month end.
- !Forgetting that a shared plant phone number mixes personal and business contacts and breaks opt-in tracking.
Frequently asked questions
Does abas ERP have a built-in WhatsApp feature?
Not as a standard function that we can point to for every version. Most abas sites connect WhatsApp through a relay service that reads data via EDP or REST and calls the WhatsApp Business Platform. Check your abas release and any add-on modules before building.
Can replies from WhatsApp update abas automatically?
Technically yes, but we recommend writing to a staging field or note first and having a person or a rule accept the change. That avoids bad dates or quantities landing in posted documents from a free-text reply.
Do we need to expose abas to the internet?
No. Run the relay inside your network, make only outbound calls to Meta, and receive webhooks through a small receiver in a DMZ or cloud queue that your relay pulls from.
What does it cost to run?
Meta charges per conversation or message category depending on the current pricing model, plus any BSP fee and your hosting. Transactional utility messages are generally cheaper than marketing ones. Check Meta's current rate card for your country.
Can AI read the replies?
Yes. A small open-weight model running locally can classify a reply as confirm, reject or reschedule and extract a date, with the result still going to a review field before any ERP update.
Want WhatsApp working on your abas ERP?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment