, ,

Acumatica 2026 R2 Ships APS Engine and Shop Floor Kiosk 2.0

Jessica Nicole
Acumatica 2026 R2 Ships APS Engine and Shop Floor Kiosk 2.0

Acumatica made 2026 R2 generally available on October 1, 2026—embedded AI Assistant and Automation across everyday ERP workflows, a forced move to the modern UI for all customers, and industry depth that manufacturers will feel first. On the plant side, the release ships a new Advanced Planning and Scheduling (APS) Engine, Shop Floor Kiosk 2.0, and production-planning enhancements with AI-assisted insights—not a bolted chat window over the ledger.

That matters for industrial ERP because mid-market shops live or die on schedule truth and floor execution. Finite vs infinite APS against real calendars and shifts, a single kiosk for issue/substitute/lot-serial/corrections, and AI that can answer schedule risk from live Generic Inquiries are the daily fights—not another BI export. The same release also hardens the data path so agents and humans share one governed source of truth with MES-adjacent execution and BUS controls.

Two people walking a warehouse aisle with a clipboard—where ATP, picking, and production material decisions meet inventory. Photo: Centre for Ageing Better / Unsplash.
R2’s distribution ATP and manufacturing APS only count when warehouse and floor share the same committed supply picture. Photo: Centre for Ageing Better (Unsplash).

Manufacturing detail from Acumatica’s community notes: APS schedules forward or backward with finite or infinite logic against calendars, shifts, and efficiencies. Shop Floor Kiosk becomes the operator’s single screen—issue materials to the operation, add substitutes, capture lot and serial attributes, and correct on the spot. Four new manufacturing Generic Inquiries let AI Assistant speak to schedule performance, material needs, and production-order risk; MRP and DRP now treat safety stock and reorder points as separate methods.

Analytics is the other half of the bet. Reporting moves to a Native Data Warehouse—a performance-optimized copy of ERP data—so dashboards stop fighting order entry. A Model Context Protocol (MCP) connection lets Claude, ChatGPT, Gemini, and other MCP tools query published inquiries with role-based permissions, inherited security, and field-level masking—no CSV dump into a separate AI workspace. That is the industrial pattern: governed context first, then agents.

Operators on a factory assembly line—where Shop Floor Kiosk 2.0 has to be the only screen that matters. Photo: Remy Gieling / Unsplash.
Shop Floor Kiosk 2.0 only wins if issue, substitute, lot/serial, and corrections stay on one screen at the station. Photo: Remy Gieling (Unsplash).

The category is racing the same way. Oracle’s September 29 Fusion Claw announcement pushes governed agentic execution—Enterprise Operating Envelope, Outcome Trust Harness, Outcome Receipts—across 25 Claw-powered apps inside Fusion Cloud ERP/SCM. Different packaging, same demand: agents that execute under policy, not pilots that chat.

For N23D, the bar is plain English: APS against real capacity, one-screen floor execution, MRP/DRP that separates safety stock from reorder, and AI that reads the same governed ERP data the plant owns—inside one native Rust binary with ERP, MES, and BUS, not a mid-market bolt-on.

Sources/References