BPA vs Digital Worker: Customer Order, Inventory, Material Replenisher

• IFS Expert Inc. (principal) • 8 min read • IFS.ai

25R2 made Digital Workers a product. Unleashed 2026 will put them on a stage. Most mid-market manufacturing estates still have exception queues that belong in native BPA. This note is how we decide.

IFS now talks about two execution surfaces that a plant can actually touch:

  • BPA, custom events, workflow logic. Already in IFS Cloud. This firm has been automating order release, service objects, credit holds, and replenishment exceptions on that surface for years.
  • Loops Digital Workers. Agentic "virtual colleagues" introduced with IFS Cloud 25R2 (27 November 2025). First five named workers: Material Replenisher, Customer Order Manager, Supplier Order Manager, Inventory Replenisher, Operations Analyst. Governed, auditable, human-in-the-loop, per IFS. Product: IFS Agentic AI.

A third surface, Nexus Black / Agent Studio, is IFS's lab and build environment. It is not this firm's delivery SKU.

The rule: Use BPA when the path is known, the volume is human-scale, and the failure mode is "this approval did not fire." Use a named worker when the path is high-volume, the rules are stable, master data is clean, and you can explain every action in an audit. If master data is dirty, a worker will scale the dirt.

Mapped to work this practice already does

Plant domain Stay on BPA when Consider the named worker when Worker (IFS name)
Customer order release, holds, charges, notifications Release rules are local, volume is a planner's day, credit/charge checks are finite Order intake is high-volume, status and promise dates must move without a queue, exceptions are coded Customer Order Manager
Inventory accuracy, put-away, exception workflow Cycle-count and location discipline are still the problem Replenishment is rules-stable and stock records are trusted Inventory Replenisher
Material / spare-part replenishment Min/max is wrong or unowned Demand signals are in IFS and buyers are drowning in the same exceptions Material Replenisher
Supplier orders / invoicing Matching is a finance exception list Invoice capture and supplier comms are volume work with clean POs Supplier Order Manager (only if the estate is ready)
Ops analysis / briefing Lobby and reports are the gap You have trusted measures and want a consolidation worker, not another spreadsheet Operations Analyst (rarely first)

What the IFS.ai Readiness Sprint produces

Not a running worker. A written go / no-go / not-yet for the three manufacturing-first workers above, the copilot that sits next to them, the master-data gaps, and the BPA that has to ship first. CA$130 per hour.

What we will not do

Quote IFS's "10X industrial workforce capacity" or "60% of agentic transactions fully automated" as your outcome. Those are IFS figures (25R2 and H1 2026 releases). Attribute them if you mention them. Do not put them on a homepage tile.

Sources

Discuss the IFS.ai Readiness Sprint

If you already know the domain is BPA, discuss the Workflow Automation Sprint instead.

IFS.ai Readiness Sprint Workflow Automation Sprint