How to add WhatsApp to SYSPRO
Short answer
SYSPRO has no built-in WhatsApp channel, so you connect the WhatsApp Business Platform (Cloud API or a BSP) to SYSPRO through an integration layer that reads data via e.net business objects or SQL Server and writes replies back through business objects. Start with outbound template messages, then add two-way replies with human review.
SYSPRO customers are often mid-sized discrete and process manufacturers and distributors, many on-prem on SQL Server, with sales teams, drivers and suppliers who live on WhatsApp rather than in the SYSPRO client. The pain is familiar: customers ask for order status by message, suppliers confirm dates by voice note, and someone retypes it all into SYSPRO.
WhatsApp is a good fit for short, structured, high-frequency exchanges: order acknowledgements, ship notices, delivery slots, supplier date confirmations and quick approvals. It is a poor fit for anything that needs a full document or a long thread, which should stay in email or the SYSPRO document store.
What teams use it for
Order and dispatch status for customers
Send an approved template when a sales order is released, dispatched or invoiced, and let the customer reply with a PO number or order number to get current status back without calling the desk.
Supplier date confirmation
Message suppliers about open purchase order lines that are due or late, parse a reply such as a new ship date, and queue the change for a buyer to approve before it touches the PO.
Delivery and driver updates
Notify customers of a delivery window and collect proof such as a photo or a name from the driver's number, attached to the dispatch note for audit.
Quote and credit approvals
Push a quote or a credit-hold release request to a manager as a short message with Approve and Reject quick-reply buttons, and log the decision with the approver's identity.
Internal shortage alerts
Alert a planner or production supervisor when a job is short of a component or a due date slips, with the job number and the item, drawn from SYSPRO WIP and inventory data.
SYSPRO integration surface
- SYSPRO e.net Solutions business objects (XML in, XML out) such as the sales order, purchase order and inventory query objects. Exact object names and parameters vary by version, so check the e.net documentation for your release.
- The SYSPRO e.net REST or web service layer in current SYSPRO 8 releases, where available, as an HTTP-friendly way to call business objects from a middleware service.
- Direct read access to the SYSPRO company SQL Server databases (for example SorMaster, SorDetail, PorMasterHdr, PorMasterDetail, ArCustomer, ApSupplier) for status lookups. Treat this as read-only and avoid writing to tables directly.
- SYSPRO Workflow Services and trigger or event hooks, where your edition offers them, to start an outbound message when a status changes without polling.
- Customer and supplier contact fields in the SYSPRO masters, which usually need a mobile number held in a consistent international format and an opt-in flag you maintain yourself.
How it works
- 1
Register the WhatsApp Business account
Choose the Cloud API directly through Meta or a business solution provider. Verify the business, register a sending number, and submit message templates for approval, because anything outside a customer's 24-hour service window must be a template.
- 2
Stand up a small middleware service
Run it on your network or in your cloud. It holds the WhatsApp access token, receives inbound webhooks, and talks to SYSPRO. Keep SYSPRO unaware of WhatsApp so the channel can change later.
- 3
Detect the SYSPRO event
Either poll a read-only SQL view for status changes since the last run, or have a SYSPRO workflow or trigger call your middleware. Polling every few minutes is usually enough and is easier to support.
- 4
Map recipients and consent
Resolve the customer or supplier contact to a mobile number, check your stored opt-in, and pick the right template and language. Skip and log anything without consent.
- 5
Send and track delivery
Call the Cloud API, store the message ID against the SYSPRO order or PO reference, and update status from delivery and read webhooks so support can see what was sent.
- 6
Handle inbound replies
Match the sender number and any quoted reference to a SYSPRO document. For read-only requests such as status, answer automatically. For changes, create a proposed update for a user to approve, then apply it through an e.net business object.
Example flows
Dispatch notification with delivery slot choice
Trigger: A sales order line moves to dispatched in SYSPRO.
- Middleware sees the status change and finds the customer contact number.
- A dispatch template is sent with order number, carrier and expected date.
- The customer taps a quick reply to choose a morning or afternoon slot.
- The reply is stored and a proposed delivery note comment is queued for the dispatcher.
Result: Fewer status calls and a recorded delivery preference the dispatcher can see.
Supplier confirms a late purchase order
Trigger: A purchase order line is past its due date.
- Middleware reads the open line from SQL Server and finds the supplier contact.
- A template asks the supplier to confirm a new ship date.
- The supplier replies with a date in free text.
- The reply is parsed, shown to the buyer with the original line, and applied on approval.
Result: Promise dates stay current in SYSPRO without the buyer retyping messages.
Keeping data on-prem
On-prem SYSPRO does not need to be exposed to the internet for WhatsApp to work. Keep SYSPRO and SQL Server inside your network, run the middleware in a DMZ or on an internal host, and allow only outbound HTTPS to the WhatsApp Cloud API plus an inbound webhook endpoint published through a reverse proxy with signature verification. Message content leaves your network to Meta by design, so keep payloads minimal: an order number and a date, not pricing or drawings. If free-text replies need AI parsing, run an open-weight model locally so customer messages are not sent to a third-party model.
Security checklist
- Verify the webhook signature on every inbound call and reject anything unsigned.
- Store the access token in a secrets manager, not in config files on the SYSPRO server.
- Use a dedicated SYSPRO operator with the minimum business-object permissions for write-back.
- Keep personal data in messages to the minimum and honour opt-out keywords immediately.
- Log every message and every resulting SYSPRO change with the sender number and approver.
Ways to get it done
Off-the-shelf connector or BSP workflow tool
Effort: Days to a couple of weeks, plus template approval time.
Simple outbound notices from a status field, no replies into SYSPRO. Check the SYSPRO ecosystem and your BSP for existing connectors.
Build in-house on e.net and the Cloud API
Effort: A few weeks for notices, longer for reliable two-way flows.
You have developers comfortable with SYSPRO business objects and want full control of templates and logic.
Partner build with Netray
Effort: Scoped per flow, typically weeks for a first production flow.
You want replies understood and routed into SYSPRO with approval, optionally with a private on-prem model for parsing.
Pitfalls
- !Sending free-form text outside the 24-hour window fails, so every proactive message needs an approved template.
- !Mobile numbers stored with spaces, local prefixes or extensions in SYSPRO contact fields will not match, so normalise to international format first.
- !Writing replies straight into SYSPRO without review lets a mistyped date or quantity corrupt supply plans.
- !Polling SQL Server heavily during month-end can slow the SYSPRO client, so poll a light view on an index.
- !Forgetting that one phone number may serve several customer accounts, which breaks reply matching.
Frequently asked questions
Does SYSPRO have a native WhatsApp integration?
Not as a core feature that we can point to across versions. You normally connect the WhatsApp Business Platform through middleware that reads SYSPRO data and writes back through e.net business objects. Check with your SYSPRO partner whether a marketplace connector exists for your release before building.
Can customers ask SYSPRO for order status over WhatsApp?
Yes. Middleware receives the message, matches the sender and order reference, queries SYSPRO read-only, and replies with a status template or session message. Keep it to read-only answers at first, and never expose another customer's data if numbers are shared.
Do I need SYSPRO 8 for this?
Not strictly. The pattern works with any version that exposes e.net business objects or a readable SQL Server database. Newer releases make HTTP access easier. Exact object names and the available web service options vary by version, so confirm them against your installed release.
Is WhatsApp safe for supplier and pricing data?
Treat it as a notification channel, not a document store. Send references and dates, keep prices and drawings in SYSPRO or email, and rely on end-to-end encryption plus your own logging. If your contracts forbid certain data on third-party platforms, do not send it.
Can AI read the free-text replies?
It can, to extract a date or a yes or no. Use a model that runs on your own hardware if the content is sensitive, return a confidence value, and route low-confidence replies to a person. The result should still be a proposed change that a user approves.
Want WhatsApp working on your SYSPRO?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment