# How to add WhatsApp to Infor SyteLine

> Source: https://netray.co/integrations/infor-syteline-whatsapp
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Integrations

## Short answer

Put a small middleware service between SyteLine and the WhatsApp Business Platform (Cloud API or a BSP). SyteLine pushes events out through Application Event System handlers or ION, the service sends approved template messages, and customer or supplier replies come back as IDO REST calls. It works on-prem and in CloudSuite Industrial, with different auth in each.

## System

Infor SyteLine (CloudSuite Industrial)

## Capability

whatsapp

## Intro

Most SyteLine shops already run on email and phone for the conversations that matter: where is my order, did the PO ship, can you confirm the new date. Customers and suppliers in India, Latin America, the Middle East and Southeast Asia increasingly expect those answers on WhatsApp, and your planners are already using personal WhatsApp to chase vendors. The result is order data living in chat threads that never touch the ERP.

SyteLine does not ship a WhatsApp connector, so this is an integration project. The good news is that SyteLine's Mongoose framework exposes almost everything through IDOs (Intelligent Data Objects), and those are reachable over a REST service, so the SyteLine side is well understood. The harder parts are WhatsApp policy (opt-in, template approval, the 24 hour customer service window) and getting identity right when a phone number replies.

This page walks through a design that keeps SyteLine as the system of record, treats WhatsApp as a messaging channel only, and routes every inbound reply through validation before it changes anything.

## Use Cases

### Customer order status on demand

**Description:** A buyer messages 'status PO 4471' and gets the customer order line status, promise date and tracking number read from the customer order (co/coitem) IDOs, no CSR in the loop.

### Shipment and delivery alerts

**Description:** When a packing slip is shipped in SyteLine, a template message goes to the customer contact with carrier, tracking number and expected delivery.

### Supplier PO confirmation

**Description:** Released purchase orders trigger a template to the vendor contact asking to confirm date and quantity. A button reply updates a custom field on the PO line for the buyer to review.

### Late-order escalation to planners

**Description:** When a job or PO line slips past its due date after an MRP run, the planner on that item gets a message with the item, the shortage and a link into the SyteLine form.

### Approvals for expedite requests

**Description:** A manager receives a quick-reply message to approve an expedite or a rush freight charge, and the decision is logged back with the approver's mapped SyteLine user.

### Field service and installation updates

**Description:** Service technicians send a photo and a short note, which the integration attaches to the related service or project record as a document.

## System Surface

IDO REST service on the Mongoose application server: load collections such as the customer order, customer order line, purchase order and item IDOs with filter and property lists, and invoke IDO methods for standard business logic.

Application Event System (AES): event handlers fire on IDO or form events, and an action can call an IDO method or a stored procedure. This is the cleanest way to emit 'order shipped' or 'PO released' without polling.

Infor ION (on CloudSuite Industrial and most current on-prem installs via Infor OS): publishes BODs for documents like sales orders and shipments, and ION API Gateway fronts REST calls with OAuth2 service accounts. Exact BOD names and availability vary by version.

Direct SQL Server access for read-only reporting, using a dedicated reader account against replicas or views. Fine for look-ups, but writes should always go through IDOs so business logic and validation run.

Contact and notification data: customer and vendor contact phone numbers are usually in contact-related tables and custom user-defined fields. Plan a clean 'WhatsApp number' and 'opted in' field rather than parsing free-text phone fields.

## How It Works

### Choose the WhatsApp access path

**Detail:** Use the Meta Cloud API directly if you have a verified business and an engineer, or a Business Solution Provider if you want console tooling and shared inbox features. Both give you template management and webhooks.

### Build a small middleware service

**Detail:** A stateless service that owns WhatsApp credentials, the webhook endpoint for inbound messages, and a queue. SyteLine never talks to Meta directly, which keeps secrets and outbound firewall rules in one place.

### Emit events from SyteLine

**Detail:** Create AES event handlers on shipment, PO release and promise-date change that call a lightweight outbound action, or subscribe to the relevant ION BODs. Include only keys (order number, line, release) and let the middleware fetch details.

### Enrich through the IDO REST service

**Detail:** The middleware reads the exact fields it needs using a service account scoped to read-only IDOs. Never send raw ERP rows to WhatsApp, format a short message with only what the recipient is entitled to see.

### Register and approve templates

**Detail:** Notifications that start a conversation must use pre-approved templates. Write short, parameterised templates for shipment, PO confirmation and delay notices, and keep marketing language out so they are categorized as utility.

### Handle inbound replies with identity checks

**Detail:** Map the sender's phone number to a customer contact or vendor contact. Unknown numbers get a canned reply and no data. Known numbers can run a small set of intents such as status or confirm.

### Write back through IDO methods, with review

**Detail:** A confirmation updates a staging field or an approval record. Anything that changes quantities, prices or dates goes to a planner queue first. Log every message ID against the SyteLine document for audit.

## Example Flows

### Shipment notification with tracking

**Trigger:** A packing slip is shipped in SyteLine and an AES handler fires on the shipment IDO.

**Steps:**

- Handler posts the order number, line and shipment sequence to the middleware.
- Middleware reads carrier, tracking number and ship date via the IDO REST service.
- It looks up the customer contact's WhatsApp number and opt-in flag.
- It sends the approved shipment template with order and tracking as parameters.
- Delivery and read receipts are stored against the shipment record.

**Result:** The buyer knows about the shipment minutes after it leaves the dock, and CSRs get fewer 'where is it' calls.

### Supplier confirms a purchase order

**Trigger:** A buyer releases a PO in SyteLine and the event handler fires.

**Steps:**

- Middleware pulls PO header, lines, due dates and the vendor contact.
- It sends a template with quick-reply buttons: Confirm, Change date, Cannot supply.
- The vendor taps a button, and Meta posts the reply to the webhook.
- Middleware matches the reply to the PO line and writes a confirmation status to a custom field through an IDO update.
- For 'Change date' the vendor is asked for a new date, which is recorded as a proposed date for the buyer.

**Result:** Buyers see confirmation status in SyteLine without reading chat threads, and date changes wait for approval.

## On Prem

On-prem SyteLine does not need to be exposed to the internet. Run the middleware inside your network or DMZ, let it call the IDO REST service internally, and allow only outbound HTTPS to the WhatsApp endpoints plus an inbound webhook path published through a reverse proxy or a relay. WhatsApp message content passes through Meta's infrastructure, so for regulated or export-controlled work keep messages to status and identifiers, never drawings, part specifications or controlled technical data. If you want natural-language replies, run the language model locally and keep it to a fixed set of read-only tools.

## Security

- Use a dedicated SyteLine service user with read-only IDO permissions plus narrow write access to specific custom fields, never a shared admin login.
- Verify the webhook signature header on every inbound request and reject unsigned calls.
- Store opt-in evidence (timestamp, source) per contact and honor opt-out keywords immediately.
- Never include prices, costs or controlled technical data in messages unless the recipient role is entitled to them in SyteLine.
- Keep an audit table of message ID, SyteLine document, template and result, with retention matching your records policy.

## Options

### Off-the-shelf BSP workflow tool plus CSV or webhook export

**Fit:** Small volumes, one or two notification types, no inbound logic.

**Effort:** Days, but you will maintain the SyteLine export or trigger yourself.

### Build in-house middleware against IDO REST and AES

**Fit:** Teams with a developer who knows Mongoose and wants full control.

**Effort:** Typically a few weeks for outbound alerts, longer with two-way flows.

### Partner build with Netray

**Fit:** When you want inbound intents, an approval layer, and optionally a local model for natural-language status questions.

**Effort:** Scoped per flow after a short discovery on your version and hosting.

## Pitfalls

- Sending templates to numbers without recorded opt-in, which risks quality rating drops and blocked sending.
- Polling SyteLine tables on a timer instead of using AES or ION events, which loads the database and misses ordering.
- Treating a phone number as proof of identity for anything beyond read-only status.
- Using one global service account that bypasses SyteLine site and user restrictions.
- Forgetting the 24 hour window: free-form replies only work after the customer messages you, so confirmation requests need a template.

## Faq

### Does Infor SyteLine have native WhatsApp support?

**Answer:** No native connector that I can point to. You integrate through the IDO REST service, Application Event System handlers or ION, and a WhatsApp Business Platform account. Check your Infor OS or marketplace catalog for third-party apps, since availability changes by region and version.

### Can this work with on-premises SyteLine?

**Answer:** Yes. The middleware runs inside your network, calls the IDO REST service locally, and only needs outbound HTTPS to WhatsApp plus a published webhook path. You do not have to open SyteLine itself to the internet.

### Can customers place orders through WhatsApp?

**Answer:** Technically yes, but it is a poor first project. Start with read-only status and notifications, then add order entry only with structured forms, price and credit validation, and a human review step before the order is committed.

### Which messages need a pre-approved template?

**Answer:** Anything you initiate outside the 24 hour customer service window, such as shipment alerts or PO confirmation requests. Replies inside that window can be free-form. Template categories and rules are set by Meta and change, so check current policy before launch.

### How do replies get back into SyteLine safely?

**Answer:** Through the middleware, which identifies the sender, parses a limited set of intents, and writes via IDO methods to a staging field or approval queue. Anything that alters quantities, prices or dates is reviewed by a planner before it commits.

## Search terms

infor syteline whatsapp integration, whatsapp for infor syteline, syteline whatsapp api, cloudsuite industrial whatsapp, syteline order status whatsapp, syteline shipment notification whatsapp, whatsapp business api erp manufacturing, add whatsapp to syteline, syteline supplier po confirmation whatsapp, infor syteline customer notifications

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json