How to add WhatsApp to Oracle Fusion Cloud ERP
Short answer
Connect the WhatsApp Business Platform to Oracle Fusion by listening to Fusion business events (through Oracle Integration or an outbound event feed), sending approved template messages, and writing replies back through the Fusion REST APIs. Keep a small middle service in charge of opt-in records, phone number mapping and approval checks.
Fusion Cloud ERP customers rarely lack data. What they lack is a channel their suppliers, drivers and plant supervisors will actually answer. Buyers chase purchase order confirmations by email for days, while the same supplier answers a WhatsApp message in minutes. That gap is why teams on Fusion Procurement, Inbound Logistics and Manufacturing ask for WhatsApp.
Fusion is a SaaS suite, so you do not install anything inside it. Everything runs through its supported extension points: REST resources under the fscmRestApi and similar roots, business events, scheduled ESS jobs, BI Publisher reports and Oracle Integration. WhatsApp sits outside, on Meta's Cloud API or through a Business Solution Provider, and a thin service joins the two.
The hard parts are not the API calls. They are template approval by Meta, opt-in proof, mapping a WhatsApp number to a Fusion supplier site contact or employee, and making sure a reply like 'confirmed' can only change what that person is allowed to change.
What teams use it for
Supplier PO acknowledgement
When a purchase order is approved and communicated, send a template message with PO number, lines and promise date, and let the supplier reply CONFIRM or propose a new date.
Inbound shipment alerts
Notify the receiving team and the buyer when an advance shipment notice arrives or an in-transit receipt is overdue against the expected date.
Mobile approvals for requisitions
Send a requisition summary to an approver and take APPROVE or REJECT replies, then complete the matching task in the approval workflow.
Customer order status
Let a customer text an order number and receive sales order status, ship date and tracking, read from order management.
Expense and invoice exceptions
Ping an employee when an expense report is returned, or a requester when an invoice is on hold for a price mismatch.
Oracle Fusion Cloud ERP integration surface
- REST resources for purchase orders, requisitions, receiving, sales orders and suppliers, versioned in the URL (for example 11.13.18.05); exact version and resource names depend on your release update.
- Business events raised by Fusion applications (such as PO approval) that Oracle Integration can subscribe to, or that can be pushed to an external endpoint by event subscription where your release supports it.
- BI Publisher reports and OTBI analyses as a polling fallback when an event does not exist for the status you care about.
- Approval tasks run in the BPM worklist, with task actions exposed through the human workflow REST API on supported releases.
- Oracle Integration (OIC) adapters for the ERP Cloud, plus generic REST adapters for calling the WhatsApp Cloud API.
How it works
- 1
Pick the messages first
List the three or four notifications that justify a template (PO sent, ASN overdue, approval needed). Each needs a Meta-approved template with fixed wording and variables.
- 2
Set up the WhatsApp Business Platform
Register a business account and number with the Cloud API or a BSP, submit templates, and configure a webhook URL that will receive inbound messages and delivery status.
- 3
Capture the trigger from Fusion
Subscribe to the relevant business event in Oracle Integration, or schedule a BI Publisher query through ESS and have OIC pick up new rows.
- 4
Resolve the recipient
Map supplier site contact, employee or customer contact to an E.164 number and an opt-in record held in your own table, not only in Fusion.
- 5
Send and track
Call the messages endpoint with the template and variables, store the message ID against the PO or order, and update status on delivery webhooks.
- 6
Handle the reply
Parse the inbound reply, find the open document by stored context, check that the sender is the registered contact, and call the Fusion REST API or complete the worklist task.
- 7
Log everything
Write each send, reply and ERP change to an audit table so a buyer can see exactly what the supplier said and when.
Example flows
PO acknowledgement by WhatsApp
Trigger: A purchase order reaches the Communicated state for a supplier flagged for WhatsApp.
- OIC receives the event and reads the PO header and schedule lines through the REST API.
- The service picks the supplier contact number and checks the opt-in record.
- A template message goes out with PO number, total and requested date.
- The supplier replies CONFIRM or a new date; the service validates the sender.
- The promised date is written to the PO schedule through a change order flow, not a silent edit.
Result: Confirmations arrive in minutes, and the buyer only handles real exceptions.
Requisition approval on a phone
Trigger: A requisition over a threshold lands in an approver's worklist.
- A poll or event delivers the task ID and requisition summary.
- The approver receives a short template with requester, amount and cost center.
- A quick-reply button returns APPROVE or REJECT.
- The service completes the task as that user's delegated action or routes it to the approver's own sign-in link.
Result: Approvers act between meetings, with the ERP approval history still intact.
Keeping data on-prem
Fusion itself is Oracle's cloud, so the question is where the glue and any AI run. Keep the middle service in your own VPC or data center, reach Fusion over its public HTTPS endpoints with integration-user credentials, and call WhatsApp from there. If you add AI to read free-text replies ('can do Friday if you split the order'), run an open-weight model on your own GPUs so supplier text and order data never go to a third-party model API. Only the template text and variables cross to Meta, which is a design choice you control.
Security checklist
- Use a dedicated Fusion integration user with a narrow role, never a named buyer's credentials.
- Store opt-in evidence and phone mappings yourself; verify the sender number against the registered contact before acting.
- Keep templates free of pricing detail or margins when the message may be forwarded.
- Verify the webhook signature from Meta and rotate tokens; log every ERP write with the originating message ID.
- Require a change order or human confirmation for anything that alters price or quantity.
Ways to get it done
Oracle Integration plus a BSP
Effort: Typically a few weeks for two or three message types.
Teams already licensed for OIC that want standard notifications and simple replies.
Build a custom service
Effort: Several weeks plus ongoing template and token maintenance.
Teams with engineers who want full control of mapping, retries and reply parsing.
Work with a partner such as Netray
Effort: A scoped pilot on one flow, then extend.
Manufacturers who want reply understanding by a private model and strict write-back controls.
Pitfalls
- !Sending outside the 24-hour window without an approved template; Meta will reject it.
- !Treating any reply from a number as authoritative when several people share a supplier phone.
- !Updating the PO directly and bypassing change order rules that the auditors rely on.
- !Polling BI reports too often and hitting concurrency limits on the Fusion pod.
- !Forgetting that business event names and payloads vary by release update; test after each quarterly update.
Frequently asked questions
Does Oracle Fusion have native WhatsApp support?
Not as a built-in channel in the core ERP applications. Fusion offers email and notification features, and some Oracle CX products have messaging channels, but for ERP procurement and logistics you typically connect WhatsApp through Oracle Integration or a custom service.
Can a supplier approve or change a PO by WhatsApp?
Technically yes, but treat it as a request. Confirmations are safe to write back. Date or quantity changes should go through your normal change order process, with the reply attached as evidence.
Do I need a BSP or can I use the Cloud API directly?
You can call Meta's Cloud API directly if you can host a webhook and handle templates yourself. A BSP adds dashboards, number management and support. Either way the Fusion side is identical.
How do I handle opt-in?
Capture consent before the first template, for example through a supplier onboarding form or portal, and store the proof with a timestamp. Honor STOP replies immediately and flag the contact in your mapping table.
Can AI read free-text supplier replies?
Yes. A private model can classify intent, extract dates and flag ambiguity, then pass a structured proposal to a buyer. It should suggest, not commit, until a person confirms.
Want WhatsApp working on your Oracle Fusion Cloud 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