Infor October 2026 release: what changed and what M3 customers should review

Infor's October 2026 feature release gives M3 customers a broad set of updates to assess across AI-supported work, role-based applications, planning, scheduling, traceability and warehouse processes.

But the useful question is not only: What is new?

It is: Which changes are relevant to our environment, which require attention, and what should we test before deciding to adopt them?

For most customers, the best starting point is to shortlist the capabilities connected to a known operational problem. Then confirm availability, licensing and configuration, involve the responsible process owner, and make a clear decision: adopt, place on the roadmap or defer.

The October 2026 release in brief

• Review AI agents as controlled support for specific decisions and repeated analysis.
• Inspect Experience Designer applications as workflow changes, especially where standard applications or local copies are already in use.
• Involve planning and production owners before testing new inventory-planning or scheduling capabilities.
• Test traceability and catch-weight processes across the complete operational flow.
• Confirm which features are automatic, configurable, feature-toggled or limited in availability before committing.

On this page

• What is included in the Infor October 2026 release?
• AI agents move closer to operational work
• Experience Designer applications require workflow review
• Planning and scheduling need business ownership
• Traceability and catch weight should be tested end to end
• Which release changes require attention?
• A practical review plan for M3 customers
• Frequently asked questions

What is included in the Infor October 2026 release?

The October feature release covers a broad set of Infor products and Industry CloudSuites. Complete product-specific details are available through Infor's current documentation and each customer's Release Center.

This guide does not try to reproduce that catalogue. Instead, it focuses on four areas that deserve a closer look from M3 customers:

• M3 and Supply Chain Planning agents in Infor GenAI Assistant
• M3 Experience Designer applications
• strategic inventory planning and production-scheduling support
• traceability and catch-weight processes

These areas are not equally relevant to every customer. The value depends on the CloudSuite, modules, industry, tenant configuration, licences, data and processes already in place.

The common question is where the release can remove friction from real work without adding uncontrolled complexity.

1. AI agents move closer to operational work

One of the clearest areas to review is the connection between Infor GenAI Assistant and operational M3 data.

Infor's public documentation describes M3 Analytics agents for financial controlling, accounts payable, procurement, sales and warehouse management. The use cases include analysing overdue exposure, supplier performance, sales and profitability, stock levels and warehouse activity.

Infor's 2026.10 Supply Chain Planning documentation also describes three production-scheduling agents:

• a Data Insights agent for questions about active schedules, changeovers, production quantities and timelines
• an End-of-Shift Reporter agent for structured shift-handover reports
• a Documentation agent for questions about production-scheduling functionality and configuration

Importantly, Infor documents these three scheduling agents as read-only. They can retrieve and present information, but they cannot change the production schedule or trigger recalculation.

Who should care?

Finance, procurement, sales, warehouse, planning and production teams that repeatedly collect information from several views before making a decision.

Why could it matter?

The potential value is not the chatbot itself. It is faster access to relevant operational information in a form that supports the next decision.

That only works when the source data is trusted, the question is well defined and a person remains responsible for validating the answer. An agent can make weak data or unclear ownership easier to access; it cannot make them reliable.

What should customers verify?

• Which agents are available in the customer's CloudSuite and tenant?
• What licences, roles, feature enablement and API access are required?
• Which data sources and definitions does each answer use?
• Is the agent read-only, recommendation-based or able to trigger an action?
• Who validates the output when it affects an operational or financial decision?

Recommended next action

Choose one repeated, low-risk analysis task and test it with the process owner. Compare the answer with the existing source and document where human validation is still needed.

Read Infor's public descriptions of the M3 Analytics agents and the 2026.10 production-scheduling agents.

2. Experience Designer applications require workflow review

Role-based applications are another important review area. M3 Experience Designer is embedded in M3 H5 and allows applications to combine API-fed lists, forms, tabs, grids and other components around a task or role.

This matters because many ERP users do not struggle with a lack of data. They struggle to find the right data and action at the right point in the process.

A focused application can reduce the need to move between programs, reports, spreadsheets and email. But an updated standard application can also affect a workflow that has already been adapted locally.

Infor's public guidance says that industry-specific Experience Designer applications are delivered as part of M3 Core. It recommends taking a copy of a standard application before deploying it to production, and notes that updates to standard Experience Designer applications are deployed immediately in feature releases.

Who should care?

M3 application owners, solution architects, administrators and process owners responsible for role-based workflows or local Experience Designer applications.

Why could it matter?

The opportunity is to make daily work simpler without defaulting to heavy custom development. The risk is treating the change as a visual update and missing its effect on local applications, personalisations, roles or ways of working.

What should customers verify?

• Which standard Experience Designer applications are present in the test and production tenants?
• Are local copies or extensions based on an earlier standard version?
• Which roles, permissions, APIs and data definitions does the application use?
• Does the update change the order in which users complete the process?
• What user guidance or training is required?

Recommended next action

Inventory the standard and locally adapted applications used in priority workflows. Review the relevant standard versions in the test tenant with the people who use them before deciding what should move to production.

Infor explains the release behaviour and recommended deployment approach in its Experience Designer Applications documentation.

3. Planning and scheduling need business ownership

The October release also puts planning decisions in focus.

Infor's public 2026.10 documentation describes Strategic Inventory Planning simulations that use monthly or weekly forecasts, inventory policies and performance parameters.

This gives planning teams another way to explore questions such as service levels, safety stock and inventory policy. It does not remove the need to agree how those decisions should be made.

The production-scheduling agents described above add another layer: natural-language access to schedule insights and structured shift reports. Together, these capabilities make it easier to surface information, but the planning model, data and decision rights still determine whether that information is useful.

Who should care?

Demand planners, inventory planners, production schedulers, supply chain leaders and the M3 or SCP teams supporting them.

Why could it matter?

Planning improvements can affect inventory, service levels, production stability and working capital. They can also produce confident-looking results from assumptions that the business has not agreed or data it does not trust.

The useful starting point is therefore not “Which engine should we enable?” It is “Which planning decision are we trying to improve, and how will we judge the result?”

What should customers verify?

• Which inventory policy and performance measure should guide the simulation?
• Are the forecast history, item data, lead times and exceptions reliable enough?
• Who owns the decision when the model and operational experience disagree?
• Where are results published, and which downstream process uses them?
• Is the capability generally available, limited in availability or dependent on additional licensing?

Recommended next action

Select one planning entity or bounded product group. Agree the current baseline, policy and decision owner before running a simulation. Compare the result with the existing plan and document whether it improves the decision—not only whether the software produces an answer.

See Infor's 2026.10 Strategic Inventory Planning documentation for the documented forecast and simulation settings.

4. Traceability and catch weight should be tested end to end

Traceability and catch-weight capabilities are especially relevant for food and beverage businesses, but the underlying lesson applies more broadly: a process is only as strong as the data connections across it.

Infor M3 Graphical Lot Tracker can identify customer deliveries affected by selected trace objects. Its Customer List can also include delivery and contact information used in recall-related work. Infor WMS documents catch-weight information across receiving, picking and packing, while M3 uses catch weight when an item is stocked in one unit but valued or priced in another.

These are useful capabilities, but a screen or report working correctly does not prove that the whole process is ready.

Who should care?

Quality, warehouse, production, customer service and supply chain teams—particularly where lot traceability, variable-weight products or recall readiness are business-critical.

Why could it matter?

During an exception or recall, the organization needs to connect supplier, item, lot, production, stock, delivery and customer information quickly and accurately. Missing units of measure, weak contact data or manual corrections can break that chain.

What should customers verify?

• Can a lot be followed from receipt and production to stock and customer delivery?
• Are the relevant units of measure and actual weights consistent across M3 and WMS?
• Does the customer list contain the information needed by the recall process?
• How are returns, reclassification, corrections and incomplete data handled?
• Which report, integration or API is authoritative at each step?

Recommended next action

Run a realistic trace or recall exercise in the test environment. Include at least one exception, such as a return, correction or missing contact, and record where the process still depends on manual work.

Infor documents the M3 Graphical Lot Tracker Customer List and 2026.10 WMS Catch Weight/Data screen.

Which Infor October 2026 release changes require attention?

Not every feature reaches a customer in the same way.

Infor M3 distinguishes between changes with no expected user impact, capabilities controlled by functional settings, feature-toggled changes and immediate changes that can require customer action. Feature toggles can provide a transition period, while immediate changes may require preparation before the feature release.

That distinction should shape the review order.

Start with:

1. Changes that can affect an existing process automatically.
2. Features with a toggle that will expire or later become active.
3. Local applications, extensions, integrations or reports connected to the changed area.
4. Capabilities that require new licences, roles, configuration or services.
5. Optional innovations with a clear business owner and test case.

Infor documents feature types, review progress and toggle management in Manage features. Customers should use their current Release Center and tenant information as the final source for what applies to their environment.

What should different M3 industries prioritise?

The same release can create different priorities by industry.

Industry	Useful starting point
Food and beverage	Traceability, catch weight, inventory policy, production scheduling and trusted product or lot data.
Distribution	Warehouse analysis, inventory planning, role-based applications and repeated sales or procurement analysis.
Fashion	Role-based work, demand and inventory planning, supplier analysis and product-data ownership.
Manufacturing	Production-schedule visibility, shift handovers, inventory planning and applications supporting operational roles.

This is a starting point, not a product-availability statement. Each customer still needs to verify the exact capabilities, licences and dependencies in its own CloudSuite.

For a deeper look at industry context, see Elvenite's work with food and beverage and retail and distribution.

A practical review plan for M3 customers

The strongest release process connects product information to a business decision.

Use this five-step review:

Step 1: Build a relevant shortlist

Start with current operational problems, not the complete release catalogue. Identify the capabilities that could affect a priority process, an existing risk or a recurring source of manual work.

Step 2: Confirm status and dependencies

For every shortlisted capability, record:

• CloudSuite, module and tenant relevance
• availability and release status
• feature type or toggle behaviour
• licensing and role requirements
• data, integration and security prerequisites

Step 3: Assign a process owner

Every test needs someone from the business who can define the expected result and decide whether the change improves the process.

Step 4: Test the complete workflow

Include local applications, integrations, reports, exceptions and user roles. A successful screen test is not enough if the surrounding process still fails.

Step 5: Make and record the decision

Classify the capability as:

• Adopt: relevant, verified and ready for controlled use.
• Roadmap: valuable, but dependent on further data, process, integration or licensing work.
• Defer: not relevant or not mature enough for the current priorities.

This keeps release work connected to the broader Infor M3 CloudSuite roadmap. Where data quality or integration is the constraint, the review should also connect to Data Intelligence rather than treating it as an isolated ERP issue.

Turning the October release into practical value

The Infor October 2026 release gives M3 customers several areas to explore. The useful work is deciding which of them matter.

AI agents need trusted data and human validation. Experience Designer applications need workflow and deployment review. Planning capabilities need agreed policies and business ownership. Traceability and catch weight need end-to-end testing.

Customers do not need to adopt every new capability. They need a repeatable way to understand what changed, verify what applies and focus effort where it can improve real work.

That is where Feature Release Management and long-term Managed Services become useful. If you want to understand which October 2026 updates are relevant to your M3 environment, Elvenite can help you review the fit, dependencies and test plan.

Review your M3 release plan

Availability note: Availability varies by CloudSuite, module, region, tenant, licence and release status. Some capabilities require configuration, feature enablement or additional services. Confirm current details in Infor's public documentation and your own Release Center before making implementation or purchasing decisions.

Frequently asked questions

What is included in the Infor October 2026 release?

The October 2026 feature release covers multiple Infor products and Industry CloudSuites. For M3 customers, relevant review areas include AI-supported analysis, Experience Designer applications, inventory planning, production scheduling, traceability and warehouse processes. Exact availability depends on the customer's CloudSuite, modules, tenant, configuration and licences.

What should Infor M3 customers review first?

Start with changes connected to a current operational problem or existing risk. Then check whether they affect an established process automatically, require a feature toggle or setting, depend on additional licensing, or need stronger data and integration foundations before they can create value.

Are the new Infor AI agents autonomous?

Do not assume that every agent can act autonomously. Infor's 2026.10 Supply Chain Planning documentation describes its production-scheduling agents as read-only. Customers should verify the permissions, data sources and behaviour of each agent, and define who is responsible for validating its output.

Does every M3 customer receive every October feature automatically?

No. Feature delivery can depend on the product, module, tenant, configuration, feature type, release status and licensing. Infor distinguishes between zero-impact changes, functional settings, feature toggles and immediate changes. Customers should verify the current status in their Release Center and tenant.

How should an M3 customer prepare for a feature release?

Build a shortlist based on business priorities, verify status and dependencies, assign a process owner, test the complete workflow and record an adopt, roadmap or defer decision. Include local applications, integrations, reports, permissions and exception scenarios in the test—not only the new feature itself.