A practical guide to demand forecasting, production planning and order promising, before you evaluate any tool.
Most manufacturers don't have a forecasting problem. They have a data problem that shows up as a forecasting problem. Before you compare AI planning tools, it helps to know what those tools actually do and what they need from you.

Forecasting, planning and promising are three different jobs

Vendor demos tend to blend these together. Pulling them apart makes every evaluation easier.

• Forecasting answers "what will we sell?" This is where machine learning earns its place. A model learns from your posted sales history and predicts demand by item and period.
• Planning answers "what do we make or buy, and when?" MRP and master production scheduling are rules-based. They apply your BOMs, routings, lead times and reorder policies to the forecast and open orders.
• Promising answers "what date can we commit to this customer?" Available to promise checks stock and scheduled supply. Capable to promise works out when new supply could cover a shortfall. If an order needs 10 and 6 are on hand or scheduled, capable to promise looks at when the other 4 can be made or bought.

Rules-based planning is not a weakness. It's predictable and you can audit it. The AI part is usually the forecast that feeds it and the assistants that sit on top of it.

Why forecasting matters more in a volatile year

A forecast is only useful if it keeps up with reality. In the NAM's Q1 2026 Manufacturers' Outlook Survey, 70.6% of manufacturers named trade uncertainty as their top business challenge. When input costs and lead times move, a forecast you refresh once a quarter falls behind fast.
That's the practical case for AI forecasting. It's not about predicting the future perfectly. It's about updating the picture faster than a planner can by hand.

Readiness, not budget, is the real gap

Almost every manufacturer is looking at this. Research has shown nearly 98% are exploring AI, but only 20% feel fully prepared. In our experience, the gap comes down to four things:

1. Clean master data. Items, BOMs, routings and vendor lead times you trust. AI repeats your errors at speed.
2. History in the ERP. Posted sales history the model can learn from, not a spreadsheet kept on the side.
3. Shop floor data in the system. Output, consumption and capacity recorded when they happen.
4. Planning parameters set up on purpose. Reorder policies, safety stock and lead times that match how you really run.

None of these are exotic. They're the same habits that make MRP trustworthy, which is why a readiness check tends to pay off before any AI is switched on.

It also takes pressure off your planners

Planning talent is hard to find. The Deloitte and Manufacturing Institute 2025 Smart Manufacturing Survey found 46% of manufacturers struggle to fill planning and scheduling roles. A system that handles the first draft of the forecast gives your planners time for the judgment calls only they can make.

Five questions to ask any ERP vendor about AI planning

1. Is this feature generally available, in preview, or something we'd build?
2. How much sales history does the forecast need, and at what level (item, location, variant)?
3. Which parts of planning are AI, and which are rules-based?
4. Does a person review what an agent drafts before it reaches a customer?
5. Can we build our own agents on our own data, or are we locked into what ships?

If a vendor can't answer the first question clearly, treat the rest of the demo with care. Preview features can be useful. You just want to know when you're signing up for one.

Seeing it in one system

Answers to those questions vary by product. For a worked example, our team at Western Computer is walking through them in Dynamics 365 Business Central on Thursday, October 8, in a 30-minute webinar: Stop Guessing, Start Predicting: AI in Manufacturing Forecasting & Scheduling. We've spent nearly 40 years and 1,750+ implementations helping manufacturers plan on Microsoft ERP, and we'll be straight about what's ready and what isn't.

The post AI Forecasting for Manufacturers: What It Can Do Today and What It Needs From Your ERP appeared first on ERP Software Blog.

As Microsoft's Latest Business Central Release Doubles Down on Native Financial Tools, Counter Sales Extends That Same Philosophy to the Sales Counter

Insight Works, a developer of add-on applications for Microsoft Dynamics 365 Business Central, today reaffirmed its commitment to eliminating disconnected point-of-sale systems for trade desks, parts counters, and industrial retail operations with Counter Sales, a point-of-sale and trade-desk solution built directly into Business Central.
The reminder comes as Microsoft's 2026 release wave 1 for Business Central continues to push more financial capability natively into the core product, including AI-assisted bank account reconciliation, expanded cash-flow forecasting, and deeper embedded reporting, all aimed at reducing the manual reconciliation and disconnected tools that have historically slowed finance teams down. That same problem has long existed one step earlier in the process, at the sales counter itself. Many organizations running Business Central still take trade-desk and counter payments through a separate system entirely, which creates manual reconciliation work, delayed visibility into cash flow, and duplicate data entry between the point-of-sale tool and the ledger.
Insight Works built Counter Sales to close that gap at the point of sale. The application adds order entry, barcode scanning, and payment processing directly inside Business Central, so a trade-desk or parts-counter transaction posts straight to the ledger without ever leaving the system. Split payments across cash, card, and other methods are supported per order, along with card-present, card-on-file, and virtual-terminal processing for phone and repeat orders. Deposits, including partial and full deposits with tax, apply cleanly to sales and return orders. At day's end, dimensions-based cash register reconciliation posts directly to the general ledger, closing out the till without a separate reconciliation step.
Counter Sales also supports a shared-terminal, device-based license model, allowing multiple shift employees to work from one counter terminal without requiring a full Business Central user license for each person, an approach built for the realities of shift-based trade-desk and counter staffing.
Mark Hamblin, Senior Solutions Advisor at Insight Works, put it this way: "Business Central keeps adding native financial capability, but that only closes half the gap if the sale itself still happens outside the system. Counter Sales was built so the counter and the ledger are never disconnected in the first place. For anyone who wants to see this in practice, we cover it in detail in our webcasts, available at dmsiworks.com/webcasts."

Availability

Counter Sales is available now as a subscription add-on for Microsoft Dynamics 365 Business Central through Microsoft Marketplace and directly at CounterSalesForDynamics.com

About Counter Sales

Counter Sales is a point-of-sale and trade-desk app built directly into Business Central for professional salespeople at parts counters, trade desks, and industrial retail operations. It brings order entry, barcode scanning, advanced item lookup, multiple payment types, deposit handling, and cash register reconciliation into the Business Central environment organizations already run on, without third-party connectors or duplicate data entry.

About Insight Works

Insight Works is a leading Independent Software Vendor (ISV) dedicated to creating apps exclusively for Microsoft Dynamics 365 Business Central. The company specializes in the manufacturing and distribution industries, providing innovative solutions that streamline operations and enhance productivity for businesses worldwide. With a vast reseller network comprising over 800 global Microsoft Partners, Insight Works ensures its apps are accessible and supported wherever businesses operate. Headquartered in Canada, Insight Works also maintains a regional office in the Netherlands, strengthening its global reach and commitment to localized support. Learn more at dmsiworks.com.

The post Insight Works Brings Professional Retail and In-Person Payments Fully Native to Microsoft Dynamics 365 Business Central appeared first on ERP Software Blog.

Inventory management is no longer just about knowing how many products are sitting in a warehouse.
Businesses also need to know what customers will buy next, which products may run out, where excess stock is building up, and when they should place the next purchase order.
This is where AI inventory management software is becoming useful.
By using artificial intelligence, machine learning, forecasting, automation, and real-time data, modern inventory software can help businesses make faster and more informed inventory decisions.
A traditional system may tell you that you have 500 units left.
An AI inventory management system can go further and tell you that demand is increasing, your current stock may not last until the next supplier delivery, and a reorder may be needed soon.
That difference is important.
In this guide, we will explain AI inventory management in simple English. We will cover how it works, its main features, benefits, use cases, limitations, and what businesses should look for when choosing software.

What Is AI Inventory Management Software?

AI inventory management software is a system that uses artificial intelligence to help businesses track, forecast, plan, and optimize inventory.
Regular inventory software mainly focuses on recording what has already happened.
For example, it may show:

• Current stock
• Sales
• Purchase orders
• Product movements
• Warehouse quantities

AI adds another layer.
It can study past and current data to identify patterns and make predictions. This may help businesses decide what products they need, how much stock they should keep, and when they should reorder.
In simple words, AI based inventory management uses AI to help answer important questions before a problem happens.
For example:
Which products may run out soon?
Which products are likely to become overstocked?
What will demand look like next month?
When should we reorder?
How much should we purchase?
This makes AI inventory management different from basic inventory tracking.

Good Read: Best AI Inventory Management Software

How Does an AI Inventory Management System Work?

An AI inventory management system works by collecting data from different parts of a business.
This may include:

• Sales history
• Inventory levels
• Purchase orders
• Supplier lead times
• Customer orders
• Returns
• Promotions
• Seasonal demand
• Warehouse activity
• Product locations

The system then uses AI models to find patterns in the data.
For example, suppose a business sells winter jackets.
Sales may be low in summer but increase sharply from October to December. A normal inventory system records those sales. An AI system can recognize the seasonal pattern and use it when forecasting future demand.
This is one of the main examples of artificial intelligence in inventory management.
The process usually looks like this:
Data → Analysis → Forecast → Recommendation → Action → New Data
As new data enters the system, forecasts and recommendations can be updated.
This makes inventory management using AI more dynamic than relying only on fixed reorder rules.

Good Read: Top Warehouse Inventory Management Systems

What Is AI in Inventory Management?

The use of AI in inventory management system processes can range from simple alerts to advanced forecasting and automated purchasing recommendations.
AI can be used to analyze:

• Demand
• Stock levels
• Product movement
• Supplier performance
• Lead times
• Seasonal patterns
• Customer behavior
• Warehouse activity

The purpose is not to use AI just because it is a new technology.
The purpose is to make inventory decisions easier and more accurate.
For example, a purchasing manager may normally spend hours checking reports to decide which products need to be reordered.
With AI in inventory management, the system can identify products that need attention and provide recommendations.
This allows the employee to spend more time reviewing important decisions instead of searching through spreadsheets.

Good Read: Best Order Management Software

Key Features of AI Inventory Management Software

Different platforms offer different features, but a strong AI inventory management software platform usually includes several capabilities that help with forecasting, planning, visibility, and automation.

1. AI Demand Forecasting

Demand forecasting is one of the most important applications of AI.
The software reviews historical sales and other business data to estimate future demand.
A simple example makes this easier to understand.
Imagine a product sells:

• 100 units in January
• 110 units in February
• 115 units in March
• 130 units in April

AI can analyze this pattern along with other information to estimate what may happen in the coming months.
The forecast can become more useful when the system also considers promotions, holidays, price changes, seasonality, and supplier lead times.
This is why AI and inventory management are becoming closely connected.

2. Automated Replenishment

Businesses need to reorder products before they run out.
Manual replenishment can become difficult when there are hundreds or thousands of SKUs.
An AI powered inventory management system can monitor inventory and identify products that may need replenishment.
It may consider:

• Current stock
• Forecasted demand
• Supplier lead time
• Safety stock
• Open purchase orders
• Minimum order quantities

The system can then create a recommendation.
An employee can review that recommendation before placing the order.
More advanced AI powered inventory management systems may automate parts of this process based on business rules.

3. AI Inventory Optimization

Holding inventory costs money.
But holding too little inventory can also be expensive because it may lead to stockouts and lost sales.
AI inventory optimization helps businesses find a better balance.
Instead of treating every product in the same way, AI can consider the characteristics of each product.
A fast-moving product with a long supplier lead time may need a higher safety stock level.
A slow-moving product with a short supplier lead time may need much less stock.
This is the basic idea behind AI inventory optimization.
The goal is not simply to reduce inventory.
The goal is to maintain the right inventory level for the business.

4. Stockout Prediction

A stockout occurs when a product is unavailable when it is needed.
Stockouts can result in:

• Lost sales
• Delayed orders
• Poor customer experience
• Emergency purchasing
• Production delays

AI stock management can help identify products that may run out.
The system can compare current inventory with expected demand and supplier lead time.
For example, you may have 200 units available today.
That sounds like enough.
But if the product is selling 50 units per day and the supplier needs 10 days to deliver more stock, the situation is very different.
An AI solution can identify this risk earlier.
That is one practical use of AI stock management.

5. Overstock Detection

Too much inventory is another common problem.
Excess stock takes up warehouse space and ties up working capital. It can also become outdated, damaged, or difficult to sell.
Using AI for inventory management, companies can identify products that are moving slowly or are likely to remain in stock for too long.
The system can compare current inventory with expected demand and highlight products that may need attention.
This helps purchasing teams avoid ordering more inventory when existing stock is already higher than necessary.

6. Real-Time Inventory Visibility

Businesses often have inventory in several places.
For example:

• Warehouse
• Store
• Distribution center
• Ecommerce fulfillment center
• Third-party logistics facility

This can make inventory visibility difficult.
AI platforms for real-time inventory visibility bring inventory information together and help teams understand what is happening across different locations.
The value of AI platforms for real-time inventory visibility becomes even greater when the system also provides forecasting and alerts.
Instead of simply seeing today's inventory, teams can see current stock and possible future risks.

7. Anomaly Detection

AI can also find unusual activity.
Suppose a warehouse normally records 10 inventory adjustments per day.
Suddenly, the number increases to 40.
A human may not notice the change immediately.
An AI system can flag it as an unusual pattern.
This is another example of artificial intelligence inventory management.
Anomaly detection may help teams investigate:

• Unusual stock adjustments
• Unexpected returns
• Sudden demand changes
• Inventory mismatches
• Unusual product movement

8. Purchase Order Recommendations

AI can help purchasing teams decide what to buy.
The software can review inventory, demand forecasts, supplier lead times, and existing purchase orders.
It may then recommend:
Buy Product A: 500 units
Buy Product B: 150 units
Do not reorder Product C
This can save time for purchasing teams.
It also gives them a clear starting point for their daily work.

9. AI Analytics and Reporting

Reports are useful, but businesses often need more than historical information.
For example, they may want to know:
“Why is inventory increasing?”
“Which products may become slow-moving?”
“Which items are likely to run out?”
“Which warehouse is carrying too much stock?”
This is where inventory management AI can become useful.
Instead of only displaying numbers, AI can help identify patterns and exceptions.
The goal of inventory management AI is to make large amounts of inventory data easier to understand.

Benefits of AI Inventory Management

Businesses adopt AI for many different reasons.

Better Demand Forecasting

AI can analyze large amounts of data quickly.
This can help businesses prepare for changes in customer demand and reduce dependence on simple averages.

Fewer Stockouts

By identifying potential shortages early, AI can give teams more time to react.

Less Overstock

Better forecasting and replenishment can help reduce unnecessary inventory.

Faster Decisions

Employees do not need to manually review every SKU to identify possible issues.

Better Visibility

Teams can get a more complete view of inventory across warehouses and locations.

Less Manual Work

Repetitive checks, alerts, and reports can be automated.

Better Use of Working Capital

Holding excessive stock can tie up cash. Better inventory planning can help businesses use their working capital more efficiently.
These benefits explain why AI powered inventory management is receiving attention across retail, ecommerce, manufacturing, distribution, and other industries.

AI Inventory Management Use Cases by Industry

The value of AI depends on the industry and the type of inventory a business manages.

Manufacturing

Manufacturers may need to manage raw materials, components, work-in-process inventory, and finished goods.
AI can help forecast material demand, identify shortages, and support purchasing decisions.
For a manufacturer, AI based inventory management can connect inventory planning with production requirements.
This is especially useful when a company handles thousands of parts and components.

Ecommerce

Ecommerce businesses often face fast-changing customer demand.
They may also sell through several channels, which makes inventory control more difficult.
AI inventory management can help with:

• Demand forecasting
• Stockout prevention
• Overstock detection
• Multichannel visibility
• Replenishment
• Seasonal planning

Businesses searching for free AI inventory management may find basic tools that support simple inventory tasks.
However, free tools often have fewer features than enterprise platforms.
A company evaluating free AI inventory management should look at scalability, integrations, reporting, and automation before choosing a solution.

Retail

Retail businesses often need to manage inventory across stores and locations.
A product may sell very quickly in one city but slowly in another.
AI can help analyze these differences.
When businesses compare best retail inventory management software 2026 options, they should look at how each system handles store-level demand, replenishment, transfers, and seasonal changes.
The same is true when searching for best retail inventory management software 2026. A long feature list does not necessarily mean that the software will fit a company's needs.

Wholesale and Distribution

Distributors may handle a very large number of SKUs.
Checking inventory manually can become difficult.
This is where inventory AI can help.
The system can identify fast-moving items, slow-moving items, stock risks, and replenishment needs.
For distributors, inventory AI can also support better purchasing decisions by bringing together sales and supply data.

Food and Beverage

Food businesses have additional challenges because many products have expiration dates and limited shelf life.
They may need to track:

• Ingredients
• Batch information
• Expiration dates
• Storage conditions
• Demand
• Waste

When reviewing AI ingredient management technology features, businesses should look at forecasting, ingredient-level visibility, expiration alerts, purchasing, and waste reduction.
The right AI ingredient management technology features can help food businesses make better use of their ingredients and reduce avoidable waste.

Healthcare

Hospitals, clinics, and healthcare suppliers need to manage medical supplies, medicines, and other products.
AI can help identify low-stock situations, forecast demand, and monitor inventory movement.
However, healthcare organizations also need strong controls around data, access, approval, and auditability.

How AI Helps With Inventory Forecasting

One of the most valuable applications of AI in inventory management is demand forecasting.
Traditional forecasting may use historical averages.
AI can look at many more signals.
These may include:

• Historical sales
• Seasonality
• Promotions
• Product trends
• Regional demand
• Supplier lead times
• Returns
• Pricing
• Customer behavior

This makes inventory management using AI useful when demand is difficult to predict.
For example, an ecommerce company may notice that a product sells much faster whenever it runs a promotion.
AI can identify this pattern and include it in future forecasts.
This is a simple example of how inventory management using AI can support better planning.

What Is AI Inventory Optimization?

The goal of AI inventory optimization is to maintain enough inventory to support demand without holding unnecessary stock.
This requires a balance.
Too much inventory can increase carrying costs.
Too little inventory can increase the risk of stockouts.
AI can analyze this balance across individual products and locations.
For example, a high-value product with unpredictable demand may require a different inventory policy from a low-value product with stable demand.
This is why AI inventory optimization can be more flexible than using one fixed inventory rule for every item.

AI Tools for Inventory Management

There are many types of AI tools for inventory management.
Some are focused on forecasting.
Others focus on purchasing, inventory optimization, warehouse management, reporting, or automation.
Common categories include:

Demand Forecasting Tools

These tools predict future demand.

Inventory Optimization Tools

They help determine suitable stock levels.

Replenishment Tools

They recommend when and how much to reorder.

AI Analytics Tools

They identify patterns and exceptions in inventory data.

AI Assistants

They help users ask questions about inventory data in natural language.
The best AI tools for inventory management depend on the company's size, industry, data, and existing software.

AI Inventory Management Companies

The market now includes many ERP providers, inventory software vendors, warehouse technology companies, and specialized AI providers.
When comparing AI-powered inventory management companies, businesses should focus on what the software actually does.
Look at:

• Forecasting capabilities
• Inventory optimization
• Integration options
• Automation
• Reporting
• Scalability
• Security
• Implementation
• Support

The goal when comparing AI-powered inventory management companies should be to match the software with the company's actual inventory problems.
A retailer, manufacturer, distributor, and ecommerce company may all need different capabilities.

AI-Powered Inventory Management Systems and Automation

Automation is another major area where AI can help.
For example, an AI powered inventory management system may automatically monitor stock and send an alert when a product is likely to reach a critical level.
More advanced AI powered inventory management systems can also recommend or trigger replenishment based on pre-defined business rules.
This does not mean businesses should automate every decision.
High-value purchases may still need human approval.
The better approach is often a combination of automation and human control.

AI-Enabled Inventory Management Software for Automation

AI-enabled inventory management software for automation combines artificial intelligence with workflow automation.
A simple workflow could look like this:
Step 1: AI detects that stock is falling.
Step 2: The system checks forecasted demand.
Step 3: It reviews supplier lead time.
Step 4: It calculates a suggested reorder quantity.
Step 5: An employee receives the recommendation.
Step 6: The employee approves the purchase.
This type of AI-enabled inventory management software for automation can make repetitive inventory work faster and more consistent.

What Is an Inventory Management AI Agent?

An inventory management AI agent is an AI-based assistant that can perform several inventory-related tasks.
Instead of asking users to open several reports, the user may be able to ask:
“Which products may run out in the next 14 days?”
The agent can analyze relevant inventory and forecast data and provide an answer.
An inventory management AI agent may also help summarize inventory problems, explain changes, and prepare recommendations.
As AI agents develop, they may become more integrated with ERP and inventory workflows.
Human oversight is still important for actions that affect purchasing, finances, or customer commitments.

What Are Advanced Inventory Solutions?

Advanced inventory solutions go beyond basic inventory tracking.
They may combine:

• Inventory management
• Demand forecasting
• Purchasing
• Warehouse operations
• Analytics
• Automation
• ERP integration
• AI

For companies with multiple warehouses or large product catalogs, advanced inventory solutions can provide a more connected way to manage inventory.
The main advantage is that teams can work from connected information instead of relying on separate spreadsheets and systems.

How to Choose AI Inventory Management Software

Choosing AI inventory management software should start with business requirements.
Do not start with the question:
“Which software has the most AI?”
Start with:
“What inventory problem do we need to solve?”
Then evaluate the software around that problem.
Here are some useful questions.

Does it integrate with your ERP?

Your inventory software should be able to work with the systems that already hold your sales, purchasing, financial, or product data.

Can it manage your SKU volume?

A system that works well for 500 SKUs may not work the same way for 50,000 SKUs.

Can it support multiple locations?

This becomes important when a business operates multiple warehouses, stores, or fulfillment centers.

Does it provide explainable recommendations?

Employees should be able to understand why the system is recommending an action.

Can users override AI recommendations?

Human control is important for unusual situations.

Does it support forecasting?

Forecasting is one of the most useful AI capabilities for inventory.

Does it automate repetitive tasks?

Automation can help employees spend more time on important decisions.
A good AI inventory management system should fit your workflows, data, and technology environment.

Best Inventory Management Software 2026: What Should Businesses Compare?

Businesses researching the best inventory management software 2026 should avoid choosing a product based only on a ranking.
Instead, compare software based on actual needs.
Important areas include:

• Inventory tracking
• Forecasting
• Replenishment
• Purchasing
• Warehouse management
• Integrations
• Automation
• Reporting
• Scalability
• Support

The phrase best inventory management software 2026 is useful for researching the market, but there is no single platform that is ideal for every business.
The right choice depends on business size, industry, inventory complexity, budget, and existing technology.

Best Inventory Optimization Software 2026: What Matters?

Businesses searching for the best inventory optimization software 2026 often have one of two major problems:
They have too much inventory.
Or they frequently run out of important products.
When comparing the best inventory optimization software 2026, pay attention to how the system handles:

• Safety stock
• Reorder points
• Demand forecasts
• Lead times
• Product demand changes
• Supplier performance
• Multi-location planning

A good solution should help users understand not just what the recommended inventory level is, but also why.

Best Ways to Manage Inventory Effectively 2025 or 2026

The best ways to manage inventory effectively 2025 or 2026 are still based on a few basic principles.
First, maintain accurate inventory data.
Second, understand demand.
Third, monitor supplier lead times.
Fourth, review fast-moving and slow-moving products regularly.
Fifth, use suitable safety stock policies.
Sixth, automate repetitive work where it makes sense.
The best ways to manage inventory effectively 2025 or 2026 also include connecting inventory systems with sales, purchasing, ERP, and warehouse data.
AI can support these processes, but technology works best when the underlying data and business processes are also reliable.

Challenges of AI Inventory Management

AI can offer major benefits, but it also has limitations.

Poor Data Can Create Poor Results

AI depends on good data.
If inventory records are incorrect or sales history is incomplete, predictions may not be reliable.

Integration Can Be Difficult

Businesses often use several systems.
Connecting an AI solution with ERP, ecommerce, warehouse, accounting, and sales systems may require technical work.

AI Does Not Understand Every Business Situation

A system may not know about a supplier issue, market event, or internal business decision unless that information is available to it.

Human Review Still Matters

AI recommendations should be reviewed when the decision has a high financial or operational impact.

Implementation Requires Planning

Businesses need training, process changes, data preparation, and clear ownership.
For this reason, artificial intelligence inventory management should be treated as a business project, not simply a software installation.

AI Inventory Management and ERP Integration

ERP integration is one of the most important parts of modern inventory management.
An ERP may contain information about:

• Products
• Customers
• Suppliers
• Sales orders
• Purchase orders
• Finance
• Warehouses
• Manufacturing
• Transfers

When an AI inventory management system can access this information, it can produce more useful recommendations.
For example, demand forecasting can become more useful when the system can also see open purchase orders and current supplier lead times.
This is one reason artificial intelligence in inventory management is closely linked to ERP and business systems.
The better the data flow, the more useful the AI can become.

How to Implement AI Inventory Management

A company does not need to automate everything on day one.
A simple implementation can start with one specific problem.
For example:

Problem

The business frequently runs out of high-demand products.

Step 1: Improve Data Quality

Make sure product, sales, and inventory data is accurate.

Step 2: Connect the Systems

Connect the AI platform with the ERP, inventory, sales, or warehouse system.

Step 3: Start Forecasting

Use AI to forecast demand for selected products.

Step 4: Add Alerts

Create alerts for possible stockouts.

Step 5: Add Replenishment Recommendations

Use forecasts to recommend purchase quantities.

Step 6: Measure Results

Track stockouts, inventory turnover, excess stock, and forecast accuracy.

Step 7: Expand

Once the process works, add more products, locations, and workflows.
This phased approach can make the use of AI in inventory management system processes easier to manage.

Is AI Inventory Management Right for Every Business?

Not necessarily.
A very small company with only a few products may not need sophisticated AI software.
Simple inventory tools may be enough.
AI becomes more useful when a business has:

• Many SKUs
• Multiple locations
• Changing demand
• Complex purchasing
• Frequent stockouts
• Excess inventory
• Large amounts of historical data
• Multiple sales channels

In these situations, AI for inventory management can provide more value because there are more variables for the system to analyze.

The Future of AI and Inventory Management

The future of AI and inventory management is moving beyond basic forecasts and alerts.
AI is gradually becoming more conversational and more connected to business workflows.
Instead of opening five reports, an inventory manager may be able to ask:
“Which products are likely to become overstocked next quarter?”
Or:
“Which items need to be reordered this week?”
The system can then analyze the available data and provide an answer.
This could make inventory management AI easier for non-technical users.
AI agents may also become more capable of handling multi-step workflows, while employees continue to approve important actions.
In this way, AI-powered inventory management is likely to become more interactive, predictive, and automated.

Frequently Asked Questions

What is AI inventory management software?

AI inventory management software uses artificial intelligence to analyze inventory and sales data, forecast demand, identify stock risks, optimize inventory, and support replenishment decisions.

What is an AI inventory management system?

An AI inventory management system combines inventory tracking with AI capabilities such as forecasting, optimization, alerts, analytics, and automation.

What is AI based inventory management?

AI based inventory management means using artificial intelligence to support inventory planning, forecasting, replenishment, and optimization.

What is artificial intelligence inventory management?

Artificial intelligence inventory management refers to the use of AI technologies in inventory-related processes such as forecasting, stock monitoring, purchasing, and optimization.

What is AI powered inventory management?

AI powered inventory management uses AI to help businesses make faster and more informed inventory decisions.

What are AI tools for inventory management?

AI tools for inventory management include demand forecasting software, inventory optimization platforms, replenishment tools, analytics platforms, anomaly detection systems, and AI assistants.

How is AI used in inventory management?

The use of AI in inventory management system workflows can include demand forecasting, stockout prediction, overstock detection, replenishment recommendations, anomaly detection, and automation.

How does AI help inventory management?

AI in inventory management helps businesses analyze large amounts of data and identify trends, risks, and opportunities that may be difficult to find manually.

What is AI stock management?

AI stock management uses AI to monitor stock levels, predict demand, identify possible shortages, and support replenishment.

What is AI inventory optimization?

AI inventory optimization helps businesses balance product availability with inventory costs by analyzing demand, stock levels, supplier lead times, and other factors.

What is inventory AI?

Inventory AI is a general term for artificial intelligence used to improve inventory planning, forecasting, tracking, and optimization.

What is inventory management AI?

Inventory management AI refers to AI technologies used to analyze and manage inventory-related data and processes.

What is inventory management using AI?

Inventory management using AI means applying artificial intelligence to tasks such as forecasting, replenishment, stock optimization, and anomaly detection.

What are AI powered inventory management systems used for?

AI powered inventory management systems are used for forecasting, replenishment, stock optimization, inventory visibility, reporting, and automation.

What are AI-powered inventory management companies?

AI-powered inventory management companies provide software and platforms that use AI for inventory forecasting, planning, analytics, optimization, and automation.

Is free AI inventory management software useful?

Free AI inventory management software can be useful for small businesses or for testing basic capabilities. Businesses with complex operations may need a paid solution with better integrations, scalability, and automation.

What are advanced inventory solutions?

Advanced inventory solutions combine inventory management with technologies such as AI, automation, forecasting, analytics, and ERP integration.

What are AI platforms for real-time inventory visibility?

AI platforms for real-time inventory visibility combine current inventory information with predictive insights, alerts, and analytics.

What is an inventory management AI agent?

An inventory management AI agent is an AI assistant that can answer inventory questions, summarize data, identify risks, and support multi-step inventory tasks.

Final Thoughts

Inventory management is becoming more predictive.
Instead of waiting for a stockout, businesses can use AI to identify risk earlier.
Instead of ordering based only on historical averages, they can use demand forecasts.
Instead of manually reviewing thousands of SKUs, employees can focus on the products and issues that need attention.
That is the main value of AI inventory management software.
A good solution can combine forecasting, inventory optimization, stock management, real-time visibility, analytics, and automation in one connected system.
However, AI is not a replacement for accurate data or good inventory processes.
Businesses should choose software based on their actual needs, existing systems, data quality, inventory complexity, and long-term goals.
The strongest results usually come when AI supports people rather than simply trying to replace them.
As businesses continue to manage more products, more locations, and more sales channels, AI inventory management can become an important part of modern inventory planning and operations.
Good Read: Best Vendor Managed Inventory Software
Good Read: Best Retail Inventory Management Software
Good Read: Best Vendor Management Software
Good Read: Best AI Inventory Management Software
Good Read: Best Warehouse Management Systems for eCommerce
Good Read: Best Supply Chain Management Software
Good Read: Best Pharma ERP Systems
Good Read: Best ERP Implementation Partners
Good Read: Top Business Central Consultants
Good Read: Best Microsoft Dynamics 365 Implementation Partners
Good Read: Top ERP Consulting Companies
Good Read: Best ERP Consultants
Good Read: Top Procurement Management Software
Good Read: Top Microsoft Business Central Partners
Good Read: Best 3PL Warehouse Management Software Solution
Good Read: Best Cloud Based Warehouse Management System
Good Read: Top Warehouse Management Systems
Good Read: Best Order Management Software
Good Read: Best eCommerce Inventory Management Software

The post AI Inventory Management Software: Features, Benefits & Use Cases appeared first on ERP Software Blog.

Securing access to your ERP’s Production Environment is one of the most crucial steps your team can take at the beginning of your implementation to set the project up for success. Since this is the environment you will eventually go live in, it is critical that no users transact in that environment or treat it like a sandbox, as this will be difficult to reverse. Luckily, Microsoft provides a handful of ways to prevent this scenario. This guide covers three methods for restricting user access to production environments: the Security Groups method, the License Configuration method, and the User Status method.
What options do I have for securing my Business Central Production Environment?
The Security Groups method leverages Microsoft Entra ID security groups assigned at the environment level to control which users can sign in to specific Business Central environments. This approach provides centralized access management through the Microsoft 365 admin center and Business Central admin center.
The License Configuration method involves customizing permission set assignments for license types, preventing new users from accessing the system or companies within the system, upon first login.
The User Status method provides direct control by disabling individual user accounts from the Users page in Business Central, immediately revoking access in a single click.
For all of these scenarios, we’ll assume that the user accounts have already been created and assigned a Business Central license. Each method shines in different situations, so let’s dive right and start setting these up.
How can I use Security Groups for managing Business Central access?
The Security Groups method provides environment-level access control by assigning Microsoft Entra ID security groups to Business Central environments. When a security group is assigned to an environment, only direct and indirect members of that group can sign in. Indirect members are users in a group that is itself a member of the assigned group. This method offers several advantages including centralized management through the Microsoft 365 admin center and synchronization with Microsoft Entra ID for consistent security policies.
Prerequisites for implementing this method include administrative access to the Microsoft 365 admin center with permissions to create and manage security groups as well as access to the Business Central admin center as an internal administrator. The security groups must be created in Microsoft Entra ID before they can be assigned to environments. It is important to note that restrictions imposed by security groups do not apply to internal administrators, who can freely sign in to all environments regardless of assigned groups.
How do I create Microsoft Entra ID Security Groups?
To create security groups in the Microsoft 365 admin center, navigate to Teams & groups and select Active teams & groups. On the Active teams & groups page, select the Security Groups tab. Click the action button labeled + Add a security group to begin creating a new group. On the Set up the basics page, enter a descriptive Name for the security group. Typically, you would note that the security group relates to production environment access by including either “Prod” or “Production” in the security group name. Click Next and finish creating the security group; you can now assign the security group to users.
How do I assign a Microsoft Entra ID Security Group to a Business Central Environment?
To restrict environment access using security groups, you must assign a specific security group to the production environment through the Business Central admin center. This is the critical step that enforces environment-level access control.
Navigate to the Environments page in the Business Central admin center and select the environment to which you want to assign the security group. On the Environment Details page, the currently assigned security group is shown under the Security Group section. If no group is assigned, the field displays Not Set, meaning any licensed user with permissions can sign in to the environment.
To assign a new security group to an environment, select the Define button. To change or remove an existing security group assignment, select the Modify button. The Edit Security Group pane displays the current security group assignment if one exists, followed by a searchable list of all available security groups in Microsoft Entra ID.
To assign or change a group, search for and select the desired security group from the list, then confirm your selection. To remove a group assignment entirely and allow all licensed users to sign in again, select the removal option under Current Security Group.
Once a security group is assigned to the environment, only direct and indirect members of that group can sign in. Users not in the assigned security group will be unable to access the production environment, even if they have valid Business Central licenses and appropriate permissions configured.
How can License Type Configuration control Business Central user permissions?
The second method provides access control by customizing which permission sets are automatically assigned to new users based on their license type within Business Central. When all permission sets are removed from a license configuration, new users attempting their first login cannot access the system because they lack the necessary permissions to view or interact with Business Central.
How can I manage user Permissions by License Type in Business Central?
To implement this method, open Business Central and search for License Configuration. The License Configuration page lists all available license types. For each License Type you wish to restrict permissions for, click on the line and select the Configure button.
Toggle the Customize permissions Boolean to enable editing of the permission set assignments. By default, many licenses include permission sets such as D365 BUS PREMIUM, D365 BUS FULL ACCESS, which provide a high level of access to the system. Remove all permission sets from the license configuration by selecting all the lines and deleting them.
 
A warning message will appear stating “Customizing permissions will affect only newly created users who are assigned to the license. Permissions for existing users who are assigned the license will not be affected.” This is the intended behavior - existing users retain their current permissions while new users receive no automatic permissions. Save the configuration by closing the page. The Permissions Customized flag will now show as checked on the License Configuration List page
When new users with the affected license attempt to log in to the production environment for the first time, they will be unable to gain access. If a user needs access at a later point, administrators must manually assign appropriate permissions on individual user cards, or via security groups. Depending on how many license types your organization employs, you may need to repeat these steps additional times.
How can you control access by User Status Business Central?
The User Status method provides immediate access control by directly disabling individual user accounts from the Users page in Business Central. This method is particularly effective for temporarily or permanently revoking access for existing users without removing their Microsoft 365 licenses or security group assignments. When a user account is set to Disabled status, the user cannot sign in to Business Central even if they have valid credentials, appropriate licenses, and security group memberships. This method is commonly used for employee offboarding, temporary suspensions during security investigations, or seasonal access restrictions.
How do I disable users in Business Central?
To implement this method, open Business Central and search for Users. The Users page displays a list of all user accounts in the environment, showing their authentication email, full name, and current state. Locate the user account that requires access restriction and click on the user name to open the User Card. On the User Card, locate the Status field which controls whether the user account is Active or Inactive. Switch the status from Active to Inactive, and the change will take effect immediately. To restore access later, return to the User Card and change the Status field back to Active.
Unlike the License Configuration method which only affects new users, the User Status method provides instant access control for existing users who have already logged in previously. This method works independently of security groups and license configurations, providing an additional layer of security control directly within Business Central.
You’re now an expert in protecting your Business Central Production Environment! You may find a particular method stands out as being the obvious choice for your organization, or you may need to mull over the choices. It is also possible to use a combination of several different methods if it makes sense for your organization. You can now be confident that your production environment is safe and secure; good luck with your implementation!
For recommendations on user permission best practices, review our earlier blogpost on this topic.

The post Managing access to the Production Environment in Business Central Online appeared first on ERP Software Blog.

Every Dynamics conversation right now includes AI. Microsoft is building it into every product, every partner is promoting it, and every vendor demo ends with an AI feature that looks impressive on screen. The technology is genuinely powerful. But after years of implementing Dynamics and, increasingly, building AI into our own work and our clients', we've learned something the hype tends to skip: the technology is rarely the hard part.

Why most AI initiatives in ERP disappoint

AI initiatives in Dynamics don't usually fail because the AI isn't capable. They fail because the foundation underneath it isn't ready. Clean data, clear processes, and real governance are what make AI useful. Without them, AI just produces confident, wrong answers faster.
We see it often: a company gets excited about an AI capability, layers it onto messy data and undefined processes, and ends up with output nobody trusts. The problem was never the AI. It was everything the AI was built on.

Get the foundation right first

Before you invest in AI features, it's worth asking a few unglamorous questions:

• Is your data clean, consistent, and structured well enough for AI to draw from?
• Are your core processes defined, or are they held together by workarounds and tribal knowledge?
• Do you have governance in place so AI-driven decisions can be trusted and explained?

If the answer to those is shaky, that's where the work is, and doing it first is what makes any AI investment pay off later. It's less exciting than a demo, but it's the difference between AI that delivers and AI that becomes shelfware.

Pick the uses that actually pay off

Not every AI capability is worth doing. The ones that deliver real ROI tend to solve a specific, repetitive, high-volume problem, invoice processing, reporting, surfacing insights from data you already have. The ones that disappoint tend to be adopted because they're new, not because they solve anything.
We'd rather help a client deliver one AI capability that pays for itself than ten that look good in a pitch. That's the test worth applying: not "can we do this with AI?" but "will this actually move the numbers?" 

The honest bottom line

AI is going to be a real part of how businesses run on Dynamics, and companies that use it well will have a genuine advantage. But the winners won't be the ones who adopted the most AI fastest. They'll be the ones who got their foundation right and applied AI where it genuinely delivered.
If someone is promising AI will transform your business before they've asked about your data, be skeptical.
 Poize2 is a senior Microsoft Dynamics team. We build real AI, including our own delivery tools, and help clients cut through the noise to find the AI uses that deliver genuine ROI. We specialize in rescuing troubled Dynamics projects and delivering ones that stay on track. Learn more at www.poize2.com.

The post AI in Dynamics 365: How to Get Real ROI, Not Hype appeared first on ERP Software Blog.

Given the capabilities of Dynamics 365 Business Central, it will not surprise anyone to learn that Tensoft uses it internally to streamline financial processes and scale efficiently.
 
A few people from our Finance team joined us for a short interview to share their experience with Dynamics 365 Business Central – the migration process from Microsoft Dynamics GP and the implementation of this robust business management system, the features they like, and its advantages. You can watch the case study video or read the transcript below:
 

 
Video Transcript:
 
Bob Scarborough, President and CEO:
Tensoft was an early adopter of Dynamics 365 Business Central. Tensoft has a high level of comfort with business systems.
 
We were on Dynamics GP, another Microsoft product. We did some design brainstorming about the Chart of Accounts we wanted and the financial Dimensions that we wanted and in January, we just implemented the system. Week one was financial setup, week two was payables, week three was customers and receivables, and we were live. We were basically live in about 3 weeks.
 
Anne Phan, Contract Management Specialist:
It was very easy for me to adapt to Business Central. I was using GP a little bit beforehand and it does feel a lot more intuitive.
 
I used to use GP to download trial balances and to help with collection calls. However, it's a lot easier to do on BC because I can very easily remove data from the screen that I don't need so that only things such as the invoice number, the amount due, the due date and things like that are available.
 
Bob Scarborough, President and CEO:
I really like the Home Page. The homepage has the links that I need to where I want to drill down to the things that I do in the system. The homepage has the key accounts that I monitor for our company health and I can monitor a dozen accounts and know pretty much where we stand at any one point.
 
A second feature I really like is the Cash reconciliation - the cash management. I do reconcile or integrate the cash to our bank most days. I can do that a lot of days in 15 minutes, 10-15 minutes at the beginning of the day with a cup of coffee and have our cash reconciled through the previous day with the bank and that's really been a streamlined and easy to use function.
 
Anne Phan, Contract Management Specialist:
One of the features that I like is the ability to personalize each screen that you go on to so that the important data and information is available to you at like instantly. I set up my sales invoice screen to show important sections that I will need to input data and so it's a lot easier for me to set them up when only the data fields that I need to input are visible.
 
Bob Scarborough, President and CEO:
I think Business Central saves us time and money because it is maintained. We don't have to worry about security, we don’t have to worry about platform integrity and upgrades. Those are all done for us.
 
Anne Phan, Contract Management Specialist:
I think I like the overall experience with Business Central. It's a very clean and modern interface. It's easy to use and easy to figure out how to use because there's just a lot of information out there and training available.
 
Bob Scarborough, President and CEO:
Microsoft is one of those companies, and they are all about cloud applications and this application Business Central is viewed as part of their Office 365 suite. And so this is really from a vision perspective, from an ability to deliver perspective, from a view of the market, this is a product that I can count on now and for foreseeable future any of us could realistically have.
 
- Tensoft, a Microsoft Dynamics 365 Business Central Partner

The post Tensoft: Customer Success Story with Microsoft Dynamics 365 Business Central appeared first on ERP Software Blog.

Most of this series has covered countries with real-time XML clearance: generate a document, send it to the tax authority, get a validation code back. Nicaragua doesn't work that way — not yet. For companies rolling out Business Central Nicaragua, that difference changes what "compliance" actually means day to day.
Understanding that gap up front prevents a common mistake: building a Nicaragua project around assumptions carried over from Costa Rica, Guatemala, or Mexico.

How Nicaragua's Model Actually Works

The Dirección General de Ingresos (DGI) authorizes companies to issue invoices directly from a computerized system — known locally as Facturación por Medios Electrónicos — instead of requiring pre-printed invoice books. That authorization request goes through the Ventanilla Electrónica Tributaria (VET), the DGI's online portal. But there's no live XML submission for each invoice and no real-time validation code returned per document, the way Costa Rica or Mexico work. The company itself, together with its accountant, carries more of the ongoing compliance responsibility.

What Gets Reported, and How

Instead, compliance centers on the monthly Libro de Ventas (sales ledger), submitted through the VET, along with authorized numbering ranges printed on each invoice. The DGI has signaled interest in a future real-time validation API, but as of this writing, that infrastructure isn't in place.

Where This Shows Up in Business Central Nicaragua Projects

For implementation teams, the priorities look different here than elsewhere in LATAM:

• Registering authorized invoice number ranges and monitoring them before they run out
• Generating the monthly Libro de Ventas in the format the DGI expects for VET submission
• Applying IR (income tax) source withholdings and VAT correctly by transaction type
• Handling the Impuesto Selectivo al Consumo (ISC) for goods it applies to
• Keeping fiscal records organized for the retention period Nicaraguan law requires
• Adapting quickly if and when the DGI introduces a real-time validation requirement

Common Challenges in Nicaragua Implementations

Most issues we see stem from carrying assumptions over from other countries:

• Building for a real-time validation API that doesn't exist yet in Nicaragua
• Underinvesting in the monthly Libro de Ventas process because there's no per-invoice validation step to force the issue
• Losing track of authorized numbering ranges without a system that monitors them
• Treating Nicaragua and Costa Rica as interchangeable simply because they're neighbors
• Assuming a lighter technical footprint also means lighter penalties for non-compliance

The lack of live validation doesn't mean the rules are lighter — it means the compliance burden shifts toward accurate monthly reporting instead of document-by-document checks.

Why a Dedicated Localization Still Matters for Business Central Nicaragua

A proper Nicaragua localization manages authorized numbering ranges, applies IR, VAT, and ISC correctly, and generates the Libro de Ventas and other DGI reports in the required format. Built as an extension, it keeps Business Central's core untouched while staying ready for whatever comes next as Nicaragua's digital tax framework evolves — including a future move toward real-time validation, if and when the DGI rolls one out.

How LLB Solutions Supports Business Central Nicaragua

LLB Solutions' Nicaragua Localization for Microsoft Dynamics 365 Business Central covers DGI tax and accounting obligations, IR source withholding, VAT, and ISC — built as an AppSource-certified extension aligned with current Nicaraguan requirements, and monitored for updates as the country's framework matures.

Final Thoughts

Nicaragua is a reminder that "LATAM electronic invoicing" isn't one single model. Companies that recognize the country's current framework for what it is — authorization-based invoicing plus monthly reporting, not live XML clearance — configure Business Central Nicaragua correctly the first time instead of building for infrastructure that isn't there yet.
For Microsoft partners moving between countries on a regional rollout, that distinction is worth calling out explicitly during scoping, before it becomes an assumption baked into the wrong design.
See how LLB Solutions' Nicaragua Localization fits your Business Central project — Contact LLB Solutions

The post Business Central Nicaragua: Why Compliance Looks Different Here appeared first on ERP Software Blog.

If you are evaluating or already using Microsoft Dynamics 365 Finance & Operations (F&O), you have probably heard terms such as General Ledger, Master Planning, Warehouse Management, or Production Control. But do you know what each capability actually does for the business, how the pieces fit together, and which to prioritize first? This 2026 guide breaks down the core Finance and Supply Chain Management capabilities in practical terms, covering what each one does, the business value it can deliver, and the implementation considerations that can determine whether that value appears after go-live.
Before we begin, it is important to make a distinction when looking at the modules. Microsoft now presents Dynamics 365 Finance and Dynamics 365 Supply Chain Management (SCM) as separate applications within its Finance and Operations application family. Organizations can license and implement these applications according to their requirements, while both share the underlying finance and operations platform. Proactively addressing core Dynamics 365 F&O implementation challenges during architectural planning prevents operational disruptions across multi-module deployments. In this article, “F&O” is used as shorthand for the combined Finance and SCM capability set commonly considered in an enterprise ERP program.
When implemented with discipline, F&O can improve the financial close, cash visibility, working capital management, inventory accuracy, production planning, fulfillment, and compliance across entities and jurisdictions. The greater value comes from integrating these capabilities into end-to-end business processes such as procure-to-pay, order-to-cash, plan-to-produce, and acquire-to-retire. An ERP with 25 modules that barely speak to one another is still a rather expensive collection of menus.

Core Finance Modules

1. General Ledger

The General Ledger is the financial foundation of Dynamics 365 Finance. It manages the chart of accounts, financial dimensions, journals, allocations, period close, consolidations, and intercompany accounting.
Business value: It provides a consistent basis for financial reporting, management analysis, multi-entity accounting, and audit controls.
Implementation consideration: Account structures, dimensions, fiscal calendars, and posting rules should be established early, as they influence transactions across the broader ERP.
Conducting a formal Dynamics 365 F&O assessment ensures your chart of accounts and financial dimension hierarchy support complex multi-entity reporting needs.

2. Accounts Payable

Accounts Payable manages the vendor invoice-to-payment cycle, including vendor records, invoice processing, purchase-order matching, approvals, payments, settlements, and credit processing.
Business value: It strengthens invoice control, payment planning, working-capital visibility, and exception management.
Implementation consideration: Approval workflows and three-way matching should align with actual purchasing policies and authority levels.

3. Accounts Receivable

Accounts Receivable manages customer invoicing, credit limits, collections, payments, settlements, credit notes, and dunning.
Business value: It supports stronger cash forecasting, collection discipline, credit control, and visibility into outstanding receivables.
Implementation consideration: AR should be designed in tandem with sales and project invoicing processes.

4. Cash and Bank Management

Cash and Bank Management oversees bank accounts, statements, reconciliations, payments, cash positions, and liquidity forecasting.
Business value: It provides clearer visibility into actual cash positions and expected inflows and outflows across banking relationships.
Implementation consideration: Automated statement imports and reconciliation are especially valuable for organizations managing multiple banks or currencies.

5. Budgeting and Budget Control

Budgeting supports budget preparation, approval, revision, allocation, spending control, and variance analysis.
Business value: It helps organizations maintain spending discipline while providing management with greater visibility into budget performance.
Implementation consideration: Controls should be placed at the appropriate points in the purchasing and expense process so they do not unnecessarily delay routine activities.

6. Fixed Assets and Asset Leasing

Fixed Assets manages acquisition, capitalization, depreciation, transfer, impairment, disposal, and reporting. Asset Leasing adds lease-accounting capabilities.
Business value: It provides accurate asset registers, depreciation records, visibility into capital expenditures, and reporting.
Implementation considerations: Asset categories, depreciation books, and capitalization thresholds should align with statutory and management reporting requirements.

7. Cost Accounting

Cost Accounting provides management with cost analysis using cost elements, cost objects, allocation bases, and overhead rules.
Business value: It helps organizations understand costs and profitability across products, departments, customers, projects, and shared services.
Implementation consideration: Cost models should have clear ownership and be backed by reliable operational data.

8. Tax and Globalization

Tax and Globalization supports tax calculation, tax codes, withholding, reporting, and country-specific regulatory requirements.
Business value: It supports compliant transaction processing and reporting across different entities and jurisdictions.
Implementation consideration: Local requirements in India, such as GST, TDS, e-invoicing, and e-way bills, should be incorporated into the solution design.

Core Supply Chain Management Modules

1. Product Information Management

Product Information Management defines products, variants, configurations, units, categories, attributes, and lifecycle information used throughout supply chain processes.
Business value: Reliable product data supports consistent purchasing, planning, manufacturing, inventory management, warehousing, pricing, and reporting.
Implementation consideration: Product governance should be treated as an ongoing business responsibility, not simply a migration exercise.
Reviewing a structured Dynamics 365 data migration guide helps clarify data cleansing requirements and entity mapping rules before importing master records.

2. Procurement and Sourcing

Procurement and Sourcing manages requisitions, sourcing events, RFQs, purchase agreements, purchase orders, receipts, returns, and supplier collaboration activities.
Business value: It improves purchasing control, supplier visibility, spend management, and compliance with procurement policies.
Implementation consideration: Procurement should be designed in collaboration with Accounts Payable to support accurate invoice matching and clear ownership.

3. Inventory Management

Inventory Management manages stock quantities, value, availability, reservations, transfers, counting, and inventory closing.
Business value: It provides better visibility into stock across sites, warehouses, locations, batches, and serial numbers.
Implementation consideration: Inventory dimensions should provide the necessary control without introducing unnecessary transaction complexity.

4. Warehouse Management

Warehouse Management supports directed warehouse operations, mobile processes, waves, replenishment, license plates, picking, and put-away.
Business value: It can improve picking accuracy, warehouse throughput, stock visibility, and replenishment control.
Implementation consideration: WMS should be introduced where warehouse operations genuinely require directed work and more sophisticated execution controls.

5. Master Planning

Master Planning uses demand, supply, inventory, lead times, forecasts, and capacity data to generate planned orders and recommendations.
Business value: It helps reduce stockouts and excess inventory while providing planners with clearer purchasing and production signals.
Implementation consideration: Planning depends heavily on reliable lead times, BOMs, safety stocks, calendars, and inventory records.

6. Production Control

Production Control supports discrete, process, and lean manufacturing, including production orders, BOMs, routes, scheduling, material consumption, and production reporting.
Business value: It provides greater visibility into production schedules, materials, capacity, costs, and manufacturing performance.
Implementation consideration: The selected manufacturing model should reflect how the organization actually produces and costs its products.

7. Transportation Management

Transportation Management manages loads, routes, carriers, freight rates, and shipment-related processes.
Business value: It provides greater visibility into freight costs, carrier performance, shipment planning, and delivery operations.
Implementation consideration: Carrier, lane, route, service, and rate data require clear ownership.

8. Landed Cost

Landed Cost tracks inbound shipments and associated costs such as freight, duty, insurance, and handling.
Business value: It gives import-heavy organizations a clearer view of the true acquisition cost of inventory and its impact on margins.
Implementation consideration: Cost allocation should reflect how the organization actually manages imports and inventory valuation.

9. Asset Management

Asset Management supports equipment and facility maintenance through work orders, preventive maintenance, asset hierarchies, spare parts, labor, and downtime tracking.
Business value: It helps reduce unplanned downtime and improves visibility into maintenance activity and asset costs.
Implementation consideration: Asset Management complements Fixed Assets: one handles operational maintenance, while the other handles financial accounting.

10. Quality Management

Quality Management supports inspections, sampling, test results, quarantine, and nonconformance management.
Business value: It strengthens quality control, traceability, supplier quality, and the management of nonconforming products.
Implementation consideration: Quality controls should fit the actual production and warehouse processes rather than create unnecessary operational delays.

Which modules should go live first?

There is no universal module sequence for F&O. The right starting point depends on the organization’s processes, legacy environment, regulatory requirements, and transformation priorities.
A common approach is to first establish the financial and core master data foundations, then build the operational capabilities most closely aligned with business priorities, such as procurement, inventory, sales fulfilment, warehousing, planning, or production. More specialized capabilities can follow in later phases.
The key is to sequence the rollout around business processes and dependencies, rather than attempting to activate every capability simultaneously.
Engaging specialized Dynamics 365 Finance & Operations implementation services ensures that module dependencies, testing schedules, and cutover timelines remain aligned with business goals.

How LevelShift helps organizations implement F&O

At LevelShift, we help organizations design and implement Dynamics 365 F&O focused on business outcomes rather than feature checklists. Our approach begins with end-to-end processes such as procure-to-pay, order-to-cash, plan-to-produce, and acquire-to-retire, then identifies the modules, configurations, integrations, and data foundations needed to support them.
Our F&O implementation expertise covers:

• Business process and solution design
• Finance and supply chain configuration
• Data migration and validation
• Integrations and security
• Testing and deployment
• Phased rollouts and post-go-live support

Whether replacing a legacy ERP, implementing F&O for the first time, or expanding an existing footprint, LevelShift helps organizations balance Microsoft best practices with industry requirements, localization, and long-term scalability.

Conclusion

Dynamics 365 Finance and Supply Chain Management is more than a collection of modules. Its value comes from connecting financial control with the physical processes that keep an organization operating, from purchasing and production through inventory, warehousing, fulfillment, and cash collection.
The right implementation does not require every module to go live at once. It requires clear priorities, sound data and process foundations, and a rollout sequence that gives each capability a defined purpose. For organizations evaluating F&O in 2026, this approach provides a practical foundation for stronger control, better operational visibility, and more informed decision-making.

FAQs

1. Is Dynamics 365 F&O a single application?
   F&O broadly refers to the finance and operations application family. Dynamics 365 Finance and Supply Chain Management are separate applications that share the underlying platform.
2. Do organizations need every F&O module?
   No. Modules should be selected according to business processes, industry requirements, and implementation priorities.
3. Which F&O modules should go live first?
   There is no universal sequence. Finance, master data, and foundational configuration often come first, followed by operational capabilities aligned with business priorities.
4. What is the difference between Fixed Assets and Asset Management?
   Fixed Assets handles the financial accounting for assets. Asset Management focuses on maintaining operational equipment and facilities.
5. How long does an F&O implementation take?
   It varies by scope, entities, countries, modules, integrations, data complexity, and rollout strategy.

The post Every Dynamics 365 F&O Module, Explained: 2026 Edition appeared first on ERP Software Blog.

Business Central has very deep functionality across most business functions, and its mechanisms such as dimensions can be used to do some amazing things.  It is an extensive application with impressive capabilities, but there are still functional limitations for certain requirements.  One of these gaps is hit when there is a need for fund accounting, and this can be surprising for users switching from other platforms that had native functionality for it. 
Fund Accounting Overview 
As a simple crash course for the uninitiated, funds are encountered often in the not-for-profit world, where there is a need to fully account for funds established for various purposes.  There may be an operating fund for ongoing expenses and other funds established through donor grants.  In these cases, a fully balanced general ledger needs to be maintained for each fund…the fund identifier is far more than just a classification for transactions.  A related core requirement here is automatic posting of due-to / due-from entries between funds when transactions cross fund lines.  As an example, a vendor invoice might be posted into the operating fund, but it might have lines that are allocated against other funds.  When this happens, those other funds will need to legally reimburse the operating fund for the expenses paid on their behalf, which creates the need for the dues entries.   
The Options in Business Central 
So, how can we handle this in Business Central?  It’s easy enough to set up a dimension for FUND, and to set up each fund as a dimension value, but we have the two core requirements above as gaps: 

1. There is no way to enforce G/L balancing by a dimension value, so nothing will keep the general ledger in balance for each fund. 
2. When transactions cross fund (dimension value) lines, there is no automatic mechanism to post the dues entries between them – users would need to do that manually for every transaction that crosses funds. 

This leaves us with three options:

1. Manual user handling – users try to post entries that are balanced by fund, manually adding due-from/due-to entries either during transactions or as adjustments after.  At month end, time is spent reconciling and investigating balancing/dues issues to post corrections. 
2. Customization – Business Central is highly extensible, so custom development can be done to implement the required functionality.  The downside here is complexity and scope.  The effort to customize the application to implement these controls and functionality is very significant and also creates ongoing maintenance work to carry the work forward and support it. 
3. Third party ISV apps – Business Central has a huge marketplace of third-party ISV apps to extend the application functionality for different industries and requirements, including options for fund accounting. 

To those moving forward with option 1, I sincerely wish you the best of luck.  We have seen this approach taken by companies on Business Central and it creates a significant workload for the accounting staff to try to manually manage balancing and dues between funds.  There’s little value in time spent posting entries manually that could be automated, or in sorting out balancing issues within each fund.  The only reason to go this route is to avoid incurring software or services costs…at the expense of higher ongoing labour costs. 
Option 2 is one way to TRY to eliminate manual work, but it is a significant undertaking that would have a very substantial IT or services cost up front that would also introduce ongoing costs to maintain the functionality, support issues that come up and handle updates for future releases of Business Central.  Also, where ISV fund accounting apps (option 3 to follow) may offer extensive functionality outside of the core balancing and dues posting, every bit of functionality in a custom approach would need to be planned out and built.  The likelihood of snowballing scope and costs is high, while the complexity of the core requirement alone makes this a risky initiative. 
This brings us to option 3, which is to leverage the extensive ecosystem of third-party ISV apps for Business Central.  The good news here is that there are options, and we have our own with DimensionPath Fund Accounting.  Our app is focused purely on the financial side of fund accounting, as opposed to other solutions in this space which take a much broader approach in terms of operational functionality for non-profits.  We openly advise prospective customers that if they need functionality to manage things like donors, constituents, etc. they should look at those other options.  Our solution focuses on the core financial requirements, providing a solution at a much lower price than our competitors for this reason.  While DimensionPath does not introduce a lot of operational functionality, it does cover other related financial requirements such as: 

• Balance controls for managing grants (using a dimension) or to protect the principle portion of funds if applicable 

• Commitment/encumbrance management, so that committed amounts on open purchase orders (not yet completed or invoiced by the respective vendors) are recognized and vetted against any applicable balance controls 

• Dimension shortcut codes 

• In the non-profit world, there tend to be several dimensions defined for various purposes, typically tied to budgetary controls 

• DimensionPath’s Dimension Relations provide a mechanism to establish shortcut codes that can populate a defined set of dimension values with one selection 

• Not to confuse matters, but DimensionPath also provides other tools related to dimension streamlining and control, such as our Allowed Dimension Combinations and even a Segmented Chart of Accounts to ease the transition for users coming from an “old school” segmented system

G/L Balancing toggle and Dues Posting Setups in DimensionPath 
Benefits of the Right Design 
When we talk about DimensionPath versus the competition, we also emphasize that our design is much closer to out of the box Business Central.  DimensionPath does not add a lot of additional tables and fields – we don’t even add a hardcoded “Fund No.” anywhere.  The product was built entirely around dimensions and other base BC functionality to fully leverage what is there out of the box without complicating life.  When looking at the app options, it is important to assess whether they come with any limitations (Can you use all base BC reporting and analysis tools for funds?  Are there base functions that cannot be used due to compatibility issues?) and also whether they collide with other ISV apps, requiring special extensions to adapt them.  Two big selling points for DimensionPath are: 

• It breaks NOTHING in base Business Central.  Every part of the base functionality works with DimensionPath with no compromises. 

• Its “clean” design enables it to work very well with almost all other ISV apps.  As I write this, we have only encountered one other ISV app that had a true compatibility issue and required a special extension.  In general, if an ISV app works with Business Central and dimensions, it will typically work with DimensionPath with nothing special to do. 

Closing Remarks 
In summary, Business Central is lacking proper fund accounting functionality out of the box but there are multiple ways to address that gap.  Once that is done, Business Central handles fund accounting beautifully, leveraging its dimension functionality (with our approach anyway) at the core.  So, don’t discount Business Central as a fund accounting platform just because it isn’t there out of the box – it is more than up to the task.  With our DimensionPath app, there is a better path! 
Learn more and download DimensionPath Fund Accounting from AppSource and please visit our Website.

The post The Fund Accounting Gap in Business Central appeared first on ERP Software Blog.

Two manufacturers with the same headcount can walk away with wildly different Business Central estimates, and it usually has nothing to do with revenue. It comes down to how the product actually gets built. 
That's the gap a generic pricing page can't close. A "starting at" number doesn't know whether you run stable, simple bills of materials or highly configurable products with engineering changes every month. Our Quick Quote tool exists to close that gap. Instead of a flat number or a "book a call" form, it asks a handful of questions specific to manufacturing and gives you a real estimate back in a few minutes, no sales conversation required.

Where the Cost Comes From 

The questions aren't generic. For a manufacturer, three things move the number more than anything else. 
Production complexity. Do you use production orders built on bills of materials and routings? If you need material requirements planning (MRP) or master production scheduling (MPS) to manage purchasing and production against demand, that's a materially bigger scope than a company doing basic kitting or light assembly. The tool asks this directly because it's the single biggest cost driver in a manufacturing implementation. 
Traceability requirements. If you're in food and beverage, life sciences, or aerospace and defense, lot or serial tracking usually isn't optional. It lets you trace raw materials through production and out to the customer who received the finished goods. We ask about this because it changes both configuration and training scope, and it's easy to underestimate if you've never scoped an ERP project before. 
Structure and volume. How many companies make up your business, how many sales orders you enter per day, and your approximate SKU count all tell us how much data has to move and how many users need access. A single-entity shop with a few hundred SKUs is a different project than a multi-company group processing dozens of orders a day. 

What This Means for Your Estimate

None of this is meant to make Business Central sound complicated for the sake of it. It's meant to explain why the number you get back is actually useful. A generic industry benchmark can't account for whether your BOMs have three levels or twelve, or whether you're tracking lots for a recall program. Ours can, because we're asking about your operation specifically before we give you a range.

Frequently Asked Questions 

Does Business Central support MRP for manufacturers? 

Yes. Business Central includes material requirements planning and master production scheduling to help plan purchasing and production against demand and existing inventory. 

How much does Business Central cost for a manufacturer? 

There's no single number. Cost depends on production complexity, how many users need access, and how much traceability and inventory tracking your industry requires. Manufacturers with basic financials and simple inventory land at the low end; those needing MRP, lot traceability, and multi-company consolidation land higher. 

Get Your Number 

Our Quick Quote tool walks through these same questions and hands you a real estimate built around how you actually manufacture, not a generic industry average. It takes a few minutes, and there's no call required to see your number.

The post Dynamics 365 Business Central Price Quote for Manufacturing Companies  appeared first on ERP Software Blog.

The delivery arrives. The receiving team checks the paperwork, posts the purchase receipt and books the stock into the warehouse. At that point, any Business Central receipt discrepancies become part of the inventory record.
Weeks later, somebody discovers one of the most common Business Central receipt discrepancies: the quantity was wrong.
Perhaps fewer items arrived than the receipt showed. The team may have accepted the wrong product, or put damaged stock away as usable inventory. The warehouse may have kept excess stock without anyone updating the invoice. Or the goods arrived correctly, but the receipt was posted late, or against the wrong purchase order.
By then the discrepancy has travelled through the business. Inventory availability is wrong, the supplier invoice does not match, purchasing places another order it did not need, and sales promises stock that is not there.
A small receiving error has become an expensive operational problem.

Why Business Central receipt discrepancies cost more than they look

Receiving is the point where a supplier's delivery becomes part of your inventory records. If the recorded receipt does not reflect what physically arrived, every process that uses that record starts from the wrong answer. That is why Business Central receipt discrepancies spread so quickly.
The consequences include:

• Paying for quantities that were not received.
• Carrying excess stock that was not required.
• Incorrect inventory availability in Business Central.
• Warehouse time spent recounting and relocating stock.
• Production or customer orders delayed by missing items.
• Emergency purchasing and premium freight.
• Supplier performance figures based on inaccurate receipts.
• Time spent reconciling purchase orders, receipts and invoices.

Take an ordinary case. A business orders 100 units of a production component, but only 95 arrive. Nobody counts, so the team posts the receipt at 100. Two weeks later, the line stops five units short. The fix is a spot purchase at a premium, air freight instead of road, and overtime to recover the schedule — and the business pays the original supplier for 100 units unless someone also catches the invoice. None of it appears under a heading called receiving errors. It lands in purchasing, freight, production and finance separately, which is exactly why the total is easy to underestimate.

How receipt discrepancies continue after posting

Posting a receipt creates the Business Central record of what entered the organisation, and it updates inventory, availability and the quantity waiting to be invoiced at the same time. Correcting it afterwards is possible but not free. While the receipt line is un-invoiced and the goods have not moved on, Undo Receipt reverses the posted quantity; once the line has been invoiced, the correction becomes a purchase return order and credit memo, with the supplier involved. Either way, the wrong quantity has been in the system for as long as it took someone to notice. The team can catch a discrepancy most cheaply before it posts the receipt and puts the goods away.
A reliable receiving process confirms that:

1. The delivery belongs to the correct purchase order.
2. The item received matches the item ordered.
3. The physical quantity matches the quantity being posted.
4. Separate damaged or rejected goods.
5. Record lot, serial and expiration information where required.
6. Retain the supplier's delivery reference.
7. Document and communicate any shortage, excess or substitution.

The purpose is not to slow the warehouse down. It is to stop an unresolved exception from becoming a larger problem elsewhere.

Short receipts are Business Central receipt discrepancies that need to stay visible

A supplier may deliver only part of the quantity ordered. Business Central supports partial receipts: the user enters the quantity actually received in the Qty. to Receive field, and the remaining quantity stays outstanding on the purchase order.
That outstanding quantity matters. It may be stock needed for a production order, a customer commitment or a planned replenishment. If teams look only at the quantity received, the remaining risk disappears from view.
A short receipt should trigger clear questions:

• Is the balance still expected?
• Has the supplier provided a revised date?
• Does the shortage affect production or customer orders?
• Is an alternative supplier or substitute item available?
• Should the outstanding quantity remain open?
• Who is responsible for following up?

Recording the correct quantity is only the first step; someone still has to manage what is missing.
How you manage it changes the numbers. When a supplier cannot complete an order, purchasing teams handle it in one of three ways in Business Central: leave the line open until the balance arrives, delete the outstanding quantity and source it elsewhere, or reduce the order to what was delivered and raise a new order for the remainder with a new promised date. Each is legitimate, and each leaves a different trace. Fill rate and in-full measures are calculated from open purchase order lines as they stand at the time of the data refresh, so an order trimmed to what actually arrived looks completely fulfilled, while the same order left open looks late. Neither view is wrong, but they are not comparable. Read vendor fill rate alongside your purchase order clean-up routine, and keep that routine consistent.

Over-receipts hide a purchasing decision

Sometimes a supplier sends more than the quantity ordered. These Business Central receipt discrepancies may seem harmless, and keeping the excess may be practical. However, the decision should be deliberate rather than an unnoticed warehouse outcome.
Business Central supports over-receipt codes that define how much extra quantity a team can accept. Administrators assign a tolerance to items or vendors, and the business can require an approval workflow. Microsoft's guidance on correcting purchase documents covers the controls available when a purchasing record has to be corrected afterwards.
Business Central does not settle the financial treatment of an over-receipt. The business still has to agree how the supplier will invoice the additional quantity, or whether the goods go back.
There is a reporting consequence too. When the receiving team accepts an over-receipt, Business Central raises the line quantity to the quantity received and records the difference in the Over-Receipt Quantity field. From then on the order looks exactly filled in any comparison of received against ordered quantity. The excess is visible, but only to someone who looks at that field, which is why over-receipts deserve their own review rather than being left to surface as a variance.
Before accepting an over-receipt, consider:

• Is there enough storage capacity?
• Will the excess stock be used before it becomes obsolete?
• Does it create additional working-capital pressure?
• Has the supplier agreed the price?
• Does the quantity exceed the approved tolerance?
• Should the goods be returned instead?

An extra ten units look harmless at the receiving dock. Repeated across many deliveries, over-receipts quietly increase inventory and eat warehouse space.

Late against which date?

“Late” only means something against a date, and a Business Central purchase line carries more than one. The Requested Receipt Date records when you asked for the delivery. By contrast, the Promised Receipt Date records the date the supplier confirmed. Business Central calculates the Planned Receipt Date for arrival at your location, then adds inbound warehouse handling time and any safety lead time to produce the Expected Receipt Date.
They answer different questions. A delivery that arrives after the requested date but on the promised date is not a supplier failure: the supplier told you when it would arrive and delivered accordingly. Measure against the requested date and you are scoring your own expectations; measure against the promised date and you are scoring the supplier. A supplier scorecard usually belongs on the promised date, while replenishment and capacity planning care about the expected date.

How posting dates affect Business Central receipt discrepancies

The posting date matters just as much. A receipt line is late when its posting date falls after the date you are measuring against. If goods arrive on Monday and the warehouse posts the receipt on Wednesday, the supplier looks two days later than it was and the receipt lands in a different week's figures. Late or early posting also distorts inventory availability, replenishment suggestions, period-end purchase accruals and the apparent time taken to receive and put away stock. Agree with the warehouse when receipts are posted, and treat the posting date as an operational fact rather than an administrative field.
Two more rules are easy to miss. The report assesses open purchase order lines against the date of your most recent data refresh, so a line becomes overdue the day after its committed date passes; measures that include open orders move as time passes, while measures based only on posted receipts stay fixed. And a line with no value in the date you selected has nothing to be late against, so it counts as on time unless blank dates are excluded from the analysis.
In the Receipt Analytics reports, the Receipt Calculation Base Date selection switches every measure between the four dates, and a separate setting assigns the receipt to either its posting period or its due period.

Averages hide the problem

A monthly total can look reasonable while individual receipts contain serious problems.
Receiving 105 units against one order and 95 against another produces the expected total of 200. The aggregate is correct, but one order was over-received and the other is still short.
The level you count at matters as much as the total.
Counted by purchase order, one late line makes the whole order late. At order-line level, a twenty-line order and a two-line order are weighted by the lines they contain, which is usually the fairer basis for a supplier scorecard. A quantity-based calculation gives one late line of 10,000 pieces more weight than ten late lines of one piece each. The report assesses a partially received order as a whole: it is on time only if every line received so far arrived on time and nothing still open is overdue. A supplier being on time with the part they have delivered does not make the order on time.
Useful receipt analysis lets teams move from the summary into the underlying vendor, item, location, purchase order and receipt-line detail, and choose the level the summary is counted at. Look for vendors with repeated partial deliveries, items that regularly arrive over or under the ordered quantity, locations that post late, and sudden changes in fill rate or on-time performance.
The aim is not to find one mistake but to find where the receiving process repeatedly creates risk.

Review Business Central receipt discrepancies after every refresh

A practical review does not examine every receipt. Start with the exceptions most likely to affect the business.
After each reporting refresh:

1. Review incomplete receipts. Identify important purchase orders with quantities still outstanding.
2. Check overdue balances. Find expected quantities that have not arrived by the agreed date.
3. Investigate unusual quantities. Review over-receipts, repeated partial deliveries and unexpected changes.
4. Prioritise critical items. Focus on shortages affecting production, customer orders or low-stock positions.
5. Assign follow-up. Give each material exception an owner and a next action.
6. Review recurring causes. Separate isolated mistakes from supplier or process patterns.

The Receipt Analytics reports in Purchasing Insights support this review process. Receipt Days shows how long each supplier takes and how far from the committed date they land, by vendor, item, location, purchaser or period; its Average Delays method answers how late a supplier is when they are late. On-Time Receipt scores purchase orders, order lines, receipts or quantity against the date you choose and drills from a company-wide percentage to the individual orders that missed. Vendor Fill Rate shows how much of what you ordered arrived without being left on back-order, by order, line or quantity. The Receipt Cube puts any of these side by side — actual receipt days, on-time percentage and fill rate by vendor and month, for example — which is the basis of a supplier scorecard. The Receipt Analytics tutorial sets out each report's definitions and settings.

Separate supplier issues from internal receiving problems

A discrepancy in the report does not mean the supplier caused it.
The supplier may have delivered the correct goods while the warehouse recorded the wrong quantity. A delayed posting can make an on-time delivery look late. The report may be scoring the supplier against your requested date rather than the date they promised. An outdated purchase order may not reflect a change that both parties agreed by email or telephone, and an incorrect unit of measure can make a valid receipt look unusual.
When investigating an exception, compare:

• The original purchase order.
• Any confirmed amendments.
• The supplier's delivery documentation.
• The physical quantity received.
• The quantity posted in Business Central.
• The date and time of arrival.
• The posting date.
• Any returns, corrections or credit notes.

The distinction matters. Supplier problems need a supplier conversation; internal process problems need training, controls or better data. Treating both as the same issue stops the team fixing the underlying cause.
Business Central receipt discrepancies are one part of the picture. Our previous article explains how Business Central supplier performance reporting can reveal hidden procurement costs.

Measure the process, not just the correction

Counting corrections tells you how many problems the team found. It does not show how many went undetected or how much disruption they caused.
Combine the exceptions with the measures that show whether the process is improving:

• Vendor fill rate by order, by line and by quantity.
• On-time receipt percentage against the promised date, by vendor and by item.
• Average delay when late, not just average lead time.
• Outstanding purchase quantity, including open lines already past their committed date.
• Items repeatedly received above or below the ordered quantity.
• Receipts posted several days after the goods arrived.
• Returns to suppliers, corrections and credit notes following receipt.
• Emergency purchases and inventory adjustments following receipt.
• Receipt and put-away time by location.

Tracked over time, these separate isolated mistakes from recurring supplier or warehouse problems. That shows whether receiving accuracy is improving and where intervention will pay back most.

Frequently asked questions

How does Business Central handle a partial purchase receipt? Enter the quantity actually received in the Qty. to Receive field and post the receipt. The remaining quantity stays outstanding on the purchase order, and the team can receive it later.
Can Business Central accept more than the ordered quantity? Yes, when an over-receipt code and tolerance are configured, and the business can require approval. Business Central records the excess in the Over-Receipt Quantity field on the purchase line, and the business and supplier must still agree how to treat the additional quantity financially.
Why might a supplier appear late when the delivery arrived on time? Three common causes. The report is measuring against your requested date rather than the date the supplier promised; the warehouse posted the receipt days after the goods arrived, and the report uses the posting date; or nobody updated the purchase order after both parties agreed a change by phone or email. Confirm which date the report uses before assessing the supplier.
What if a purchase line has no promised or requested date? The report counts a line as on time when the selected date field is blank. If you want the percentage to reflect only lines with a real commitment, exclude blank dates from the analysis.
Should teams review receipt accuracy by supplier or by item? Use both. A supplier view reveals relationship-level patterns; item and location analysis exposes problems with particular products, units of measure or warehouse processes.
How often should teams review purchase receipt discrepancies? Review material exceptions daily or weekly, depending on purchasing volume and operational risk. Monthly trend analysis then identifies recurring supplier and process issues.

Find receiving problems before they spread

Business Central receipt discrepancies become expensive when they stay hidden.
The sooner the team identifies a shortage, an excess quantity, an incorrect item or a posting delay, the easier it is to protect inventory accuracy, resolve the issue with the supplier and prevent disruption elsewhere in the business.
Purchasing Insights from Business Central Insights provides ready-made Power BI reports for purchase receipt analysis, supplier performance, fill rate and outstanding purchasing commitments.
To explore the reports with your own Business Central data, start a free 30-day trial or book a demonstration.
Accurate receiving is not a warehouse administration task. It is one of the controls that protects stock availability, supplier accountability and margin.

The post Business Central Purchase Receipt Discrepancies That Quietly Drain Your Margin appeared first on ERP Software Blog.

Ask a payment vendor whether they are PCI compliant and the answer will almost always be yes. A more useful question for a Business Central team is: What PCI assessment does your payment architecture put you on?
That question matters because PCI compliance is not simply a certification a vendor can hand over. The scope of your cardholder data environment is influenced by how payment information moves through your systems, and those decisions often happen long before anyone starts thinking about compliance.

Why Payment Architecture Affects PCI Scope

Every payment integration makes decisions about where card data enters an environment, where it is stored, and which systems have access to it.
A Business Central implementation might include online payments, card-present terminals, multiple entities, or several payment gateways. Each connection can expand the environment that needs to be considered as part of PCI compliance.
PCI DSS 4.0 also raised the bar for organizations that store, process, or transmit cardholder data. The PCI Security Standards Council organizes its requirements around areas including network security, cardholder data protection, vulnerability management, access control, monitoring, and information security policies.
The question is not whether those requirements matter. It is how much of your environment actually falls within their scope.

Scope Can Change the Compliance Burden

Businesses validate PCI compliance through a Self-Assessment Questionnaire (SAQ), and the appropriate questionnaire depends on the organization's payment environment.
When a merchant never handles raw card numbers because payment information is captured through a hosted payment page or iframe, the assessment can be significantly narrower. SecurityMetrics notes that some merchants may face questionnaires with roughly 30 questions, while environments that store or directly handle card data can face much more extensive assessments.
That difference can translate into a meaningful difference in time, documentation, and resources.
The architecture decision therefore happens before the questionnaire. By the time a business discovers that its payment environment creates unnecessary scope, changing it can be expensive.

Designing Payments to Reduce Scope

For Business Central users, an architecture-first approach starts by keeping raw card data out of the ERP and internal systems wherever possible.
A hosted payment page or iframe can capture card information outside the merchant's environment. The card can then be replaced with a token, allowing Business Central to store a reference rather than the actual card number.
This approach can also support recurring billing and repeat purchases without requiring the ERP to store sensitive card information.
An independent card vault provides another layer of separation. Instead of tying stored payment credentials directly to one gateway, tokenized information can remain in a purpose-built environment.
The same principle applies to card-present payments. A terminal that communicates directly with the processor can help keep card data off the organization's internal network instead of routing it through systems that would then need to be secured within the PCI environment.

Ask About Architecture, Not Just Certifications

When evaluating a payment provider, asking whether it is PCI compliant is only the starting point.
Business Central teams should also ask where card data is captured, whether raw card numbers ever enter the ERP or internal network, when tokenization occurs, and what happens to PCI scope when the business adds another entity, gateway, currency, or card-present location.
Those questions can reveal much more about the actual compliance burden than a certification badge alone.
PCI obligations do not disappear when an organization reduces its scope. Businesses still need appropriate policies, access controls, monitoring, and annual validation. But a smaller cardholder data environment means fewer systems and processes need to be brought into that effort.

Start With Your Current Payment Flow

Before selecting a new payment provider, map how card data currently moves through your environment.
Look at each gateway, entity, payment page, and card-present location. Identify where raw card numbers touch your systems and where tokenization occurs.
That map can reveal where unnecessary PCI scope exists and where a different payment architecture could reduce the burden.
Want to see what an architecture-first approach could look like in Business Central? Read the full article, PCI Compliance Is an Architecture Decision, Not Just a Checkbox.

The post PCI Compliance Is an Architecture Decision, Not Just a Checkbox appeared first on ERP Software Blog.

If you’re already running Warehouse Insight or recommending it to clients, you know where the friction sits today: one screen for every job, a trade-off between picking speed and verification, dead zones that stall the floor, and a device fleet that doesn’t always match what the software expects.
Webinar: Warehouse Insight 3.0: A First Look for Business Central Partners and End-users
Date & time: October 7, 2026, 1:00 pm EDT (North America)
Register: https://dmsiworks.com/events/warehouse-insight-3-0-first-look-business-central

The post Warehouse Insight 3.0: A First Look for Business Central Partners and End-users appeared first on ERP Software Blog.

Dynamics 365 earns its place in a finance stack because it holds the general ledger, customer master, and financial data that leadership relies on. Accounts receivable is one module among many, and that arrangement can work well until a business adds customers billed in multiple currencies, increases invoice volume, or acquires a company running a different ERP.
Dynamics 365 Finance and Business Central are designed to serve as the operational core of a business, covering areas such as the general ledger, inventory, procurement, payroll, and receivables. That breadth is a major advantage, but it also means individual workflows may not receive the depth that finance teams need as transaction volumes grow.
Native AR functionality in D365 handles core tasks such as generating invoices, applying payments, and running aging reports. The challenges tend to emerge in the daily work that determines how quickly a company gets paid: adjusting reminder cadences by customer segment, matching partial payments in foreign currencies against multiple open invoices, and tracking billing disputes through resolution.
Finance teams running Business Central regularly turn to Microsoft’s own user forums looking for third-party applications that can automate reminders, track overdue accounts, and provide more structure around collections. D365 remains the system of record, but asking it to also serve as the primary workspace for collections exceptions and detailed remittance reconciliation can create friction that ultimately affects cash flow.
The working capital impact is significant. The Hackett Group’s 2025 U.S. Working Capital Survey found that days sales outstanding worsened for a second consecutive year among the 1,000 largest U.S. public companies. Receivables represented the largest share of the $1.7 trillion in excess working capital identified across those companies, with an 18-day gap between top-quartile performers and the median.
Some of that difference comes from payment terms and negotiating leverage. Process also matters, particularly the friction between an invoice being issued and a matched, reconciled payment reaching the ledger.
A dedicated AR layer can address that workflow while keeping the ERP in place as the system of record. Invoices can continue to originate in D365 with the same numbering, tax logic, and customer information the finance team already uses. Flywire’s Invoiced accounts receivable solution connects directly to Dynamics 365, embedding payment links into existing invoices and emails so customers can pay through a familiar document.
From there, AR automation can handle tasks D365 is less focused on, including customer-specific reminder cadences, dispute tracking, and matching incoming payments, including partial and multi-currency payments, to the correct open invoices. For cross-border transactions, currency conversion occurs before the match posts, allowing the amount flowing back into D365 to reconcile with the original billing.
The matched and reconciled record then flows back into the ERP automatically, reducing the need for AR teams to export spreadsheets or manually re-key payments.
For finance teams looking to improve invoice-to-cash without replacing Dynamics 365, extending the ERP with a dedicated AR workflow can provide a more structured way to manage collections, payments, disputes, and reconciliation while keeping D365 at the center of financial reporting.
Read the full article on Flywire’s website.

The post AR Automation for Dynamics 365: A Finance Team’s Guide to Invoice-to-Cash Inside D365 appeared first on ERP Software Blog.

AI makes weak data harder to ignore. Inconsistent records, missing values, and unclear ownership do not stay contained when models rely on them. They shape outputs, decisions, and risk across the business. 
Many governance programs were designed for reporting, analytics, and human users. AI adds new pressure. Ownership can blur, autonomous tools need carefully defined permissions, and compliance failures can spread faster. 
The right questions bring that risk into view. Start with ownership, quality, privacy, access, and the cloud controls that make each one enforceable. 
 

Building your enterprise data governance framework for AI 

An enterprise data governance framework depends on people, processes, and technology. The people layer determines whether the other two work. If accountability is unclear, data defects linger, access decisions stall, and AI teams build on assumptions. 
Define responsibilities in plain language and tie them to measurable results: 

• Data governance council sets standards, priorities, and enterprise policies. 

• Data owners are accountable for policy, risk, access rules, and quality targets within a data domain. 

• Data stewards maintain definitions, address defects, and coordinate fixes. 

• Data custodians apply technical controls and operate the supporting platforms. 

Owners carry the outcome and the risk. Stewards handle the work that supports that outcome. Keeping those roles distinct makes it easier to spot gaps, assign fixes, and measure progress. 
Executive sponsorship gives the program budget, authority, and a path through cross-functional gridlock. Whether governance is centralized, distributed, or hybrid matters less than documenting who decides, who acts, and who is accountable. 
Document the decision path as carefully as the roles. Teams should know where to raise a quality issue, how quickly an owner must respond, and when a problem needs executive review. A lightweight process that people use is more valuable than a detailed model that exists only on paper. Build the workflow into the systems where data teams already work. 
 

Key Governance Questions Every Business Must Answer 

With the roles defined, ask how the framework will work under real operating pressure. 

Who owns the data and the model?

Name the owner for every source feeding an AI system, including shared and third-party data. Define who approves its use, who accepts the risk, and who responds when the data or model fails. 

What quality is good enough?

Set thresholds for accuracy, completeness, timeliness, and allowed null rates before data enters an AI pipeline. Document those expectations between producers and consumers so teams can test them consistently. 

What privacy rules apply?

Define consent, data minimization, retention, and deletion requirements before deployment. Stanford reports that 80% to 90% of users opt out of app tracking when given a clear choice. Treat explicit permission as a trust standard, not only a compliance step. 

Who and what can access the data?

Cover employees, applications, service accounts, and autonomous agents. Specify approved tools, allowed data, authentication methods, review intervals, and automatic expiration for permissions. 
These questions need answers at the use-case level, not only in an enterprise policy. A forecasting model, customer-facing assistant, and autonomous finance agent carry different risk. For each one, record the purpose, approved data, decision boundaries, monitoring approach, and escalation owner. That record gives business and technical teams a shared basis for approval. 
 

Preparing your cloud infrastructure for AI governance 

Policy without supporting infrastructure is hard to enforce. Begin with automated discovery and classification across cloud, SaaS, on-premises, and hybrid environments. Identify sensitive data before an AI workload reaches it, then record ownership and handling rules in a shared catalog. 
Create separate management groups for internet-facing and internal AI workloads. Microsoft’s Azure guidance recommends this structure to establish clear governance boundaries. The separation limits exposure of internal data and makes access policies easier to apply. 

A useful catalog connects technical metadata with business context. For each data product, record schema, owner, sensitivity, approved uses, and lineage. Automation can reduce upkeep, but a named owner still needs to verify that the information is current. 
The catalog should also help teams answer a practical question: can this data support the intended AI use? Include quality status, refresh frequency, known limitations, and restrictions on secondary use. That context reduces duplicate investigation and helps reviewers distinguish a usable source from one that is merely available. 
Governance should follow data from ingestion through retirement. Define review points, transition criteria, retention periods, and revocation rules for both people and automated workloads. Permissions that no longer match a business need should expire rather than accumulate. 
Monitoring turns those controls into an operating practice. Track failed quality checks, unusual access, policy exceptions, model inputs, and changes to sensitive datasets. Assign thresholds that trigger review and keep evidence of the response. As new AI use cases move into production, revisit the controls instead of assuming the original approval still fits. 
 

Conclusion 

Good data governance is practical preparation for AI. Clear ownership, measurable quality standards, privacy rules, and enforceable cloud controls give teams a stronger base for reliable results. 
Start with accountability, then build controls that can scale with new data, users, and agents. Review them as business needs change. Governance works best as an operating discipline, not a cleanup project. 
A useful first step is to select one high-value AI use case and trace its data from source to output. Confirm ownership, test the quality rules, review permissions, and document the evidence. That focused exercise will expose gaps quickly and give the governance team a repeatable pattern for the next use case.
Learn more with Velosio at your side.

The post Enterprise Data Governance Questions That Prepare Business Cloud for AI appeared first on ERP Software Blog.

The post Microsoft Copilot ROI: 5 Financial Metrics Your Business Can Improve appeared first on ERP Software Blog.

Most business owners with a legacy ERP system know, in the back of their minds, that they’ll have to deal with it eventually. The problem is that ‘eventually’ has a specific date, and for a large portion of US SMBs, it’s closer than they realize.
This isn’t a vague warning about modernization. It’s a calendar problem with real consequences.
The Dynamics GP Timeline Is Confirmed and Non-Negotiable
If you’re running Microsoft Dynamics GP, one of the most widely deployed ERP systems in the US SMB market, here are the dates Microsoft has confirmed and will not change:

End-of-life dates for the most common legacy Microsoft ERP platforms and the SQL Server and Windows Server versions they run on. The window to plan a migration is now.
 

 
Every vulnerability discovered after April 2031 remains permanently open. There’s no patch coming. No exception. No extension.
Mid-market ERP migrations take 12 to 24 months from project initiation to go-live, and that’s for well-run projects. If you want vendor support during your migration and the ability to course-correct when challenges arise, the window to start planning is now, not 2029.
 
The Hidden Risk GP Customers Miss
Most Dynamics GP customers think they have until 2031. They don’t.
SQL Server 2016, the database version most commonly paired with GP, reached end of security support on July 14, 2026. That deadline is already behind you. Windows Server 2016, its usual companion, follows on January 12, 2027, now only months away. Microsoft sells paid Extended Security Updates for SQL Server 2016 through July 2029, but that is an expensive stopgap that buys time, not a fix.
That means organizations running the most common Dynamics GP configuration are already living through a compound stack expiration, even though the ERP application itself remains supported until 2031. As of mid-2026 the database layer has already lost security support and the operating system layer is next. You are running a supported ERP on top of an unsupported database and a soon-to-be-unsupported operating system, with no patches available at any layer below the application.

 
Dynamics NAV: Even Less Runway Than GP
If you are running Microsoft Dynamics NAV (formerly Navision), the timeline is tighter still. Unlike GP, NAV follows Microsoft’s Fixed Lifecycle Policy, and nearly every version has already reached the end of the road. NAV 2016 and earlier lost extended support as of April 2026. NAV 2017 loses it on January 11, 2027. NAV 2018, the final release before the product became Dynamics 365 Business Central, reaches end of support on January 11, 2028.
There is no 2029 or 2031 backstop for NAV the way there is for GP. Once your version’s date passes, Microsoft issues no further security patches, bug fixes, or compliance updates. And because NAV is typically deployed on the same SQL Server and Windows Server versions as GP, NAV customers face the identical compound-stack exposure: an unsupported application sitting on an unsupported database and operating system, with no vendor remediation available at any layer.
The Broader Picture: 7 of 11 Major SMB Platforms Are Already Expired
The matrix below illustrates how risk compounds across the full technology stack. When the ERP application layer, the Windows Server version it requires, and the SQL Server version it runs on are all assessed together, 7 of the 11 most widely deployed legacy SMB ERP platforms currently have a fully expired security stack.

 
What About Sage and QuickBooks?
Sage 100 and Sage 300 remain under active vendor support, but organizations running versions from 2020 and earlier have already lost support. Sage applies a rolling three-year support window. If you haven’t kept up, your environment may be in the same unpatched position as a formally end-of-life platform.
QuickBooks Enterprise was not built to be an ERP. If you’re running $20M or more in revenue through it, held together with spreadsheets, workarounds, and third-party add-ons, you’re operating a platform that doesn’t meet the security, audit trail, or access control standards that cyber insurance underwriters and larger business partners now expect. That gap is widening every year.
 
The Insurance Problem
21% of cyber insurance claims were denied or partially denied in 2025, up from 15% in 2023.
 
This is where the deadline risk becomes a business risk, not just an IT risk. The single most common reason for denial is failure to maintain the security controls the policyholder said they had, which accounts for roughly a third of denied claims, and more than 80% of denied claims involve organizations that lacked multi-factor authentication. Running unpatched legacy ERP without a documented remediation plan is exactly the kind of control failure that voids a claim at the worst possible moment.
For a business that can’t absorb a $3 million loss out of pocket, that’s not a technicality. It’s an existential exposure.
A Planned Migration Beats a Forced One Every Time
The deadlines on your ERP platform are not abstract risk factors. They are dates on a calendar. April 2031 for GP security patches. July 2026 for SQL Server 2016, already behind us. January 2027 for Windows Server 2016. Each one represents a point at which your exposure grows and your options narrow.
Starting the conversation now doesn’t commit you to anything. It gives you the one thing a hard deadline will eventually take away: the ability to choose your own timing.
 
START WITH ONE QUESTION
When does your current ERP, and the infrastructure it runs on, stop receiving security patches? We offer a no-obligation environment assessment to help you answer that honestly. No pitch. Just clarity. Get in touch:   info@customsystems.com
 

The post The Clock is Already Running on Your ERP appeared first on ERP Software Blog.

Do You Need Dynamics 365 Supply Chain Management?

What Business Central Does Natively vs. What You Have to Add

The tool you are shopping for may already be installed

What if the planning engine genuinely does well

Reordering policies: choose per item profile, not per company

• Fixed Reorder Qty: replenishes inventory using a specified reorder quantity when projected availability reaches the reorder point.
• Maximum Qty: Wworks toward a defined maximum inventory level when replenishment is triggered.
• Order and Lot-for-Lot: Groups net requirements within the planning horizon and can use a lot accumulation period to combine multiple needs into one supply order

The planning parameters associated with them determine how the system reacts to demand. They exist because inventory behaves differently. The point is not to pick the "best" policy. There isn't one.

Where native planning breaks down

What Dynamics 365 Supply Chain Management adds (in plain terms)

The ISV middle ground

Diagnostic: data problem or tooling problem

How a trusted partner can guide you

The post Demand Planning Without a Crystal Ball: Do You Need Dynamics 365 Supply Chain Management? appeared first on ERP Software Blog.

Every Agentic ERP proposal that reaches a boardroom arrives with a cost-savings number attached. Fewer manual hours, lower headcount pressure, a shorter close. Those numbers are easy to build and easy to approve — which is precisely the problem. They measure the smallest part of the return and quietly define success down to it. An organization that justifies an Agentic ERP investment on cost savings alone is measuring a strategic capability with an operational ruler, and will likely conclude, a year later, that the business case underdelivered.
The most valuable returns from agentic capabilities are the ones cost accounting was never designed to see: decisions made faster, errors that never reach the ledger, capacity returned to the people who do the highest-value work. At DAX Software Solutions, we help organizations modernize Microsoft Dynamics 365 environments and adopt Agentic AI with the governance and readiness to make it work. The first decision that shapes whether the investment pays off is how you choose to measure it.

Why Cost Savings Is the Wrong Yardstick

Cost savings is the wrong headline metric because it answers a question no one should be asking: whether the project is worth doing only if it makes current work cheaper.
That framing caps the ambition of the initiative before it starts. It steers scope toward the tasks that are easiest to automate rather than the decisions that are most expensive to get wrong, and it sets up a comparison the technology tends to lose — the payback of a faster close looks modest next to the cost of the platform, the integration work, and the change management around it. Teams then optimize for the metric they are measured on: a cost-anchored program automates the cheap, safe, high-volume tasks and leaves the slow, consequential decisions untouched. The organization ends up efficient at the margins and unchanged at the core.
Gartner’s outlook underscores the risk of a narrow business case: it predicts that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals. A meaningful share of that shortfall is not a technology failure. It is a measurement failure — organizations that defined return too narrowly, delivered exactly what they scoped, and still missed the outcomes that mattered.

What Are You Actually Measuring?

The return on an Agentic ERP investment is the value released when the organization moves faster and more reliably from signal to action — not the hours it removes from a timesheet.
That is a different measurement altogether. A faster reconciliation or a more current dashboard reduces the reporting delay, but the return lives in the second half of the cycle: the time and judgment spent interpreting data, routing it, resolving exceptions, and committing to a course of action. An enterprise can be highly efficient and still slow to act. Measuring return means measuring how much of that gap the investment closes — and what closing it is worth.

The Four Dimensions of Agentic ERP Return

A credible return model looks past cost to four outcomes, only one of which is a saving.

• Decision velocity — the elapsed time between a signal appearing and the organization acting on it. Agents that surface exceptions, prepare reconciliations, and route decisions compress this lag, and what is released is working capital, capacity, and opportunities that would otherwise expire.
• Decision quality and risk reduction — fewer errors reaching the ledger, fewer compliance gaps, fewer decisions made on stale data. This return is measured in losses that never happen.
• Capacity redeployment — skilled hours returned to finance, operations, and procurement teams are worth far more spent on analysis and exception handling than counted as a headcount reduction.
• Resilience — the ability to absorb volume, complexity, and volatility without adding proportional cost, which is what lets a business scale without its operating model breaking.

Cost savings still belongs in the model. It simply belongs as one line among four, not the headline.

Establish the Baseline Before You Automate

You cannot measure a return you never baselined. Before any agent is configured, capture how the current process actually performs: how long a decision takes from signal to action, how often it is reworked, how many exceptions accumulate, and where work stalls waiting on a person.
Most organizations discover their real constraint is not the cost of the work but the delay between knowing and acting. That baseline becomes the yardstick every later claim of return is measured against — and without it, “improvement” is an anecdote rather than a number.

Where the Return Actually Shows Up

Return is best measured where decisions stall today, and it tends to concentrate in a few operational cores.

• Finance operations: an anomaly in a reconciliation is flagged early rather than at close, shortening the cycle and freeing working capital instead of consuming days of review.
• Supply chain: a demand or supply signal is acted on within the operating window rather than the next planning cycle, protecting service levels and margin.
• Procurement: an exception on an invoice or contract term is routed and resolved instead of sitting idle because no one owns the next step.

This is the direction the broader Microsoft ecosystem is taking. Microsoft frames Dynamics 365 as moving from systems of record to systems of action, where AI agents and Copilot capabilities help surface exceptions and guide decisions in the flow of work — with capabilities such as the Account Reconciliation Agent (in preview) illustrating the pattern for the financial close. The measurable return is the decision that now happens in the window that mattered.

Governance and the Cost of Getting Return Wrong

A return model that ignores governance overstates the return. Speed without oversight simply lets an organization make poor decisions faster, and the cost of one uncontrolled decision can erase a year of efficiency gains.
The discipline is controlled autonomy: decisions that move quickly within clearly defined boundaries, with human judgment applied where consequence is high. This mirrors the NIST AI Risk Management Framework, which places a Govern function across the entire AI lifecycle and treats human oversight as a defining characteristic of trustworthy AI. Governance is not a deduction from return — it is what makes a fast decision one the organization can afford to make.

DAX Software Solutions: Your Partner in Agentic ERP Value

Cost savings is where a weak business case ends and a strong one begins. The return that justifies an Agentic ERP investment lives in faster decisions, fewer costly errors, redeployed capacity, and a business that scales without its operating model breaking — and that return has to be defined and measured deliberately, on connected systems, trusted data, and clear governance.
DAX Software Solutions helps organizations get there through:

• Agentic ERP strategy and advisory, identifying where decision latency and decision risk cost the most and framing the return accordingly.
• AI readiness assessment and a structured adoption framework — ERP stabilization, data governance, integration, then AI enablement — so projected return becomes realized return.
• Human-in-the-loop operating models that pair speed with the oversight executives and regulators expect.

If your Agentic ERP business case rests on cost savings alone, it is being measured by its least important outcome. Talk to DAX Software Solutions about building a return model — and a Dynamics 365 foundation — worthy of the decision.

The post Beyond Cost Savings: How to Measure the Return on an Agentic ERP Investment appeared first on ERP Software Blog.

Understanding AI, Security, and Adoption in Business Central
part of preparing for AI-powered ERP. Organizations also need to consider security, governance, adoption speed, and whether an AI initiative delivers the expected business value.
 
What Security Considerations Should You Review Before Using AI?
Governance may not generate the same excitement as an AI demonstration, but it deserves attention early.
As Copilot and agents become capable of summarizing information, retrieving records, and taking actions, organizations need a clear understanding of who can access what. Permissions that seemed acceptable during ordinary system use may deserve another review when technology makes information easier and faster to surface.
Business Central provides administrative controls for individual Copilot and agent capabilities, including user access controls and data governance settings. The adoption plan should incorporate those controls rather than review them after a problem occurs.
The broader Microsoft environment matters, too. If an organization expects Copilot to work with content from SharePoint, Teams, Outlook, or other Microsoft 365 sources, those systems’ permissions and information architecture also need attention.
Business Central permissions govern Business Central data, while the permissions in connected Microsoft 365 services govern access to their respective content.
The important point is that AI does not create disciplined access where disciplined access does not exist. Security should not be used as a reason to stop. Treat it as one of the foundations required to proceed responsibly.
How Much Does It Cost to Run AI Agents?
Readiness also includes understanding how usage will be billed.
Business Central agents use consumption-based billing through Copilot Credits. Microsoft’s documentation currently lists the Sales Order Agent, Payables Agent, Expense Agent, and certain agent design and coding scenarios. Credit consumption can vary by agent, the actions it performs, and how often it is used.
That does not make agents too expensive or too unpredictable to consider. It simply means you should evaluate their value intentionally.
If an agent reduces manual processing hours, shortens customer response times, improves accuracy, or lets a team absorb more transaction volume, the return may justify the consumption cost. But the calculation should begin with a real process rather than a general desire to “do something with AI.”
How often does the process occur? How much employee time does it require today? Where do errors or delays appear? What would improvement be worth? What usage cost would be introduced? These questions turn AI from a technical experiment into a business investment.
The answer will differ by organization. What matters is making the economics visible before an initial pilot becomes a company-wide deployment.
 
How Fast Should Your Business Adopt AI?
The pace of change is one of the hardest parts of this transition.
Features will improve. Pricing may evolve. New agents will appear. Some early limitations will be resolved, while new governance questions will likely emerge. Waiting for everything to become stable sounds prudent, but stability may always be one release away.
A more practical approach is to choose your velocity.
Decide how quickly the organization is prepared to move and in what direction. Begin with a manageable problem, establish a baseline, test the proposed solution, measure the outcome, and document what was learned.
If the results are meaningful, expand deliberately. If they are not, adjust or select a different use case.
A roadmap should give the organization direction without pretending that every future step is already known. It should be firm about business outcomes and governance principles but flexible about the tools used to achieve them.
The organizations that benefit most may not be the ones that activate every capability first. They may be the ones that build a repeatable discipline for evaluating opportunities, managing risks, measuring results, and adapting as the technology improves.
 
What Should You Do Before Adopting AI?
Once you acknowledge the initial frustration and skepticism, the next steps become fairly practical.
Begin by looking honestly at the current environment. Where are employees losing time? Which processes depend on repetitive data entry? Where are customers waiting for responses? Which decisions are delayed because information is difficult to assemble? Where do inconsistent procedures create risk?
The answers provide a better starting point than a list of AI features.
From there, select a small number of opportunities tied to clear business outcomes. A finance team might focus on reducing invoice-processing effort. Customer service might focus on responding to order inquiries faster. Leadership might focus on making operational information easier to understand.
Measure AI usefulness against the improvement the business wants to achieve, not the excitement of the demonstration. Then, prepare the supporting foundation. Document the process. Confirm ownership. Review data quality and security access. Define where human review remains necessary. Estimate the potential benefit and consumption cost. Establish a way to measure whether the pilot worked.
This approach does not eliminate trial and error. It makes trial and error productive.
What Does a Responsible AI Adoption Strategy Look Like?
The best AI strategy starts with the business and the people who make it work.
Copilot, agents, and AI-powered workflows are tools. Their value depends on objective clarity, process quality, data reliability, governance strength, and employees’ willingness to learn.
That is why preparedness should not be confused with hesitation. Preparing does not mean forming a committee that discusses AI for a year while competitors learn by doing. It means creating enough structure to begin responsibly, learn quickly, and adjust intelligently.
At OTT, we help organizations examine real business processes, identify practical opportunities for improvement, and determine where Business Central, Copilot, and AI-powered agents can deliver measurable value.
The objective is not to introduce AI simply because it is new. It is to help people work more efficiently, improve customer experiences, strengthen operations, and support growth.
You can choose your speed and direction. You can begin with one process or several. You can move cautiously and still make meaningful progress.
What is becoming increasingly difficult to defend is standing still.
Take a deep breath, organize the effort, and begin with a plan that can change as you learn. The destination may keep evolving, but the next responsible step should not remain a mystery.

The post What Should You Consider Before Adopting AI? appeared first on ERP Software Blog.

This October, join Admiral Consulting Group for three upcoming online sessions designed to help organizations modernize financial planning, reporting, and their Microsoft Dynamics environment. Whether you’re preparing to move beyond Dynamics GP, looking to connect financial planning with operational drivers, or want to stay current on the latest Business Central capabilities, these webinars offer practical insights you can put to work.

Dynamics GP to Business Central: Modernizing Finance and Planning for Manufacturers

Wednesday, October 7 | 10:00 AM EST|Online
Join Admiral Consulting Group and Vena for a 45-minute session focused on how manufacturers can maintain reporting continuity while connecting financial planning to key operational drivers—including demand, inventory, materials, COGS, CapEx, and labor.
We’ll cover planning considerations when moving from Dynamics GP to Business Central, driver-based planning, forecasting and scenario modeling, collaboration, and a curated Vena demo featuring real-world manufacturing scenarios.
Click here to save your spot!

Beyond Dynamics GP: Modern Financial Planning for Not-for-Profit & Higher Education

Wednesday, October 21 | 11:00 AM EST | Online
For not-for-profit and higher education organizations, modernizing financial planning is about more than technology—it’s about strengthening accountability and connecting financial decisions to mission-driven priorities.
Join Admiral Consulting Group and Vena for a 45-minute session exploring planning beyond Dynamics GP, including grants, funds, enrollment, revenue, leadership reporting, and collaboration. The session will also feature a live Vena demonstration of modern financial planning and scenario modeling.
Register here!

What’s New in Business Central: 2026 Releases & More

Wednesday, October 21 | 2:00 PM EST | Online
Business Central continues to evolve, with new AI, Copilot, automation, reporting, and productivity capabilities.
Join us for a look at what’s new in the 2026 releases and discover practical ways to take advantage of the latest features. We’ll highlight AI and Copilot enhancements, workflow and automation updates, reporting and analytics improvements, and productivity tips to help you get more from Business Central.
Mark your calendar and join us this October! Whether your organization is planning its next step beyond Dynamics GP or looking to maximize Business Central, these sessions are a great opportunity to learn what’s changing and what’s possible.
Click here to learn more.

Explore More Events & Register

Interested in joining us for an upcoming webinar or event? Visit our events page to view upcoming sessions, learn more, and register: [View Upcoming Events & Register]

The post Upcoming Events & Webinars: Modernizing Finance and Making the Most of Business Central appeared first on ERP Software Blog.

Chile has run mandatory electronic invoicing since 2014, longer than most of its neighbors. That maturity is an advantage, but it also means the SII's requirements have layered up over a decade — and companies rolling out Business Central Chile today inherit all of it at once.
Three acronyms carry most of the weight: DTE, CAF, and TED. Getting them straight is the fastest way to understand how the whole system fits together.

How Chile's DTE Model Works

Every invoice, credit note, debit note, or dispatch guide is issued as a Documento Tributario Electrónico (DTE) to the Servicio de Impuestos Internos (SII). Before issuing any DTE, a company requests a CAF (Código de Autorización de Folios) — a signed range of document numbers the SII authorizes in advance. Each DTE then carries a TED (Timbre Electrónico de Documento), a two-dimensional barcode generated from the document data and the CAF's private key, which lets anyone verify the document against the SII. Run out of folios, and invoicing stops cold until a new CAF is requested.

Resolution 154: New Rules for Dispatch Guides

Starting November 1, 2026, Resolution 154 requires more detailed transport data on invoices and dispatch guides tied to the movement of goods: carrier and vehicle identification, a classified transport type, and a dedicated Registro de Guías de Despacho. Companies moving physical inventory need to review this closely, since it touches sales, inventory, and shipping processes together, not just finance.

Where This Shows Up in Business Central Chile Projects

For implementation teams, a few things come up repeatedly:

• Requesting and monitoring CAF folio ranges before they run out
• Generating the TED correctly for every DTE type, not just invoices
• Certifying as an electronic issuer with the SII before go-live
• Capturing the new transport details Resolution 154 requires for dispatch guides
• Replacing the old physical Libros de Compras y Ventas with their electronic equivalents
• Submitting the monthly F29 declaration with figures that reconcile against the DTEs actually issued

Common Challenges in Chile Implementations

Most issues trace back to a few recurring gaps:

• Running out of CAF folios during a busy sales period, which halts invoicing outright
• Treating dispatch guides as an afterthought instead of part of the core sales-to-shipment flow
• Missing the eight-day window customers have to formally accept or dispute a DTE
• Falling behind on SII resolution updates that quietly change validation rules
• Storing the certificate and CAF private keys insecurely, which the SII treats as a compliance issue in its own right

None of these are unusual for a mature e-invoicing market — but Chile's penalties for non-compliance are unusually steep, up to 500% of the transaction value plus business closure for repeated failures.

Why a Dedicated Localization Matters for Business Central Chile

A proper Chile localization automates CAF folio management, generates the TED for every DTE type, and adapts to SII resolution changes like the new dispatch guide requirements. Built as an extension, it does this without altering Business Central's core — and it keeps folio monitoring running in the background, so nobody finds out about a shortage mid-sale.

How LLB Solutions Supports Business Central Chile

LLB Solutions' Chile Localization for Microsoft Dynamics 365 Business Central covers SII electronic invoicing, tax books, and fiscal reporting — including the transport data changes introduced by Resolution 154 — built as an AppSource-certified extension that tracks SII updates as they roll out.

Final Thoughts

Chile's e-invoicing framework is stable, but it keeps evolving — Resolution 154 is only the latest example. Companies that build folio management, TED generation, and dispatch guide compliance into their Business Central Chile environment from the start spend far less time reacting to SII updates after the fact.
For Microsoft partners, that also means checking existing Chile clients' readiness for Resolution 154 well before its November 2026 effective date, rather than waiting for a support ticket.
See how LLB Solutions' Chile Localization fits your Business Central project — Contact LLB Solutions

The post Business Central Chile: SII's DTE, CAF, and TED Explained appeared first on ERP Software Blog.

The Dynamics 365 Ecosystem for Equipment Rental: Connecting Operations, Fleet, and Finance

KEY ARTICLE TAKEAWAYS:

• Standard ERPs Need Industry Specialization: Conventional ERP platforms manage linear sales well, but heavy equipment rental requires circular asset lifecycle tracking, a gap directly bridged by Sycor.Rental inside Microsoft Dynamics 365.
• Unified Data Eliminates Operational Silos: By embedding Sycor.Rental within Dynamics 365 Finance and Supply Chain Management, fleet utilization, maintenance logs, and complex recurring billing flow into a single source of truth.
• Microsoft Ecosystem Amplifies Value: Connected tools like Power BI, Power Apps, and Azure IoT extend Sycor.Rental, enabling real-time telematics integration, mobile yard check-ins, and predictive fleet analytics.
• Scalability Without Customization Overhead: Leveraging an established ISV solution like Sycor.Rental allows growing rental providers to scale across locations without maintaining risky custom-built software.

Equipment rental businesses operate in an increasingly fast-paced environment. Managing high-value assets across fluctuating delivery timelines, complex maintenance schedules, and variable billing structures requires operational precision.
While core ERP systems manage finance and supply chains well, heavy equipment and tool rental operations require specific capabilities—such as asset tracking, complex rate structures, and field service synchronization—that go beyond standard functionality.
By leveraging the broader Microsoft Dynamics 365 ERP ecosystem, equipment rental companies can unify fleet operations, asset lifecycles, and financial workflows on a single cloud platform.

Key Features of Cloud ERP Systems:

Cloud ERP systems include many elements that help businesses optimize how they manage operations. Some of the essential features include:

• Real-time data access. Cloud ERP systems provide real-time access to data, allowing businesses to make informed decisions and respond quickly to changing market conditions.
• Integration capabilities. By connecting applications across the business, such as customer relationship management and human resources systems, cloud ERP solutions unify data to create a single, accurate view of the entire business.
• Mobile accessibility. Cloud ERP systems can be accessed from any device with an internet connection, which supports remote work and distributed team models.

The Rental Operations Challenge: Beyond Standard ERP

Standard ERP systems excel at linear inventory tracking—buying, storing, and selling stock. However, equipment rental operates on a circular model where assets continuously leave, return, undergo inspection, require maintenance, and get re-rented over years.
Equipment rental companies often struggle with:

• Fragmented Systems: Relying on separate applications for rental quoting, fleet tracking, maintenance scheduling, and core accounting.
• Complex Billing Requirements: Handling flexible rates (daily, weekly, monthly, meter-based), stand-by rates, transport fees, and sub-rentals manually.
• Limited Fleet Visibility: Inability to accurately forecast equipment availability across locations in real time.
• Disconnected Field Operations: Disconnects between workshop technicians, field mechanics, and central dispatchers.

Unifying Rental Management within Microsoft Dynamics 365

Rather than introducing custom standalone software that creates data silos, modern rental organizations leverage Microsoft Dynamics 365 Finance and Supply Chain Management extended with industry-specific solutions like Sycor.Rental.

Expanding the Capabilities with Microsoft Power Platform and Azure

The true strength of built-for-Dynamics rental solutions lies in their seamless connectivity to the broader Microsoft ecosystem:

1. Power BI for Fleet Analytics: Real-time dashboards track key metrics like Total Cost of Ownership (TCO), fleet utilization rates, ROI per asset class, and maintenance downtime.
2. Power Apps for Mobile Inspections: Yard staff and field mechanics can perform digital check-ins, check-outs, damage reporting, and photo capture directly from mobile devices.
3. Azure IoT & Telematics: Direct integration with telematics devices streams equipment engine hours, GPS location, and fault codes into Dynamics 365 to trigger automatic maintenance work orders.
4. Dynamics 365 Field Service: Connect central dispatching with field service engineers to manage emergency repairs, scheduled servicing, and part replacements on customer job sites.

Why Ecosystem-Based Rental ERP Matters

Building your equipment rental management strategy around an integrated Microsoft ecosystem provides distinct advantages over proprietary niche systems:

• Single Source of Truth: Operational fleet data instantly flows into general ledgers, fixed assets, and revenue recognition modules.
• Scalability: Easily scale operations across multiple yards, regional depots, or international markets on Microsoft's secure cloud infrastructure.
• Familiar User Experience: Embedded natively inside Microsoft Dynamics 365, reducing user learning curves and accelerating adoption.

By transforming how fleet, field service, and finance connect, rental providers can maximize asset utilization, protect capital investments, and deliver better service to their customers.

Frequently Asked Questions (FAQs)

1. What is Sycor.Rental, and how does it integrate with Microsoft Dynamics 365?

Sycor.Rental is an enterprise-grade equipment rental solution built natively on Microsoft Dynamics 365 Finance and Supply Chain Management. Rather than connecting via external APIs, it operates directly within the Dynamics 365 environment, providing dedicated rental logic, dispatch boards, and asset lifecycle tools alongside standard finance and operations workflows.

2. Can Sycor.Rental handle complex rental rate structures and billing cycles?

Yes. Sycor.Rental automates complex rental pricing models, including flexible calendar or working-day rates, tiered pricing based on duration, stand-by rates, meter/usage-based charges, and recurring billing cycles across long-term and short-term rentals.

3. How does Sycor.Rental improve equipment maintenance and fleet availability tracking?

By capturing real-time asset data, Sycor.Rental links scheduled preventative maintenance, unscheduled workshop repairs, and field service work orders directly to each serialized asset. Dispatchers gain immediate visibility into equipment status across all yards—distinguishing between assets that are available, reserved, in transit, or under repair.

4. Does Sycor.Rental support field operations and telematics integrations?

Yes. Through integration with the broader Microsoft ecosystem - including Dynamics 365 Field Service, Power Apps, and Azure IoT - Sycor.Rental allows field technicians to complete inspections on mobile devices while processing telematics streams (such as engine hours and fault codes) to trigger automatic service alerts.

5. Why choose a specialized solution like Sycor.Rental over custom ERP modifications?

Custom modifications to a standard ERP can be costly to maintain and often break during regular platform updates. Sycor.Rental delivers pre-built, proven rental functionality that automatically updates alongside Microsoft Dynamics 365 releases, lowering total cost of ownership and reducing implementation risks for equipment rental companies.

The post The Dynamics 365 Ecosystem for Equipment Rental: Connecting Operations, Fleet, and Finance appeared first on ERP Software Blog.

Business Central buyers are familiar with generic demonstrations. They see a standard process, explain where their business differs and are told that the gap can be customized during implementation.
For a buyer, that creates a familiar leap of faith. The standard product may look good, but the decision often depends on a handful of business-specific processes that are not visible in the demonstration. Those are precisely the areas where misunderstandings can become expensive later.
If a partner can explore one of those gaps earlier, the buyer gets something more useful than a polished generic demo. They get evidence that the partner has understood the problem. Just as importantly, both sides get an opportunity to discover where the requirement is still vague before it becomes a committed piece of project scope.
The caution is that an early example is still an early example. It should not be mistaken for a production change simply because it appeared quickly. The business still needs the same confidence around testing, user permissions and approval before anything becomes part of the live system.
Handled well, that distinction can improve the buying experience. The customer sees more relevance earlier without being asked to lower the standard for what eventually goes live. Faster development then supports a better conversation rather than simply a faster demonstration.
AI-assisted development raises a different possibility. If a partner can respond to a real business requirement earlier, the customer can have a more concrete conversation about the outcome before committing to the full project.
That does not mean treating a quick prototype as production-ready. The same controls still matter. The requirement needs to remain clear, the finished change needs to be tested for the people who will use it, and someone needs to approve what eventually goes live.
Used well, faster development could therefore improve both sides of the relationship. Customers get a clearer view of whether the partner understands the problem. Partners get a stronger basis for the project and may be able to serve more demand without relying only on additional development capacity.
The commercial opportunity is attractive, but trust is what makes it usable. A faster route from idea to demonstration only matters if there is an equally credible route from demonstration to a controlled production change.
That can make procurement conversations more useful too. Instead of comparing partners mainly on presentation quality and broad assurances that customization is possible, buyers can learn more about how each partner understands a concrete requirement and how they think about the path from idea to dependable delivery.
It can also reduce one of the common sources of project friction: the sentence 'that is not what we meant'. The earlier a business-specific assumption becomes visible, the earlier it can be challenged. A prototype or worked example is valuable when it prompts a better conversation, not merely when it looks impressive on screen.
Buyers should still be wary of speed being used as a substitute for assurance. A rapid demonstration can create a strong impression of completeness. The responsible partner will be equally clear about what has and has not yet been proven, and what still needs to happen before the idea belongs in a live finance environment.
That combination of relevance and restraint is likely to become an important part of the buying experience. Customers can expect partners to understand their needs sooner without accepting that sooner means ready.

The post Could Faster Business Central Development Improve the Buying Experience Too appeared first on ERP Software Blog.

Quick Answer (TL;DR)

Etsy does not connect natively to Business Central, so a Dynamics 365 integration requires a connector app or custom API build. The key is mapping each Etsy variation (like size or color) to a Business Central item variant with its own SKU, while routing personalization text to sales order lines. This keeps inventory, costs, and fulfillment accurate for handmade products.

Key Takeaways

• Business Central includes a built-in Shopify connector but no native Etsy connector. You will need an AppSource app, middleware, or a custom integration built on the Etsy Open API v3.
• SKUs are the backbone of the integration. Every sellable Etsy variation combination needs a unique SKU that matches a Business Central item and variant code.
• Item variants work best for stocked combinations like size and color. One-of-a-kind pieces usually work better as separate items or with serial number tracking.
• Personalization, such as engraved names or custom text, should flow to sales order lines as text or custom fields. It should not become new variants.
• Made-to-order products need a different sync logic than ready-to-ship stock. The logic should be based on component availability or production capacity rather than finished goods on hand.
• Etsy collects and remits US sales tax as a marketplace facilitator. Your integration must avoid posting that tax a second time in Business Central.

Why Handmade Sellers Outgrow Manual Etsy Management

Most Etsy shops start with spreadsheets and the Etsy dashboard. That works until you are selling the same necklace in four metals and three chain lengths, taking custom engraving requests, and listing the same products on your own website. At that point, stock counts drift, costs get guessed, and a sold-out variation stays live long enough to create an order you cannot fulfill.
Connecting Etsy to Microsoft Dynamics 365 Business Central solves this by giving you one system of record for inventory, costing, and accounting. The hard part is not moving orders from one system to another. The hard part is translating Etsy's flexible, buyer-friendly variation model into Business Central's structured item data. That translation is where a well-planned Business Central integration makes or breaks the project.
This guide explains how the two data models differ, how to map variations correctly, and how to handle the edge cases that are unique to handmade products.

How Etsy and Business Central Think About Products Differently

Etsy is built around the listing. A single listing can carry variations on up to two properties, such as Color and Size. Within the listing editor, you choose whether price, quantity, and SKU vary by those properties. Etsy also offers a separate personalization field, where buyers type free text like a name or date.
Business Central is built around the item. An item has one item number, a base unit of measure, costing information, and posting groups. Variations of that item are stored as item variants, each with its own variant code. Stock can then be tracked per variant and per location through stockkeeping units.
The table below shows how the core concepts line up.

If you sell across several channels, this same mapping discipline carries over to your wider ERP for ecommerce setup. It keeps Etsy, your website, and wholesale orders drawing from the same stock pool.

Your Integration Options

Option 1: A Third-Party Connector App

Several AppSource and middleware vendors offer Etsy connectors for Business Central. These are the fastest route for straightforward catalogs. Before you buy, check three things: whether the app supports two-property variations, whether it can map personalization to order lines, and whether it syncs inventory at the variant level rather than only at the item level.

Option 2: Middleware or iPaaS

Integration platforms sit between Etsy and Business Central and let you build mapping rules visually. They suit businesses that already use middleware for other channels. They also make sense if you are connecting Etsy alongside marketplaces through an existing Amazon integration with Dynamics 365.

Option 3: Custom Integration

A custom integration uses the Etsy Open API v3 (with OAuth 2.0 authentication) on one side and Business Central's standard APIs or custom AL extensions on the other. This option gives you full control over variation logic, made-to-order rules, and fee posting. It is usually the right choice when your catalog has unusual structures that off-the-shelf apps cannot model. Etsy reviews apps that request API access, so build that approval time into your plan. A partner experienced in Business Central development can scope this accurately.
A useful point of comparison: Business Central's native Shopify connector already handles product variants and order import out of the box. If you also sell on Shopify, a dedicated Shopify integration with Dynamics 365 can be set up alongside your Etsy connection, and both should share the same SKU conventions.

Mapping Etsy Variations to Business Central Item Variants

Step 1: Build a SKU Convention Before You Sync Anything

Every integration issue we see with handmade catalogs traces back to inconsistent SKUs. A simple, readable pattern works best:
[Product Code]-[Property 1]-[Property 2]
For example, NCK-LEAF-SLV-18 for a silver leaf necklace on an 18 inch chain. Apply this pattern to every Etsy variation combination and every Business Central variant. The integration can then match records on SKU without any guesswork.
If your existing SKUs are a mix of old listing codes, blanks, and duplicates, clean them before go-live. The approach is the same one we describe in our guide to migrating messy legacy data into Business Central: audit, standardize, deduplicate, then load.

Step 2: Decide What Becomes a Variant and What Does Not

Not every Etsy option should become a Business Central variant. Use this rule of thumb:

• Make it a variant when the option changes what physically sits on the shelf, such as color, size, or material.
• Keep it as an order detail when the option only changes how you finish the item after the sale, such as engraving text, a monogram, or a gift note.
• Make it a separate item when the piece is truly one of a kind, such as a single hand-thrown vase or a vintage find. Alternatively, keep one item and use serial numbers so each unique piece is tracked individually.

This distinction prevents variant explosion. If every personalized name created a new variant, your item list would grow endlessly and your stock data would become meaningless.

Step 3: Use Item References for Channel-Specific Codes

Business Central's Item Reference feature lets you link an external code to a specific item and variant. If your Etsy SKUs cannot be changed to match your internal numbering (for example, because long-running listings would lose history), store the Etsy SKU as an item reference. The integration then resolves each Etsy order line to the correct item and variant automatically.

Step 4: Map Variation Pricing Carefully

Etsy lets price vary by variation. In Business Central, you can reflect this with sales prices defined per variant, often in a price list dedicated to the Etsy channel. Decide which system owns the price. In most setups, Business Central is the master for price and quantity, while Etsy is the master for orders.

Handling Personalization and Custom Orders

Personalization is where handmade businesses differ most from standard retail. A buyer who orders a "Custom Name Bracelet" might select Gold and Medium as variations, then type "Amara, 2019" in the personalization box.
The integration should:

1. Resolve Gold and Medium to the correct item variant, so inventory and cost are correct.
2. Write the personalization text to the sales order line, either in an extended description or in a dedicated custom field.
3. Carry that text through to pick lists, production or assembly documents, and packing slips, so the maker sees it without opening Etsy.

Standard Business Central does not have a dedicated personalization field on sales lines. A small Business Central customization that adds one, and prints it on warehouse documents, is often the highest-value change in the whole project.
For fully custom commissions that Etsy sellers handle through custom listings, create a generic "Custom Order" item or a nonstock item in Business Central. Capture the specifics on the order line. That way, you record revenue and costs correctly without cluttering your item catalog with pieces you will never sell again.

Syncing Inventory for Ready-to-Ship vs Made-to-Order Products

Ready-to-Ship Stock

For finished goods, the logic is simple: Business Central calculates available quantity per variant (on hand minus reserved and open orders) and pushes it to the matching Etsy variation. Consider holding back a small buffer on fast sellers, so a sale on another channel does not oversell Etsy between sync runs.

Made-to-Order Products

Many handmade items are not sitting in stock at all. They are made after the order arrives. Pushing a quantity of zero would hide them, and pushing a high fixed number risks promising more than you can make.
Two approaches work well:

• Component-based availability. Set up the product as an assemble-to-order item with an assembly BOM (for example, a pendant, a chain, and a clasp). The integration calculates how many finished pieces the available components can produce and publishes that number to Etsy. Businesses with multi-step making processes can extend this with production BOMs, the same foundation used in Dynamics 365 ERP for manufacturing.
• Capacity-based availability. Publish a set weekly capacity per product, reduced as orders come in. This suits makers whose limiting factor is time rather than materials.

Also align your Etsy processing times with realistic production lead times. Your integration can keep listings accurate, but it cannot fix a promise the workshop cannot keep.

Tracking Materials With Batch Differences

Handmade materials vary between batches. Hand-dyed yarn, glazes, and leather hides are common examples. Business Central's lot tracking lets you record which batch went into which order. This helps when a customer wants a matching second item or when a batch has a quality issue. If you ship from more than one location or use a third-party fulfillment partner, review how WMS integration with ERP affects lot and variant visibility.

Order, Fee, and Tax Handling

Order Import

Etsy orders (called receipts in the API) should become Business Central sales orders on a regular schedule. Map the buyer to either an individual customer record or a single "Etsy Customer" account, with shipping address details stored on the order. Most small handmade businesses prefer the single-customer approach, since it keeps the customer list clean.

Marketplace Tax

In the US, Etsy collects and remits sales tax as a marketplace facilitator. If your integration imports the tax amount onto the sales order and then posts it to your tax liability account, you will overstate what you owe. Configure the Etsy channel so marketplace-collected tax is recorded for reference but not posted as your liability. Confirm the setup with your accountant, since rules differ outside the US.

Fees and Payouts

Etsy deducts transaction fees, payment processing fees, listing fees, and advertising costs before paying you. Post these as expense entries and reconcile each payout against your bank statement. Posting one summarized journal per payout, rather than one per order, keeps your general ledger readable.

Common Mistakes to Avoid

• Syncing before SKUs are clean. Mismatched SKUs cause failed order imports and orphaned stock.
• Turning personalization into variants. This bloats your item list and breaks inventory reports.
• Letting both systems edit quantities. Choose one master for stock, or you will chase conflicting numbers.
• Relying purely on default setup. Handmade workflows rarely fit a standard configuration, which is a pattern we cover in why out-of-the-box Business Central fails.
• Skipping testing with real variation data. Test with your most complex listings, not your simplest ones.

Practical Go-Live Checklist

1. Audit every Etsy listing and export its variations and SKUs.
2. Standardize SKUs and create matching items, variants, and item references in Business Central.
3. Define ownership rules: BC owns price and quantity, Etsy owns orders.
4. Set up personalization handling on sales lines and warehouse documents.
5. Configure made-to-order logic (assembly BOMs or capacity rules).
6. Configure marketplace tax, fee posting, and payout reconciliation.
7. Run a parallel test period with a small set of listings.
8. Roll out to the full catalog and monitor sync error logs daily for the first few weeks.

For a broader view of what to verify before switching on, our ERP go-live checklist covers data, users, and cutover planning in more detail.

Getting More Value After the Integration

Once Etsy data flows cleanly into Business Central, you can see real margins by variation. That often reveals that your best-selling color is not your most profitable one. Connecting Business Central to Power BI services turns that data into dashboards for sell-through by variation, material usage, and channel profitability.
Business Central's Copilot features can also help with catalog work. For example, it can draft marketing text for new items, which you can then refine for your Etsy listings. We explain what these features really do in practice in what Copilot actually does in Business Central.

What Does It Cost?

Costs depend on your integration route. A connector app has a subscription fee and modest setup time. A custom integration costs more upfront but fits unusual catalogs exactly. Licensing, data cleanup, and customization all add to the total. Our breakdown of Business Central cost walks through each component so you can budget realistically. Growing makers can also explore our ERP for small business options.

Frequently Asked Questions

Does Business Central have a native Etsy connector?

No. Business Central includes a built-in Shopify connector, but Etsy requires a third-party app, middleware, or a custom integration built on the Etsy Open API v3.

How do Etsy variations map to Business Central?

Each Etsy variation combination maps to a Business Central item variant under a parent item. A unique, matching SKU or item reference links the two, so orders and inventory updates reach the correct variant.

Should personalized products be set up as variants?

No. Personalization text such as names or dates should be stored on the sales order line. Only options that change the physical stock item, like color or size, should be variants.

How do I sync inventory for made-to-order items?

Calculate availability from component stock using assembly BOMs, or publish a fixed production capacity that decreases with each order. Both methods prevent overselling without hiding listings.

Will Etsy sales tax be recorded twice?

It can be if the integration is not configured correctly. Because Etsy collects US sales tax as a marketplace facilitator, set up the Etsy channel so that tax is recorded for reference only and not posted as your liability.

Ready to Connect Etsy to Business Central?

If your handmade business is juggling variations, personalization, and multiple sales channels, a structured integration will save hours every week and protect your margins. Not sure whether your data and processes are ready? Start with an ERP readiness assessment, or talk to our Business Central team about your catalog.

The post Etsy Integration with Business Central: Managing Handmade Product Variations appeared first on ERP Software Blog.

The “one size fits all” approach hardly works for project management tools. What was once sufficient for project-based teams to coordinate their work might now become an obstacle for growing teams. Most of the time this is not a matter of bad project management solutions but rather process misalignment.  
If you're questioning whether your current project management solution still meets your needs and are curious about possible next steps, this article offers practical guidance to help you move forward. 

What are the early warning signs of project misalignment? 

Reporting requires manual labor 

When your team spends too much time manually switching between tools to create reports and forecasts, it is a sign of structural misalignment. This constant need for manual clarification on project status signals that your current tool lacks project visibility and automated updates.  

Missed deadlines 

Teams start doubting the efficiency of their project management tools when their project deadlines get missed regularly and become a structural issue. This can happen when changes in scope and available resources aren't reflected quickly and automatically — often due to too much time spent manually updating the system. 

Teams work with multiple tools for the same project 

Outdated project tools push teams such as finance to work on budgeting and revenue tracking with spreadsheets or other tools that fulfill their operational needs, while the project teams work on one system. Having financial operations being updated on other systems may lead to time loss, budget overruns, and outdated actuals that need to be manually added to the ERP system. 
In an ideal situation, your ERP solution should be able to unify all areas of a project in one place: financials, resource management, task tracking, communication, risk management, and documentation, providing a comprehensive platform for end-to-end project oversight. 

Scaling is limited and increases complexity 

When processes are disconnected and happen across multiple tools, scaling becomes particularly challenging: As a project grows, so does the manual coordination, reworks, and miscommunication. This results in operational inefficiency and a lack of visibility over the latest data status. If you want your business to grow, you should consider looking for a solution that grows with you instead of slowing you down. 

Too many meetings and conversations about project status 

Finally, teams that spend more time discussing project status instead of actually working on them might consider rethinking their current tools. To truly scale, project management solutions must centralize communication and offer transparent progress tracking, allowing teams to collaborate efficiently without unnecessary interruptions or duplicated efforts.  

What scalable project operations solutions offer: D365 Project Operations 

When your project management tool has reached its maximum capabilities, it's time to look for a solution that grows with your business. Looking for the right one might take you on a long journey of going from one comparison page to another but in this section, we will present you some key features you should look out for and why Dynamics 365 Project Operations could be an option for your business. 
One of the key features your future project management tool should have is global visibility into your project's data so your team can make faster, fact-based decision-making at every level. Having a tool that presents the same up-to-date information across different areas such as finance and delivery can save you time and scale much easier.  
Since this aspect of visibility is quite important, we should mention that one should value the tool's ability to predict risks, addressing issues before they escalate. Nowadays AI features are evolving at a record pace making forecasting easier than ever and allowing businesses to be more proactive. 
Third, consider solutions that allow for personalization. Every business is unique and although some competitors might have chosen a tool that makes sense for them, it doesn't mean that it would fit your exact business needs. Rather, choose a platform that really adapts to your changing goals easily. 
Lastly, make sure your project management platform complies with current data protection standards, so your most sensitive project and financial data is safe.  
If you're already familiar with Microsoft's ecosystem and considering a solution that can cover the features mentioned above, you might consider the end-to-end platform Dynamics 365 Project Operations. This solution covers sales, project management, and finance in one system, allowing you to have full visibility into your financial data, resources, and other project data. The solution can be easily customized to your own business needs, and there are three deployment models to choose from, each with their own benefits. 
As your organization grows, so does the complexity of your resource management. D365 Project Operations can help with resource allocation and optimization, making sure you always assign the right people to the right projects at the right time. 
Thanks to its AI-powered tools such as Copilot, users can also accelerate their processes and be more proactive by preventing risks. Built on Microsoft’s secure cloud platform, D365 Project Operations also offers role-based access and governance capabilities that help businesses protect sensitive project and financial data and meet their compliance requirements.  
Curious about all you can achieve with D365 Project Operations? 
Check out our success stories! 

Conclusion & next steps 

By this point, you may have realized that your current project management tool no longer supports the way you need to work as your projects scale. By choosing the right project management solution that grows with your business, you are taking the first step towards a new era of business growth.  
Contact us and discover what D365 Project Operations can do for your business! 
 
 
 

The post From project tracking to project operations: Main signs your project management tool stopped scaling appeared first on ERP Software Blog.

Copilot in ERP for Industrial Distributors: Where AI Pays Off, and Where It Doesn't Yet

It is 7:40 on a Monday. A maintenance planner at a food plant emails 23 part numbers. Nine use the manufacturer's code, six use a competitor's, two are superseded, and one bearing only appears on a spreadsheet your longest-serving rep keeps on his desktop. The quote is due by noon.
Every industrial distributor knows this email. The real question is not whether AI can "transform" it. The question is narrower: which parts of that work can Copilot take over inside the ERP today, and what has to be true in your data before it can?
This article answers that. We will cover the specific Copilot and agent capabilities Microsoft now ships in Business Central and Dynamics 365 Supply Chain Management, map them to the workflows that eat time in MRO, PVF, fastener, bearing and power transmission distribution, and flag the preconditions that decide whether you see a return.

The Short Answer for Industrial Distributors

Copilot delivers the most value today in three places:

1. Inbound customer requests. Turning emailed RFQs and orders into quotes and sales orders.
2. Supplier follow-up. Reading vendor confirmations and change notices against open purchase orders.
3. Order entry assistance. Suggesting sales lines based on history and item data.

It delivers much less where your item master is inconsistent, where cross-references and supersessions live in a salesperson's head, or where branch stock is reconciled in spreadsheets. AI reads your ERP data. It does not fix it.
That distinction matters, because adoption is running ahead of results across supply chain functions. Gartner's survey of 265 supply chain organisations found that 72% are deploying generative AI, yet most report middling productivity and ROI results. A separate Gartner study found just 23% of supply chain leaders have a formal AI strategy in place. The gap between those two numbers is where most distributors lose money on AI.

Where Industrial Distribution Time Actually Goes

Before choosing any AI feature, look at where your inside sales and purchasing teams spend their hours. In the industrial distributors we work with, the pattern is consistent.
Inside sales spends a large share of the day on inbound email. A maintenance planner sends a list of part numbers, some in your numbering, some in the manufacturer's, some in a competitor's. Someone has to match each line to a stocked SKU, check availability across branches, find a substitute for anything superseded, price it against the customer's contract, and send a quote. Most of that is lookup work, not selling.
Purchasing chases vendors. Confirmations arrive by email with revised ship dates, partial quantities, or price changes. Each one needs matching to an open PO, a decision on whether to accept, and an update to promise dates on the customer orders that depend on it.
Branch and warehouse teams juggle transfers, special-order (non-stock) items, drop-ships and counter sales. Visibility across locations is often the weakest link.
These are the workflows to target first. They are high-volume, rules-based, and already recorded in the ERP.

What Copilot Does in Business Central for SMB Distributors

For small and mid-sized industrial distributors, Dynamics 365 Business Central is usually the right platform. Three Microsoft-documented capabilities stand out.
Sales Order Agent. Microsoft's Sales Order Agent monitors a mailbox, identifies customer requests, finds the customer record, checks item availability, and drafts a sales quote with a PDF reply. If details are missing, it asks the customer follow-up questions by email. When the customer confirms, it converts the quote to a sales order for your team to approve. For a distributor handling hundreds of emailed RFQs a week, this targets the exact lookup work described above.
Sales line suggestions. Copilot can propose sales lines based on past orders and item data. That helps with repeat MRO consumables, where the same customer reorders similar baskets.
Governance controls. Administrators switch each Copilot and agent capability on or off individually, so you can pilot one workflow without exposing the rest of the business.
The honest caveat: the Sales Order Agent matches against items that exist and are described consistently in Business Central. If your item cards lack manufacturer part numbers, or you keep cross-references outside the system, the agent will stall on exactly the lines that cost your team the most time. Fix the item master first.
Our UK team has written a practical breakdown of the top Copilot features in Business Central if you want a wider feature view.

What Copilot Does in Dynamics 365 Supply Chain Management for Larger Distributors

Multi-branch, multi-entity industrial distributors with high PO volumes typically outgrow Business Central and move to Dynamics 365 Supply Chain Management (part of Finance & Operations). Here the most useful AI capability for distribution is on the procurement side.
Supplier communications with the Procurement Agent. Microsoft documents a supplier communications capability that lets Copilot read vendor emails, decide whether each is a confirmation or a change request, and link it to the right purchase order. It detects changes to quantity, unit of measure, price, confirmation, delivery date and cancellation.
Confirmed purchase orders with changes. A dedicated workspace summarises changes to already-confirmed POs in plain language and drafts vendor replies. Buyers see which downstream sales orders a slipped delivery date affects, rather than discovering it when a customer calls. 

The Preconditions That Decide Your Return

We see AI projects in distribution succeed or stall based on four factors. None of them is the AI itself.
1. Item master quality. Manufacturer part numbers, customer part numbers, cross-references and supersession chains need to live in the ERP. This is the single biggest predictor of whether quote automation works.
2. Pricing structure. Contract pricing, cost-plus matrices and vendor rebate agreements need to be modelled in the system, not calculated on the side. Copilot can only quote what the ERP can price.
3. One inventory truth. Branch stock, in-transit transfers and consignment locations must reconcile in real time. An agent that promises stock from a branch with phantom inventory creates a worse customer experience than a slow human.
4. A named owner and a baseline. Measure quote turnaround, PO exception handling time and order-entry errors before you switch anything on. Without a baseline, you cannot tell whether the tool is helping. This is the discipline Gartner's 23% figure points to.

A Practical Rollout Sequence

Here is the order we typically recommend for industrial distributors. Treat timelines as planning estimates to validate against your own scope and data readiness.

• Weeks 1 to 4: Data readiness. Audit item cards, cross-references and pricing. Clean the top 20% of SKUs that drive most order lines.
• Weeks 4 to 8: Single-workflow pilot. Switch on one capability (usually the Sales Order Agent or supplier communications) for one branch or one customer segment. Keep a human approving every output.
• Weeks 8 to 12: Measure and decide. Compare against your baseline. Expand only what moved the numbers.
• Beyond 12 weeks: Extend. Add further agents, connect CRM data through Dynamics 365 Sales, and review licensing as usage grows.

Keep human approval in place until error rates are proven low. In distribution, one wrong part shipped to a plant maintenance team can cost more than a month of saved admin time.

Frequently Asked Questions

Is Copilot included in Dynamics 365 Business Central? Microsoft includes a range of Copilot capabilities in Business Central, and administrators enable them feature by feature. Agent capabilities such as the Sales Order Agent may carry separate consumption-based costs. Check current Microsoft licensing terms for your region before budgeting, as these change regularly.
Can Copilot handle manufacturer and competitor part number cross-references? Only if those cross-references are stored in the ERP. Copilot and agents work from your item data. If cross-references sit in spreadsheets or a salesperson's memory, load them into Business Central item references or the equivalent in Supply Chain Management first.
Should an industrial distributor choose Business Central or Dynamics 365 Supply Chain Management for AI? Choose based on operational complexity, not AI features. Business Central suits single-entity or smaller multi-branch distributors. Supply Chain Management suits multi-entity groups with high PO volumes, advanced warehousing and complex procurement. Both receive Copilot investment from Microsoft.
How long does it take to see results from AI in distribution ERP? With clean item and pricing data, a single-workflow pilot can typically produce measurable data within one quarter. Without that groundwork, expect the data clean-up to take longer than the AI configuration. Validate any timeline against your own baseline.

Talk to a Consultant Who Knows Distribution

If you are weighing Copilot for quoting, purchasing or branch operations, start with a data-readiness review, not a licence purchase. Our consultants will look at your item master, pricing and inventory setup and tell you plainly which AI workflows are ready now and which need groundwork first.
Book a consultation with Dynamics Square
You can also explore how we support distributors on our Microsoft Dynamics 365 for Distribution page.

The post Copilot in ERP for Industrial Distributors: A Guide appeared first on ERP Software Blog.

Fabric modernization stalls when the first project is not analytics, but rewriting production-tested SSIS packages. Many Dynamics GP, NAV, SL, AX, and SQL-backed ERP environments already have years of extraction, lookup, validation, and error-routing logic in SSIS. Rebuilding that logic before data reaches OneLake adds cost before value.
A rewrite discards work that already sits on stable ground. COZYROC has built SSIS tooling for 20 years, the SSIS+ suite spans 200+ components, and an Ultimate subscription costs $1,199 per year with 2 license keys. Set that against the contractor hours needed to rebuild tested package logic as notebooks, and the comparison is not close.

The Rewrite Problem

Fabric is often chosen as the analytics destination: OneLake, Lakehouse storage, SQL endpoints, Power BI, and AI-ready data products. The hard part is getting controlled ERP data into that destination without discarding the integration work the company already paid for.
For teams with existing SSIS assets, the architecture decision usually looks like this:

1. Rewrite package logic as Fabric Dataflows.
2. Rewrite orchestration and transformation logic as notebooks.
3. Provision another SSIS execution path.
4. Use a managed package runtime that can run existing SSIS workloads.

Option four is where COZYROC Cloud Flex fits. Flex is the COZYROC Cloud mode for custom-built SSIS packages. Existing packages are developed and tested in Visual Studio, uploaded to COZYROC Cloud, parameterized, scheduled, and monitored.

COZYROC Components For Fabric Lift-And-Shift

Where “Zero Code Rewrites” Is Accurate

“Zero code rewrites” is accurate only for an existing SSIS package that can be uploaded and executed through COZYROC Cloud Flex after normal compatibility, parameter, connection, and runtime checks. It is not a promise that every integration problem disappears.
Use this phrase only in this narrow scenario:
Existing SSIS package + compatible runtime target + COZYROC Cloud Flex upload = no manual conversion into Dataflows or notebooks.
For new Fabric integrations, the better claim is reduced custom development through SSIS package design, reusable components, REST configuration, scheduling, and webhook orchestration.

Fabric Landing Pattern

A practical pattern looks like this:

1. Keep proven ERP extraction and validation logic in SSIS.
2. Upload the package to COZYROC Cloud Flex.
3. Parameterize source, target, credentials, and environment values.
4. Schedule package execution or trigger it with a webhook.
5. Land validated ERP data into the Fabric-facing destination selected by the data team.

TCO And ROI Framing

The ROI case is strongest when the organization already owns SSIS logic:

1. Reduced rewrite labor.
2. Lower regression risk from preserving tested package behavior.
3. Faster time to Fabric analytics because integration migration is not the first bottleneck.
4. Better use of existing SSIS developer skills.

FAQ

Do we have to rewrite SSIS packages as Dataflows or notebooks to adopt Fabric?

No, rewriting is one option, not the requirement. COZYROC Cloud Flex runs existing SSIS packages: develop and test in Visual Studio, upload, parameterize, schedule, and monitor. Production-tested extraction, lookup, validation, and error-routing logic keeps working while the data team builds on OneLake, instead of being rebuilt before any analytics value lands.

When is “zero code rewrites” actually true?

Only in one narrow scenario: an existing SSIS package, a compatible runtime target, and a COZYROC Cloud Flex upload after normal compatibility, parameter, connection, and runtime checks. It is not a promise that every integration problem disappears. For brand-new Fabric integrations, the honest claim is reduced custom development through package design, reusable components, and REST configuration.

How do cloud-run packages reach on-prem ERP systems?

Through SSH Configurations in COZYROC Cloud. Connection details for on-prem or private resources are exposed through reusable SSH expressions and environment variables, and packages reference them as parameters. Private hosts and ports stay configuration values instead of hardcoded strings, which keeps one package portable across environment targets.

Can scheduled and event-driven execution coexist after lift-and-shift?

Yes, both are platform features. Scheduled Jobs cover recurring or one-time runs, and Inbound Webhooks let external HTTP events trigger package executions and pass request data. A nightly ERP extract and an on-demand reload triggered by an upstream system can be the same uploaded package with different entry points.

The post Bypassing The Code-Rewrite Trap Facing Microsoft Fabric ERP Migrations appeared first on ERP Software Blog.

Setting up Product Configurator does require dedicated planning, since a working configuration depends on item categories, options, and option choices being defined correctly before that category can generate a usable bill of materials and routing. That said, Product Configurator includes several built-in tools aimed specifically at reducing this setup burden, including the ability to copy an existing item category as a starting point, share reusable sets of option choices across categories, and validate a category's structure before it goes into production use. Insight Works also provides training on setup along with ongoing product support as part of every subscription, which further shortens the learning curve for whoever builds the initial configuration.

Copying an Existing Item Category as a Starting Point

One of the most direct ways Product Configurator reduces setup time is Copy Configurator Item Category, which duplicates an existing category, including its options, option choices, and any rules, into a new category that can then be adjusted rather than built from nothing. This matters most for companies with several similar product lines, such as different frame sizes or material grades of an otherwise similar item, since the shared structure only needs to be built once and then adapted for each variation. Instead of recreating the same options and pricing logic repeatedly, an implementer can clone a proven category and change only what is different about the new product line.

Reusable Option Choice Sets

Product Configurator also allows a set of option choices, for example a standard list of finish colors or fastener types, to be defined once and reused across multiple categories or options rather than rebuilt every time a similar choice is needed. This keeps setup consistent across a product catalog and reduces the amount of duplicate data entry required as a company adds more configurable product lines over time. Reusable choice sets also make ongoing maintenance simpler, since a change made to a shared set applies everywhere that set is used rather than requiring updates in multiple places.

Validating a Configuration Before Go-Live

Check Configuration is a validation tool built into Product Configurator that reviews a category's setup and flags structural issues before that category is used to build real quotes or orders. Running this check as part of implementation gives an implementer a chance to catch setup mistakes in a test or sandbox environment rather than discovering them after a salesperson has already built a configuration in production. This is particularly useful during the initial rollout of a new product line, when the option structure and rules are still being refined.

What About Migrating Existing Configuration Data

Product Configurator does not include a dedicated bulk import tool for bringing configuration data over from a legacy or third party configurator, so most companies build their item categories, options, and choices directly in the app rather than migrating a pre built dataset. For a company with an existing library of product variations, this typically means treating the initial setup as a chance to rationalize choices, using Copy Configurator Item Category and reusable option choice sets to speed up building the smaller number of underlying category structures actually needed, rather than mapping and importing every historical combination individually. If you are still weighing how Product Configurator fits your environment before setup begins, it is worth reviewing how the app works across cloud and on-premises deployments of Business Central and how its per company licensing model applies as more of your team gets involved in building configurations.

Relevant Tools

Product Configurator is the Insight Works app discussed here. It adds configure, price, quote functionality directly inside Business Central, and its Copy Configurator Item Category, reusable option choice sets, and Check Configuration features are specifically aimed at reducing the effort required to complete initial setup and keep it consistent as a product catalog grows.
Initial setup for Product Configurator does require real planning work, but it is not a process a company has to complete from a blank page for every product line. Copying existing categories, reusing option choice sets, and validating a category's structure before go live all reduce the amount of setup and testing required, and support from Insight Works is available throughout that process.

The post What tools simplify the initial setup process for Product Configurator in Business Central? appeared first on ERP Software Blog.

There's a change happening in back office operations. That change is of course AI, and it's going to keep being shaped and reshaping process management for years. While this change is happening throughout the back office, the Accounts Payable department is a smart place to invest some AI budget. It is one area where the positive impacts AI can have are clear.
For teams running Microsoft Dynamics GP or Dynamics 365 Business Central the capture tool is only as good as its connection to your ERP. A tool that reads invoices well but fumbles the handoff to GP or BC creates a new kind of manual work. This guide walks through the criteria that matter most when selecting AI invoice capture for the Dynamics ecosystem.

Why AI for Invoice Capture

Traditional OCR data capture converts an image into text. It can read characters but it does not understand what they mean, so older systems relied on vendor templates that told the software where to find the invoice number, date and total on each layout. When a vendor changed its invoice format the template broke and someone had to fix it.
AI invoice capture goes further. It recognizes invoice fields by context rather than fixed position, which means it can handle new vendors and changing layouts without template maintenance. The better systems also learn from corrections so accuracy improves over time. Because of this, AI can unclog an obvious bottleneck that has been plaguing AP automation efforts for decades.

Criteria for Selecting AI Invoice Capture Software

1. Accuracy You Can Measure

Accuracy is the first number to ask any vendor for and the hardest one to verify. Look for a clear statement of how many invoices pass through without manual correction, not just character level recognition rates. A system that reads 99 percent of characters correctly can still require edits on a large share of invoices if it misplaces a single field.
Fidesic publishes its results in these terms. Its MagiCapture engine reports 96% of invoices captured without edits, requires no invoice templates to create or adjust and gets more accurate with each submission, many times reaching 99% accurate within 6 weeks.

2. Native ERP Integration

This is where many AP automation projects stall. Generic capture platforms often connect to Dynamics through middleware, flat file imports or third party connectors. Each layer adds a point of potential failure.
Ask vendors how their product is built to work with your ERP. For Business Central the gold standard is an extension written in AL, the same language Microsoft uses for BC itself. Fidesic uses Business Central's AL programming language to create a truly native integration, and Fidesic AP is Microsoft approved and available on Microsoft Marketplace. Its tools are built in the same programming languages as Business Central and Dynamics GP for seamless integration, so GL updates happen automatically.

3. Setup Without Mapping or Coding

Implementation timelines vary widely. Some platforms require weeks of field mapping, vendor template building and IT involvement before the first invoice is processed. AP teams rarely have that kind of bandwidth.
Favor solutions that go live quickly and adapt to your vendors on their own. Fidesic describes its capture as requiring no mapping and no coding, which keeps onboarding light for finance teams without dedicated developers.

4. A Safety Net for Exceptions

No AI reads every invoice perfectly. Handwritten notes, poor scans and unusual formats will always appear. What matters is what happens next. Some vendors push every exception back to your clerks. Others provide human verification as part of the service.
Fidesic takes the second approach. If AI can't capture an invoice, the Fidesic team makes sure it is entered properly. For AP managers this means predictable outcomes rather than a growing exception queue.

5. Coverage Beyond Capture

Invoice capture is the front door of AP automation, not the whole house. Consider whether the vendor also supports approval routing, vendor payments and vendor self service so you avoid stitching together multiple tools. Fidesic offers a connected suite that includes AI powered invoice capture, visual workflow editor, simplified vendor payments and a self serve vendor portal. Payments can go out by ACH or paper check directly from Business Central.

6. Multi-Entity and Location Support

Organizations with multiple companies or locations need capture that codes invoices correctly across entities. Confirm the product handles location data and works with multi-entity tools you already use. Fidesic includes location capture and encoding.

7. Dynamics Expertise and Long Term Commitment

A vendor that specializes in Microsoft Dynamics will understand your chart of accounts, your posting logic and your upgrade path. This matters even more for GP users weighing a move to Business Central. Look for a partner that supports both platforms and can carry your AP process through a migration.
Fidesic was founded in 2008, with Business Central customers since 2021 that now accounts for 80% of new customers. The company has also stated a commitment to helping Microsoft Dynamics GP users stay contemporary with tools for the future, which gives GP teams a path forward whether they stay on GP or transition to BC.

8. Security and Hosting

Invoice data includes bank details, pricing and vendor information. Ask where data is hosted and what standards protect it. Fidesic is Azure hosted, with data protected by strict security standards and high availability and performance.

Questions to Bring to Every Vendor Demo

Use the above criteria to compare options side by side.

• What percentage of invoices post with zero manual edits?
• Is the integration native to GP and BC or built on middleware?
• How long until the first invoice is processed?
• Who handles invoices the AI cannot read?
• Does the platform include approvals and payments or only capture?
• How does pricing scale with invoice volume?

The Business Case

Higher levels of efficiency are assumed when it comes to data capture. The decision to implement comes down to the solution's value beyond efficiency. The solution you want is the one that can not only reduce the hours spent on monthly invoice approval, but drives strategic workloads, reduces fraud and errors, and provides a more accurate data set that informs decisions in every department.

How Fidesic Helps AP Teams on Dynamics GP and Business Central

Fidesic is built specifically for accounts payable teams using Microsoft Dynamics GP and D365 Business Central. Instead of adapting a generic capture engine to fit Dynamics, Fidesic works inside the ERP your team already knows.
MagiCapture by Fidesic delivers AI powered invoice capture that improves with every invoice and requires no templates. Native integration means captured data flows straight to your GL without imports or workarounds. From there, Fidesic makes the entire AP process seamless so every invoice gets capture, approved, paid and posted without stress. Thousands of monthly invoices processed in hours not days, with fewer duplications and other errors.
For GP users planning a move to Business Central, Fidesic supports both platforms, so your AP automation can move with you, and we'll be with you at every step of the way. Teams can get started through free and PRO pricing plans and install the Business Central app directly from Microsoft AppSource.
If you're looking for a smart way explore AI-powered process optimization for GP or Business Central, Fidesic offers the most direct route to accurate, touchless invoice processing inside Microsoft Dynamics.
Learn More

The post Choosing AI Invoice Capture for Dynamics GP and Business Central appeared first on ERP Software Blog.

Microsoft Dynamics 365 Business Central, ERP Migration

Your ERP Has the Data. So Why Is Finance Still in Excel?

Turn ERP Data into Smarter Decisions
Your ERP may be the financial system of record—but should it also be your planning system? Dominick Zappia, Partner at Admiral Consulting Group, sits down with Gurpreet Chaggar, Product Marketing Manager at Prophix, to explore why growing finance teams often outgrow ERP-only financial processes. They discuss the role of CPM and FP&A, reducing spreadsheet dependency, improving forecasting and financial close, connecting Business Central with Prophix, and why clean, governed data must come before AI.
Key Discussion Points
1. Your ERP isn't designed to do everything finance needs.
ERP systems excel at recording transactions and showing what happened. As companies become more complex, budgeting, forecasting, scenario planning, and forward-looking analysis often require capabilities beyond the ERP itself.
2.Excel can be a warning sign that finance has outgrown its current architecture.
When critical planning processes move into spreadsheets, organizations can face disconnected files, version-control problems, manual consolidation, and uncertainty about whether leadership is working from trusted numbers.
3.A new ERP alone may not solve the planning problem.
For CFOs evaluating ERP modernization, one of the most important lessons is architectural: distinguish the system of record from the system of analysis, intelligence, and control. Prophix can complement an ERP such as Microsoft Dynamics 365 Business Central rather than forcing the ERP to handle every financial process.
4.Modern FP&A gives CFOs more powerful ways to model the future.
Instead of exporting data into spreadsheets to answer every new "what if?" question, finance teams can use multi-scenario modeling to evaluate variables such as cash, headcount, investments, and other assumptions side by side.
5.Faster close creates capacity for higher-value finance work.
Gurpreet says Prophix customers can potentially remove three to seven days from the close process. The broader opportunity is moving finance professionals away from data manipulation and toward analysis and decision support.
6.AI readiness starts with the data—not the AI tool.
Adding AI on top of fragmented, ungoverned financial information doesn't fix the underlying problem. CFOs should first ask, "Is our data ready for AI?" Clean, governed, connected information creates the foundation for trustworthy AI-powered analysis.
7.ERP modernization is an opportunity to rethink the entire finance architecture.
Prophix can bring information together from ERP, CRM, HRIS, flat files, and other source systems. That gives CFOs an opportunity to think beyond replacing their ERP and instead build a connected financial environment for reporting, planning, forecasting, analytics, and eventually AI.
Notable Quotes:
- “An ERP is built more to be a transactional system of records. So it's showing what happened.”
- On the cost of manual warehouse operations: “A lot of manual effort or processes from receiving to picking and then manually posting it later…”
- “It's pretty much moving through that mess faster rather than giving you an answer that is correct and grounded in reality.”
- “The greatest reason to have a CPM tool is to bring all of that data into one place.”
- On eliminating tribal knowledge risk: “Now they’re doing everything from one system… it’s available to everybody to see in real time.”
Chapters
[00:00] Why Your ERP Can't Do Everything
[01:32] Why Finance Keeps Falling Back on Excel
[03:03] Automating Reporting, Dashboards & Financial Processes
[03:36] Why AI Can Accelerate Bad Financial Data
[04:44] How Prophix Is Bringing AI into Finance
[05:49] ERP vs. CPM: Understanding the Difference
[07:00] Business Central + Prophix
[08:40] Connecting Prophix with ERP Data
[09:24] The Business Case for Faster Financial Close
[11:05] Moving Beyond Basic Budgeting with Scenario Planning
[12:03] Bringing Enterprise Planning Power to the Mid-Market
[14:27] Why Most AI Strategies Should Start with Data
[15:43] What a Prophix Implementation Looks Like
[17:23] Connecting ERP, CRM, HR & Other Business Data
[19:21] The First Question CFOs Should Ask About AI
[20:41] How Long Does Prophix Take to Implement?
[22:22] Supporting Finance After Go-Live
[25:28] Self-Service Financial Reporting & Analytics
[26:37] Why Finance Leaders Don't Always Know They've Outgrown Their Tools
[29:33] Better Decisions Through Connected Financial Data
[32:16] Prophix Updates, Integrations & Platform Evolution
[34:37] Closing Thoughts
Why Watch This Episode
If your finance team is outgrowing spreadsheets, or you're evaluating a new ERP, this episode will help you understand what your ERP should do, what it shouldn't, and where modern FP&A fits. Learn how connected financial planning, forecasting, scenario modeling, and AI can help your team spend less time managing data and more time making confident business decisions.
Ready to get more intelligence from Business Central?
Discover how AI and modern financial planning can help you turn Business Central data into deeper insights, smarter forecasts, and more confident decisions.
Talk with Admiral Consulting Group about the next step in your finance transformation.

The post Beyond ERP: How CFOs Can Plan, Forecast & Close Faster appeared first on ERP Software Blog.

Seafood Operations Put Unusual Demands on ERP

Seafood is not a simple buy, stock, sell business.
A company may purchase product by case, receive and value it by actual weight, track it by lot and origin, monitor expiration dates, transform raw product into multiple finished products, and sell it under customer-specific pricing and packaging requirements.
The same product can touch purchasing, inventory, quality, processing, warehousing, sales, costing, and finance before it leaves the building.
That creates an important question for any seafood company evaluating Microsoft Dynamics 365 Business Central:
Which requirements can Business Central handle as the core ERP platform, and where does the seafood operation require industry-specific functionality?
That distinction matters.
Business Central can provide the ERP foundation for financial management, purchasing, sales, inventory, warehousing, reporting, item tracking, and integration. Seafood companies may then need specialized capabilities around catch weight, advanced lot management, processing, yield, traceability, warehouse execution, and other industry requirements. This core-platform-plus-extension approach is also the central positioning required by the article brief.
The goal should not be to force seafood operations into the software. Instead, build an ERP environment that reflects how the business actually works.
 

Why Seafood Companies Need More Than Basic ERP Functionality

The challenge in seafood is that physical product movement and financial information are tightly connected.
Consider a processor or distributor that purchases seafood in cases but needs to maintain its actual weight. That product may need to retain information about its supplier, origin, lot, expiration date, quality status, and warehouse location. It may then be sold by actual weight.
For a processor, the situation becomes even more complex. Whole fish might become fillets, portions, trim, and packaged finished goods. Management needs to understand not only what went into the process and what came out, but also yield, loss, actual weight, cost, and lot genealogy.
This is where ERP evaluations can go wrong. A checklist may show that a system has “inventory,” “lot tracking,” or “warehouse management.” But those labels don’t tell you whether the system can support the actual transaction from beginning to end.

“The feature isn’t the important part. The important question is whether the information survives the transaction.” — Andrew Good, CEO, DynamicsFoodERP

For seafood companies, the real evaluation needs to happen at the workflow level.
 

Where Microsoft Dynamics 365 Business Central Fits

Microsoft Dynamics 365 Business Central can provide seafood companies with a core ERP platform that connects financial management with purchasing, sales, inventory, warehouse processes, reporting, item tracking, and other business functions. Seafood-specific functionality can then extend that foundation where required.
Don't underestimate the importance of that foundation.
When purchasing, inventory, sales, and finance share the same ERP environment, a transaction does not have to be reconstructed across separate departmental systems before management can understand its financial impact.
Business Central also provides native item-tracking functionality. Microsoft documents the ability to assign serial, lot, and package numbers to inbound and outbound transactions, with the resulting tracking information associated with item ledger entries.
But an important distinction exists between native Business Central functionality and the full requirements of a seafood business.
Standard lot tracking, for example, does not automatically cover every advanced seafood traceability workflow. Don't confuse standard inventory functionality with a complete catch-weight solution.
That distinction is not a weakness in the platform. That's why seafood companies need to evaluate the combination of platform, configuration, integrations, and industry-specific functionality rather than simply asking whether Business Central “does seafood.”
 

Lot Tracking and Seafood Traceability in Business Central

Business Central provides native serial, lot, and package tracking, but seafood traceability can require more information and workflow control than basic lot identification alone.
Microsoft’s item-tracking functionality can trace tracked inventory through inbound and outbound documents and internal warehouse movements. Microsoft also notes that tracked serial and lot numbers can be traced backward and forward through the supply chain.
For a seafood company, however, traceability questions often go further:

• Which supplier provided the product?
• What was its origin?
• Which incoming lot was received?
• Was the product processed, split, combined, or repacked?
• What finished lots resulted?
• What is its expiration or quality status?
• Which customers received the finished product?

For seafood importers, there can also be regulatory recordkeeping considerations. NOAA’s Seafood Import Monitoring Program, for example, establishes reporting and recordkeeping requirements for covered seafood imports from harvest through entry into U.S. commerce.
Seafood traceability should preserve product information from catch and receiving through processing, distribution, and customer shipment.

Catch Weight and Dual Units of Measure

Catch-weight is one of the clearest examples of where standard inventory requirements and seafood-specific requirements diverge.
Suppose 20 cases of seafood arrive at the warehouse.
The logistical quantity is:
20 cases
But the actual received weight is:
812 pounds
Both numbers are correct. More importantly, both may need to remain connected.

 
The warehouse may handle cases. Purchasing and costing need the actual received quantity. Sales may price the product by weight. The invoice may depend on actual shipped weight. Finance ultimately needs reliable cost and margin information.
If those quantities diverge at any point in the process, employees start compensating with spreadsheets, manual adjustments, re-entry, and reconciliation.
The result can affect inventory accuracy, purchasing, invoicing, costing, and ultimately margin.
Business Central has standard inventory and unit-of-measure functionality, but companies should not assume that this is equivalent to a complete seafood catch-weight workflow. The evaluation should confirm how logistical units and actual weight stay synchronized through the relevant transactions.

“With catch weight, the question isn’t whether the system can store two numbers. The question is whether those two numbers stay connected everywhere they matter.” — Andrew Good

Managing Product Transformations and Processing Yield

Seafood processors need ERP workflows that preserve inventory, traceability, and financial visibility as raw material becomes finished product.
Imagine a lot of whole fish entering processing.
It becomes fillets. Some fillets become portions. Product may be graded, combined, split, repacked, or moved into different finished SKUs.
At each stage, management may need visibility into:
Raw material → processing → finished product
But the physical transformation is only part of the story.
The operation may also need to retain lot genealogy, actual weight, yield, trim or loss, and cost. If the transformation creates a new inventory item but severs the relationship to the original lot or cost information, the ERP record becomes less useful precisely when the business becomes more complex.
This is an area where requirements need to be documented carefully. The right solution depends on what the company actually processes, how it measures yield, what genealogy it needs to preserve, and how costs should flow through production.
The objective is not simply to record production.
It is to preserve the product's operational and financial story as it changes form.
 

Shelf Life, Expiration, and Inventory Rotation

For seafood companies, inventory availability is not only about how much product is on hand. It is also about whether that product can still be sold to the intended customer.
Business Central supports expiration-date information as part of its item-tracking configuration. Microsoft documents expiration rules for serial- and lot-tracked items, including requiring expiration-date entry and calculating expiration dates.
Business Central also supports FEFO, or First-Expired-First-Out, in applicable warehouse configurations. When FEFO is enabled at the location, tracked items can be picked according to expiration date, with the earliest expiration dates selected first.
That provides an important platform capability.
But seafood companies should still evaluate their complete shelf-life requirements. A sales team, for example, may need to know not merely that 5,000 pounds are on hand, but how much has sufficient remaining shelf life to meet a particular customer’s requirements.
That difference can directly affect waste, inventory utilization, fulfillment, and margin.
 

Understanding the True Cost and Margin of Seafood Products

Accurate seafood margins depend on accurate operational information.
Purchase price alone rarely tells the entire story.
Depending on the business, true product economics may include:

• Purchase cost
• Actual received weight
• Freight
• Duties and other landed costs
• Processing costs
• Yield and trim loss
• Packaging
• Storage
• Spoilage
• Customer-specific pricing

Business Central provides item-charge functionality for adding costs such as freight, physical handling, insurance, and transportation to inventory. Microsoft also documents landed cost as the purchase price plus direct item charges assigned to the receipt.
This is particularly relevant to seafood importers and distributors because the difference between purchase price and landed cost can materially change the view of product profitability.
But costing accuracy still depends on operational accuracy.
If actual weight is wrong, yield is calculated elsewhere, or processing loss isn't captured consistently, a sophisticated financial system still works with incomplete information.
That leads to a more useful executive question:
Can we confidently determine actual profitability by product, customer, and order?
“Revenue tells you where you’re selling. Margin tells you where you’re creating value. Your ERP should help management understand both.” — Andrew Good
 

Connecting the Warehouse to the ERP

ERP value diminishes when the warehouse has to build a separate information system around it.
A typical seafood receiving process can involve weighing, lot capture, labeling, quality information, expiration dates, warehouse placement, and inventory updates.
Now compare two information flows:
Scale → paper → spreadsheet → ERP
versus
Physical transaction → connected digital workflow → ERP
The first creates multiple opportunities for delay and discrepancy. The second aims to capture information as close as possible to the physical transaction.
Business Central provides warehouse functionality supporting inbound and outbound processes, while Microsoft’s item-tracking documentation also covers lot and serial information within warehouse activities.
Barcode scanning, mobile workflows, scales, label systems, and other warehouse technologies may form part of the broader solution depending on the operation and integrations selected.
The objective is simple: employees should not have to become the integration layer between the warehouse and the ERP.
 

EDI and Customer Requirements

Seafood companies often serve retailers, foodservice organizations, distributors, and other trading partners with specific transaction requirements.
These may include:

• Purchase orders
• Order acknowledgments
• Shipment information
• Invoices
• Customer-specific labels
• Pack configurations
• Weight information
• Traceability information

EDI can reduce manual transaction handling, but it should be evaluated as part of the complete order-to-cash process rather than as an isolated technical feature.
The important question is whether customer requirements can flow through the ERP environment without repeatedly creating duplicate entries or one-off processes.
Every seafood company has a different customer mix, so evaluate EDI requirements against the company’s actual trading relationships rather than treating them as a universal checklist item.
 

Where Seafood-Specific Functionality Extends Business Central

Business Central provides the ERP foundation. Seafood-specific functionality can extend that foundation to support industry requirements.
That distinction is central to evaluating Business Central for seafood companies.
A seafood business may need additional functionality around:

• Catch weight and synchronized units of measure
• Advanced lot management
• Seafood traceability
• Processing and product transformations
• Yield and loss
• Warehouse scanning and data capture
• Scale integration
• EDI
• Quality workflows
• Customer-specific requirements

Not every seafood company needs every capability.
A seafood distributor with relatively straightforward operations will have different requirements from a processor that transforms variable-weight raw material into multiple finished products across several facilities.
DynamicsFoodERP is designed around this platform-plus-industry-functionality model, extending the Microsoft Dynamics 365 Business Central environment for food and seafood requirements.
The deeper question, then, is not simply, “Can Business Central support seafood?”
It is:
What combination of Business Central, configuration, integration, and industry-specific functionality will support the way our seafood business actually operates?
Learn more about Seafood ERP Software.
 

What Seafood Companies Should Evaluate Before Choosing Business Central

Before selecting Business Central, I recommend testing several real products and transactions end to end.
Don’t evaluate only from a feature checklist.
Ask the prospective solution to demonstrate how it would handle:

1. Variable weights: Can cases and actual weight remain synchronized?
2. Lot traceability: Can you follow product from supplier through inventory, transformation, and customer shipment?
3. Processing: Can product splitting, combining, repacking, and transformation be represented accurately?
4. Yield and loss: Can operations and finance understand what went into processing and what came out?
5. Shelf life: Can employees identify inventory by expiration and determine what should move first?
6. Warehouse capture: How are weights, lots, labels, scans, and movements recorded at the point of activity?
7. Customer requirements: How are EDI, labels, weights, shipping, and other requirements handled?
8. Cost and margin: Can management see the financial effect of actual weight, landed costs, processing, and yield?
9. Architecture: Which requirements are native to Business Central, which depend on configuration or integration, and which require industry-specific extensions?

That final question is especially important.
The objective should not be to minimize extensions at all costs. It should be to understand why each component of the solution is needed and how it supports the business.
Learn more about the distinction between general ERP vs. seafood ERP.
 

Frequently Asked Questions About Business Central for Seafood Companies

Is Microsoft Dynamics 365 Business Central good for seafood companies?

Yes, Business Central can provide a strong core ERP platform for seafood companies, including financial management, purchasing, sales, inventory, warehouse processes, reporting, and native item tracking.
However, seafood operations may require additional industry-specific functionality for areas such as catch weight, advanced traceability, processing, yield, warehouse execution, and EDI.
The correct solution depends on the company’s actual workflows and complexity.
 

Does Business Central support catch weight?

Business Central provides standard inventory and unit-of-measure capabilities, but companies should not assume these cover a complete seafood catch-weight solution.
True catch-weight requirements may involve keeping logistical quantity, such as cases, synchronized with actual weight through receiving, inventory, sales, shipping, invoicing, costing, and reporting. Seafood companies should validate this workflow during solution evaluation rather than relying on a feature label.
 

Can Business Central track seafood lots?

Yes. Microsoft Dynamics 365 Business Central provides native item tracking using serial, lot, and package numbers on inbound and outbound transactions.
Seafood businesses may need to extend basic lot tracking when requirements include richer information and workflows around origin, transformations, quality status, expiration, genealogy, or compliance.
 

What additional ERP functionality do seafood processors need?

Requirements vary, but seafood processors may need functionality for catch weight, advanced lot management and traceability, raw-to-finished-product transformations, yield and loss, shelf-life management, warehouse data capture, quality workflows, EDI, and accurate costing.
The correct approach is to map these requirements to actual transactions and determine what Business Central provides natively and what should be handled through configuration, integration, or seafood-specific extensions.
 

Building Business Central Around the Realities of Seafood

Microsoft Dynamics 365 Business Central can provide a strong ERP foundation for seafood processors, distributors, importers, and wholesalers. The more important question is whether the complete solution reflects how the company buys, receives, weighs, tracks, processes, stores, sells, and measures seafood profitability.
That requires a clear distinction between what Business Central provides natively and where industry-specific functionality adds value.
For executives, this is ultimately less about software architecture than business confidence. Can sales trust inventory? Can operations trust the lot information? Can finance trust product cost? Can leadership trust the margin?
When those answers come from the same connected operational foundation, ERP becomes much more than a system for recording transactions.
Learn more about DynamicsFoodERP and what to evaluate when building a Business Central environment around the realities of a seafood business.

The post How Microsoft Dynamics 365 Business Central Supports Seafood Companies appeared first on ERP Software Blog.

Latin America is one of the fastest-growing regions for Microsoft Dynamics 365 Business Central adoption. It's also one of the most complex when it comes to fiscal compliance. Every country in the region runs its own electronic invoicing mandates, tax authorities, and reporting rules, and few partners have the bandwidth to build that expertise in-house.
As a result, many U.S. and Canadian Business Central partners turn down LATAM opportunities entirely — not because the client relationship isn't valuable, but because the localization work looks too heavy to take on alone. LLB Solutions is hosting a live session on this exact problem, and it's worth a look if LATAM keeps coming up in your client conversations or sales calls.

Reserve Your Spot

Register for the LATAM Localizations webinar directly on Microsoft Teams:
REGISTER HERE
You can also view the full event listing on ERP Software Blog for the complete agenda and add-to-calendar options.
 

Why LATAM Compliance Trips Up Partners Who Haven't Done It Before

The complexity isn't hypothetical. Mexico's CFDI requires real-time SAT validation before an invoice has any legal standing. Colombia's DIAN issues a unique CUFE code for every document. Chile's SII authorizes folio ranges in advance and expects a digital stamp on every DTE. Multiply that by 17 countries, each with its own tax authority, document formats, and update schedule, and it's clear why building this in-house rarely makes sense for a single project.

What the LATAM Localizations Webinar Covers

The session walks through five specific areas, plus live Q&A:

• Why LATAM is a growth market right now — the trends pushing multinational and mid-market companies to standardize on Business Central across their Latin American subsidiaries
• How LLB's localizations work — certified e-invoicing, tax, and regulatory functionality already built and maintained for Argentina, Mexico, Colombia, Peru, Panama, and 12+ other countries
• Compliance without the complexity — fiscal requirements automated natively inside Business Central, with no custom code and no regulatory maintenance on the partner's side
• Partnership models that fit your business — referral, reseller, and co-delivery options, each built for recurring revenue
• What a real LATAM engagement looks like — from the first client conversation to go-live, including implementation, licensing, and support

Who Should Attend This Business Central Partner Session

This session is built for Dynamics 365 Business Central partners, VARs, ISVs, and independent consultants across the U.S. and Canada — whether LATAM is still a hypothetical growth market or clients are already asking about operating in Latin America. If either of those describes your practice, the content applies directly.

Why Turning Away LATAM Work Costs More Than It Looks Like

Declining a LATAM request rarely means losing just that one piece of work. More often, it means losing the entire client relationship to a partner who can say yes to the whole scope. This session addresses that risk directly: how to keep LATAM business in-house by partnering with a team that has already solved the compliance problem, instead of referring it out and hoping the client comes back.

LATAM Localizations Webinar: Date, Time, and Format

The session runs live via Microsoft Teams on October 21, 2026, from 11:00 AM to 12:30 PM EST, followed by open Q&A. Attendees can bring questions about specific countries, client scenarios, or how a partnership with LLB Solutions could work for their practice.
LLB Solutions currently maintains certified, AppSource-published localizations across 17+ Latin American countries, giving partners a way to extend their practice regionally while LLB handles the fiscal complexity behind the scenes.
 
LATAM fiscal compliance isn't something a Business Central partner needs to build from scratch to serve clients there. The point of this webinar is showing exactly what that partnership can look like in practice — the technical side, the commercial models, and what a real engagement timeline looks like from first conversation to go-live. It's a 90-minute investment that can open up a market most partners currently leave to someone else.
Register now to see how LLB Solutions can help you expand your Business Central practice into Latin America

The post LATAM Localizations Webinar: What Business Central Partners Need to Know appeared first on ERP Software Blog.

Key Takeaways

• Disconnected systems between estimating, shop floor, and finance are the leading cause of quiet margin loss in print businesses.
• Connecting shop floor reporting to ERP can cut job processing time significantly, based on Boyer client results.
• Microsoft Dynamics 365 F&SCM paired with DynamicsPrint gives print businesses one connected system for estimating, production, and finance data.

A print job can look profitable on the estimate and still lose money on the shop floor. That gap, between what a job was supposed to cost and what it really cost, is where most print businesses quietly lose their margin. It rarely shows up as one big mistake. It shows up as a dozen small ones: an estimate built in one system, a job ticket rekeyed into another, actual material use tracked on a clipboard that never makes it back to finance. By the time anyone reconciles the numbers, the job is done and the loss is already booked.
This is the hidden cost of systems that don't talk to each other in print. Not a single dramatic failure, but a slow leak that adds up across every estimate, every run, and every invoice.

What Does "Disconnected Systems" Actually Mean for a Print Business?

Disconnected systems means the tools that touch a job, estimating, scheduling, shop floor reporting, and finance, don't share the same data in real time. Each system holds its own version of the truth. The estimating spreadsheet says one thing. The production floor's paper tickets say another. Finance finds out what a job really cost weeks after it shipped.
Print businesses often accumulate these gaps over time. A spreadsheet gets built to solve one problem. A standalone scheduling tool gets added later. An accounting system runs separately from both. None of it was a bad decision in isolation. Together, it means no one in the business can answer a simple question with confidence: what did this job actually cost us to produce?

Where Print Margins Quietly Disappear

Margin erosion in print rarely traces back to one cause. It builds up across three specific points where systems fail to talk to each other.

Estimating Blind Spots

Estimates are only as good as the cost data behind them. When estimating runs on a spreadsheet disconnected from actual production history, quotes get built on assumptions instead of real numbers. Material waste from the last similar job, actual machine hours, actual labor cost, none of that feeds back into the next estimate. The result is a bid that looks competitive on paper and erodes margin the moment the press starts running.

Shop Floor Data Lag

Job tickets, material consumption, and machine hours often get tracked on paper or in a system that isn't connected to finance. That data eventually gets entered somewhere, but by the time it does, the job is finished and any correction is too late to help. Boyer has seen print businesses cut an average job's processing time from 17 hours and 37 minutes down to 7 hours and 36 minutes, simply by connecting shop floor reporting directly to their ERP. That's a reduction of more than 50 percent, and it comes from eliminating the delay between when work happens and when it gets recorded. Similar results show up across Boyer's print and packaging case studies.

Manual Rekeying Between Systems

Every time data moves from one disconnected system to another by hand, it introduces two costs: the labor to do the rekeying, and the risk of error when it doesn't get done correctly. A material quantity typed wrong, a job cost applied to the wrong account, a scheduling change that never reaches the floor. None of these mistakes are dramatic on their own. Across a full production schedule, they add up to real dollars.

The Real Cost of Chasing Data Across Systems

Beyond the direct cost of errors, these fragmented systems carry a hidden labor cost: the time staff spend chasing information instead of doing their jobs. Estimators tracking down actual costs from the last run. Production managers calling finance to confirm material costs. Finance teams rebuilding job profitability reports manually because the data doesn't live in one place.
That time is real money, even when it never shows up as a line item. It's also the reason job costing in print so often happens after the fact instead of in real time. A connected system lets a business see job profitability while the job is still in production, not weeks after it's invoiced.
According to Smithers' The Future of Global Printing to 2030, the global print and packaging market is forecast to grow to $969.7 billion by 2030 at a 2.2% compound annual growth rate. Growth is good news for print businesses, but it also means more jobs, more estimates, and more data moving through the business every day. Systems that were manageable at a smaller volume start breaking down at scale.

How Connected ERP for Print Businesses Closes the Margin Gap

Closing the margin gaps described above requires one thing: a system where estimating, production, and finance share the same data instead of working from separate records.
Microsoft Dynamics 365 Finance & Supply Chain Management (F&SCM), paired with DynamicsPrint, gives print businesses a single system where estimating, production, and finance data live together instead of across separate tools. Actual costs from a completed job feed directly into the next estimate. Shop floor activity updates job costing in real time instead of after the fact. Finance sees true job profitability as production happens, not after month-end close.
This isn't about adding another tool to the stack. It's about replacing the disconnected pieces with one connected system built specifically for how print businesses operate, from quoting through shop floor management to reporting.

What This Looks Like in Practice

Boyer works with print and packaging businesses to identify exactly where fragmented systems are costing them money before recommending a fix. Sometimes the gap is in estimating. Sometimes it's shop floor data that never makes it back to finance. Usually it's some combination of both.
The starting point is always the same: map where data breaks down between systems, then connect those points through Microsoft Dynamics 365 F&SCM and DynamicsPrint so estimating, production, and finance are working from the same numbers.

Frequently Asked Questions

What causes margin loss in print businesses with disconnected systems?

Margin loss typically comes from three sources: estimates built on outdated cost data, shop floor activity that isn't recorded until after a job ships, and manual rekeying of data between systems, which introduces errors and delays.

How does ERP for print businesses connect estimating and production?

A connected ERP system feeds actual production costs, material use, and machine hours back into the estimating process, so future quotes reflect real performance instead of assumptions.

What is DynamicsPrint and how does it work with Microsoft Dynamics 365 F&SCM?

DynamicsPrint is an industry-specific functionality built on top of Microsoft Dynamics 365 F&SCM, adding print-specific estimating, scheduling, and shop floor management to the core ERP platform.

How long does it take to see results after connecting disconnected systems?

This varies by business and by how many systems are involved. Boyer typically starts with a review of where data currently breaks down before scoping a timeline.

What print segments benefit most from a connected ERP system?

Commercial print, packaging, labels, large format, and digital print businesses all rely on accurate job costing, which makes them strong candidates for a connected ERP approach.

Ready to Find Where Your Margins Are Leaking?

Want to see how this works in your environment? Our team is happy to walk through where your systems may be disconnected and what closing those gaps could mean for your margins. Our team can also walk you through how Microsoft Dynamics 365 F&SCM fits into that picture, or you can reach out to Boyer directly to start the conversation.

Boyer & Associates is a Microsoft Dynamics 365 implementation partner that helps print and packaging businesses connect estimating, production, and finance data through Microsoft Dynamics 365 Finance & Supply Chain Management (F&SCM) and DynamicsPrint. Our team has helped print businesses replace disconnected systems with a single source of truth for job costing and margin visibility.

The post How Disconnected Systems Quietly Drain Print Margins appeared first on ERP Software Blog.

When a company has spent time negotiating a merchant account, choosing an acquirer, and securing processing rates it is happy with, switching processors just to integrate payments with Microsoft Dynamics 365 Business Central can feel unnecessary.
That is the problem Bring Your Own Processor (BYOP) is designed to solve.
Instead of requiring businesses to adopt a specific processor, a BYOP payment solution connects the merchant account and processor they already use to Business Central. The payment platform becomes the connection between the ERP and the existing processor, rather than forcing the business to replace a working payment setup.

Why Processor Flexibility Matters

A single-provider payment model can create a dependency that becomes difficult to unwind.
When the same provider controls the payment gateway and card vault, it often also controls the tokens associated with stored customer cards. Those tokens allow recurring billing and saved payment methods to work without customers entering their card details repeatedly.
The problem comes when a business wants to change processors. Gateway-issued tokens may not be transferable, which can mean re-tokenizing stored cards or asking customers to enter their payment information again.
For businesses with recurring payments or automated accounts receivable processes, that creates more than an inconvenience. It can introduce customer friction and make changing processors significantly more difficult.

Saving Time During Implementation

BYOP can also reduce implementation work.
Setting up a new merchant account, completing approvals, and migrating stored payment information takes time. If a business already has an established processor and merchant account, connecting that existing relationship to Business Central can eliminate much of that work.
The result is a payment implementation that can focus on connecting the ERP to the existing payment infrastructure rather than rebuilding the infrastructure itself.

Lowering Processing Costs

Processor flexibility is only part of the equation. Businesses also need to understand what they are paying for each transaction.
For commercial card payments, Level 3 data can help eligible transactions qualify for lower interchange rates by passing enhanced information such as line-item details. That data may already exist inside Business Central, but if it is not passed to the processor, the business may miss the opportunity to qualify for better rates.
Visa's retirement of its legacy Level 2 interchange program in 2026 makes understanding Level 3 data even more important for organizations processing commercial and purchasing cards.
BYOP does not eliminate interchange fees. Instead, it gives businesses the flexibility to keep their existing processor while using payment infrastructure that can support enhanced transaction data.
USTPay reports that clients commonly see 10 to 30 percent lower processing costs, depending on transaction volume and card mix, when processor pricing and payment data are optimized together.

The Value of an Independent Card Vault

An independent, PCI-compliant card vault is another important part of the BYOP model.
When payment tokens are stored in a neutral vault rather than tied to a single gateway, businesses can change processors without necessarily having to rebuild their stored payment credentials.
It can also make redundancy easier. A backup gateway can provide an alternative payment path if a primary processor experiences an outage.
For growing organizations, the same architecture can make expansion easier. Adding another entity, market, currency, or payment provider does not necessarily require rebuilding the entire payment stack.

What Business Central Users Should Ask

Before choosing a payment solution, ask who owns the card vault, whether stored tokens can move if you change processors, whether you can keep your existing merchant account, and whether Level 3 data is supported.
It is also worth asking how the payment solution handles reconciliation and how long implementation actually takes.
The broader point is simple: payments should work around your business, not force your business to work around the payment provider.
Want to learn more about how BYOP can reduce payment costs and implementation time? Read the full article, Bring Your Own Processor: How BYOP Saves Business Central Users Time and Money.

The post Bring Your Own Processor: How BYOP Saves Business Central Users Time and Money appeared first on ERP Software Blog.

Every organization that runs more than one reporting tool eventually holds the same meeting. Two people arrive with two numbers for the same month. Both numbers come out of systems the company paid for. Neither person can say which one belongs in the board pack, and the next twenty minutes go to reconciliation rather than to the decision the meeting existed to make.

The instinct at that point is to consolidate. One platform, one place to look, and the argument goes away. Power BI is usually the candidate, because the licences already sit in the tenant. That instinct is sound. The reasoning behind it is usually wrong, and DAX Software Solutions sees the consequence often enough to name it.

Why Two Reports Disagree

Two reports disagree because two people defined the measure differently. One counts revenue at invoice, the other at shipment. Perhaps one excludes intercompany and the other forgot to. Or a ledger balance as of last night sits next to a transactional table as of an hour ago.

None of those differences live in the reporting tool. Move both reports to Power BI without settling any of them, and you now own two Power BI reports that disagree.

That is how consolidation programs become sunk cost. A company migrates the whole inventory, retires the old tools, then watches the same reconciliation meeting happen the following month inside one platform. The migration was real work. It bought no agreement, because agreement never appeared in the scope.

What Consolidation Actually Consolidates

Start with the decisions rather than the report inventory. Ask each function for the recurring calls it makes: reprice, restock, extend credit, approve overtime, escalate a late account. Then ask which number each one turns on.

The list comes back far shorter than the inventory, and the gap is the useful finding. Most estates carry many times more reports than the organization has recurring decisions to make. Everything else is context, history or one person's preferred layout.

For each number on that list, write four lines before anyone opens Power BI Desktop:

• Definition — one sentence a non-analyst can read without asking a follow-up question.
• Source of record — named to the table or entity, not to a team.
• Owner — by role rather than by person, so it survives someone leaving.
• Refresh window — stated as a duration the business has accepted.

Circulating that set forces the disagreements into the open while they stay cheap. A definition argument during design costs a meeting. The same argument after two hundred people have built habits on the old number costs a quarter.

What "Current" Means Once the Data Lands

Analytical data arrives on an interval. It does not arrive instantly, and pretending otherwise creates a trust problem later.

Microsoft documents configurable intervals of 5, 15, 60 or 1440 minutes for finance and operations data in Azure Synapse Link for Dataverse, and notes that observed freshness can exceed the chosen interval depending on compute pool size and incremental data volume. Some kernel tables refresh every 24 hours instead.

None of this is a defect. Near real-time describes a well-built analytical estate honestly, and for most decisions it suffices. What matters is that each consolidated measure carries a stated "as of", and that the business accepts the window before anyone builds on it. Executives lose confidence in a dashboard when its currency surprises them, not when it lags.

What Should Stay in the Ledger

Consolidation is not a directive to move everything, and one category should stay where it is.

Statutory financial statements belong in the ledger's own reporting. Dynamics 365 Finance ships financial reporting as an add-in, documented as letting financial professionals create, maintain, deploy and view financial statements, with dimension support available immediately after installation. Its reporting tree definitions follow the dimensional relationships already present in the financial data, and twenty-two default reports cover income statement, balance sheet, cash flow and trial balance.

Rebuilding that estate in Power BI costs real money, complicates the audit conversation, and solves a problem the platform already handles. Power BI earns its place on the analytical side: cross-system views, operational monitoring, and the questions the ledger alone cannot answer.

How People Know Which Report to Trust

Publishing a good report does not make anyone use it. A user facing nine dashboards with similar names has no way to tell which one the company stands behind, so they keep their spreadsheet.

Power BI and Microsoft Fabric carry a documented endorsement mechanism for exactly this. Microsoft describes the Promoted badge as the creators considering an item ready for sharing and reuse, applicable by any user with write permissions. Certified goes further: an organization-authorized reviewer confirms the item meets the organization's quality standards and counts as reliable and authoritative, and only users a Fabric administrator specifies can apply it. A Master data badge marks an item as the authoritative source for core organizational data such as product codes or customer lists.

Most estates never turn this on. Decide who certifies, what the bar is, and how often someone revisits it. Then give the business one rule: if it is not certified, do not run a decision on it.

Why Reports Keep Changing in Production

People edit reports in production because nobody built anywhere else to edit them.

Microsoft's deployment pipelines exist for this. They move content through development, test and production stages, letting creators develop and test in the service before it reaches users.

Set this up before the first certified report goes live. Retrofitting a lifecycle onto a live estate takes considerably longer than starting with one.

The Three Tests That Turn a Report Into a Decision

A number earns a place on a decision dashboard when three things hold true.

• Someone owns it. A role, not a distribution list.
• A threshold exists. A value agreed in advance separates normal from not normal.
• An action follows. Crossing the threshold triggers something specific, done by the owner.

Numbers that fail all three are reference material. Keep them, but keep them away from the page where people make decisions, because their main effect there is to dilute the numbers that matter.

DAX Software Solutions: From Reports to Decisions

DAX works with organizations consolidating fragmented reporting onto Power BI and the wider Microsoft data platform. That work starts with the measures and the decisions they support, because a migration skipping this step reproduces the original disagreement in a newer tool.

DAX helps clients:

• Define the measures an organization runs on, each with an owner, a source of record and a stated refresh window.
• Build shared Power BI semantic models and reporting on Dynamics 365 Finance, Supply Chain Management and Business Central data.
• Connect ERP, CRM and operational systems, including through the Aonflow integration platform, for near real-time analytical data.
• Establish endorsement, security and deployment practices so people know which report carries authority.
• Assess readiness before introducing automation or AI into decisions that rest on unsettled measures.

Consolidating reporting onto Power BI is worth doing. It just does not, by itself, decide which number is right. Somebody still has to, and doing that first turns reports into decisions.

The post From Reports to Decisions: Consolidating Reporting onto Power BI appeared first on ERP Software Blog.

Panama gives smaller taxpayers a free invoicing tool, and for years many companies leaned on it instead of a full integration. Starting January 1, 2026, though, that free tool comes with strict limits. Companies running Business Central Panama above those limits now need a real PAC integration, not a workaround.
That shift makes this a good moment to understand how Panama's model actually works.

How the Panama Electronic Invoicing Model Works

Under the Sistema de Factura Electrónica de Panamá (SFEP), every invoice is generated as XML, digitally signed, and sent for validation through a Proveedor Autorizado Calificado (PAC) — or, for qualifying small taxpayers, through the Dirección General de Ingresos (DGI)'s free tool. Once validated, the document receives a CUFE (Código Único de Factura Electrónica) and an authorization, and the buyer gets a CAFE (Comprobante Auxiliar de Factura Electrónica) — the human-readable version carrying the CUFE and a QR code. The PAC then transmits the authorized document to the DGI within a set window, typically 48 hours.

Why the Free Tool's New Limits Matter

As of January 2026, the DGI's free facturador is limited to taxpayers billing up to B/.36,000 annually and issuing no more than 100 documents a month. Cross either threshold, and the company must migrate to a PAC or build its own DGI-certified integration. For a growing business, that migration point can arrive faster than expected.

Where This Shows Up in Business Central Panama Projects

For implementation teams, a few configuration points recur:

• Confirming whether the taxpayer qualifies for the free tool or needs a PAC integration
• Maintaining the electronic signature certificate issued by the Dirección Nacional de Firma Electrónica
• Generating the CAFE with its QR code for delivery to buyers
• Transmitting authorized documents to the DGI within the PAC's required window
• Archiving electronic documents for the minimum five-year retention period
• Handling the transition cleanly when a company crosses from the free tool into a PAC mid-year

Common Challenges in Panama Implementations

Most issues we see come from a handful of recurring gaps:

• Staying on the free facturador past the new volume or revenue limits without noticing
• Double-entering data between a standalone facturador and the core business system
• Missing the PAC's specific technical requirements during migration
• Failing to reconcile CUFE and CAFE records with sales and inventory when the process isn't automated
• Underestimating how quickly a growing business crosses the free tool's thresholds

Each one is manageable in isolation, but together they add real operational drag as transaction volume grows — exactly the growth a successful Business Central rollout is usually meant to support.

Why a Dedicated Localization Matters for Business Central Panama

A proper Panama localization generates invoices directly from the sale, integrates with a certified PAC, and produces the CAFE automatically — no re-keying data into a separate facturador. Built as an extension, it does this without changing Business Central's core, and it keeps working as the company grows past the free tool's limits without a disruptive mid-year migration.

How LLB Solutions Supports Business Central Panama

LLB Solutions' Panama Localization for Microsoft Dynamics 365 Business Central covers DGI electronic invoicing through certified PAC integration, tax reporting, and detailed fiscal information — built as an AppSource-certified extension. For companies approaching the free tool's new limits, the localization is designed to make that migration a configuration change rather than a system replacement.

Panama's 2026 changes push more companies out of the free facturador and into a real PAC integration. Rather than treating that migration as a scramble, companies that plan the transition into their Business Central Panama environment early keep invoicing running without interruption.
For Microsoft partners, this is also a natural moment to check in with clients who set up Panama invoicing years ago on the free tool and may not realize the limits have changed.
See how LLB Solutions' Panama Localization fits your Business Central project — Contact LLB Solutions

The post Business Central Panama: The 2026 Shift from Free Invoicing to PAC appeared first on ERP Software Blog.

Listen to the Podcast

RFID belongs in a Microsoft Dynamics 365 Business Central warehouse when you receive pallets that arrive already tagged, count inventory in open space, or track large assets across a yard. It does not belong in dense piece picking, around metal or liquid, or anywhere a worker needs to confirm the exact item in hand. Barcodes still win those jobs, and the two work well together.
This article explains why, in enough depth that you can make the call for your own operation instead of taking a vendor's word for it.

How does passive RFID actually work?

A passive RFID tag has no battery. It is a small microchip bonded to a thin metal antenna and sealed inside a paper label. When a reader sends out a radio signal, the tag's antenna captures a small fraction of that energy, converts it to enough current to wake the chip, broadcasts the chip's data, and goes dormant again. Think of it as a solar panel that harvests radio waves instead of light.
That single fact explains most of RFID's strengths and most of its failures. The tag answers whenever enough energy reaches it, whether or not anyone is pointing at it. That is what makes bulk reads possible, and it is also what makes stray reads inevitable.

Serial numbers vs EPC data

Every tag carries a factory-burned serial number that is unique in the world. On its own, that number is like an unassigned license plate: unique, but meaningless until someone maps it to a specific item in the ERP. Building and maintaining that cross-reference is an administrative chore.
The more useful tier is EPC data, the Electronic Product Code defined in the GS1 EPC Tag Data Standard. An EPC-encoded tag carries the equivalent of the product's GS1 identifier plus attributes such as lot number, expiration date, or weight. When the reader wakes it, the tag announces its complete identity, and the ERP needs no lookup table.
Encoding your own EPC tags is not the same as printing a shipping label. It requires RFID-capable printers, specific thermal label stock, and staff who can troubleshoot a misaligned encoding head. The best case for any warehouse is a supplier who ships product already tagged with full EPC data. If your vendors do not, the encoding burden is yours, and it should be counted as part of the cost of integration.

What does an RFID reader deployment involve?

There are two hardware paths, and they differ far more in scope than in price.
Mobile readers are handheld devices or sleds that hold a smartphone. A worker uses one much like a barcode scanner: walk up, hold the trigger, sweep the area. They need no facility changes and suit receiving and inventory counting well.
Fixed readers are antenna portals mounted at choke points such as dock doors or the passage between receiving and storage. A forklift drives through, and the portal registers everything on the pallet with no trigger pull. That is the frictionless data capture RFID is sold on, and it is real. It is also never one project. A fixed portal is three:

1. Construction. Heavy equipment bolted to industrial walls, dedicated power, and steel conduit to protect cabling from forklift strikes.
2. Networking. Each reader securely connected to your internal systems.
3. Middleware. A portal reading a hundred tags may capture each of them many times per second. Business Central cannot consume raw radio pings. Something has to deduplicate them, work out direction of travel, and hand the ERP a clean statement such as "these 100 items moved from receiving to zone A."

The middleware layer is where fixed-reader projects most often stall, because nobody budgeted for it. If you are evaluating fixed portals, ask who owns that layer before you ask what the antennas cost.

Where does RFID earn its place?

RFID's defining advantage is the bulk read. Hold a trigger for a couple of seconds and register dozens of items at once, with no line of sight, including tags sealed inside cartons in the middle of a shrink-wrapped pallet. As long as the radio energy reaches the tag, it answers.
That advantage pays off in a specific set of jobs:

• Bulk receiving of pre-tagged product. A uniform pallet from a supplier who encodes EPC data can be received in seconds rather than carton by carton.
• Inventory counts in open storage. Sweeping a reader through a bay is faster than scanning each label, provided the products themselves do not block the signal (more on that below).
• Asset tracking in spacious layouts. Locating cable spools or equipment spread across an outdoor yard, where items sit far enough apart that every read is unambiguous.
• Loss prevention at exits. A tagged carton passing a dock portal without a matching shipment can trip an alert immediately.

Notice what these have in common: items that are either physically separated or meant to be read as a group. RFID is at its best when "everything in range" is exactly what you want to know.

Where does RFID fail?

The same physics that enables the bulk read causes three failure modes. None of them can be fixed with better software.

Stray reads in piece picking

Depending on reader power and tag antenna size, a handheld can pick up tags from several meters away. In the Inside Insights episode on this topic, the hosts put that range at 20 to 30 feet. In a narrow picking aisle, that means the scanner may confirm the bottle you need while actually reading a tag two aisles over. There is no laser dot on a label, so there is no physical proof that the item in your hand is the item the system recorded.
The obvious fix is to turn the reader power down. It works, and it destroys the business case. Once the read range drops to a few feet, the worker has to walk up to every item anyway. You are now scanning at barcode speed with hardware and consumables that cost far more.

Metal reflects the signal

Radio energy does not cooperate with density. Metal acts as a chaotic reflector, bouncing the signal unpredictably and creating dead zones where waves cancel each other out. A tightly bundled pallet of pipe is the classic example: the reader energizes the tags on the outside of the bundle and never reaches the ones in the center.

Liquid absorbs it

Water absorbs radio frequency energy at the molecular level, the same principle a microwave oven uses. A pallet of eggs, beverages, or anything else that is mostly water swallows the signal before it reaches the inner tags. The outer cartons read and the pallet count comes up short, every time.
If your product mix is heavy in metal or liquid, or if most of your labor is spent picking individual units from crowded shelving, RFID will underperform no matter how well the integration is built.

How do modern barcode processes close the gap?

The usual argument for RFID is speed. Barcode workflows have evolved to answer that argument while keeping the one thing RFID cannot offer: physical verification of the item being scanned.

License plating deserves a closer look because it solves the mixed-pallet problem RFID is often bought for. When a worker scans the wrong item onto a plate, the system rejects it on the spot rather than three days later when the customer opens the box. Insight Works publishes an app for this workflow; the License Plating app page describes how mixed items are tracked across containers with a single license plate number.

Should you integrate RFID with Business Central? A decision checklist

Work through these in order. The first "no" is usually the answer.

1. Do your suppliers ship product already encoded with EPC data? If not, you own the encoding printers, label stock, and training. Factor that in before anything else.
2. Is the job a bulk read or a targeted read? Receiving a uniform pallet, counting a bay, or locating assets is bulk. Picking one unit for one order is targeted, and RFID is the wrong tool for it.
3. What is the product made of? Significant metal or liquid content in the load means inner tags will not read reliably.
4. How dense is the storage? Items in open space read cleanly. Items packed on shelving in narrow aisles produce stray reads.
5. Mobile or fixed readers? Mobile readers deploy quickly and need no construction. Fixed portals require construction, networking, and middleware, and someone must own all three.
6. Where is the bottleneck today? A slow receiving dock and a picking accuracy problem call for different technologies. Diagnose first, then select.

A useful summary from the podcast episode: never lead with the technology. Do not buy an RFID system and then walk the floor looking for a problem it solves.

How does Warehouse Insight handle RFID and barcodes together?

The practical answer for most Business Central warehouses is not RFID or barcodes. It is RFID at the dock and barcodes in the aisles, on the same devices and in the same app.
Warehouse Insight supports RFID alongside 1D and 2D barcode scanning, and the RFID scanning page for Business Central describes how the RFID side works. Workers hold down a trigger on an RFID-capable Android device, built in or via an attached sled, and the reader captures every tagged item in range. Tags encoded with GS1 data are resolved through the GS1 barcode rules already configured in Business Central, so no separate item mapping is needed. Tags without GS1 data are matched through a one-time cross-reference. Reads are deduplicated automatically, so a tag captured several times counts once.
RFID is available in three Warehouse Insight workflows: receiving against purchase orders, inventory counting, and shipping. Serial number capture during receiving or counting is configurable. The same page is candid about the physical limits covered above: performance depends on tag placement, reader range, and product density, and palletized shipments read better than densely staged mixed orders.
That candor is the point. The right design uses RFID where physics favours it and barcodes where certainty matters, without forcing either technology to do a job it was not built for. Microsoft's own warehouse management overview for Business Central describes the receiving, put-away, pick, and shipping activities these scans feed into.

Frequently asked questions

Does RFID replace barcodes in a warehouse?

No. RFID suits bulk reads of pre-tagged, well-spaced product. Barcodes suit targeted reads where the worker must confirm the exact item. Most operations that use RFID successfully use both.

Why does my RFID reader miss items in the middle of a pallet?

Metal reflects the radio signal and liquid absorbs it. Either one prevents enough energy from reaching tags at the center of a dense load. Restacking or reorienting the load can help; changing the software cannot.

Can I reduce stray reads by lowering reader power?

Yes, but doing so removes the range advantage that justified RFID. At short range you are scanning at barcode speed with more expensive equipment.

Do I need fixed reader portals to use RFID with Business Central?

No. Warehouse Insight's RFID support runs on RFID-capable Android handhelds or sleds. Fixed portals add construction, networking, and middleware work and are a separate decision.

What is EPC data and why does it matter?

EPC is the GS1 Electronic Product Code. A tag encoded with EPC data identifies the product and its attributes directly, so the system does not need a cross-reference table. Tags with only a factory serial number do.

What is the best first step if we are considering RFID?

Identify the specific bottleneck, then check the product mix and storage density against the failure modes above. If the job is bulk receiving of supplier-tagged pallets, RFID is a strong fit. If it is piece picking, start with barcode process improvements instead.

The post RFID in Business Central: When It Pays Off and When Barcodes Win appeared first on ERP Software Blog.

Inventory forecasting software helps businesses estimate how much inventory they are likely to need in the future. It uses past sales, current inventory, demand patterns, lead times, and other business data to predict future requirements.
In simple terms, it helps answer three important questions:
What are we likely to sell? How much stock will we need? When should we replenish it?
These questions become harder to answer as a business grows. A company may start with a few products and a simple Excel sheet. Over time, it may have hundreds or thousands of SKUs, multiple warehouses, different sales channels, and suppliers with different lead times.
At that stage, manual forecasting can become slow and difficult to maintain.
This is where inventory forecasting software becomes useful. Instead of asking employees to collect information from different spreadsheets and systems, the software can bring the data together and create forecasts automatically.
An inventory forecasting solution can also help identify potential stockouts, excess inventory, changing demand patterns, and future replenishment requirements.
That makes inventory forecasting an important part of modern inventory planning.

Good Read: 10 Best Retail Inventory Management Software

Why Do Businesses Need Inventory Forecasting Software?

Poor inventory planning creates problems on both sides.
If a business keeps too much stock, money gets tied up in inventory. Warehousing costs can increase, products may become obsolete, and slow-moving stock can become difficult to sell.
If a business keeps too little stock, it may face stockouts, delayed shipments, lost sales, and unhappy customers.
Inventory forecasting helps businesses find a better balance.
For example, imagine an ecommerce company that sells 500 units of a product every month. Historical data shows that demand usually increases before the holiday season. Without forecasting, the company may continue ordering the usual amount and run out of stock when demand rises.
An inventory forecasting tool can identify that seasonal pattern and alert the business that more stock may be required.
The software does not remove uncertainty. Instead, it gives planners better information to make decisions.

Good Read: 10 Best Vendor Managed Inventory Software Globally

How Does Inventory Forecasting Software Work?

Most inventory forecasting platforms follow a similar process.
The first step is collecting data. The system may pull information from sales orders, inventory records, purchase orders, warehouses, ecommerce stores, ERP systems, and accounting platforms.
The software then analyzes historical demand.
It looks for patterns such as increasing demand, declining demand, seasonal changes, unusual sales spikes, and differences between locations.
After analyzing the data, the system creates a demand forecast.
The next step is where forecasting becomes inventory planning. The software can compare expected demand with current inventory, supplier lead times, safety stock, and open purchase orders.
Suppose the system expects demand of 10,000 units next month. If the business already has 7,000 units available and another 2,000 units are arriving, the actual replenishment requirement is very different from simply ordering 10,000 units.
This is why forecasting and inventory management software works better when forecasting is connected to actual inventory information.
The final output may include expected inventory levels, reorder recommendations, projected stockouts, excess inventory alerts, and suggested purchase quantities.

Good Read: 10 Top Warehouse Inventory Management Systems in 2026

Types of Inventory Forecasting Software

There are several types of forecasting and planning solutions. The right option depends on the size and complexity of the business.

Spreadsheet-Based Inventory Forecasting

Many companies start with Excel because it is familiar, flexible, and inexpensive.
An inventory planner Excel model can include historical sales, expected demand, stock on hand, purchase orders, safety stock, and reorder calculations.
For a small business with a limited product range, this may be enough.
However, problems often appear as the business grows. Data has to be entered manually, different people may use different versions of the spreadsheet, formulas can be changed accidentally, and managing several locations can become difficult.
This is often the point where an inventory planner software solution becomes more practical.

Cloud-Based Inventory Planning Software

Cloud-based inventory planning software is hosted online and accessed through a browser.
Instead of storing planning logic across individual spreadsheets, teams can work from a central system.
Cloud-based platforms are useful for businesses with distributed teams, multiple locations, and large amounts of inventory data. They can also make software updates and system maintenance easier.
For growing companies, a cloud-based inventory planning solution can provide more automation without requiring a large internal IT infrastructure.

Demand and Inventory Planning Software

Demand and inventory planning software connects demand forecasting with inventory decisions.
This is important because knowing future demand is only half the job.
A planner also needs to know whether current stock is sufficient, when new inventory should arrive, and how much should be ordered.
For example, if demand is expected to increase by 20%, the system can help determine whether current inventory and incoming purchase orders are enough to handle that increase.
This is one of the main differences between simple forecasting tools and broader inventory planning platforms.

Inventory Planning and Optimization Software

Inventory planning and optimization software goes beyond basic demand forecasting.
It can help businesses determine the right inventory level for different products and locations.
Instead of simply asking how much demand is expected, the system can consider inventory costs, lead times, service-level targets, demand variability, and supply constraints.
For larger businesses, inventory planning and optimization software can be particularly useful because inventory decisions are often interconnected across multiple warehouses and distribution centers.

Stock Forecasting Software

Stock forecasting software focuses on understanding future inventory positions.
It can show how much stock a business is expected to have in the coming weeks or months based on forecast demand, purchase orders, production, transfers, and current inventory.
This makes stock forecasting software useful for identifying potential shortages early.
For example, if projected inventory drops below the required safety stock in three weeks, the planner has time to take action instead of discovering the problem when the product is already out of stock.

Production Inventory Planning Software

Manufacturing businesses often need more advanced forecasting because inventory is tied to production.
A production inventory planner may need to consider raw materials, work-in-progress, finished goods, production schedules, bills of materials, and supplier lead times.
In this environment, the forecast for finished products can directly affect the amount of raw material that must be purchased.
That makes a production inventory planner an important part of manufacturing planning.

Inventory and Scheduling Software

Some organizations need to coordinate inventory with production or operational schedules.
In these cases, inventory and scheduling software can connect material availability with planned production or operational activities.
This can be helpful when a shortage of one component could delay an entire production process.

Aggregate Planning Software

Aggregate planning software works at a broader level.
Instead of forecasting one SKU at a time, it can help businesses plan demand and capacity across product groups, categories, or business units.
For example, a manufacturer may first forecast total demand for a product family and then use that information to build detailed SKU-level plans.
This is where aggregate planning software can complement detailed inventory forecasting.

Good Read: 10 Top 3PL Warehouse Management Systems

Key Features of Inventory Forecasting Software

The features available in different systems vary, but several capabilities are particularly important.

Demand Forecasting

Demand forecasting is the foundation of an inventory forecasting platform.
A good system should allow businesses to forecast at the level that makes sense for their operation. Some businesses need SKU-level forecasts, while others need forecasts by warehouse, channel, product category, or region.
The more complex the business, the more important forecasting flexibility becomes.

Historical Sales Analysis

Reliable forecasting begins with reliable historical information.
An inventory forecasting system may analyze previous sales, order frequency, returns, product seasonality, and other demand signals.
The system can use these patterns to estimate future demand.
However, businesses should remember that historical data is not automatically perfect. A major promotion, stockout, supply shortage, or unusual event may have affected historical sales.
That is why many systems allow planners to review and adjust forecasts.

Inventory Projections

One of the most useful features is the ability to see future inventory levels.
Inventory projections software can estimate how stock may change over time based on expected demand and supply.
This gives planners a forward-looking view rather than simply showing what is in the warehouse today.
Projected inventory software is especially valuable when suppliers have long lead times.

Safety Stock Planning

Demand is rarely perfectly predictable.
Even when the forecast is accurate, unexpected events can still happen. A supplier may be late, customer demand may increase suddenly, or a shipment may be delayed.
Safety stock provides a buffer.
Modern stock planning software can use demand variability, lead time, service-level targets, and other factors to help determine an appropriate safety-stock level.

Reorder Point Management

A reorder point tells the business when it should consider replenishing a product.
A simple calculation might consider expected demand during supplier lead time plus safety stock.
More advanced systems can continuously adjust replenishment recommendations as demand and supply conditions change.

Multi-Location Planning

Managing inventory across multiple warehouses is much more complicated than managing a single stock location.
A product that is overstocked in one warehouse could be out of stock in another.
An inventory forecasting platform can help compare demand and available inventory across locations and identify where stock should be purchased or transferred.
This is especially important for growing retailers, distributors, and ecommerce businesses.

Inventory Planner Integrations

Inventory planner integrations can have a major impact on the value of a forecasting platform.
A forecasting system needs access to reliable data. It may therefore need to connect with an ERP, WMS, ecommerce platform, accounting system, POS platform, CRM, or procurement system.
For example, an inventory planner Shopify app may bring ecommerce sales and inventory information into a planning environment.
A business using QuickBooks may instead search for an inventory planning solution that works with its accounting setup.
Integration is therefore an important factor when evaluating software.

Inventory Management Software Demand Forecasting Integration

Inventory management software demand forecasting integration is particularly important because forecasts need to reflect actual inventory conditions.
Imagine that demand for a product is expected to be 8,000 units next month.
That number alone does not tell the purchasing team how much to order.
Suppose the business already has 3,000 units in stock and 3,500 units are scheduled to arrive from suppliers.
The actual purchasing requirement may be much smaller.
This is why inventory management software demand forecasting integration is so valuable. It connects demand forecasts to stock levels, purchase orders, incoming supply, and replenishment decisions.
In a well-connected system, the flow looks something like this:
Demand → Forecast → Inventory Position → Replenishment → Purchasing → Warehouse
This creates a more complete planning process.

Inventory Forecasting vs. Inventory Planning

These two concepts are closely related, but they are not exactly the same.
Inventory forecasting estimates what may happen.
Inventory planning decides what the business should do about it.
For example, a forecast may indicate that a company is likely to sell 20,000 units next month.
Inventory planning then looks at available stock, purchase orders, supplier lead times, safety stock, and service-level requirements to determine whether additional inventory should be ordered.
This distinction matters when evaluating the best inventory planning software.
A system that only produces a forecast may not be enough for a business that wants purchasing and replenishment recommendations.

AI in Inventory Forecasting Software

AI and machine learning are becoming increasingly common in inventory planning.
These technologies can analyze large volumes of information and identify patterns that may be difficult to spot manually.
For example, an AI-enabled inventory forecasting tool may detect seasonal demand patterns, changes in sales velocity, product relationships, or unusual demand behavior.
However, AI does not automatically solve forecasting problems.
If inventory records are inaccurate or product information is incomplete, the forecast may still be unreliable.
The strongest systems generally combine automation with human review.
Planners should be able to understand why a forecast changed and make adjustments when they have business information that the system does not know.

Inventory Forecasting Software Cost

The cost of inventory forecasting software can vary significantly.
There is no single standard price because vendors may charge based on users, SKUs, locations, transactions, modules, integrations, or planning complexity.
A small business may use a simple tool for a relatively low monthly cost, while a large enterprise may spend significantly more on software, integration, implementation, and support.
Here is a general planning framework:

These figures are planning ranges, not vendor quotations. Actual pricing can be substantially different.
The biggest cost drivers are usually data volume, integrations, number of locations, number of users, advanced planning functionality, implementation, and support.

Is Inventory Planning Software Free Enough?

Businesses searching for inventory planning software free often want to test forecasting before committing to a paid system.
Free solutions can be useful for learning, basic forecasting, and small product catalogs.
However, free tools commonly have restrictions.
For example, they may limit the number of products, users, integrations, or forecasting features.
A company with hundreds or thousands of SKUs may quickly outgrow an inventory planning software free option.
The important question is not whether the software is free. It is whether it can support the complexity of the business.

Inventory Forecasting Software ROI

The return on investment from forecasting software does not come from one metric alone.
A company may see value through lower excess inventory, fewer stockouts, better working-capital management, faster planning, and reduced manual work.
Suppose better inventory planning helps a company reduce average excess inventory by $200,000 while improving planner productivity and avoiding several stockouts.
The benefit is greater than the software subscription alone.
Businesses evaluating an inventory planning solution should therefore consider the total economic impact rather than only the monthly license price.

How to Choose the Best Inventory Forecasting Software

Choosing the best inventory forecasting software starts with understanding the business problem.
A company with 200 SKUs and one warehouse has very different requirements from a global distributor with 100,000 SKUs and dozens of locations.
Start by looking at forecasting capability.
Can the system forecast demand by SKU, location, category, and sales channel?
Next, look at integrations.
Can the software connect with the ERP, WMS, ecommerce platform, accounting software, and other systems that contain inventory information?
Then evaluate planning capabilities.
Can the platform calculate safety stock, identify replenishment requirements, model future inventory, and flag exceptions?
Usability is equally important.
The best inventory forecasting software is not useful if planners find it difficult to understand or trust.
Finally, evaluate the total cost, including implementation, integration, training, support, and ongoing administration.

Inventory Forecasting Software for Ecommerce

Ecommerce companies often face fast-changing demand.
A product can suddenly become popular because of advertising, social media, a seasonal event, a promotion, or a marketplace trend.
This makes forecasting especially important.
An inventory planner Shopify app, for example, can connect ecommerce sales information with inventory planning processes.
The same principle applies to businesses selling through multiple marketplaces.
For ecommerce companies, forecasting software can help answer questions such as:
"Which products are likely to run out?"
"Which products are becoming slow moving?"
"How much stock should be ordered before the next sales event?"
"Which warehouse should hold the inventory?"
That makes forecasting an important part of ecommerce inventory management.

Inventory Planning and Demand Planning Accuracy

Businesses often search for the best inventory software for demand planning accuracy.
Accuracy certainly matters, but it should not be viewed in isolation.
Suppose a forecast is 95% accurate, but the business does not have the supplier capacity needed to meet the forecast.
The forecast is accurate, but the inventory plan can still fail.
Similarly, a highly accurate forecast may not create business value if stock is positioned in the wrong warehouse.
This is why effective inventory planning considers forecasting accuracy together with supply constraints, lead times, service levels, and inventory costs.

Inventory Planning Software for Enterprise Businesses

Enterprise companies usually have more complex requirements.
They may have thousands of products, multiple warehouses, regional demand patterns, different suppliers, and large planning teams.
For these businesses, an enterprise inventory planner may need to support advanced forecasting, scenario planning, multiple locations, workflows, reporting, and ERP integration.
Organizations searching for the best enterprise inventory planner alternative for large inventory teams should look beyond individual features and evaluate the complete planning process.
Questions around scalability, implementation, integration, governance, data volume, and total cost become particularly important.

Inventory Planner Software and Human Planners

Automation does not mean that businesses no longer need planners.
A human inventory planner still brings important business knowledge to the process.
For example, a planner may know that a major customer is preparing for a product launch, a supplier is experiencing production issues, or a promotion will increase demand next month.
Software may not have that information unless it is connected to the right data sources.
This explains why businesses continue to hire roles such as assistant inventory planner, inventory planner, and supply-chain analysts.
An inventory planner job description may include forecasting, replenishment, supplier coordination, inventory analysis, and reporting.
The required inventory planner skills often include data analysis, supply-chain knowledge, ERP experience, spreadsheet skills, communication, and problem-solving.

Inventory Planner Salary vs. Software Cost

Searches such as inventory planner salary and inventory planning salary reflect another side of the same discussion.
Companies may compare the cost of manual planning with the cost of automation.
However, salary varies significantly by location, experience, industry, and employer.
For that reason, specific queries such as inventory planner salary Coca Cola or inventory planner salary San Francisco should not be treated as universal benchmarks.
The bigger business question is whether technology can help a planning team handle more inventory with greater visibility and less repetitive work.

Inventory Forecasting for Global Operations

Global businesses often need more sophisticated inventory planning.
An inventory planning software EMEA deployment, for example, may have to deal with regional demand patterns, different supply routes, distribution centers, currencies, and service-level requirements.
Global planning can become complicated when different regions use different systems.
A centralized inventory planning software EMEA strategy can therefore help create a more consistent planning process while still allowing regional teams to manage local requirements.

Common Inventory Forecasting Mistakes

One of the most common mistakes is relying entirely on historical sales.
Historical data is valuable, but it does not always represent future conditions.
A new product launch, major promotion, supplier disruption, price change, or market event can change demand quickly.
Another common mistake is choosing software based only on the number of features.
A system can have dozens of capabilities and still fail to solve the actual business problem.
Companies should also avoid comparing only subscription prices.
Implementation, integration, data migration, training, support, and internal resources can all affect the real cost.
Finally, businesses should not ignore user adoption.
A forecasting system needs planners and managers to trust the information and use it in their daily decisions.

What Should an Inventory Forecasting Dashboard Show?

A useful dashboard should provide a clear picture of both demand and inventory.
For example:

The dashboard should also allow users to move from summary information to SKU-level details.
That way, managers can see the overall picture while planners can investigate individual products.

10 Frequently Asked Questions About Inventory Forecasting Software

1. What is inventory forecasting software used for?

Inventory forecasting software is used to estimate future demand and understand future inventory requirements. It can help businesses plan purchases, maintain safety stock, identify stockout risks, reduce excess inventory, and improve replenishment decisions.
An inventory forecasting solution can also automate calculations that would otherwise require manual spreadsheet work.

2. How does inventory forecasting software calculate demand?

Different systems use different forecasting methods.
Some rely mainly on historical sales trends. More advanced systems may consider seasonality, demand variability, product relationships, promotions, inventory availability, and other signals.
AI and machine learning can also be used to identify patterns in large datasets.

3. What is the difference between inventory forecasting and demand forecasting?

Demand forecasting estimates future customer demand.
Inventory forecasting focuses on what that demand means for inventory requirements.
The two are closely related, but inventory forecasting usually considers additional information such as current stock, incoming purchase orders, lead times, and safety stock.

4. What features should I look for in inventory forecasting software?

Look for forecasting, inventory projections, safety-stock planning, reorder point management, multi-location support, exception alerts, reporting, integrations, and scenario planning.
If the business is large or complex, advanced inventory planning and optimization software may also be appropriate.

5. How much does inventory forecasting software cost?

There is no fixed price.
Some tools are free or low-cost, while advanced enterprise platforms can cost thousands of dollars per month plus implementation fees.
Pricing often depends on users, SKUs, locations, integrations, transaction volume, and modules.

6. Can inventory forecasting software replace an inventory planner?

Usually, software and people serve different roles.
An inventory planner provides judgment, business context, supplier knowledge, and strategic decisions.
The software automates calculations, collects data, produces forecasts, and identifies exceptions.
For many organizations, the most effective model is a combination of technology and human expertise.

7. Can inventory forecasting software integrate with Shopify?

Many inventory platforms offer ecommerce integrations, including connections with Shopify.
An inventory planner Shopify app can potentially bring sales and inventory information into a centralized planning process.
The exact integration capabilities should be checked before purchasing because different platforms support different data types and synchronization methods.

8. Can inventory planning software work with QuickBooks?

Some inventory planning platforms integrate with QuickBooks or work alongside accounting systems.
Companies researching what's the best inventory planner alternative that integrates with quickbooks should look at more than basic connectivity.
They should check whether the integration supports inventory, products, sales, purchasing, and synchronization requirements.

9. Is free inventory planning software suitable for small businesses?

It can be.
Businesses with a small number of SKUs and simple inventory requirements may find an inventory planning software free option useful for basic forecasting.
However, as the business adds products, warehouses, users, or integrations, a paid system may become more suitable.

10. What is the best inventory forecasting software?

There is no single platform that is best for every business.
The right solution depends on the organization's product count, locations, planning process, integrations, industry, budget, and level of forecasting complexity.
The better approach is to compare software based on real business requirements and test the system with actual inventory and sales data.

Final Thoughts

Inventory forecasting is about more than predicting future sales.
It is about using those predictions to make better inventory decisions.
The right inventory forecasting software can help a business understand future demand, identify stock risks, improve replenishment, manage safety stock, and reduce unnecessary inventory.
For a small company, an Excel-based inventory planner Excel model may still be sufficient. A growing business may need cloud-based inventory planning software, while a larger organization may require advanced inventory planning and optimization software connected to ERP, WMS, ecommerce, and procurement systems.
The most useful solution is the one that fits the way your business actually operates.
A good system should make it easier to answer three simple questions:
What are customers likely to need?
How much inventory should we keep?
When should we replenish it?
When software can answer these questions using reliable data and turn them into practical actions, inventory forecasting becomes a valuable part of the overall supply-chain strategy.

The post Inventory Forecasting Software: Types, Features and Cost appeared first on ERP Software Blog.

Fractional D365 support gives manufacturers senior expertise on their side of the table, for exactly as many hours as the situation needs.

Go-live day feels like the finish line. In manufacturing, it is usually the start of the most important stretch of the whole project.

The first few months after go-live are when production, warehouse, and finance run on the new system for real. It is also when the implementation partner starts scaling back, and when your internal team is still learning how everything fits together.

This blog is for the IT leader at a manufacturing company who is recently live on D365, or about to be, and wants a plan for what comes next. It covers what fractional support looks like, the two moments manufacturers use it most, and a real example from one of our clients.

What fractional D365 support means

Fractional D365 support is a senior independent contractor who works for you part-time, on a set number of hours per week or days per month.

They sit on the client side. That means they work only in your interests, alongside your internal team and, where it is still involved, your implementation partner.

The hours flex with the situation. A few days a month is common once things are stable. A few days a week is common when something needs fixing quickly.

The two moments manufacturers bring in fractional support

1. When go-live has been rough

Sometimes the first weeks on D365 bring production delays, shipping problems, or inventory that does not match what is on the shelf. Your partner is working the issue list, but you need someone on your side who can:

• • Separate configuration issues from process issues

• • Tell you which problems the partner should fix and which your team can own

• • Bring calm to a stressed operation so people can focus

2. When the partner rolls off

Implementation partners are built to deliver projects. Once the statement of work is complete, their senior people move on to the next implementation.

Your team then owns a system they did not fully build. A fractional contractor who knows D365 manufacturing inside out keeps that knowledge in the building. Many of the manufacturers we work with keep a senior contractor on a few days a month for years, purely for continuity. That tribal knowledge is priceless.

For a practical plan of what to improve once you are stable, see the D365 F&O post go-live optimization roadmap.

Our D365Contractors.com community exists to serve D365 ERP customers who want to beef up their internal capability and drive projects forward internally. Chat with us today about our vetted consultants who are ready to jump in and help:

A real example: getting a Midwest manufacturer shipping again

One of our clients is a discrete manufacturer in the US Midwest. A few weeks after going live on D365 Finance & Operations, operations had stalled.

Very little was shipping. Revenue had dropped by more than a third, and the cost to the business was running into millions of dollars. Everyone in the building felt the pressure.

The client needed someone on their side of the table, fast. We placed an independent D365 contractor with deep production and operations experience, working directly for the client at around 25 hours a week on a six-month engagement. Which turned into over 12 months (so far).

Their first job was bringing some calm to the situation. From there, the work focused on three things:

• • Pinpointing the configuration fixes. They identified exactly where the setup needed correcting, so the implementation partner could come back and fix it with a clear, specific list.

• • Improving internal processes. They highlighted operational changes the client's own team could make, so issues were handled better in-house.

• • Getting product out the door. With both workstreams moving, the plant started shipping again.

The part I like most about this story is how the work was split. The partner fixed what the partner needed to fix. The client's team got stronger. And one senior person on the client side made sure both happened at the same time.

What a good fractional D365 contractor does first

Whether you are stabilizing or planning for the long term, the first few weeks usually follow the same pattern:

• • Listen first. Walk the plant floor, sit with planners and warehouse leads, and understand how the business actually runs.

• • Triage the issue list. Sort every open item into partner fixes, internal process fixes, and training gaps.

• • Protect revenue first. Focus on whatever is stopping production or shipping before anything else.

• • Build internal capability. Leave your team more confident each week, so they depend less on outside help over time.

That last point matters. The goal of fractional support is a stronger internal team. For a structured way to assess yours, see how to build your internal D365 ERP team.

How many hours do you actually need?

It depends on where you are.

• • Stabilizing after a rough go-live: typically 20 to 40 hours a week for a few months, often with some onsite time at the start.

• • Steady state after the partner rolls off: typically a few days a month, scaling up around enhancements, new sites, or year-end.

The right contractor will tell you honestly when it is time to scale back.

Frequently asked questions

What is fractional D365 support?

Fractional D365 support is a senior independent Dynamics 365 contractor who works for your company part-time, on a set number of hours per week or days per month. They work on the client side, alongside your internal team and implementation partner.

Can a fractional contractor work alongside our implementation partner?

Yes, and this is one of the most common setups. The contractor gives you independent oversight, helps prioritize the partner's fix list, and makes sure issues are resolved in a way that suits how your plants actually operate.

When should a manufacturer bring in fractional support?

The two most common moments are a difficult go-live, when you need senior help on your side quickly, and the point where your implementation partner rolls off, when you need continuity and ongoing expertise.

Can we scale fractional support up and down?

Yes. Most engagements start with more hours during stabilization and drop to a few days a month once things are running smoothly. You engage for as long as you need.

Find the right D365 specialist for your plant

The right fractional contractor has already run D365 in a real production environment and knows what "normal" looks like on the plant floor.

Our guide to how manufacturers hire D365 manufacturing contractors covers the modules, roles, vetting, and pricing in one place.

If you are recently live on D365 and need someone in your corner, or your partner is about to roll off and you want continuity, we can help. We typically present two or three vetted matches within 48 hours:

About the Author

Ryan Carolan is the founder of D365Contractors.com, connecting North American companies with pre-vetted, independent D365 experts. 14 years exclusively in D365 staffing. Hundreds of contractor placements into implementations across the US.

Most weeks, he waffles on about stuff like this online.

Follow Ryan on LinkedIn →

The post Fractional D365 Support for Manufacturers After Go-Live appeared first on ERP Software Blog.

El Salvador's electronic invoicing model has one detail that surprises teams coming from Mexico, Colombia, or Peru. The documents aren't XML. Instead, they're JSON. For companies rolling out Business Central El Salvador, that choice ripples into how teams build, validate, and deliver documents. It also affects the schema tooling they use and how they parse errors.
Beyond the format, however, the underlying logic follows a familiar LATAM pattern: generate, sign, transmit, validate.

How DTE Validation Works in El Salvador

Every invoice, credit note, or other tax document becomes a Documento Tributario Electrónico (DTE), built in JSON and digitally signed with a certificate issued by the Dirección General de Impuestos Internos (DGII), part of the Ministerio de Hacienda. The signed DTE is transmitted for validation, and once approved, the DTE receives a Sello de Recepción — a UUID-based stamp that confirms the document was received and is legally valid. Without that stamp, the document carries no fiscal weight, no matter how correctly it was built.

What Happens When Transmission Fails

El Salvador's regulation includes formal contingency rules for when normal transmission isn't possible. Documents can be issued to the buyer without a Sello de Recepción during the outage, but the issuer must transmit the full contingency batch within 72 hours once service is restored. Skipping that step means the documents never gain full tax validity — and the buyer can't use them to support a tax credit until they do.

Where This Shows Up in Business Central El Salvador Projects

For implementation teams, a handful of configuration points recur:

• Generating DTEs in the correct JSON schema for each document type
• Maintaining a valid, renewed DGII signing certificate
• Registering the correct establishment and point-of-sale codes assigned by Hacienda
• Handling contingency transmission within the required window
• Supporting the different DTE types — invoices, fiscal credit documents, export invoices, and excluded-subject invoices
• Meeting the differentiated invalidation deadlines that now apply depending on document type

Common Challenges in El Salvador Implementations

In practice, most issues come down to a few recurring gaps:

• Using unregistered establishment or point-of-sale codes, which triggers automatic rejection
• Missing the field-naming conventions Hacienda's updated normativa now requires exactly
• Letting the signing certificate lapse without a renewal process in place
• Delivering a rejected DTE to a customer, which the regulation treats as a direct infraction
• Reusing invalidation windows meant for one document type on another, since deadlines now differ by type

Each of these is avoidable with the right configuration — but expensive to fix retroactively once documents are already in the field, since a rejected or invalidated DTE can mean re-issuing the transaction entirely.

Why a Dedicated Localization Matters for Business Central El Salvador

A proper El Salvador localization automates DTE generation in the correct JSON structure, manages the signing and transmission cycle, and handles contingency scenarios automatically. Built as an extension, it does this without touching Business Central's core, keeping future upgrades simple. It also tracks Hacienda's periodic normativa updates, so a schema change doesn't surface as a wave of rejected documents.

How LLB Solutions Supports Business Central El Salvador

LLB Solutions' El Salvador Localization for Microsoft Dynamics 365 Business Central covers DTE generation, ISR and VAT withholdings, and fiscal reporting — built as an AppSource-certified extension integrated with a DGII-recognized provider. The localization also keeps pace with Hacienda's periodic catalog and normativa updates, so a schema revision doesn't turn into a wave of rejected documents.

El Salvador's DTE model is stable, but its JSON-based format and formal contingency rules are different enough from neighboring countries that assumptions carried over from another LATAM project rarely hold. Companies that plan for the format and the certificate lifecycle from day one avoid the compliance gaps that come from treating it as "just another XML invoice."
For Microsoft partners moving between Mexico, Guatemala, and El Salvador projects, that format switch is worth flagging early — it's an easy assumption to carry over by mistake.
See how LLB Solutions' El Salvador Localization fits your Business Central project — Contact LLB Solutions

The post Business Central El Salvador: How DTE Validation Really Works appeared first on ERP Software Blog.

If your ERP still lives on a server in the corner of your IT room, you're not alone. But you may be falling further behind every quarter.

The post Is Your Manufacturing ERP Holding You Back? The Case for Going Cloud-Native appeared first on ERP Software Blog.

Introduction - Traditional Control Towers Provide Problem Visibility But No Solution

Supply chain control towers give complete visibility into your supply chains. You can see delayed shipments, demand fluctuations, inventory levels, and operational disruptions. So, they solve the visibility problem.
But do these towers also fix the problems they identify?
No. Because they were never built to do that.
Then, what solves it?
Agentic AI supply chains are the best bet, where AI agents execute the next course of action. They send emails, make calls, forward for approvals, or anything else. These AI agents understand the context, decide the action, and execute within approved guardrails.
Control towers help manufacturers identify problems, but involve manual decisions and actions that cause delays or inaccuracies. Agentic supply chains let manufacturers see, understand, decide, and act proactively to ensure efficiency and productivity.
This article looks at the limitations of traditional control towers and how agentic AI supply chain management closes that gap.

Limits of Traditional Supply Chain Control Towers

A manufacturing supply chain control tower provides end-to-end supply chain visibility. It serves as a single interface collating data from inventory, logistics, sourcing, and supplier performance to facilitate visibility and cross-functional collaboration. But it lacks the following:

Proactiveness

Control towers provide visibility into ‘what is happening’ but don’t tell ‘what will happen next’. They can’t identify disruptions before the damage begins. So, they are reactive by design.
Dynamic operations need predictive intelligence, including disruption forecasts, operational simulations, response optimization, and impact modelling, which towers lack.

Intelligent Decision-making And Execution

Control towers do not provide resolutions. A problem is visible - stockouts, supplier price rises, delayed shipments, or blocked production. But who is responsible, what’s the impact, and what options are available – these require human input.
Teams own decisions and actions, but under time pressure, prioritization, quality decisions, and appropriate action can stall.

Real-time Coordination

A supply chain tower provides a centralized dashboard, combining data from ERPs, logistics platforms, procurement tools, customer service solutions, and warehousing systems. Data reconciliation from multiple sources happens manually, resulting in a single view. This means you cannot trace accountability, respond on time, or decide collaboratively.
Such siloed systems lead to siloed decisions without real-time coordination and decision orchestration.

Scalability

Businesses are getting more complex day-by-day. Every new customer trend, regulation, and compliance requirement is a new exception, responding to which requires a model change or more human learning.
After visibility, you need human-led decision-making, which requires identification, understanding, prediction, and collaboration that can’t happen at the same rate as the changes. So, you see more noise, but action is still slow.
Thus, manufacturing supply chain control towers solve the visibility issue. But decision-making and action still require human intervention.

What is Agentic AI in Supply Chain Management?

Agentic AI in supply chain management means AI agents facilitate data understanding, reasoning, decision-making, and action execution across workflows.
It is A + A + A (automation + advanced analytics + action).
Not just rule adherence. It evaluates context, considers competing options, acts intelligently, learns from outcomes, and improves continuously to stay aligned with evolving business goals.

What Are the Benefits of an Agentic Supply Chain?

• Agents coordinate activities across planning, logistics, production, procurement, and customer service departments, resulting in end-to-end supply chain visibility.
• AI agents analyze structured and unstructured data across your systems and applications to decide and act quickly, enhancing decision quality and speed.
• Automating routine decisions and consolidating data across functions optimizes operations, leading to high efficiency and reduced operational costs.
• Agents respond immediately to disruptions, new opportunities, evolving trends, and changing customer demands, ensuring risk management and resilience.
• Humans define limits for AI agents’ operations; agents escalate a decision to a human only when critical or outside their authority.

Thus, real-time decision-making and execution allow agentic AI supply chains to take proactive action – a step succeeding insight generation. That is why Gartner predicts that advancements in AI and agentic AI will resolve 60% of supply chain disruptions by 2031.

The Shift From Control Tower to Agentic AI Supply Chain

Adopting agentic AI in the supply chains doesn’t mean control towers cease to exist. Now, they become agentic supply chain control towers, with the features of:

• Visibility from control towers
• Decision, action, automation, coordination, and response from AI
• The shift is in the way supply chains operate:
• Instead of just monitoring and flagging issues, they shift to orchestration and autonomous responses and actions.
• Instead of centralized decisions, AI agents’ functional operations lead to simultaneous distributed intelligence.
• Instead of planning in fixed cycles, real-time insights and simulations enable continuous plan adaptations to evolving business conditions.
• Instead of humans weighing in on every decision, AI agents escalate a problem only when confidence is low or human judgment is truly needed.

Control towers show problems. Agentic manufacturing supply chains think of or generate solutions.

The Microsoft Blueprint for Agentic Supply Chain

Microsoft ecosystem enables a strong foundation with a connected architecture, where data, intelligence, and execution work together. It includes:

Dynamics 365 Supply Chain Management: The Execution Backbone

It enables:

• Purchase order updates, approvals, and confirmations
• Supplier communications
• Inventory updates and adjustments
• Production planning
• Coordination between teams

Microsoft Fabric: The Data Foundation

It creates a unified data foundation, connecting data from ERP, SCM, IoT tools, and external sources. So, procurement, production, logistics, and customer service departments work with the same real-time data picture.

Copilot Studio and Power Platform: The AI Agent Layer

This is where actual decision-making happens. This layer lets you build and deploy custom AI agents that execute workflows based on business logic, rules, and interactions with other applications.

The Intelligence Layer: The Decision-Making Unit

Fabric’s built-in AI and analytics capabilities provide contextual awareness, create summaries, and generate insights that support intelligent, proactive decision-making.
Thus, data, execution, decision, and intelligence help create a closed loop within Microsoft.

Use Cases of Agentic AI in Supply Chain

Agentic supply chain intelligence is evident in real-world scenarios, such as the following:

Logistics and Route Management

AI agents evaluate data on:

• Fuel prices
• Traffic
• Delivery schedules
• Weather

In coordination with warehouse operations, agents identify the best route to reduce costs, delays, fuel consumption, and emissions. Shipments are rerouted based on real-time identification of route blockages and other disruptions. Automatic carrier selection is based on pricing, capacity, and reliability.
Result:

• Efficient deliveries
• Reduced transportation costs
• Minimized carbon emissions
• Higher customer satisfaction

Demand Forecasting and Inventory Optimization

AI agents forecast demand by continuously monitoring:

• Inventory levels
• Market trends
• Weather
• Seasonal changes
• Promotion initiatives
• Competitor activities
• Sales patterns

These forecasts lead to automatic replenishment ordering, inventory stocking, and production scheduling, resulting in balanced inventory allocation and supply planning.
Result:

• Overstocking and stockouts are minimized.
• Accurate, real-time forecasts reduce inventory costs and lost sales.

Dynamic Procurement and Supplier Management

AI agents:

• Assess existing suppliers’ performance and risks to manage deliveries and quality effectively.
• Continuously evaluate new vendors as potential contract partners and run automated negotiations based on pricing, quality, sustainability, and lead time.
• Compare suppliers and recommend a shift when conditions change, such as geopolitical tensions or a performance drop.

Result:
Optimized sourcing that reduces costs, strengthens supply security, and minimizes disruption risks.

Predictive Maintenance and Shop Floor Optimization

AI agents analyze data from machines, vehicles, and robotics to detect anomalies and predict failures. Automated alerts or triggers for machine maintenance requests result in scheduled servicing. This scheduled machine maintenance ensures equipment availability at full capacity, allowing production to run on plan and resources to be allocated accordingly.
Result:

• Reduced disruptions
• Improved asset life leads to higher throughput
• Reduced emergency repair or replacement costs
• Enhanced resource utilization and scheduling

Why are Manufacturers Adopting Agentic Supply Chains Now?

The ‘now’ in AI-powered supply chain management for manufacturers is crucial because of:

• Increasing supply chain complexity due to geopolitical shifts
• Unpredictability in global trade policies
• Increasing supplier instability and demand volatility

Handling these complex situations requires faster decisions and actions based on real-time insights. You don’t want to miss production windows, face overstocking or understocking, or pay higher freight costs just because a decision came too late. Agentic AI supply chains are designed to close these gaps, where data volume outpaces human decision-making capacity.
Moreover, AI for manufacturing supply chain optimization is also driven by:
Agentic AI Maturity
Earlier, AI investments focused on forecasting, reporting, and recommendations. But now, AI agents help coordinate across systems, operate autonomously, and execute workflows.
Technology Ecosystem Readiness
The Microsoft ecosystem provides the required architecture to take the leap. You have the data platform (Fabric), ERP systems (Dynamics 365), and low-code AI agent frameworks to add intelligence and automation to your supply chains.
Delaying the transformation or missing the train this time means losses in cost, customer satisfaction, and scale. You need to decide faster, coordinate better, operate dynamically, and execute immediately. And this is how you will earn a competitive advantage.

What It Takes to Build Agentic Supply Chain Operations

The benefits are established. The urgency is real. But we cannot start AI supply chain transformation just like that. Foundational readiness is needed to ensure sustained value. And this comes from:

A Strong Data Footing

A cohesive data and decision environment, including unified data, clear ownership, and structured relationships, facilitates responsible, contextual, and accurate actions.

Hybrid AI+ERP Modernization Strategy

The best strategy is gradual modernization - updating legacy systems and adding AI capabilities to select enterprise platforms. Connect it all through a scalable data and orchestration layer built for multi-agent collaboration and scalability when needed.

Standardized and Business-aligned Processes

For AI agents to act autonomously and unlock efficiencies, you need well-defined and business-aligned processes.

Human Oversight Rules

Detect human-in-the-loop workflow stages so that decision-making, execution, and approvals in ‘human + AI’ processes are reliable.

Governance and Security

Agentic AI supply chains must operate within strict accessibility and interaction controls, industry-specific audit trails, and cybersecurity rules to prevent data leakage and ensure confident compliance.

Change Management

Phased rollouts, transparent decision-making processes, role-based user training, and explainability in every AI-assisted process improve teams’ trust and readiness.
Address these gaps in data, processes, integrated systems, governance, and smooth adoption to make implementing and deriving value from AI-powered supply chain solutions easier.

How Intech Enables AI-driven Supply Chain Transformation?

Intech, a certified Microsoft partner, fills these gaps with its expertise and experience. Our tailored services help manufacturers build smarter, connected operations with Microsoft-powered AI solutions. Our unique IPs for manufacturing enable end-to-end operational control, boosting efficiency and growth.
Our structured approach brings about your agentic AI supply chain transformation, starting with an assessment of data, process, and technology readiness. Based on this evaluation, we prepare a roadmap to proceed with clarity while keeping all stakeholders involved.
Implementation starts with deploying Fabric as the data foundation, followed by designing and installing supply chain workflow-aligned AI agents. We modernize your existing ERP systems with Dynamics 365, running change management and user training initiatives in parallel to ensure smooth adoption. Lastly, optimization and ongoing managed support services ensure continuous, long-term value delivery after go-live.
Beyond the technology implementation, we make sure the agentic supply chain operations it powers are scalable, business-aligned, and value-generating.

Conclusion

Supply chain control towers achieved what they were meant to do – visibility. But acting on what they saw required human intervention.
The current business landscape, geopolitical disruptions, and global pricing fluctuations need a more robust system. More autonomy. Faster action. Continuous adaptation.
This is what AI-powered supply chain solutions help you achieve with custom AI agents developed for your requirements.

• They don’t just monitor operations; they draw conclusions and execute.
• They don’t just react to events after their occurrence; they anticipate them and act proactively.
• They don’t just manage the supply chain cycle; they orchestrate it on a central platform that connects data, processes, and people.

If you’ve decided on a workflow that is ready for an agent or if you’re still figuring out your readiness,
Connect with Intech to build and deploy custom AI agents or to get your organization ready for AI.

The post Agentic AI Supply Chain vs. Traditional Control Towers for Manufacturers appeared first on ERP Software Blog.

Legacy ERP migration fails when historical data is treated as a single load problem. GP, NAV, and AX environments contain years of ledger, customer, vendor, item, payroll, and operational records. Moving all of it directly into a new cloud ERP can increase storage cost, slow the new system, and make reconciliation harder.
Tool longevity matters when the data being moved is older than the destination platform. COZYROC has spent 20 years inthe SSIS market with customers in 140+ countries, and the 200+ component SSIS+ suite supports SQL Server versions from 2005 through 2025. That version range matters here because GP, NAV, and AX history often sits on the older instances a migration package still has to read.

The Better Migration Question

The question is not “How do we move everything?” The better question is:
What data must live in the new operational ERP, what data must remain queryable for audit and reporting, and what data only needs controlled retention?
That distinction leads to a staged architecture:

1. Extract from the legacy ERP.
2. Clean and normalize records outside the target ERP.
3. Load only active operational data into the new system.
4. Preserve older history in a lakehouse, archive, or reporting store.
5. Use delta detection during the hybrid period while old and new systems overlap.

COZYROC Components For Legacy Dynamics Migration

Migration Architecture Pattern

Use a three-zone migration structure:

1. Legacy extraction zone. COZYROC Dynamics adapters read GP, NAV, AX, or SQL-backed ERP data into staging.
2. Control and cleansing zone. DFT+, lookup logic, and validation tables normalize customers, vendors, dimensions, chart of accounts, addresses, and item records.
3. Target and history zone. Active data loads to the new ERP, while historical data lands in reporting tables, OneLake, SQL endpoints, or archive storage.

During phased deployment, Table Difference can compare legacy source rows with staged or target records to isolate changes. That lets teams maintain parity without running full reloads every night.

TCO And ROI Framing

The savings come from avoiding three expensive mistakes:

1. Overloading the new ERP with decades of inactive history.
2. Hiring developers to rewrite existing SSIS migration logic into notebooks or custom services.
3. Running repeated full-history loads when changed-row detection is enough.

COZYROC also helps preserve existing SSIS knowledge. If the team already understands package design, the migration work can stay closer to the skills and assets they already have.

FAQ

Do we have to move all Dynamics GP history into the new cloud ERP?

No, load only active operational data into the new system. Older ledger, customer, vendor, and payroll history belongs in a lakehouse, archive, or reporting store where it stays queryable for audit without inflating ERP storage cost or slowing the new platform. The migration question is what must live in the operational ERP, not how to move everything.

How do we keep the old and new ERPs in parity during cutover?

Use changed-row detection instead of full reloads. Table Difference compares legacy source rows with staged or target records and isolates new, changed, and deleted rows, so only deltas move during the hybrid window. That keeps nightly parity work small even while both systems overlap.

Which components extract data from GP, NAV, and AX?

Each legacy platform has its own adapter. Dynamics GP Source reads historical and operational GP records, Dynamics NAV Connection manages NAV connectivity ahead of staging, and Dynamics AX Source moves AX records into staging, cleansing, and archive stores through normal SSIS data flow logic.

Can our existing SSIS migration packages run in the cloud?

Yes, COZYROC Cloud Flex executes existing SSIS package assets. Packages are uploaded, parameterized, scheduled, and monitored, which means the migration logic the team already tested does not need a rewrite into notebooks or custom services just to get a managed runtime.

The post Securing Historical Data Continuity: Lower-Risk Cloud Migrations From Dynamics GP, NAV, And AX appeared first on ERP Software Blog.

Listen to the Podcast

A Device Fleet Built One Job at a Time

People in warehouse organizations have different roles that require different devices that run different platforms: an Android mobile device for pickers on the warehouse floor, a Windows PC at the receiving desk, and a forklift-mounted Chromebook tablet at shipping. That is what a real device fleet looks like inside a real warehouse, and nobody bought it all at once. It accumulated, one purchase at a time, for reasons that made sense when each purchase happened. Now, you need everything to connect to your Microsoft Dynamics 365 Business Central. What do you do?

Replace the Hardware or Double the Work, Time, and Cost

Do you limit your choice of a Warehouse Management System (WMS) to match your hardware, or do you upgrade hardware to match your WMS? If the WMS only runs on one platform, then you may have existing hardware that you need to replace. Now you need to budget for new hardware while shelving perfectly good existing hardware because it is not compatible with the WMS.
If a WMS supports multiple operating systems (OS), that usually means a separate set of configurations for each platform, adding work and complications for the IT team managing the infrastructure. Once a change is required for a WMS screen, that means IT is performing twice the work to update two platforms, which can quickly become out of sync, causing risk and chaos on the warehouse floor. Multiple configurations are required for any change, and a third platform only compounds the issues.

Match the Best Hardware to the Role, Without the Headaches and Expense

Warehouse Insight by Insight Works is an app built into Business Central that improves warehouse accuracy and boosts efficiency with mobile devices and barcode integration. Warehouse Insight supports Android, Windows, and Chrome OS, enabling organizations to provide their staff with hardware that serves them best. With Warehouse Insight, only one configuration is needed for all three operating systems, so updates and support are timely, dependable, and consistent.

What Does "One Configuration" Actually Mean in Business Central?

With Warehouse Insight, menus, applications, column layouts, workflows, and overrides get defined once in Business Central. Every device reads that same configuration the moment a worker signs in, regardless of hardware and OS. A picker on an Android mobile device, a supervisor using a Windows PC at a receiving desk, and a forklift operator on a Chromebook tablet access the same WMS configurations within Business Central.

Hardware and Interface-View Flexibility

In addition to the hardware and OS choices Warehouse Insight provides, users can select from three different views to best suit their role. Rich Tile View, Directed Card View, and Compact Grid View are tailored, out-of-the-box views for specific roles. Every role can use the right device to easily access the information they need.

Built for Warehouse Staff and IT Teams

Picker. Works a mobile device through pick after pick, moving fast enough that reading a part number costs time. They carry a mobile device running Android and work in Rich Tile View, where the item picture on each tile lets them confirm a line immediately instead of reading a field.
Receiving associate. Splits time between a mobile device at the dock and a laptop checking a purchase order at a desk, so the software needs to follow them across Android and Windows. Rich Tile View works either way: the same picture check confirms the line whether they're scanning a pallet or working from a screen.
Forklift operator (shipping). Running a vehicle-mounted tablet with attention split between driving and the screen, so the view has to hold still. Directed Card View shows one instruction at a time, with nothing to scroll through while moving a load, and it runs on whatever operating system the mount happens to use: Android, Chrome OS, or Windows.
Putaway associate. Guided from bin to bin with hands often full, so a single instruction is worth more than a full list. On a wearable or tablet running Android, Chrome OS, or Windows, Directed Card View gives them the same one-task, one-screen approach as the forklift operator, with nothing to hunt for.
Quality inspector. Checking one item's detail against an inspection standard before moving to the next, which calls for depth over breadth. On a tablet or wearable, again across Android, Chrome OS, or Windows, Directed Card View puts the inspection instructions and item image in a factbox without a grid competing for attention.
Receiving clerk. Working a full desk screen with a keyboard and mouse, reconciling several lines against each other, which is exactly what a sortable list is for. At a Windows PC, Compact Grid View lets them work the document their own way instead of one line at a time.
Warehouse supervisor. Sitting at the same kind of desk setup as the receiving clerk, but scanning across lines for exceptions and patterns rather than working a single document. Compact Grid View on a Windows PC gives them the full list, sortable, which is what oversight needs.
IT administrator. Not doing floor work at all, but responsible for supporting and configuring what everyone else sees. On a Windows PC, they need visibility into any view, since their job is setting up and troubleshooting the other seven roles' screens rather than working one of their own.
Because device, OS, and view are all set per device configuration in Business Central, none of these eight roles requires a different product, a separate license tier, or a compromise on someone else's setup to get what they need.

Why Does This Matter for Warehouse Operations and Business Central Integration Partners?

For the warehouse, the hardware already on hand stays useful instead of becoming an exception that needs its own procurement round. A worker moving between a fixed station and a mobile device sees the same screen either way, so there is nothing new to learn, just a different device in hand.
For a Microsoft Partner, the win is what disappears from the project plan: no per-platform configuration to build, test, or maintain, and no forced hardware purchase standing between a signed contract and a working demo. A client on older Windows devices can start configuring before a single new scanner arrives.
This is what cross-platform support in Warehouse Insight delivers: one app, one Business Central configuration, and three platforms that all read it the same way. See the full platform list and device guidance on the cross-platform support feature page, or bring your current device inventory to your Microsoft Partner and find out what's already usable before you buy anything new.

The post Three Operating Systems, One Configuration: Cross-Platform Warehouse Management in Business Central appeared first on ERP Software Blog.

Artificial intelligence is now central to how project-based businesses talk about the future of forecasting, resource planning, and profitability analysis. Finance leaders want AI to speed up decisions, and project managers want it to flag risks before they hit delivery. But AI cannot create knowledge on its own. It depends entirely on the timesheets, expenses, budgets, invoices, and resource data that project teams generate every day, and if that data is incomplete or inconsistent, AI's output will be too.
Before adopting another AI tool, project-based organizations need to answer a more basic question: is our project data actually ready for AI?

Key Highlights

• AI-driven forecasting and insights are only as reliable as the project accounting data feeding them.
• Late timesheets, inconsistent project coding, and undocumented change requests undermine AI accuracy long before the AI itself is the problem.
• Structured, standardized project data (consistent categories, phases, tasks, and billing methods) lets AI recognize real patterns instead of reporting noise.
• Project accounting has shifted from a historical reporting function to the operational foundation of AI readiness.
• Data governance, not additional software, is what determines whether AI recommendations can be trusted.

What AI Promises for Project-Based Businesses

The use cases for AI in project accounting are genuinely compelling. Organizations want systems that can:

• Predict project overruns before they occur
• Identify projects with declining margins
• Recommend corrective actions for budget variances
• Forecast future revenue and cash flow
• Detect billing delays and revenue leakage (unbilled or under-billed work that quietly erodes margin)
• Highlight underutilized resources
• Provide real-time executive insights

These capabilities could turn project accounting from a look-back reporting exercise into a proactive, decision-making process. But every one of these predictions depends on the quality of the data behind it.

The Garbage In, Garbage Out Problem in AI-Driven Project Accounting

The technology industry has repeated one phrase for decades: garbage in, garbage out. AI has not changed that rule, it has just raised the stakes.
Picture a professional services firm where consultants submit timesheets days late, use generic project descriptions, and track time inconsistently across phases and tasks. Add expense reports that lack detail and project managers who delay updating budgets and forecasts, and AI has almost nothing reliable to work with.
The consequences show up quickly:

• A forecasting model cannot predict profitability accurately if labor costs are assigned to the wrong project or task.
• An AI assistant cannot catch scope creep (uncontrolled expansion of a project's original requirements) if teams never document change requests.
• A resource-planning tool cannot optimize utilization (how much of a resource's available time is billable or productively assigned) if project assignments are incomplete.

In each case, the technology is not at fault. The data is.

Why Structured Project Data Produces Better AI Insights

Organizations seeing strong results from AI tend to share one trait: consistent, well-structured project data. (This isn't something new, read the blog we wrote last year on the topic!)
Project accounting systems already contain valuable information, but AI can only analyze it when it is captured in a structured format, including:

• Accurate timesheet entries
• Consistent project categories
• Standardized phase and task structures
• Well-defined billing methods
• Complete expense reporting
• Reliable budget tracking
• Timely project updates

When this information is standardized, AI can spot patterns across hundreds or thousands of projects, which leads to sharper forecasting, more relevant recommendations, and more confidence in the numbers behind them. Without that structure, AI cannot tell the difference between a meaningful business signal and ordinary reporting noise.

Project Accounting: The New Foundation for AI Readiness

Project accounting used to mean; tracking costs, managing billing, and supporting financial reporting. Today, it plays a much bigger role: it is the foundation AI readiness is built on.
Every project transaction eventually feeds an AI-generated recommendation. Time entries shape profitability analysis. Expense allocations affect margin calculations. Revenue recognition drives forecasting models. Resource assignments inform capacity planning.
When these processes are not governed properly, the inaccuracies they create spread throughout the entire reporting environment. That is a problem for a growing number of organizations, many of which are investing in AI while still relying on inconsistent timesheet compliance, manual spreadsheets, disconnected systems, and unreliable project reporting.
In those environments, AI tends to magnify existing data problems rather than fix them.

Data Governance: The Missing Link in AI Success

A successful AI strategy needs more than a technology investment. It needs data governance, meaning clear, enforced standards for how project data is created and maintained.
Project-based organizations should set clear standards around:

• Project creation and coding structures
• Timesheet submission requirements
• Expense capture procedures
• Budget management processes
• Change request documentation
• Billing workflows
• Resource planning practices

None of this is about satisfying an accounting checklist. It is about making sure every business decision downstream is based on information leadership can actually trust.

AI Rewards Operational Maturity, Not Shortcuts

A common misconception is that AI removes the need for process discipline. The opposite is true.
As AI becomes more embedded in project accounting systems, the organizations with mature processes will gain the most from it. Clean project data lets AI identify trends accurately, surface exceptions that matter, and generate recommendations decision-makers can act on with confidence.
Organizations with poor data quality will still get recommendations. They just will not be able to trust them.
The real competitive advantage will not come from simply having AI. It will come from feeding AI the right information in the first place.

Start With Data, Not Technology

AI's potential for project-based organizations is real: better forecasting, reduced risk, improved profitability, and sharper decision-making. But AI is not a shortcut around data management, and treating it that way undermines the investment before it starts.
The organizations getting the most out of AI are not necessarily the first to adopt it. They are the ones that prepared their data foundation first.
Before launching your next AI initiative, take an honest look at your project accounting environment:

• Are timesheets accurate and submitted on time?
• Are project structures standardized?
• Can you trust the profitability information in your reports?
• Is billing and revenue data consistent across projects?

If the answer to any of these is no, the next investment your organization needs may not be an AI tool. It may be improving the quality of the project data that AI will depend on, because your AI strategy will only ever be as good as your project data. Look at your processes, read: Faster Billing is a Team Effort

Before You Invest in AI, Invest in Your Project Data

AI has real potential to improve forecasting, profitability, and decision-making for project-based businesses, but only when it is built on a foundation of clean, structured, and consistent project data. Take stock of your project accounting processes now, so the AI initiatives you invest in next actually deliver the results you expect.
 

Frequently Asked Questions

Why does an AI strategy depend on project data quality?
AI does not generate insight independently. It analyzes the timesheets, expenses, budgets, and resource data an organization already produces, so inaccurate or inconsistent data leads directly to unreliable AI output.
What does "garbage in, garbage out" mean for AI in project accounting?
It means AI cannot correct for poor-quality inputs. Late timesheets, generic project descriptions, or undocumented change requests will produce flawed forecasts and recommendations no matter how advanced the AI model is.
What is data governance, and why does it matter for AI readiness?
Data governance is the set of standards an organization enforces around how project data is created and maintained, covering areas like project coding, timesheet submission, expense capture, and billing workflows. Strong governance is what makes AI recommendations trustworthy.
How can a project-based organization prepare its data for AI?
Start by standardizing project categories, phase and task structures, billing methods, and budget tracking. Consistent, complete, and timely data is what allows AI to recognize real patterns instead of noise. (Hint: a PSA tool can help you with this!)
What happens if an organization adopts AI without fixing its data first?
AI will still generate recommendations, but confidence in them will stay low. In many cases, AI ends up magnifying existing data problems, such as inconsistent timesheet compliance or disconnected systems, rather than solving them.
 

How OMZY Supports AI-Ready Project Data

OMZY, the project accounting and project management solution built for Microsoft Dynamics 365 Business Central, helps professional services and project-based organizations bring exactly this kind of structure to their project data. By standardizing how timesheets, budgets, billing, and project transactions are captured within Business Central, OMZY gives organizations a consistent, reliable data foundation, the same foundation that any future AI initiative will depend on. Getting that foundation right today is what will let your organization take full advantage of AI-driven insights tomorrow.

The post Your AI Strategy Is Only as Good as Your Project Data appeared first on ERP Software Blog.

Business Central supplier performance is about more than the price shown on a purchase order. A supplier may offer the lowest unit price, but when the delivery arrives three days late or contains only part of the ordered quantity, that apparent saving can quickly disappear.
The price on the purchase order has not changed, but the cost to the business has.
This is why businesses should review Business Central supplier performance alongside purchase price. A reliable supplier helps you plan stock, labour and customer commitments with confidence. An inconsistent supplier creates work and risk that may never appear in a simple spend report.

How can you measure Business Central supplier performance?

Compare suppliers using on-time receipt performance, fill rate and lead-time consistency, then review the operational impact of the exceptions. The aim is to see which vendors repeatedly deliver late, deliver incomplete quantities or make receipt dates difficult to predict.
Purchasing Insights from Business Central Insights provides ready-made Power BI reports for purchase receipt analytics, on-time receipt performance and fill rate analysis. These reports help procurement teams analyse results by vendor, item, location and company without first assembling the figures in spreadsheets.
APQC also identifies supplier on-time delivery and average supplier lead time as important procurement benchmarks for measuring supplier performance.

Purchase price is only the visible part of supplier cost

A lower price can be cancelled out by the work required to manage unreliable supply. The effect depends on the item and how your business uses it, but common consequences include:

• Production downtime or rescheduling when a required component is missing.
• Extra purchasing time spent chasing confirmations and revised dates.
• Emergency freight or last-minute purchases from another supplier.
• Receiving congestion when late orders arrive at the wrong time.
• More safety stock held to protect the business from inconsistent lead times.
• Missed customer commitments when stock is not available as planned.

These costs sit across several teams, which makes them easy to overlook. Purchasing sees the order and invoice. Operations sees disruption. Finance sees extra freight or working capital. Customer service sees the effect on the customer.
A supplier scorecard does not need to turn every disruption into an exact monetary value. It should make the pattern visible enough for the business to ask whether the quoted saving is real.

Agree what an on-time receipt means

Business Central contains several receipt dates, and they answer different questions. Before comparing suppliers, decide which commitment the measure is testing.
The Requested Receipt Date records when you want the goods. The Promised Receipt Date records when the vendor has committed to supply them. The Planned Receipt Date is based on the order date and lead-time calculation. The Expected Receipt Date also allows for inbound warehouse handling time and safety lead time, so it represents when the goods should be available for use.
Microsoft's purchase date guidance explains how Business Central calculates planned and expected receipt dates and where its lead-time settings come from.
Use the requested date when assessing whether a supplier met your original requirement. Use the promised date when assessing whether it kept the commitment it gave you. Both views are useful, but mixing them in one score without explanation can make the result difficult to interpret.
The same discipline applies to the actual receipt date. Agree whether performance is measured when goods physically arrive, when the receipt is posted, or when stock becomes available. If the warehouse team posts receipts a day late, the report may show a supplier as late even when the vehicle arrived on time.

Measure completeness as well as timing

An order can arrive on time and still leave the business short. For example, a supplier may deliver 80 of 100 units on the promised date and send the remaining 20 a week later. A receipt-level measure may recognise the first delivery, while production still lacks the quantity it needs.
Fill rate adds the missing context by comparing the quantity ordered with the quantity received. Review it alongside on-time performance so that a supplier cannot appear reliable simply because it sends a partial delivery by the due date.
For a practical walkthrough, see our receipt analytics tutorial, which shows how to investigate purchase receipt performance in more detail.
Look for recurring patterns such as:

• Orders received on time but consistently short.
• First receipts arriving on time while final quantities arrive late.
• Reliable supply for standard items but poor performance on critical components.
• A recent decline that is hidden by a strong annual average.

The right level of detail depends on the decision. A vendor-level scorecard supports a supplier review. Item and location detail helps explain why performance differs and where the operational risk sits.

Separate supplier failure from planning and data problems

Poor receipt performance does not always mean the supplier caused the delay. A fair review should check the process behind the number.
Order amendments can move quantities or dates after the supplier has confirmed them. Lead-time settings may be out of date. Requested dates may be unrealistic. A purchase order may be raised late, or the warehouse may take longer than expected to post the receipt. Blank or inconsistent dates can also distort the result.
When a supplier's performance changes, review a sample of the underlying purchase orders before drawing a conclusion. Check the original requirement, the vendor's promise, subsequent amendments and the actual receipt. This turns a score into evidence for a useful conversation rather than an accusation based on an unexplained percentage.
It also exposes internal improvements. If actual lead times are consistently longer than the value stored in Business Central, updating the planning data may improve replenishment decisions even before the supplier changes anything.

Connect Business Central supplier performance to business impact

Not every late receipt carries the same risk. A delayed low-value consumable with ample stock is different from a missing component that stops a production order or prevents a customer shipment.
Prioritise exceptions using business context:

1. Criticality. Does the item support production, customer fulfilment or another time-sensitive process?
2. Stock position. Is there enough available inventory to absorb the delay?
3. Substitutability. Can another item or supplier meet the requirement?
4. Frequency. Is the exception isolated or part of a repeated pattern?
5. Recovery cost. Did the business use premium freight, extra labour or an emergency purchase?

This helps procurement focus on suppliers whose unreliability creates material operational risk, rather than treating every late line as equally important.

Make Business Central supplier performance reporting part of the review process

A practical supplier review can start with a small set of measures: purchase spend, on-time receipt percentage, fill rate, average receipt delay and the number of overdue outstanding lines. Review the trend as well as the current result.
For the suppliers needing attention:

1. Confirm that the date basis and data quality are sound.
2. Drill into the affected items, locations and purchase orders.
3. Record the main causes and the operational consequences.
4. Agree a corrective action with an owner and review date.
5. Check whether performance improves over the following periods.

Use the same measures in supplier conversations so both sides can work from specific orders and dates. If the issue is capacity, transport, order frequency or inaccurate lead times, the action should reflect that cause. A general request to “improve service” is hard to manage and harder to verify.

Frequently asked questions

What is supplier on-time receipt performance?

It measures whether the supplier delivered purchased goods by the agreed date. The result depends on the date used, such as the requested or promised receipt date, and on how partial and outstanding quantities are treated.

What is supplier fill rate?

Supplier fill rate shows how much of the ordered quantity was received. It complements on-time performance because a delivery can arrive by the due date without containing the full quantity required.

Should supplier performance be measured by vendor or item?

Use both. A vendor-level view shows the overall relationship, while item-level analysis reveals where performance differs. This matters when one supplier provides a mix of standard, made-to-order and critical items.

How often should supplier reliability be reviewed?

Review operational exceptions at least weekly when late receipts can affect production or customer orders. Use a monthly or quarterly trend for formal supplier reviews, depending on purchase volume and risk.

See Business Central supplier performance reporting in action

Business Central Insights provides purchasing reports for supplier spend, receipt performance, fill rate and outstanding commitments. You can also read more articles from Business Central Insights on ERP Software Blog.
To explore the reports with your own Business Central data, start a free 30-day trial or book a demo.
The first step is to move the supplier conversation beyond price. When timing, completeness and operational impact are visible together, you can see which relationships are supporting the business and which are quietly adding cost.

The post Business Central Supplier Performance: Which Vendors Are Creating Hidden Procurement Costs? appeared first on ERP Software Blog.

Managing inventory sounds simple until a business has hundreds or thousands of products, multiple warehouses, and several suppliers.
Too much inventory increases storage and carrying costs. Too little inventory can lead to stockouts, delayed orders, and lost sales. The challenge becomes even bigger when suppliers and customers do not have the same view of inventory.
This is where Vendor Managed Inventory (VMI) can make a difference.
Vendor Managed Inventory Software helps suppliers and customers work together to keep inventory at the right level. Instead of waiting for the customer to place an order every time stock gets low, the supplier can monitor inventory data and take responsibility for replenishment based on agreed rules.
In simple words, VMI helps answer three important questions:
How much inventory do we have? When will we need more? When should it be replenished?
This guide explains what VMI software is, how it works, its main features, benefits, implementation process, and how it differs from traditional inventory management and vendor management software.

Good Read: 10 Best Vendor Managed Inventory Software Globally

What Is Vendor Managed Inventory Software?

Vendor Managed Inventory Software is a system that allows a supplier or vendor to monitor a customer's inventory and manage, recommend, or automate replenishment.
Under a traditional inventory model, the customer usually checks stock and places an order when inventory becomes low.
With a vendor managed inventory system, the supplier gets access to agreed inventory and usage information. The supplier can then monitor stock and decide when replenishment is needed.

A simple example

Imagine a grocery store sells 500 bottles of a particular product every month.
In a traditional process:

1. The store checks its inventory.
2. The store notices that stock is getting low.
3. The store contacts the supplier.
4. The store places an order.
5. The supplier sends the products.

With VMI:

1. The supplier can see the store's inventory data.
2. The supplier monitors stock levels and product usage.
3. The system identifies when inventory reaches a reorder point.
4. The supplier plans replenishment.
5. The products are delivered before stock becomes critical.

This approach creates a more proactive inventory management process.

Good Read: 10 Top Warehouse Inventory Management Systems in 2026

What Is VMI in Simple Terms?

Vendor Managed Inventory means the supplier helps manage the customer's inventory.
The customer does not have to handle every replenishment decision manually. Instead, the supplier uses inventory data to make better replenishment decisions.
A simple way to remember VMI is:

The customer uses the products. The vendor watches the inventory and helps keep it stocked.

This is why VMI is closely connected to inventory visibility, supplier collaboration, inventory replenishment, demand planning, and supply chain management.

How Does Vendor Managed Inventory Software Work?

A VMI system connects the supplier and customer through shared inventory information.
The process generally works like this.

1. Inventory data is shared

The customer provides inventory and product movement information to the supplier.
Depending on the setup, data can come from:

• ERP systems
• Warehouse Management Systems (WMS)
• Point-of-sale systems
• Inventory management software
• EDI
• APIs
• Other supply chain systems

The supplier may receive information about stock levels, sales, consumption, shipments, and orders.

2. The vendor monitors inventory

The supplier uses the VMI software to monitor inventory across customer locations.
The dashboard may show:

• Current inventory
• Available stock
• Reserved inventory
• Products below reorder level
• Product consumption
• Stock movement
• Pending replenishment
• Stockout risk

This gives the vendor a clearer picture of what is happening.

3. The system identifies replenishment needs

The software can use rules such as:

• Minimum stock level
• Maximum stock level
• Reorder point
• Safety stock
• Lead time
• Historical usage
• Demand forecasts

When inventory reaches a predefined threshold, the system can flag it for replenishment.

4. The vendor plans replenishment

The supplier reviews the requirement and decides how much inventory should be sent.
Depending on the system, this can be a manual decision, a software recommendation, or an automated process.

5. Products are shipped

The supplier prepares and ships the required products.
The inventory records are then updated, creating a continuous flow of information between the customer and supplier.
The overall process can be simplified as:
Inventory Data → Inventory Monitoring → Replenishment Planning → Shipment → Inventory Update

Good Read: Top ERP Consulting Companies in 2026

Why Is Vendor Managed Inventory Important?

Many inventory problems happen because businesses do not have enough visibility.
A customer may think there is enough inventory while the supplier is unaware that stock is running low. In another situation, a supplier may send too much inventory because demand was not properly understood.
VMI helps both sides work with better information.
Instead of reacting after inventory becomes a problem, suppliers can monitor stock and respond earlier.

Key Features of Vendor Managed Inventory Software

A strong VMI system usually combines inventory visibility, replenishment, analytics, and supplier collaboration.
Here are the most important features to look for.

1. Real-Time Inventory Visibility

A VMI platform should provide accurate and timely information about inventory.
Suppliers can see stock levels across different customer locations instead of relying entirely on emails, spreadsheets, or phone calls.
This is especially useful for businesses operating multiple warehouses, stores, or distribution centers.

2. Inventory Tracking

The system tracks inventory movement and helps suppliers understand how quickly products are being consumed.
This makes it easier to identify products that are:

• Selling quickly
• Moving slowly
• Approaching reorder levels
• At risk of stockout
• Overstocked

3. Reorder Point Management

A vendor managed inventory system can use predefined reorder points.
For example, a business may decide that a product should never fall below 100 units.
When stock reaches that level, the VMI software can create an alert or recommend replenishment.

4. Automated Inventory Replenishment

Automated inventory replenishment is one of the main reasons businesses adopt VMI.
Instead of manually checking every product, the system can identify replenishment requirements based on inventory rules, usage, lead times, and demand.
This can reduce repetitive work and help teams respond faster.

5. Demand Forecasting

Some VMI solutions include demand forecasting capabilities.
Historical sales, consumption patterns, seasonality, and other data can be used to estimate future demand.
Better forecasts can lead to better replenishment decisions.

6. Inventory Alerts

A VMI platform can generate alerts when something needs attention.
Examples include:

• Low stock alerts
• Stockout warnings
• Excess inventory alerts
• Slow-moving inventory
• Unexpected demand changes
• Delayed replenishment

These alerts help vendors act before a small issue becomes a larger supply chain problem.

7. Multi-Location Inventory Management

Many businesses manage inventory at multiple customer sites.
A VMI software platform can provide a centralized view across those locations.
For example, a supplier may be able to see:

• Customer Warehouse A
• Customer Warehouse B
• Customer Store C
• Distribution Center D

This makes inventory planning more coordinated.

8. Reporting and Analytics

Reporting helps vendors understand how inventory is performing.
Useful reports may include:

• Inventory turnover
• Stock availability
• Replenishment frequency
• Fill rate
• Stockout rate
• Slow-moving inventory
• Excess inventory
• Product consumption

Analytics can also help suppliers improve future inventory planning.

9. ERP and WMS Integration

Most businesses already have systems for managing operations.
A VMI solution should ideally integrate with an ERP, WMS, POS, or inventory management system.
For example, VMI WMS integration can allow warehouse inventory data to flow directly into the VMI platform.
This reduces duplicate data entry and helps maintain consistent information.

Good Read: 10 Top 3PL Warehouse Management Systems

Benefits of Vendor Managed Inventory Software

VMI can provide benefits to both customers and suppliers.

Better Inventory Visibility

Suppliers gain better visibility into customer stock and product movement.
This makes inventory decisions more data-driven.

Fewer Stockouts

When vendors can see inventory levels and reorder points, they can identify potential stockouts earlier.
This can help improve product availability.

Lower Excess Inventory

Holding too much inventory can increase storage and carrying costs.
Better replenishment planning can help businesses avoid unnecessary inventory buildup.

Less Manual Work

Employees spend less time checking spreadsheets, sending emails, and manually calculating replenishment needs.
The software can handle many repetitive inventory tasks automatically.

Better Supplier Collaboration

VMI creates closer cooperation between suppliers and customers.
Both sides can work from shared inventory information instead of relying entirely on manual communication.

Better Demand Planning

When suppliers can see actual customer consumption, they may be able to plan future inventory and production more effectively.

More Predictable Replenishment

Instead of waiting for urgent purchase orders, suppliers can plan replenishment based on inventory trends and agreed rules.

Good Read: Top Business Central Partners in 2026

Vendor Managed Inventory vs Traditional Inventory Management

The biggest difference is who takes responsibility for monitoring and replenishment.

VMI does not mean the customer loses control of inventory.
Instead, it creates a model in which the supplier takes a more active role while both parties continue to follow agreed inventory policies.

Vendor Managed Inventory vs Vendor Management Software

The names are similar, but these are different solutions.

Vendor Managed Inventory Software

VMI software focuses on:

• Inventory monitoring
• Stock levels
• Replenishment
• Product consumption
• Inventory visibility
• Supplier-customer collaboration

Vendor Management Software

Vendor Management Software generally focuses on managing the supplier relationship.
It may include:

• Vendor onboarding
• Contracts
• Supplier information
• Supplier performance
• Compliance
• Procurement workflows
• Approvals

So, Vendor Managed Inventory Software is not the same as Vendor Management Software.
A VMI platform focuses primarily on inventory and replenishment, while a vendor management system focuses primarily on managing suppliers.

Who Uses Vendor Managed Inventory?

VMI can be useful in industries where suppliers and customers need close coordination.

Manufacturing

Manufacturers can use VMI to manage raw materials, components, packaging, and production supplies.
For example, a supplier can monitor the stock of components used on a production line and replenish them before inventory becomes critical.

Retail

Retailers and suppliers can use VMI to improve product availability across stores and distribution centers.

Wholesale and Distribution

Distributors can use VMI to coordinate inventory between suppliers and customers.

Automotive

The automotive industry often depends on reliable availability of parts and components. VMI can help suppliers and manufacturers coordinate inventory more efficiently.

Healthcare

Healthcare businesses can use supplier collaboration and inventory visibility to improve the management of important products and supplies.

E-commerce

E-commerce companies can use VMI to support inventory replenishment across fulfillment centers and warehouses.

How to Implement a Vendor Managed Inventory System

A successful VMI program requires both technology and clear business processes.

Step 1: Decide What the Vendor Will Manage

Start by defining responsibilities.
Decide which products, locations, and replenishment activities will be handled by the supplier.

Step 2: Set Inventory Rules

Create clear rules for:

• Minimum inventory
• Maximum inventory
• Reorder points
• Safety stock
• Lead times
• Replenishment quantities

Step 3: Connect Your Systems

Integrate the VMI platform with relevant systems such as your ERP, WMS, POS, or inventory management software.

Step 4: Define Data Access

Decide what inventory and sales information the vendor can access.
Data security and user permissions are important because suppliers may need access to customer inventory information.

Step 5: Create Replenishment Rules

Decide how the system will determine when and how much inventory should be replenished.

Step 6: Start With a Pilot

Instead of changing the entire supply chain at once, businesses can start with selected products, customers, or locations.
This helps teams identify problems before expanding the program.

Step 7: Measure Results

Track performance using metrics such as:

• Stockout rate
• Fill rate
• Inventory turnover
• Inventory carrying cost
• Replenishment accuracy
• Excess inventory
• Supplier performance

Step 8: Improve the Program

A VMI program should be reviewed regularly.
As demand, products, suppliers, and customer requirements change, inventory rules may also need to change.

How to Choose the Right VMI Software

There are many inventory and supply chain platforms in the market. The right choice depends on your business needs.
When evaluating vendor managed inventory software, consider the following.

Inventory Visibility

Can the software provide accurate inventory information across customer locations?

Replenishment Capabilities

Can it support reorder points, safety stock, minimum and maximum inventory, and automated replenishment?

Integration

Can it connect with your existing ERP, WMS, POS, EDI, or API infrastructure?

Scalability

Can it support more products, customers, warehouses, and locations as the business grows?

Analytics

Does it provide useful dashboards, reports, and inventory analytics?

Alerts and Automation

Can the system alert teams about low stock, stockout risks, and unusual demand?

Security

Can you control which users and suppliers can access inventory information?

Ease of Use

The software should be easy for both suppliers and customers to understand and use.
A technically advanced system is not useful if the people responsible for inventory cannot use it efficiently.

Is VMI Software the Same as Inventory Management Software?

Not exactly.
Inventory Management Software is generally designed to help a business manage its own inventory.
Vendor Managed Inventory Software is designed around collaboration between a supplier and customer.
For example:
Inventory management software may answer:

"How much inventory do we have?"

VMI software can help answer:

"How much inventory does our customer have, and when should we replenish it?"

Modern ERP, WMS, and supply chain platforms may include VMI capabilities. In other words, VMI may be a dedicated solution or a feature within a broader business platform.

VMI, WMS, ERP, and Supply Chain Software

VMI does not operate in isolation.
It often works together with other business systems.

VMI + WMS

A Warehouse Management System manages warehouse operations such as receiving, putaway, picking, packing, and shipping.
VMI uses inventory information to support supplier-driven replenishment.

VMI + ERP

An ERP system manages broader business processes such as finance, purchasing, sales, inventory, and operations.
VMI can use ERP data to improve replenishment and supplier collaboration.

VMI + Supply Chain Management

Supply chain platforms can bring together demand planning, inventory management, procurement, transportation, suppliers, and other processes.
VMI can become one part of this connected supply chain environment.

What Is the Future of Vendor Managed Inventory?

The future of VMI is increasingly focused on automation and better data.
Businesses want to know what is happening with inventory in real time and respond before problems occur.
Modern VMI solutions are moving toward capabilities such as:

• Real-time inventory visibility
• Automated replenishment
• Demand forecasting
• Predictive analytics
• AI-assisted inventory planning
• Supplier collaboration
• Multi-location inventory management
• ERP and WMS integration
• Supply chain dashboards

The goal is not simply to keep more inventory.
The goal is to keep the right inventory in the right place at the right time.

Frequently Asked Questions About Vendor Managed Inventory Software

What is Vendor Managed Inventory Software?

Vendor Managed Inventory Software is a system that allows suppliers to monitor customer inventory and manage or recommend replenishment based on inventory levels, usage, demand, and predefined rules.

What does VMI software do?

VMI software supports inventory visibility, stock monitoring, replenishment planning, supplier collaboration, demand forecasting, inventory alerts, and inventory analytics.

How does a VMI system work?

The customer shares inventory and usage data with the supplier. The vendor monitors the information, identifies replenishment needs, and manages or recommends the next inventory shipment.

What is the difference between VMI and traditional inventory management?

In traditional inventory management, the customer usually monitors inventory and places orders. In VMI, the supplier takes a more active role in monitoring inventory and managing replenishment.

Can VMI software integrate with a WMS?

Yes. VMI WMS integration allows inventory information from a Warehouse Management System to be shared with the VMI platform, helping suppliers make better replenishment decisions.

Can VMI software integrate with an ERP?

Yes. Many VMI solutions can connect with ERP systems using APIs, EDI, or other integration methods.

Does VMI reduce inventory costs?

VMI can help businesses reduce excess inventory and improve replenishment efficiency. However, results depend on demand accuracy, inventory rules, supplier performance, data quality, and implementation.

Who benefits from VMI?

Both suppliers and customers can benefit. Customers can improve inventory availability and reduce manual work, while suppliers can gain better visibility into demand and improve replenishment planning.

Is VMI the same as vendor management?

No. Vendor Managed Inventory focuses on inventory and replenishment, while Vendor Management Software generally focuses on supplier relationships, contracts, performance, compliance, and related processes.

Final Thoughts

Vendor Managed Inventory Software brings suppliers and customers closer together through shared inventory data and coordinated replenishment.
Instead of waiting for a customer to place an order after inventory becomes low, the supplier can monitor stock levels and take action earlier.
With capabilities such as real-time inventory visibility, inventory tracking, automated inventory replenishment, demand forecasting, reorder point management, supplier collaboration, inventory alerts, analytics, and ERP/WMS integration, VMI can make inventory management more proactive.
For businesses managing multiple products, suppliers, warehouses, or customer locations, a vendor managed inventory system can help create a smoother and more connected supply chain.
Ultimately, the purpose of VMI is simple:
Keep products available without holding more inventory than necessary.

The post What Is Vendor Managed Inventory Software? A Simple Guide appeared first on ERP Software Blog.

B2B ecommerce extends Microsoft Dynamics 365 Business Central with a digital buying experience designed for manufacturers, distributors, dealers, and business customers. Business Central can continue to manage operational data such as customers, products, pricing, inventory, orders, manufacturing, shipments, and financials, while the ecommerce platform gives buyers a convenient way to research products, place orders, request quotes, and manage their accounts online.

Key Highlights

• Dynamics 365 Business Central can remain the operational system for customers, products, pricing, inventory, orders, manufacturing, shipments, and financial data while ecommerce provides the customer-facing buying experience.
• Manufacturing ecommerce often requires capabilities beyond a typical consumer storefront, including account-specific pricing, purchasing hierarchies, complex products, distributors, dealers, approvals, and repeat ordering.
• Customer portals can move routine activities such as reordering, shipment tracking, invoice retrieval, and account management into self-service.
• Manufacturers with multiple brands, regions, or customer groups can use a multi-store ecommerce approach while connecting those experiences to Business Central.
• Successful Business Central ecommerce integration requires clear data ownership and the right combination of real-time and scheduled data exchanges.

What Role Does B2B Ecommerce Play Alongside Dynamics 365 Business Central?

Gartner reported in 2026 that 70% of B2B buyers prefer a completely digital, self-service buying experience. B2B ecommerce extends information and business processes from Business Central into a digital environment designed around how customers search, purchase, reorder, and manage their accounts.
Business Central can manage core processes such as financials, sales, purchasing, inventory, supply planning, and manufacturing. The ecommerce platform serves a different purpose by presenting the products, pricing, account information, and purchasing tools customers need in an accessible online experience.
For example, an authorized buyer might sign in to an ecommerce portal, see the products available to their organization, receive the correct negotiated price, check appropriate inventory information, and submit an order. That transaction can then flow into Dynamics 365 Business Central for fulfillment, invoicing, and financial processing.
As the transaction progresses, relevant information from Business Central, such as order status, shipment details, or invoices, can be made available again through the ecommerce portal. This gives customers better self-service access while keeping Business Central at the center of operational processing.

Why Is B2B Ecommerce More Complex for Manufacturers Using Business Central?

Manufacturing ecommerce often needs to reflect business relationships and purchasing rules that go far beyond a typical consumer checkout. The ecommerce system may need to determine not only what a customer wants to buy, but also what that customer is allowed to purchase, which Business Central pricing applies, who can approve the purchase, and how the order should move into manufacturing and fulfillment.
A manufacturer may sell through distributors, dealers, branches, purchasing departments, or multinational customer accounts. Within one customer organization, several users may have different responsibilities, purchasing limits, locations, approval authority, or access to different product catalogs.
Common B2B requirements include:

• Customer, distributor, or dealer-specific catalogs
• Contract, tier, quantity, or account-specific pricing
• Parent-child account structures and purchasing permissions
• Purchase-order fields and established procurement workflows
• Quotes and approval routing
• Saved lists and repeat ordering
• Multiple storefronts, brands, or business units
• Different shipping, payment, and purchasing rules by customer
• Quote-to-order workflows for purchases requiring sales involvement

An ecommerce platform designed for B2B commerce can provide more structure for these relationships than a storefront designed primarily for consumer transactions.
Znode's manufacturing ecommerce capabilities include customer-specific catalogs, contract pricing, purchasing hierarchies, quote workflows, dealer and distributor portals, and account-level permissions.

How Can Manufacturers Sell Complex Products Online with Business Central?

Complex products do not automatically have to remain offline. The goal is to give buyers enough product information and structure to identify the right item, narrow their options, request assistance when necessary, or complete the transaction when self-service makes sense.
Manufacturers using Dynamics 365 Business Central may need their ecommerce platform to represent:

• Configurable products with selectable attributes
• Variants and product families
• Kits and assemblies
• Product bundles
• Replacement or compatible parts
• Accessories and related products
• Products that require a quote before purchase

Search, filtering, product relationships, and configuration become especially important in these scenarios. A customer should not have to know an exact Business Central item number simply to locate the product or replacement part they need.

For products that require more guidance, B2B ecommerce does not have to force the transaction into a standard checkout. The digital process can instead help the customer identify compatible options, gather the information needed for a quote, or move the request to a salesperson or product specialist.
The Znode B2B ecommerce platform supports product structures including variants, kits, bundles, replacement products, and personalized catalogs.
Product information management is another important consideration. Business Central may remain responsible for operational product and item data, while the ecommerce platform or a product information management system handles richer digital content such as technical attributes, categories, product relationships, descriptions, images, and other information needed to support online product discovery.

What Should a Business Central Customer Portal Let Buyers Do?

A useful B2B customer portal should move frequent, repeatable activities into self-service while keeping sales and customer service available for situations where human expertise adds value.
Depending on the manufacturer's products and customer relationships, self-service can include:

• Viewing account-specific products and catalogs
• Checking negotiated pricing from Business Central
• Reviewing appropriate inventory availability
• Reviewing previous orders and reordering common items
• Requesting quotes
• Routing purchases through required approvals
• Tracking orders and shipments
• Retrieving invoices, receipts, and product documentation
• Managing customer users, permissions, locations, and spending limits

Rather than removing humans from the equation, offering a self-service portal frees your sales reps from simple information requests, delivering the needed data directly to your customers. Then, your sales staff can focus on helping customers complete more complex transactions.

A B2B portal can also reflect the customer's account structure and responsibilities. Different users may see different Business Central orders, customer accounts, prices, or available actions based on their assigned roles and permissions.

When routine ordering, document retrieval, and status checks move online, sales and service employees can spend more time helping with complex purchases, technical questions, exceptions, and customer relationships that require direct involvement.

How Can Business Central Manufacturers Manage Multiple Brands and Ecommerce Experiences?

A multi-store ecommerce model allows manufacturers to create different customer experiences while continuing to connect those channels with Dynamics 365 Business Central.
This can be useful when a manufacturer acquires another business, launches a new brand, expands into another region, adds a direct sales channel, or creates a dedicated distributor or dealer portal. Each storefront may require its own catalog, branding, customers, pricing, content, currency, shipping rules, or permissions while still sharing common ecommerce infrastructure.
Znode's multi-store ecommerce capabilities allow businesses to manage multiple brands, catalogs, sites, and sales channels within a common platform and administration environment. Catalogs and business rules are applied differently according to the store, account, user, or customer profile.
Centralizing ecommerce infrastructure reduces duplicated systems and administration, while individual brands or business units still deliver experiences appropriate for their customers.

How Should B2B Ecommerce Integrate with Dynamics 365 Business Central?

A successful Business Central ecommerce integration starts by determining which system owns each type of data. Without that distinction, manufacturers can end up with duplicate records, conflicting updates, or uncertainty about whether Business Central, ecommerce, CRM, or another application contains the authoritative value.
A typical integration structure might look like this:

Znode provides a native Microsoft Dynamics 365 Business Central integration through Znode Commerce Connector. It supports exchanges involving products, pricing, inventory, customers, and orders between Business Central and the ecommerce environment.

When Should Business Central Ecommerce Data Be Real-Time or Scheduled?

Not every exchange between Business Central and ecommerce needs to run at the same frequency. Information that affects an immediate purchase decision may need to be retrieved or updated in real time, while other data can often be synchronized on a schedule.
For example, customer-specific pricing or inventory availability may require current information during the buying process. Product content and other less time-sensitive information may be appropriate for scheduled synchronization.
Znode Commerce Connector supports real-time, on-demand, and scheduled exchanges, allowing manufacturers to choose an integration approach based on the type of data and the business process involved.

What Should Manufacturers Decide Before Connecting Ecommerce to Business Central?

Before integrating Dynamics 365 Business Central with a B2B ecommerce platform, manufacturers should answer several practical questions:

1. Which application creates and maintains each type of data?
2. Which information must be available in real time?
3. Which information can move through scheduled synchronization?
4. How will ecommerce orders enter Business Central?
5. How will Business Central pricing, discounts, and payment terms be applied?
6. What happens if customer, pricing, inventory, or order data fails to synchronize?
7. How will duplicate records and incomplete transactions be detected?
8. Who will monitor and maintain the integration after launch?

Technical connectivity is only one part of the project. Manufacturers also need to understand how exchanges will be configured, secured, monitored, updated, and supported over time.

How Should Business Central Manufacturers Evaluate a B2B Ecommerce Platform?

Manufacturers should evaluate B2B ecommerce platforms around actual buying and Business Central workflows rather than comparing feature lists in isolation.
Consider how the platform would handle a distributor placing a repeat order, a purchasing department requesting approval, a customer searching for a replacement part, or a buyer configuring a complex product before requesting a quote. The important question is how naturally each scenario connects with the customer, product, pricing, inventory, order, and fulfillment processes already managed in Business Central.
Useful evaluation questions include:

• Can the platform represent our products? Review support for configurations, variants, kits, bundles, replacement parts, attributes, and related products.
• Can it support our customer agreements? Test contract pricing, account catalogs, payment terms, shipping rules, and user permissions.
• Can it work with our Business Central data? Determine how products, customers, pricing, inventory, orders, shipments, and invoices move between systems.
• Can it support our sales channels? Consider distributors, dealers, direct sales, multiple brands, regions, and future channels.
• Can customers follow their normal purchasing process? Test quotes, approvals, purchase orders, repeat ordering, invoice access, and account administration.
• Can business users maintain the experience? Determine how much day-to-day catalog and content management requires development support.
• How much customization is actually necessary? Separate native capabilities and configuration from extensions or custom code.
• Can the platform scale with future requirements? Consider more transactions, brands, acquisitions, storefronts, regions, and product information.
• What is the long-term operating cost? Look beyond licensing to implementation, Business Central integration, support, hosting, maintenance, upgrades, and internal resources.

The people who work with Business Central and the customer buying process should also be part of the evaluation. Sales, customer service, operations, finance, IT, marketing, and selected customers can often identify requirements that a technical feature comparison alone will miss.

Why Consider Znode for Dynamics 365 Business Central B2B Ecommerce?

Znode was built specifically for the complexities of B2B ecommerce for manufacturers and distributors, drawing on more than 20 years of ecommerce consulting experience. Rather than adapting a consumer-focused storefront to B2B requirements later, Znode was designed around challenges such as complex and configured products, aftermarket parts, contract pricing, purchasing hierarchies, multiple brands, and different sales channels.
For manufacturers using Dynamics 365 Business Central, that B2B focus extends to integration. Znode uses an API-first architecture, and its native Commerce Connector is designed to simplify and manage data exchanges with ERP, CRM, PIM, and other business systems. With Business Central, manufacturers can connect products, customers, pricing, inventory, and orders while choosing real-time, on-demand, or scheduled exchanges based on the needs of each process.
Znode also supports manufacturers whose ecommerce requirements become more complex as they grow. Its Azure-based SaaS architecture supports multiple storefronts, portals, brands, business units, and digital sales models on one platform, while native personalization can apply pricing, promotions, content, and catalogs by user, account, or profile. This gives Business Central manufacturers a way to build ecommerce around existing B2B relationships and operational data without treating every customer group or sales channel as a separate ecommerce project.

Frequently Asked Questions About Business Central B2B Ecommerce

Q: Does a manufacturer need to replace Dynamics 365 Business Central to add B2B ecommerce?

A: No. Business Central can remain the operational ERP while the ecommerce platform provides the customer-facing catalog, ordering, account management, and self-service experience.

Q: What information can Business Central share with a B2B ecommerce platform?

A: Depending on the integration, Business Central can provide information such as products, customers, account-specific pricing, inventory, order status, shipments, and invoices while ecommerce orders can flow back into Business Central for processing.

Q: What makes manufacturing ecommerce different from normal B2C ecommerce?

A: Manufacturing ecommerce may need to handle contract pricing, account hierarchies, distributors, dealers, complex products, purchasing approvals, multiple users, customer-specific catalogs, and ERP-driven order processes.

Q: Can B2B ecommerce support manufactured products that require configuration or quoting?

A: Yes. The ecommerce experience can help buyers select options, identify compatible products, gather information for a quote, or complete a purchase when self-service is appropriate.

Q: How does Znode integrate with Dynamics 365 Business Central?

A: Znode Commerce Connector provides native integration capabilities for exchanging products, customers, pricing, inventory, and orders with Business Central using real-time, on-demand, or scheduled processes.

Explore B2B Ecommerce for Your Dynamics 365 Business Central Environment

If you are evaluating B2B ecommerce for Dynamics 365 Business Central, start with the customer journeys and operational processes you want to improve. Then determine how products, pricing, customers, inventory, orders, shipments, and account information should move between Business Central and the ecommerce experience.
A tailored demonstration can help you evaluate these workflows using scenarios that reflect your actual customers and products.
Request a Znode demo to explore how Znode can work with Dynamics 365 Business Central and your B2B ecommerce requirements.
By Znode | www.znode.com

The post B2B Ecommerce for Manufacturers Using Dynamics 365 Business Central appeared first on ERP Software Blog.

The Masthead Post - Navigating Success Together

Feature Spotlight

Take Control of your Workspace with Personalization
Did you know you can completely change how Business Central looks to match exactly how you work? You don't need an administrator to hide fields you never use or to bring important metrics to the top of your screen.
How to get started:

1. Click the Settings gear icon in the top right corner and select "Personalize".
2. Hover over any column banner, field, or action button.
3. Click the red arrow to hide, move, or make a field required.
4. Click "Done" in the top banner to save your changes.

Pro Tip: Use this on your Sales Orders or Purchase Orders page to hide fields your company doesn't use, drastically reducing scrolling time for your data entry team.

Webinar: What’s New in Business Central: 2026 Releases & More

AI is changing what’s possible in Business Central. Are you ready to see what’s next?
Business Central is continuing to evolve, with new features and updates designed to make everyday tasks easier and more efficient.
Join us this October for a look at the 2026 releases, including the latest AI and Copilot capabilities, automation updates, reporting improvements, and productivity features. We’ll also share a few practical tips for making the most of what’s new.

What we'll cover:

• 2026 release highlights
• New AI and Copilot features
• Automation and workflow updates
• Reporting and analytics improvements
• Productivity tips and useful features

Before AI, Fix Your Finance Foundation

See why clean, governed data is key to building an AI-ready finance team.
As finance teams grow, so do the demands on their financial systems. In our latest podcast, Dominick Zappia, Partner at Admiral Consulting Group, sits down with Gurpreet Chaggar, Product Marketing Manager at Prophix, to explore why an ERP may be the system of record—but shouldn’t necessarily be the system for everything finance needs.
They dive into how CPM and FP&A can help growing organizations move beyond spreadsheet-heavy processes, improve budgeting and forecasting, streamline financial close, and enable smarter scenario planning. Plus, discover why clean, governed data is the real starting point for building AI-ready finance.

If you're rethinking your finance architecture or wondering whether your ERP can keep up with your growth, this conversation is worth a listen.

Listen now to learn why modern finance teams need more than ERP.
 

From Dynamics GP to Business Central: What's Next for Finance & Manufacturing?

Moving from Dynamics GP to Business Central is more than a system migration. It's an opportunity to transform how your organization plans, forecasts, and reports.

Join Admiral Consulting Group and Vena to discover how manufacturers can connect financial and operational data, improve forecasting accuracy, model business scenarios, and gain deeper insights across demand, inventory, labor, materials, and more.
In just 45 minutes, you'll see how leading manufacturers are moving beyond spreadsheets to create a more connected, agile planning process.

October 7, 2026 | 10:00 AM EDT | Online
Reserve your spot and see what's possible when finance and operations plan together.

The post Admiral Consulting Group | September Newsletter appeared first on ERP Software Blog.

As your company grows, you collect data about your performance, customers, products, and more, but if you aren't using that data to better your workflows or strategy, the information is basically worthless.
To take full advantage of all the data you have, it helps to create reports that are easy to read and analyze. Popdock is the tool you need to help with all your ad hoc reporting needs.

What Stands in the Way of Good Reporting?

Taking the time to create ad hoc reports can be incredibly beneficial to any business, but you still may run into some common challenges, including:
Limited access to data: If employees can't reach the data relevant to their role, reporting can't happen. Make sure your people can access the information they rely on.
Poor data management: Not only do your employees need access to the data, but that data also needs to be clean. Manage your data so that missing, wrong, and duplicated data are fixed before anyone tries to run reports.
Lack of training: Teams need to understand when ad hoc reporting is useful and how easy it can be to generate a report. Give your team the proper training so they can start using the data they have at their fingertips.
Inconsistency: Reporting really pays off when it becomes a habit. Make sure your end-users know they should be reporting on and analyzing their data regularly.

Why Should You Take Advantage of Ad Hoc Reporting?

Unmanaged data turns an asset into a burden. All the data you could use to make your business better suddenly becomes just another thing you need to maintain.
Thankfully, ad hoc reporting turns that burden into insight. Done well, it can:

• Identify and fix productivity bottlenecks.
• Improve flexibility in addressing problems and questions.
• Make data accessible and easy to act on for end users.
• Encourage broader use of data across the company.
• Let employees use data themselves instead of waiting for a developer.

Popdock Makes This Simple

Popdock removes the friction that stops teams from getting started with ad hoc reporting. It lets users pull data from multiple sources, including apps, websites, SQL Servers, data lakes, and more, into one place. That means you don't have to log into each system separately or ask another department to run a report for you. Read more about reporting on our Self-Service Reporting page.
With Popdock you can:

• Search, filter, group/subgroup data
• Add or remove columns as needed
• Combine data from multiple sources
• Apply calculations to transform raw data into insight
• Export, share, and format results
• Visualize data with charts and summaries
• Drill into details and take action directly

Sign up for our weekly demo, Intro to Popdock, to see all of these features in action.

Try Popdock for Ad Hoc Reporting

Popdock makes gathering the data you need seamless, fast, and simple. Stop relying on IT to pull data for you and empower your team to work with and report on data themselves.
Learn more about the kind of reports you can make with Popdock by calling 888-319-3663 or emailing sales@eonesolutions.com.

The post Unlock the Power of Ad Hoc Reporting appeared first on ERP Software Blog.

Business Central vs. Finance & Operations: Which Dynamics 365 ERP Is Right for You?

Choosing between Microsoft Dynamics 365 Business Central and Dynamics 365 Finance & Operations is one of the most consequential decisions a company makes when moving to Dynamics. Pick wrong, and you either outgrow the platform in two years or pay for complexity you'll never use. After years of implementing both, and rescuing projects where the wrong one was chosen, here's how we help clients think it through.
Start with the honest question: how complex is your business, really?
The instinct is to reach for the bigger, more powerful platform. Resist it. The right answer isn't about which system does more; it's about which one fits how your business actually operates.

Where Business Central fits

Business Central is built for small to mid-sized organizations that need solid, integrated ERP without heavy complexity. It's a strong fit when:

• You're a single entity or a handful of legal entities, not a sprawling multinational.
• Your operations are relatively straightforward: standard finance, distribution, light-to-moderate manufacturing.
• You want faster implementation, lower cost, and a system your team can actually manage.
• You don't need deep, high-volume warehouse automation or complex global compliance out of the box.

For most growing companies, Business Central does more than they expect, and often the manufacturing or process needs people assume require F&O can be met with Business Central plus the right ISV.

Where Finance & Operations fits

Finance & Operations is built for larger, more complex enterprises. It's the right call when:

• You're running many legal entities across multiple countries, with complex intercompany and global compliance needs.
• You have high-volume, sophisticated operations: advanced warehouse management, complex manufacturing, deep supply chain.
• You have the scale and internal capability to support a larger, more configurable platform.
• Native process manufacturing, catch weight, or advanced planning are core to your operation.

F&O is powerful, but that power comes with cost and complexity. If you don't need it, it becomes overhead, not advantage.

The mistake we see most often

The most expensive errors happen when a company chooses the platform based on ambition rather than reality. We've been called in to rescue Business Central implementations that were stretched far past what the platform was designed for, and F&O implementations where a company paid for enterprise complexity it never used. In both cases, the fix started with an honest assessment of what the business actually needed, something that should have happened before the platform decision.

How to decide well

Before committing, get clear on three things: the true complexity of your operations, your realistic growth trajectory, and your internal capacity to support the platform. The right choice sits at the intersection of those three, not at whichever system has the longer feature list.
And if you're already partway down a path that doesn't feel right, it's rarely too late to correct course. The sooner you get an honest read on the fit, the cheaper the correction.

Poize2 is a senior Microsoft Dynamics team specializing in rescuing troubled implementations and delivering ones that stay on track, across Business Central and Finance & Operations. If you're weighing the two, or worried you chose wrong, we're glad to give you a straight answer. Learn more at www.poize2.com

The post appeared first on ERP Software Blog.

 
 
 
 
 
 
 
Your accounts payable team runs the same check batch process every pay cycle. It used to take thirty seconds. Now it takes five minutes. Nothing obvious has changed, the system hasn't thrown any errors, and yet the slowdown gets a little worse each month.
If you're running EFT payments through Microsoft Dynamics GP and this sounds familiar, the problem almost certainly lives in a single database table called PM20100. And the fix takes about five minutes once you know where to look.

Why Does the Dynamics GP PM20100 Table Cause Check Batch Slowdowns?

To understand the problem, it helps to understand what PM20100 is designed to do. It's a remittance holding table: a temporary staging area where Dynamics GP stores details about which invoices are being paid before printing that information on a check stub. The table was built around an assumption: every payment eventually results in a printed check, and the act of printing clears out the remittance records.
EFT payments broke that assumption. When a vendor payment goes out electronically, GP still creates remittance records in PM20100 exactly the same way it would for a paper check. But because there's no check to print, there's no print event to clear those records out. They just stay there.
The result compounds over time. Every pay cycle adds another batch of remittance records to the table. When your team goes to build a new check batch, GP has to scan through all of them to determine what needs to be included. Fifty records is fast. Three hundred is noticeable. A thousand is the kind of slowdown that sends someone to Google looking for a new ERP system.

What Setting Is Actually Causing the PM20100 Records to Accumulate?

The culprit is a checkbox in the Select Checks window called "Print Previously Applied Documents." When this option is enabled, GP creates remittance records in PM20100 for every payment, whether or not the payment will ever result in a printed document. For check payments, this works correctly because the print event clears the records. For EFT payments, it creates an ever-growing backlog.
Here's what drives me crazy about this: it's entirely silent. No warning, no error, no performance alert. The checkbox is enabled by default, EFT payments are increasingly standard, and the two interact in a way that nobody designed anyone to notice until the slowdown becomes impossible to ignore.

How Do You Fix Slow Dynamics GP Check Batch Processing?

There are two fixes, and you should do both. The first stops new records from accumulating. The second prevents the problem from coming back.
Fix 1: Uncheck the setting during batch creation.
When building your next check batch in the Select Checks window, find the "Print Previously Applied Documents" checkbox and uncheck it. That's the entire fix for new batches. With the setting off, GP stops creating remittance records in PM20100 for your EFT payments. Nothing accumulates; nothing slows down.
Fix 2: Change the default so it stays off.
Unchecking it manually each time works, but it relies on whoever builds the batch to remember. The more durable solution is to change the default in Payables Setup, so the checkbox comes pre-cleared every time. Here's how:

1. Go to Microsoft Dynamics GP > Tools > Setup > Purchasing > Payables.
2. Find the default settings for check processing.
3. Set "Print Previously Applied Documents" to unchecked.
4. Save the change.

Every new check batch will now start with the correct setting automatically. The manual memory requirement is gone.

What If the PM20100 Table Already Has Thousands of Stuck Records?

Changing the checkbox setting prevents new records from piling up, but it doesn't clear the ones already there. If you've been running EFT payments with this setting enabled for months or years, GP is still wading through a backlog every time you build a batch. Fixing the setting helps going forward, but the existing records are still slowing things down.
Clearing stuck PM20100 records requires direct SQL work against the database. Done correctly, it removes only the orphaned remittance records without touching legitimate payment history. Done incorrectly, it can create data integrity problems you don't want. This isn't a task to run from a forum script without understanding what you're deleting.
If you're dealing with significant existing slowdowns after correcting the setting, that's the signal that your PM20100 table needs to be cleaned up by someone who knows the GP data structure. The fix is reliable and not complicated for an experienced GP consultant, but it does require a careful hand.

Is This Problem Worth Fixing on a System Approaching End of Life?

It's a fair question. Microsoft has confirmed that Dynamics GP reaches end of life in December 2029, and many GP customers are somewhere in the process of evaluating migration options. So why invest time in optimizing a system you may be leaving?
The answer depends on your timeline. A well-planned migration from GP to a modern cloud platform typically takes six to twelve months from evaluation to go-live. Organizations that start serious evaluation in 2026 or 2027 are in a comfortable position. Ones that wait until 2028 or 2029 are in a different situation entirely.
In the meantime, there's no reason to tolerate avoidable performance problems in a system your team uses every pay cycle. A five-minute fix that gets check batch processing back to thirty seconds is worth doing regardless of what comes next. Your AP staff shouldn't be losing time to a fixable setting while migration planning runs in the background.
For GP customers thinking through migration options, both Acumatica and Microsoft Dynamics 365 Business Central are worth evaluating. Both are cloud-native, actively developed, and built to handle the payables workflows GP customers rely on.

Frequently Asked Questions About Dynamics GP Check Batch Performance

Does unchecking "Print Previously Applied Documents" affect what prints on EFT remittances?
No. EFT remittances are generated and delivered through a separate process from the check batch creation setting. Unchecking this option affects only whether GP creates records in the PM20100 staging table. Your vendor remittance notifications are not impacted.
How do I know if PM20100 is the cause of my slowdown and not something else?
The clearest indicator is that the slowdown is progressive and correlates with payment volume. If batch creation has gotten slower every month and you're running a significant volume of EFT payments, PM20100 accumulation is the most likely cause. A GP-experienced consultant can query the table directly to confirm record counts and advise on next steps.
Can I clear PM20100 records myself with a SQL script?
Technically, yes. Practically, it depends on your comfort level with GP's database structure and your ability to verify that you're targeting only orphaned remittance records. If you're not certain what you're deleting, reach out to a qualified GP support resource rather than running an untested script against a production database.

Still Dealing with GP Performance Issues?

If your check batch slowdown persists after correcting the setting, or if you want help clearing existing PM20100 records safely, the team at CAL Business Solutions can help. Contact CAL to talk through your specific situation.
CAL Business Solutions is an Acumatica and Microsoft Dynamics 365 Business Central implementation partner serving distribution, manufacturing, brick & block, and professional services businesses across the United States. CAL has supported Microsoft Dynamics GP customers for over 40 years and continues to provide GP optimization, support, and migration planning services.

The post Fix Slow Dynamics GP Check Batches with One Setting appeared first on ERP Software Blog.

Dynamics 365 Finance includes the Subscription Billing module, and for structured, stable transactions it works well: fixed pricing, finalized invoices, stable contract terms, and linear revenue recognition. The limitations show up as billing gets less stable: when contracts change after invoicing, recognition stops being linear, or charges are driven by rules instead of negotiated terms. Here’s where those gaps happen, and how an advanced layer like Advanced Subscription Management (ASM) closes them.

What does D365 Finance’s native Subscription Billing handle well?

Native Subscription Billing is built for structured transactions: fixed pricing, finalized invoices, stable contract terms, and linear revenue recognition. If a business runs standard, predictable subscription contracts that don’t change once invoiced, native billing largely covers it. The gaps appear once billing stops being that stable.

What happens when a contract changes after the invoice is already posted?

This is the first major gap. Native billing assumes finalized invoices, not contracts that keep changing (backdated rate changes, mid-term pricing updates, or invoices that need to be split or rebilled). When that happens, finance teams end up rebuilding schedules manually, making backdated adjustments by hand, and managing credit-and-rebill cycles outside the system, which fragments the audit trail.
An advanced subscription control layer, like ASM, adds amendments on live subscriptions, backdated adjustments, invoice splitting and rebilling, and invoice sequencing, so post-invoice changes are handled with a clean, traceable record instead of manual rework.

Can D365 Finance handle complex or non-linear revenue recognition?

Read the full article.

The post FAQ | Where does subscription billing in Dynamics 365 F&O hit a wall? appeared first on ERP Software Blog.

Accounts payable is one of the few finance processes where the cost is visible to everyone and questioned by almost no one. A team keys invoices. Volume grows. The team grows with it, or the backlog does. Because the work is steady and the people are capable, it rarely reaches an executive agenda until a close slips or a supplier calls about a payment that was never entered.

The decision worth examining is not whether to automate invoice capture. That technology is mature and the case for it is usually straightforward. The harder decision is what happens to the invoices capture cannot clear, because that is where the cost sits and where automation programs quietly underdeliver. DAX Software Solutions works with finance organizations at this point, and the finding is consistent: the keying was never the expensive part.

Where the AP Hours Actually Go

Manual invoice entry has a property that makes it easy to underfund. It is predictable. A clerk keys a known number of invoices in a known number of hours, nothing breaks, and the cost reads as a budget line rather than an incident.

What that line does not capture is everything downstream. Late entry delays the accrual. A mis-keyed purchase order number sends an invoice into a queue nobody owns. A duplicate is paid twice. Early-payment discounts lapse because approval outran the terms. None of these are filed as data-entry costs, and all of them are.

The costs that sit outside the keying line:

• Missed early-payment discounts where approval outran the terms.
• Duplicate or incorrect payments that later require recovery.
• Accrual accuracy that depends on how much of the month's volume was entered in time.
• Supplier relationships managed through exception calls rather than reliable payment.

What Does Invoice Capture Actually Automate?

It automates the reading and creation of the invoice record, not the decision about whether the invoice is correct.

Microsoft's Invoice capture solution for Dynamics 365 Finance uses optical character recognition together with AI Builder in the Power Platform to create vendor invoices from digital invoice images. It reads varying formats from different vendors, applies derivation and validation logic, and lets an accounts payable clerk review and correct captured invoices before they are transferred into Finance. Invoices that pass validation can follow a touchless path without review.

That is a real reduction in typing. It is not the same as a reduction in work, because whether a captured record can proceed depends on matching.

Matching Is Where Invoices Stop

Dynamics 365 Finance supports invoice totals matching, two-way matching of price information against the purchase order, three-way matching that adds quantity against product receipts, and charges matching. Price comparison is configured as either net unit price matching or price totals matching, with tolerance percentages set on the price tolerances page. Results show as passed or failed, with variance detail available on the invoice matching details page.

The point for a finance leader is that all of this is configuration, and the configuration is a policy decision wearing technical clothing. Tolerances set too tight generate exceptions that consume the capacity capture just released. Tolerances set too loose admit variances someone will have to explain later. Set them from the historical distribution of variances rather than from instinct.

Matching also depends on conditions AP does not control. Purchase orders raised without the line detail the invoice will carry, receipts entered late, and a vendor master carrying duplicates all produce exceptions no capture engine can prevent.

The Exception Path Is the Real Design Problem

An exception is not a failure. It is an invoice the system has correctly declined to process without a human decision. The question is whether that decision has somewhere to go.

A usable exception taxonomy separates at minimum:

• Capture exceptions, where the document could not be read reliably.
• Matching exceptions, where the invoice disagrees with the purchase order or receipt.
• Approval exceptions, where the invoice is valid but awaiting a decision.
• Master data exceptions, where the vendor or item record is the problem.

Each type has a different owner and a different fix, named by role rather than by individual. Reported as a single number, they hide which category is growing. That data is also the most useful process-improvement signal AP produces, and it is routinely discarded. A recurring matching failure against one vendor is a contract or purchasing issue. A recurring receipt exception is a warehouse process issue. Automating AP without routing that signal upstream means the same exceptions arrive next month.

Where Humans Still Sit in the Flow

Automation in accounts payable works best when it is explicit about what stays human, and why.

The steps that remain with people, by design:

• Approval of spend above threshold, which is a control rather than an inefficiency.
• Vendor master changes, which are a fraud surface requiring separation of duties.
• Disputed variances, where judgment is the work rather than an obstacle to it.
• Exception triage, where a person decides whether the invoice or the upstream process is wrong.

The aim is not an AP team that touches nothing. It is an AP team that touches the invoices worth touching.

What to Measure Before and After

Automation programs are often evaluated on invoice volume processed, which barely moves and proves nothing. Three measures describe whether anything changed.

The measures worth baselining:

• Monthly invoice volume, separated by channel, since paper, email and electronic invoices behave differently.
• Touch rate, the proportion of invoices requiring any human interaction between arrival and posting, measured before and after.
• Exception rate, the proportion stopping for a decision, broken down by the taxonomy above rather than reported as one figure.

Baseline all three before anything is configured. Without a before, the after is an anecdote.

DAX Software Solutions: Your Partner in Accounts Payable Automation

DAX works with finance organizations to implement accounts payable automation in Dynamics 365 Finance environments, and to design the exception handling that decides whether it pays off. That work starts with the current state of AP volume, data quality and process rather than with a tool.

DAX helps clients:

• Implement OCR accounts payable automation within Dynamics 365 Finance.
• Configure matching policies and tolerances so exception volume is deliberate rather than accidental.
• Design exception taxonomies, routing and human-in-the-loop operating models with governance intact.
• Improve the vendor and purchase order master data that matching depends on.
• Assess readiness before automation is applied to a process that is not yet stable.

Capture applied to a clean process is a substantial gain. Capture applied to a disordered one relocates the work rather than removing it. The difference is decided before the first invoice is scanned.

The post Accounts Payable Without the Data Entry appeared first on ERP Software Blog.