# How to add WhatsApp to JD Edwards EnterpriseOne > Source: https://netray.co/integrations/jd-edwards-whatsapp > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Integrations ## Short answer Connect the WhatsApp Business Platform (Cloud API or a BSP) to JD Edwards through the AIS Server and Orchestrator. Outbound alerts are triggered by Real Time Events or scheduled orchestrations; inbound replies call an orchestration that writes back to the right JDE application. Keep template messages free of sensitive pricing and put a human approval step in front of any write. ## System JD Edwards EnterpriseOne ## Capability whatsapp ## Intro Many JD Edwards EnterpriseOne shops run on-prem or in a customer-hosted cloud, with a small number of power users who live in the web client and a much larger group of buyers, drivers, supervisors and suppliers who live on their phones. The gap is familiar: a sales order ships, a purchase order is promised late, an approval waits in a Work Center queue, and nobody outside JDE finds out until someone phones. WhatsApp is the channel most suppliers, drivers and field technicians already use, especially in India, the Middle East, Latin America, Africa and Southeast Asia. The goal is not a chatbot gimmick. It is a controlled two-way channel where JDE events produce a short message and a reply becomes a validated transaction. The good news is that EnterpriseOne already ships the pieces you need: the AIS (Application Interface Services) Server exposes REST services, Orchestrator turns a sequence of form and data service calls into a callable endpoint, and Real Time Events can push changes out. What is missing is the WhatsApp side, the template governance, and the identity mapping between a phone number and an Address Book or user record. ## Use Cases ### Shipment and delivery notices to customers **Description:** When ship confirm completes for a sales order (P4205 / F4201 and F4211 status change), send the customer contact a template with carrier, tracking reference and expected date. ### Supplier confirmation of purchase order promise dates **Description:** Send the buyer's open PO lines (F4311) to a supplier contact and let them reply with a date. The reply updates the promised date through a controlled orchestration. ### Approval requests for vouchers and requisitions **Description:** Notify an approver that a requisition or voucher is waiting in the Work Center, with a Yes or No quick reply that maps to the approval action. ### Driver and dock coordination **Description:** Message inbound carriers with dock door and appointment time derived from open receipts, and capture an arrival confirmation. ### Field service and maintenance dispatch **Description:** For shops using Capital Asset Management or Service Management, push a work order assignment to a technician and capture completion notes. ### Overdue invoice nudges **Description:** Send a polite reminder for past-due receivables (F03B11) to opted-in customer contacts, with a link to a payment portal rather than account details in the message. ## System Surface AIS Server REST: Form Service, Data Service and Orchestrator endpoints behind a token or basic-authenticated session; the standard route for calling JDE from outside. Version and path names vary by Tools release. Orchestrator Studio: build orchestrations that wrap form interactions, data requests and business function calls into a single REST call, with input and output mapping and rules. Real Time Events (RTE) and Notifications: publish events such as order or PO changes to a listener, and trigger orchestrations from them. Tools release determines the exact set of supported event types. Tables as the read model: F4201/F4211 for sales orders, F4301/F4311 for purchase orders, F0101/F0111 for Address Book and contacts, F0116 for addresses. Read through AIS rather than direct SQL where you can. Business Services (BSSV) and Business Functions for older integrations, and Workflow or Work Center for approval routing. Scheduled orchestrations or UBE-driven exports as a fallback for sites that cannot expose event listeners. ## How It Works ### Register a WhatsApp sender **Detail:** Create a WhatsApp Business Account with Meta (Cloud API) or go through a business solution provider. Verify the business, register the number, and request the message templates you need. Utility templates for order and delivery updates are the usual starting point. ### Map phone numbers to JDE identities **Detail:** Store opt-in status and a verified mobile number against the Address Book contact (F0111 or a user-defined table). Never accept a reply from an unmapped number as an authenticated transaction. ### Create a JDE integration user and orchestrations **Detail:** Use a dedicated JDE user with narrow security. Build orchestrations such as GetOrderStatus, ConfirmPoPromiseDate and ApproveRequisition in Orchestrator Studio, each doing one thing with validated inputs. ### Detect the trigger **Detail:** Use a Real Time Event or notification where available. Otherwise schedule an orchestration that polls for status changes since the last run and records a watermark so messages are not repeated. ### Run a middle service **Detail:** A small service (in your DMZ or private cloud) receives the JDE event, picks the template, fills variables and calls the WhatsApp Cloud API. It also exposes the webhook that WhatsApp calls for inbound messages. ### Handle inbound replies **Detail:** Verify the webhook signature, resolve the sender, parse the reply (quick-reply buttons are far safer than free text), and call the matching orchestration. Log the full exchange. ### Add approval and monitoring **Detail:** Route anything that changes money or dates through a review state first. Monitor template quality ratings, delivery failures and AIS error rates. ## Example Flows ### Supplier confirms a late purchase order **Trigger:** A scheduled orchestration finds PO lines in F4311 whose promised date is within three days and not yet confirmed. **Steps:** - The middle service looks up the supplier contact and opt-in flag. - It sends a template with PO number, item description and the current date, plus Confirm and Change buttons. - On Change, the supplier replies with a date; the service validates it is a future date. - The ConfirmPoPromiseDate orchestration is called in proposed mode and a buyer is notified to accept. **Result:** The buyer sees a supplier-confirmed date without chasing by phone, and the PO is updated only after a person accepts it. ### Delivery notice to a customer **Trigger:** Ship confirmation updates the order status on F4211. **Steps:** - The event reaches the middle service with the order number and ship-to. - The service fetches carrier and tracking through GetShipmentSummary. - A utility template goes to the opted-in receiving contact. **Result:** Customers stop calling customer service to ask where the order is. ### Mobile approval of a requisition **Trigger:** A requisition reaches an approver's queue in Work Center. **Steps:** - The service sends requester, amount band and a link to the approval screen. - The approver taps Approve or Reject. - The reply is mapped to the approval orchestration for that approver only. - A confirmation message with the new status is returned. **Result:** Approval latency drops for people who are away from a desk, with the audit trail kept in JDE. ## On Prem Your JDE stack can stay entirely on-prem. Only the middle service needs outbound HTTPS to Meta's endpoints and an inbound HTTPS webhook path, which you can place in a DMZ reverse proxy that forwards only that single route. JDE itself does not need to be reachable from the internet: the middle service calls the AIS Server over your internal network. If message content could reveal customer or pricing data, send only identifiers and a link to an authenticated page. If you add an AI layer to interpret free-text replies, run an open-weight model locally so supplier text never leaves your network. ## Security - Use a dedicated JDE integration user with minimal application security, and never reuse a personal login in the middle service. - Verify the Meta webhook signature on every inbound call and reject anything unsigned or replayed. - Keep opt-in records, template versions and message logs for audit and for WhatsApp policy compliance. - Avoid prices, bank details and personal data in message bodies; use short links to authenticated pages instead. - Require a second approval for any reply that changes a date, quantity or amount. ## Options ### Off-the-shelf connector from a BSP or integration platform **Fit:** Good for simple outbound alerts if the vendor has a JDE or generic REST connector you can point at AIS. **Effort:** Days to a few weeks; limited two-way logic. ### Build in-house on AIS and Orchestrator **Fit:** Best when you have JDE developers and want full control of identity mapping and approvals. **Effort:** A few weeks for a first flow; ongoing template and policy management. ### Partner build with Netray **Fit:** Useful when you want replies understood by a private model, multiple flows, and on-prem hosting handled for you. **Effort:** Scoped per flow; typically a pilot followed by expansion. ## Pitfalls - Sending marketing-style messages from a utility template, which gets the template rejected or the number's quality rating lowered. - Skipping the 24-hour customer service window rules and trying to send free text outside it. - Matching a reply to the wrong order because the message carried no correlation identifier. - Polling JDE without a watermark, causing duplicate notifications after a restart. - Letting a supplier reply change a promised date directly, with no buyer review. ## Faq ### Does JD Edwards have a native WhatsApp connector? **Answer:** Not as a standard feature. You normally integrate through the AIS Server and Orchestrator, or use a third-party platform that can call REST services. The WhatsApp side is handled through the Cloud API or a business solution provider. ### Can I use Orchestrator alone without custom code? **Answer:** For the JDE half, yes: Orchestrator exposes secure REST endpoints. You still need a small service for the WhatsApp webhook, template selection and identity checks, because Orchestrator is not a messaging gateway. ### Do I need to expose JD Edwards to the internet? **Answer:** No. The middle service calls AIS over your internal network. Only the WhatsApp webhook endpoint needs to be reachable from outside, and it can sit behind a reverse proxy. ### Is WhatsApp acceptable for approvals? **Answer:** It can be, if the approver identity is verified, the action is limited to approve or reject with context, and the decision is logged in JDE. Many finance teams still restrict high-value approvals to the web client. ### Will this work with older JD Edwards releases or World? **Answer:** EnterpriseOne with a Tools release that includes AIS and Orchestrator is the smooth path. Older releases or JD Edwards World usually need Business Services, flat-file exports or a different adapter, so check your release first. ## Search terms jd edwards whatsapp integration, whatsapp for jd edwards, jd edwards enterpriseone whatsapp, jde whatsapp api, jd edwards purchase order whatsapp, jd edwards orchestrator whatsapp, jde ais server whatsapp, send whatsapp from jd edwards, whatsapp supplier confirmation erp --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json