How to add WhatsApp to IFS Cloud
Short answer
Add WhatsApp to IFS Cloud by pairing a WhatsApp Business Platform number (Cloud API or a BSP) with a small middleware service. The service listens to IFS Business Events or polls OData projections for outbound messages, and writes inbound replies back through projections or IFS Connect with a human check on anything that changes data.
IFS Cloud customers in manufacturing, aerospace and field service usually have the same gap: the people who must act on an ERP event (a supplier, a field technician, a plant manager on the road) are not logged into Aurena. They are on WhatsApp. A late purchase order line, a customer order that needs credit release or a work task that needs a yes or no sits in an inbox until someone opens the client.
WhatsApp fits because it is already on every phone, supports rich buttons and photos, and works for external parties such as suppliers and subcontractors who will never get an IFS user. The catch is that WhatsApp is a regulated channel with templates, opt-in rules and a 24 hour service window, and IFS Cloud is a layered platform where the supported integration path is projections and IFS Connect, not direct database access.
This page walks through the realistic architecture for both IFS Cloud managed by IFS and customer-managed deployments, what to build versus buy, and the places these projects tend to go wrong.
What teams use it for
Supplier confirmation of purchase order lines
Send a template message when a purchase order is released, with Confirm and Reschedule buttons. A reply with a new date becomes a proposed change to the PO line promised delivery date, held for a buyer to accept.
Field technician work task updates
Technicians receive a new work task summary and reply with a photo and a status word. The message is attached as a document to the task and the status change is staged for review.
Customer shipment notifications
When a shipment is closed for a customer order, send tracking and delivery window to the customer contact, and take a 'wrong address' reply back to customer service as a task.
Manager approvals on the move
Push a short approval card for a requisition or a customer order held for credit, with the key numbers, and take an Approve or Reject tap that is recorded against a named IFS user.
Shop order shortage alerts
Notify a planner on WhatsApp when a shop order operation is short of material, with part number, quantity and the supplying PO, so the conversation starts before the shift change.
Subcontractor and MRO turn-time chasers
For repair orders sent outside, ask the vendor on a schedule for status and expected return date, and log each answer on the order.
IFS Cloud integration surface
- OData REST projections: IFS Cloud exposes entities as projections under /main/ifsapplications/projection/v1/<ProjectionName>.svc, and the API Explorer lists the ones available in your release. This is the supported read and write path.
- Business Events and Event Actions: configure an event on an entity (for example a purchase order released) and an action that sends to a queue, a mail or a web endpoint through IFS Connect. Names and availability vary by release, so check your version's documentation.
- IFS Connect: the messaging layer for inbound and outbound integration, with routing addresses, connectors for REST and SOAP, and message queues with retry. Good for calling your middleware and receiving its callbacks.
- Authentication through the IFS identity layer using OpenID Connect: a service client with the client credentials flow is the normal pattern, with an IFS permission set limiting what the integration user can touch.
- Documents: the Document Management area (document reference objects) lets you attach inbound photos and PDFs to the originating order, task or part.
- Database access: in managed cloud you do not get direct Oracle access, and even on-premise you should treat PL/SQL internals as unsupported for integration.
How it works
- 1
Register a WhatsApp sender
Use Meta's WhatsApp Business Platform Cloud API directly or a Business Solution Provider. Verify the business, register a number that is not already on a personal WhatsApp account, and create display name and quality settings.
- 2
Create an IFS integration user and client
Create a service identity in IFS with a dedicated permission set limited to the projections you need. Note the token endpoint and scopes for your deployment.
- 3
Choose the event source
Prefer Business Events through IFS Connect for push. Where an event is not available for your entity, poll the projection with a modified-since filter on a short interval and keep a high-water mark.
- 4
Build the middleware
A small service maps IFS records to message templates, looks up the recipient's phone and opt-in status from a table you own, calls the WhatsApp API and stores message ids against the IFS key.
- 5
Handle inbound webhooks
WhatsApp posts replies to your HTTPS endpoint. Verify the signature, match the reply to the open conversation by message context, and parse buttons first, free text second.
- 6
Write back safely
Read-only facts can be written directly. Anything that changes dates, quantities or status goes to a review queue, then a projection action under the integration user.
- 7
Monitor and replay
Log every outbound and inbound message with its IFS key, and make the Connect queue replayable so a bad day does not lose approvals.
Example flows
PO confirmation loop
Trigger: A purchase order is released to a supplier
- Business Event posts the PO number to middleware via IFS Connect
- Middleware reads the order lines through the purchase projection
- Template message with line list and Confirm and Change date buttons goes to the supplier contact
- Supplier taps Change date and sends 14 June
- A proposed promised date is staged; the buyer accepts it in a review screen and the projection is updated
Result: The buyer sees supplier answers in minutes, not after a chased email, and the date change has an audit trail.
Technician photo to work task
Trigger: A work task is assigned to a field technician
- Technician gets a summary message with site contact and priority
- They reply on site with a photo and the word Done
- Middleware downloads the media within its expiry window and uploads it as a document on the task
- A completion request is queued for the dispatcher
Result: Evidence sits on the task record and dispatch confirms closure without phoning.
Credit hold approval
Trigger: A customer order lands on credit hold
- Poll or event identifies the held order
- Approver receives order value, customer balance and ageing
- Approver taps Release or Keep held
- Middleware calls the release action as the mapped IFS approver identity
Result: Orders stuck on hold move the same day, with the approver identity logged.
Keeping data on-prem
If you run IFS Cloud customer-managed or in a private cloud, keep the middleware inside your network and expose only the narrow webhook path WhatsApp needs through a reverse proxy. Message content, phone numbers and order data then never sit in a third party automation tool. WhatsApp itself is a cloud service, so decide what is allowed in a message: many defense and aerospace teams send only a reference number and a link to an authenticated page, and keep part details, drawings and anything export controlled out of the chat. For free-text understanding of replies, an open-weight model served on your own GPUs can classify intent without sending supplier text to a public API.
Security checklist
- Use a dedicated IFS service client with least privilege permission sets, never a shared named user.
- Verify the WhatsApp webhook signature and reject anything unsigned.
- Keep an opt-in register per phone number and purpose, and honour stop replies automatically.
- Do not put export-controlled or customer-confidential data in message bodies; send identifiers and deep links.
- Log message ids against IFS keys so an approval can be proven later.
Ways to get it done
Off-the-shelf BSP workflow tool plus IFS REST calls
Effort: A few weeks including template approval
Simple outbound notifications with few replies
Build in-house middleware on projections and IFS Connect
Effort: Roughly two to three months for a first set of flows
Teams with IFS technical staff and a clear message catalog
Partner build with Netray and your IFS partner
Effort: Typically a phased project, with a pilot flow first
Two-way flows, intent parsing of replies and on-prem constraints
Pitfalls
- !Sending free-form messages outside the 24 hour window; they fail unless sent as approved templates.
- !Using polling without a high-water mark, which duplicates messages after a restart.
- !Matching replies by phone number only, so two open orders for one supplier get confused.
- !Writing supplier replies straight into dates or quantities without a review step.
- !Forgetting that one supplier contact in IFS may have several phones or none that are WhatsApp enabled.
Frequently asked questions
Does IFS Cloud have a built-in WhatsApp connector?
Not as a standard feature that we can confirm across releases. IFS offers its own mobile and messaging options, and marketplace or partner add-ons may exist for your version. Most teams use projections and IFS Connect with a small middleware service, so check your release notes first.
Can suppliers reply without an IFS login?
Yes. The supplier only needs WhatsApp. Their reply goes to your middleware, which stores it against the order and stages any change for a buyer. The supplier never touches IFS, and you control what they can see.
Is WhatsApp suitable for regulated or export-controlled data?
Usually not for the content itself. Send a reference and a link to an authenticated page behind your own controls. Treat the chat as a notification channel, and check your compliance team's rules before including part or program details.
Should messages be pushed by events or polled?
Events through IFS Connect are cleaner and lower load when your entity supports them. Polling a projection with a modified-since filter is a dependable fallback. Whichever you use, store a high-water mark and deduplicate by IFS key and event version.
How long does a first WhatsApp flow take?
A single outbound alert with a confirm button can be live in a few weeks, mostly waiting on business verification and template approval. Two-way flows with free-text parsing and review screens take longer, and are best started with one supplier group.
Want WhatsApp working on your IFS Cloud?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment