Ask about a purchase order instead of hunting for it

Buyers spend their day answering the same four questions: where is it, who is it from, why is it late, and can we get it sooner. Every one of those answers is already in IFS. Getting it out should not require a screen tour.

Book a demo How it works

NgageChat — purchasing IFS Cloud connected

Which purchase orders from Acme are still awaiting delivery?

search_ifs_pages purchase order, supplier

ifs_search_lov supplier name contains "Acme" → 1042

ifs_read_data $filter=VendorNo eq '1042' and Objstate ne 'Closed'

Six open purchase orders with Acme Industrial (1042). Three are past their promised date.

PO	Line	Part	Qty	Promised	Status
88421	1	74821	40	28 Jul	Released
88421	2	74822	12	28 Jul	Released
88512	1	61190	200	31 Jul	Confirmed
88604	1	74821	40	12 Aug	Confirmed

Push line 2 on 88421 to 15 September

Confirm update to PO 88421 line 2

Field: PromisedDeliveryDate
From: 2026-07-28
To: 2026-09-15

Yes, create it Change something

ifs_update_record PATCH with If-Match ETag

PO 88421 line 2 updated

Concurrency checked against the current IFS ETag before writing.

What can NgageChat do with IFS purchasing?

NgageChat lets you query and update IFS Cloud purchasing data in plain language. Ask which purchase orders are overdue, what a supplier’s open commitment is, or which lines are still awaiting receipt, and NgageChat builds the OData query against your live IFS environment. It can also create requisitions and purchase orders, and run actions such as release, within your IFS permissions.

Last reviewed 3 August 2026 · NgageChat by EX10

What you can ask it

Purchase orders overdue, by supplier, site or buyer
Open order value and line-level receipt status
Supplier master data, addresses and contact details
Agreed prices, lead times and blanket agreements
Requisition status and approval position

What it can change in IFS

Create a purchase requisition from a plain-language request
Create a purchase order and add order lines
Update quantities, dates, prices and delivery addresses
Release a purchase order via the IFS bound action
Create a supplier or add a supplier address

Every write is shown to you as a complete summary and only executes after you approve it — then runs under your own IFS login, inside your own IFS permissions.

Try it like this

Things people actually type

Which purchase orders from Acme are still awaiting delivery?

What is our total open PO value with supplier 1042?

Raise a requisition for 20 bearings, part 74821, needed by Friday

Change the promised date on PO 88421 line 2 to 15 September

Who is the buyer for supplier 1042?

Show late deliveries this quarter as a bar chart by supplier

Why it matters

The friction this removes

None of this is a failure of the ERP. It is the cost of a very large system being used occasionally by people who were trained on it once.

The expediting spreadsheet

Every purchasing team has one, and it is always a day out of date because it is a copy of IFS rather than a view of it.

"Can you check a PO for me?"

Occasional users cannot navigate purchasing screens, so they ask a buyer, who stops buying to look things up.

Supplier data drifts

Addresses and contacts get corrected in email and never make it back into the master record, because the master record is four clicks away.

IFS objects this typically touches

PurchaseOrderHandlingPurchaseOrderLineSupplierHandlingPurchaseRequisitionSupplierInfoAddresses

Exact projections depend on your configuration and IFS release — NgageChat resolves them from its index of the IFS Cloud data model, with your custom fields read live from your environment.

FAQ

Questions about purchasing & suppliers

Can NgageChat raise a purchase order in IFS Cloud?

Yes, within your permissions. It resolves the supplier, part, site and required fields from your live IFS metadata, fills defaults using the entity’s _Default() function, shows you the complete order for approval, and then writes it through the IFS OData REST API.

How does it avoid overwriting someone else’s change?

Updates use IFS ETag concurrency control. NgageChat sends the current ETag with the PATCH, so if another user changed the record first, IFS rejects the write and NgageChat tells you rather than silently clobbering it.

Can it answer spend questions?

It can aggregate what your IFS permissions let you read — open order value by supplier, late lines by buyer, receipts in a period — and render the result as a table or a chart. For scheduled, reusable reporting, a purpose-built report is the better tool.

Also worth reading

Inventory & stock Customer orders & sales Projects & finance

Early access

See it do this against your own IFS environment

Bring one real scenario from your system. Thirty minutes, no slideware — we run it live and you watch every step.

Book a demo See how it works