Location was everything. Prime mall space, busy shopping centers, and high-traffic intersections separated the retailers who thrived from the ones who struggled.

Today, the conversation has changed.

Retailers now ask a harder one: What role should our physical stores actually play in the business?

Stores are no longer just places to sell products; they’re fulfillment centers, customer experience hubs, community destinations, and strategic assets bridging in-store and digital commerce.

That shift in retail real estate strategy is not only changing how retailers think about real estate but also how they invest in it.

From retail store expansion to retail store optimization

Growth used to mean opening more stores. Now it means getting more out of the ones you already have.

That can mean closing underperforming locations, remodeling, downsizing to neighborhood formats, or carving out square footage for curbside pickup and prepared foods.

The goal is to make every square foot earn its keep in revenue, customer experience, and efficiency.

Retailers now judge a store on more than sales. Profitability, fulfillment capability, customer demographics, and long-term strategic value all factor into the decisions.

Why stores are becoming multi-purpose business assets

Omnichannel retail has rewritten the store’s job description.

Many physical locations now support services such as Buy Online, Pick Up In Store (BOPIS), ship-from-store, same-day delivery, and returns for online purchases. Rather than operating solely as retail outlets, stores are becoming local distribution centers that help retailers shorten delivery times and improve inventory utilization.

This creates new opportunities as well as new complexities.

A store with modest walk-in sales might be quietly fulfilling hundreds of online orders a week. But if you judge it solely on foot traffic, you might close your most valuable fulfillment hub.

Retailers need a wider lens on store performance that counts what a location does for the whole business, not just what it rings up at the register.

How mixed-use developments are reshaping retail real estate

Redevelopment is reshaping retail real estate, too.

Across North America, aging malls and struggling shopping centers are being reborn as mixed-use developments that blend retail with housing, entertainment, hospitality, offices, healthcare, and gathering spaces.

These aren’t shopping destinations anymore; they’re places people live, work, dine, and socialize.

Foot traffic still matters, but so do demographic shifts, local development plans, residential density, and the neighboring businesses that keep people coming back.

Using data to make smarter retail real estate decisions

Maybe the biggest change is how these decisions are made. Site selection used to run on experience, intuition, and historical sales.

Now retailers have far richer data to work with.

Sales per square foot remains an important metric, but now it is joined by inventory turnover, fulfillment volume, labor efficiency, customer demographics, loyalty activity, basket size, foot traffic analytics, and online purchasing behavior.

Together, those numbers tell a fuller story: the store with “average” revenue might be a top fulfillment hub, while the one with strong sales might be quietly bleeding labor costs.

Better data means better decisions.

Why connected business systems matter

Collecting data is only part of the equation.

The real value comes from connecting information across the business.

When finance, inventory, purchasing, point-of-sale, eCommerce, warehouse, and customer data all reside in separate systems, it’s nearly impossible to see how a single location is really performing.

Integrated ERP and retail management platforms help eliminate those silos by providing a single view of operations.

A modern ERP platform like LS Central brings financial performance, inventory movement, store operations, purchasing, and customer activity into a single environment.

Instead of stitching together reports from five systems, executives can finally see each store’s full financial and operational performance in a single view.

That makes it easier to answer the questions that matter most:

1. Which locations drive the most profit, not just the most sales?
2. Which stores should become fulfillment hubs?
3. Where is inventory turning too slowly?
4. Which locations are best positioned for remodeling or expansion?
5. How do labor costs compare across stores with similar sales volumes?

Answer those, and real estate decisions stop being guesses.

Building a more agile retail real estate strategy

Retail real estate isn’t just about owning or leasing space anymore.

It’s about building a network of physical assets that earns its place through customer experience, efficiency, and long-term profitability.

As shopping habits continue to shift, retailers need technology that keeps pace. Cloud-based systems provide the visibility needed to adapt store formats, optimize inventory, support omnichannel fulfillment, and achieve long-term profitability.

Turn retail real estate into a competitive advantage

By connecting financial, operational, inventory, and customer data, modern ERP and retail management solutions give retailers the insight needed to make more informed decisions about where to invest, where to optimize, and how each location contributes to overall business performance.

If you’re ready to modernize your retail operations, ArcherPoint by Cherry Bekaert can help. We help retailers implement connected business solutions that sharpen visibility, support smarter decisions, and build the operational foundation for long-term growth.

The post Retail Real Estate: From Location to Operational Asset appeared first on ArcherPoint.

Not because I did not know what to say, but because the tool I was using to write it kept breaking mid-sentence. I was running into max compaction errors, “response could not be fully generated” messages, and conversations that stopped dead with no clear explanation and no obvious way to recover what had been in progress.

This has been happening more and more lately. Not because AI is getting worse, but because I am asking it to do more.

Twenty-nine weeks into this journey, I am working inside a Claude Project loaded with every published article from this series, a comprehensive Project Bible containing all my frameworks and voice guidelines, and the accumulated context of everything we have built together. That richness is what makes the work good. It is also what keeps pushing me into limits I cannot easily diagnose.

That is the frustrating paradox of getting better at AI: the more you can do, the more you want to do, and the harder you eventually hit the ceiling.

The ceiling you don’t hit until the work gets real

In Week 1, I asked AI simple questions and was impressed by the answers. I never hit a token limit. I never saw an error message. Everything just worked.

That was not because the limits did not exist. It was because I was not doing enough to find them.

Twenty-nine weeks later, the work looks very different. I am collaborating with AI on complex writing projects that require deep context: the full arc of a 28-week series, the frameworks I have developed along the way, and a specific voice and editorial sensibility that has taken months to refine. I am building organizational tools that need to synthesize evidence against development dimensions. I am running multi-platform research projects that generate hundreds of lines of strategic analysis.

Every one of those activities pushes harder against the limits than anything I was doing in the early weeks, and each one breaks in a slightly different way.

What nobody tells you at the start is that the frustration does not disappear as you build AI literacy. It changes character. Early frustration is about not knowing what AI can do. Later frustration is about knowing exactly what AI can do, but not being able to get there because of constraints you cannot see, cannot diagnose, and cannot always solve by paying for a higher tier.

The black box diagnosis problem

In Week 16, I built a diagnostic framework for process problems, adapted from medical differential diagnosis. The idea was simple: start with a vague frustration, systematically examine People, Process, Technology, and Data, and identify which barrier is actually blocking progress.

That framework works because you can examine the system, ask questions, and get answers that narrow down the cause. Now I am the one with the problem, and my own framework cannot fully help me.

When an AI conversation fails, I get almost nothing useful. Sometimes the conversation stops and produces an error message like “max compaction exceeded” or “response could not be fully generated.” Other times, it just does not finish. When I ask the AI what happened, it cannot really tell me, not because it is refusing, but because the diagnostic information is not available in the chat interface.

Was it the token budget? The context window filling up? Connector overhead? The complexity of the request? Some combination of all of those?

I do not know. More importantly, I cannot easily find out. Not through the chat interface. Not through subscription settings. Not through any tool available to me as a normal user.

That is what makes AI infrastructure problems different from the enterprise software problems I have spent 23 years solving. In Business Central, when a batch posting fails, I usually get an error log, a stack trace, or at least a specific record that caused the failure. I can diagnose the root cause and fix it.

With AI, I often get the equivalent of a check engine light, but there’s no OBD port to plug into.

What I tried and what actually worked

Let me walk through what happened while writing this article, because it illustrates both the problem and the solution.

My first instinct was to continue in the current chat. Sometimes when a response fails, you can ask Claude to continue, and it picks up where it left off. I have used that successfully many times. This time, it did not work. Multiple attempts produced the same result. The conversation had hit a wall it could not get past.

Next, I tried retrying. Claude suggested retrying the last exchange, so I did, and I immediately regretted it. Retry does not simply re-attempt the failed response. It starts over from the prompt that triggered the failure. Everything Claude had generated after that prompt, including partial output from the failed response that I wanted to reference, disappeared. I was now in a worse position than before I retried because I had lost the partial work and gained nothing.

That was the moment I realized I needed a different strategy.

I opened a new conversation within the same Project and asked Claude to review the previous chat so we could pick up where we left off. Sometimes that works because the new conversation inherits the Project context, including files, instructions, and accumulated knowledge, and Claude can search past conversations to find relevant history. In this case, even that approach failed. The new conversation also hit limits before producing meaningful output. The act of searching for and loading context from the prior conversation was itself consuming the token budget I needed for the actual work.

What finally worked was manual context transfer with everything else stripped down.

I turned off every connector I was not actively using. I deleted Project files that were not essential for this specific task. Then I opened a new conversation and, instead of asking Claude to find anything, I explicitly carried forward what mattered: my original prompt, the feedback and partial output I had received before the conversation broke, and the specific documents I wanted Claude to reference.

In other words, I hand-delivered the context instead of asking the system to retrieve it. It was not elegant. It was not effortless. But it worked.

Three tactics that made the difference

I want to be explicit about what I learned because anyone who keeps pushing AI into more serious work will eventually hit similar walls. And if you have not hit them yet, it helps to know these tactics exist before you need them.

The first tactic is to turn off what you are not using.

Every connector and integration you have enabled, including web search, MCP servers, platform tools, or external apps, can consume context at the start of a conversation. Even when you are not actively using them. Even when they have nothing to do with the work in front of you. I had too much turned on by default: tools for Monday.com, MCP servers, web search, and other integrations that were consuming context budget in conversations where I did not need them.

The practical move is simple. Before starting complex work, check what is enabled. Turn off web search if you are not researching. Disable connectors you do not need in the current session. You can always turn them back on later. Think of it like closing background apps when your computer is running slow. It seems obvious once someone points it out, but it is invisible until then.

The second tactic is to explicitly carry context forward.

When a conversation breaks, and you need to continue in a new chat, do not just ask the AI to “reference our prior conversation” and hope for the best. That search-and-retrieve process can consume a meaningful amount of the same context budget you are trying to preserve.

Instead, manually carry forward the pieces that matter. Copy your original prompt. Save any useful output you received before the break, even if it was partial or rough. Load the specific documents you need referenced rather than relying on the system to find them through search. The principle is to minimize what the model has to retrace and maximize what you hand it directly. You know what matters. The system does not.

The third tactic is to design for multiple conversations, not one marathon.

I had been approaching complex work as if it needed to happen in a single continuous conversation. When the conversation broke, I treated that as a failure. But that framing was wrong. Some work needs to span multiple conversations, just as some projects need to span multiple meetings. The skill is not avoiding the boundary. The skill is crossing it cleanly. For complex work, periodically ask the AI to summarize the current state: what has been established, what remains, and which decisions or constraints matter most. That summary becomes your carry-forward artifact if the conversation breaks. Do not wait for failure to create it.

What money fixes and what it doesn’t

Some of these limits respond to a higher subscription tier. More context capacity, more capable models, and faster throughput can genuinely help, especially if you are hitting limits on a free or lower plan. But some limits do not respond to money, at least not at the tiers available to individual users. Without better diagnostic information, you cannot always tell which category you are in before you spend.

I am already on a top-tier subscription and using one of the most capable models available, and I am still hitting walls I cannot fully diagnose. What I have not been willing to do yet is downgrade from my preferred model or turn off extended thinking to conserve capacity. For now, I would rather find workarounds that let me keep pushing the ceiling than lower my ambitions to fit comfortably below it.

That may change, but it is a conscious choice about what I am optimizing for: capability ceiling versus comfort zone.

There is also a structural issue I am watching closely. My Project Bible, which is the compressed summary of 28 weeks of articles, frameworks, and context, is itself growing. It replaced loading individual articles, which was a major improvement. But at some point, even the Bible may exceed what fits comfortably in a context window alongside actual work.

My understanding is that Anthropic’s platform currently switches from loading all Project files directly into the context window to a retrieval-based approach only when the files are too large to load entirely. A better default would be retrieval-based from the start: load what is relevant rather than loading everything. I am hoping that architectural change arrives before my Project Bible forces the issue.

The deeper pattern

The pattern I keep coming back to is that constraints are the teacher.

I would not have learned about connector overhead if my conversations had not been breaking. I would not have developed a manual context transfer protocol if the automated one had worked reliably. I would not have started designing for multi-conversation workflows if single conversations always succeeded.

That does not mean I am romanticizing the limitations. Some of these are genuine product gaps, and the lack of diagnostic information is the most obvious one. Better error messages, accessible telemetry, and clearer feedback about what is consuming context would make all of this easier.

I hope those improvements come.

But waiting for perfect tooling is exactly the trap I have been writing about since Week 19. The tools are not perfect, and they are not going to be perfect next quarter either. The question is whether you develop the literacy to work with what exists, including its constraints, or wait for those constraints to disappear.

In Week 13, I hit the infrastructure wall for the first time and discovered that the gap between an AI demo and AI production is enormous. In Week 17, I built a context architecture using Projects, bounded contexts, and a three-layer system to work within those constraints. This week, I learned that even well-designed architecture still needs a recovery protocol for when things fail anyway.

That is infrastructure literacy growing in real time. Not theoretical understanding, but operational resilience built from direct experience with failure.

And underneath all three tactics is a principle that connects to something I have been saying since the beginning of this series: you cannot delegate context management to the platform any more than you can delegate AI literacy to a vendor or career development to a manager.

For now, the most reliable path is the one where you carry the context forward yourself.

Because you know what matters, and the system does not.

Your Week 29 challenge: Build your recovery protocol

You may not be hitting these limits yet. But if you keep building AI literacy and pushing your AI work forward, you probably will. The time to build a recovery protocol is before you desperately need one.

Start by testing your recovery options. Take a moderately complex task, let it run for a while, then deliberately start a new conversation and try to continue. What survives? What gets lost? What does the AI remember, and what do you have to provide again? Understanding that boundary before you are frustrated changes everything.

Next, audit what is consuming your context budget. Look at the connectors, integrations, and tools loaded in your AI environment. Which ones are you actively using right now? Which ones are passively consuming space? Turn off what you do not need for the current session.

Then practice the carry-forward. Before closing any meaningful working session, copy your key prompts and the AI’s most important output somewhere accessible. Build the habit before you need it. Your future frustrated self will thank you.

Also pay attention to what you cannot diagnose. The next time something does not work the way you expected, notice what information you wish you had. Can you tell why it failed? Can the AI tell you? What are you guessing, and what do you actually know? That gap between what you need to diagnose and what you can access is the frontier of infrastructure literacy.

Finally, decide what you are willing to trade. Every limit has potential workarounds: simpler models, shorter context, fewer features, or less ambitious tasks. Knowing which tradeoffs you are willing to make, and which ones you are not, is itself a form of strategic clarity.

The bottom line

Twenty-nine weeks in, I am doing things with AI I could not have imagined when I started. I am also more frustrated than I have been since the beginning.

Those two facts are not contradictory. They are causally linked.

The early weeks were about discovering what AI can do. These weeks are about discovering what happens when you push hard enough to find the edges. Those edges are not clean, well-documented, or easy to understand. The system often will not tell you where they are until you have already crossed them, and it may not tell you why you crossed them even afterward.

But I know something now that I did not know in Week 1: the constraints are not obstacles to the journey. They are part of it.

Every limit I have hit has forced me to understand something about how these tools actually work, not theoretically, but operationally. That operational understanding is what separates someone who uses AI from someone who can work with it reliably enough to build real things.

The frustration is with the curriculum. The recovery protocol is the homework. And the growing capability, despite the constraints and because of them, is evidence that the learning is working.

This post is part of my “AI Over 40” series. It first appeared on LinkedIn: AI for the Over 40 [Week 29]: When Getting Better Makes Everything Harder.

Read more AI and Copilot blogs.

The post AI for the Over 40 – Week 29: AI Context Management: What Happens When You Hit the Ceiling appeared first on ArcherPoint.

The trouble is that most retail technology wasn’t built to handle this level of complexity. Legacy POS systems, disconnected inventory tools, siloed financials, and manual processes make it hard to see what’s happening across the business, react quickly, or deliver the experience today’s shoppers expect.

Modern grocery retailers need more than a POS system. They need a unified retail platform that connects inventory, loyalty, finance, self-checkout, eCommerce, and store operations. LS Central, built on Microsoft Dynamics 365 Business Central, provides that foundation in a single solution.

That need is one reason LS Retail was recently recognized as a Major Player in the 2026 IDC MarketScape for Worldwide POS Software in Grocery and Food Store Retail.

Why IDC recognized LS Central as a major player in grocery retail software

Grocery retailers face plenty of competing claims from software vendors, which is why independent analyst evaluations matter. IDC MarketScape is one of the most respected industry assessments, built on extensive research, customer interviews, product analysis, and vendor evaluations, with vendors scored on both current capabilities and future strategy.

For the 2026 grocery and food store retail POS evaluation, IDC focused on what’s increasingly critical for modern food retailers: omnichannel capabilities, AI and Copilot readiness, loss prevention, payment innovation, and the ability to support multiple markets and regions.

The report highlights an important shift across the grocery industry, as IDC Retail Insights Research Manager Filippo Battaini explains:

“Grocery POS is no longer a checkout technology; it is the operational core of the modern store. The vendors that are pulling ahead have built open, composable platforms in which AI, loss prevention, payments, and food service capabilities converge on a shared foundation, giving retailers the freedom to build differentiated experiences without being constrained by their technology stack.”

What grocery retailers actually need from their retail software

For many grocery retailers, technology decisions have historically been made one system at a time: a POS for transactions, a separate solution for inventory, an accounting platform for financials, and often yet another platform for loyalty. Over time, this patchwork has made operations harder to manage.

Today’s retailers need a different approach — one platform that connects operations across the business while supporting the unique requirements of food retail. This is where LS Central stands out.

Built on Microsoft Dynamics 365 Business Central, LS Central combines retail operations, inventory management, point-of-sale, loyalty, eCommerce, and financial management in a single platform. Instead of integrating disconnected applications, retailers operate from a single data foundation, providing real-time visibility across stores and departments, resulting in greater efficiency, more accurate information, and faster decision-making.

Grocery-specific features that help reduce complexity

LS Retail’s IDC recognition reflects its ability to address grocery-specific needs. Managing perishables, for example, requires more than standard inventory tracking — retailers need to monitor expiration dates, reduce spoilage, and keep product moving efficiently through the supply chain. LS Central’s best-before date tracking helps stores manage that inventory while reducing shrinkage and waste.

The platform also supports mobile self-scanning via ScanPayGo, letting shoppers scan items as they shop and check out faster, easing labor pressure while meeting customer expectations for speed and service. Integrated self-checkout adds further flexibility, helping stores improve throughput and reduce bottlenecks at the register.

Electronic Shelf Label integrations keep pricing consistent and reduce the labor required to manually update tags, helping retailers manage frequent promotions and large assortments. Mobile inventory tools let store associates perform counts and check stock directly from handheld devices, improving accuracy and saving time.

Together, these capabilities help grocery retailers run more efficiently while delivering a better customer experience.

How AI is changing grocery store operations

Artificial intelligence is quickly becoming a practical tool for retailers, not just a future concept. Because LS Central is built on Microsoft technology, grocery retailers can tap into innovations like Microsoft Copilot and Microsoft Fabric.

Copilot lets users interact with data more naturally and accelerate routine tasks. For example, managers can use conversational prompts instead of digging through reports. Microsoft Fabric extends this by bringing data, analytics, and business intelligence into a single environment, giving retailers deeper visibility into sales trends, inventory performance, customer behavior, and operational efficiency.

A scalable grocery retail software platform for future growth

One challenge many retailers face is balancing today’s needs with future growth. Some platforms are too limited and require replacement as the business expands, while others add unnecessary complexity and cost from day one.

LS Central’s modular architecture addresses this. Retailers can start with what they need today and add functionality as requirements evolve — whether that’s e-commerce, self-service technology, loyalty programs, or advanced analytics — without creating a disconnected environment. That flexibility lets organizations modernize at their own pace while protecting their technology investment.

Why choosing the right LS Central partner matters

Even the best software can’t deliver value without a successful implementation. Technology projects succeed when software, process, people, and business goals are aligned, which is why the right implementation partner matters as much as the right platform.

As a certified LS Retail partner and Microsoft Dynamics 365 Business Central partner, ArcherPoint by Cherry Bekaert helps grocery retailers plan, implement, integrate, and support their retail technology environments from strategy and rollout through training, optimization, and ongoing support. ArcherPoint’s focus on North American retailers provides additional value through an understanding of the market, regulatory requirements, and operational challenges specific to grocery and food retail organizations.

That expertise has been recognized industry-wide. ArcherPoint was recently named a 2026 LS Retail Diamond Partner, reinforcing our position as a trusted advisor for retailers looking to modernize operations and improve performance.

Building a connected grocery retail operation

The modern grocery store doesn’t need another point-of-sale system; it needs a connected platform that supports inventory management, perishables, self-service technology, loyalty programs, financial visibility, and data-driven decision-making. LS Retail’s recognition as a Major Player in the 2026 IDC MarketScape underscores the importance of a unified platform.

For grocery retailers looking to modernize, improve visibility, and deliver a better customer experience, LS Central offers a strong foundation for growth.

Ready to modernize your grocery operations?

ArcherPoint helps grocery retailers implement and optimize LS Central and Microsoft Dynamics 365 Business Central to improve efficiency, reduce complexity, and create a stronger foundation for growth.

Contact ArcherPoint by Cherry Bekaert today to see how LS Central and ArcherPoint can help modernize your grocery retail operations.

The post Why Grocery Retailers Choose LS Central…and Why IDC Agrees appeared first on ArcherPoint.

If you’re planning a move from Microsoft Dynamics GP to Microsoft Dynamics 365 Business Central, one question always comes up: What do we do with all those years of Dynamics GP data? Do we move it over? Do we archive it? Do we just keep the old system around “just in case”?

I spent 20+ years as a Dynamics GP consultant in a previous life, and I’ve helped a lot of businesses successfully migrate to Business Central. So I’ve seen how this decision plays out — and I want to share some honest insights on each option, because every approach has its pros and cons.

Should you move GP data into Business Central at all?

Unless you have a regulatory requirement to do so, I generally wouldn’t recommend migrating your historical Dynamics GP data directly into D365 Business Central. I’ve done it a handful of times, so I know it’s possible — but it can be painful and expensive, especially when it comes to reconciling everything.

A few things are worth thinking through before you go down this road:

• Data translation. GP and Business Central are structured differently, so the data has to be mapped and translated. That work adds up.
• Data cleanliness. Is your historical data actually clean? Migrating messy data just moves the mess into a brand-new system.
• Relevance. Does that old data still make sense for the way you report today? Sometimes, years-old records add noise rather than value.

There are tools out there that can move historical data into Business Central, and I’d encourage you to research them carefully. A few details about how they handle the data stand out to me as things worth a closer look before you commit.

The upside, of course, is that once the data lives in your Business Central environment, it’s much easier to query and report on alongside your current data — no jumping between systems.

The simple (and cheap) option: keep GP running

One of the easiest options is to keep a computer with your SQL database and the Dynamics GP application on it, tuck it away, and turn it on whenever you need to look something up. It’s the least expensive route, but it’s also the most inconvenient — and it does mean maintaining aging hardware and software you’ll need to keep secure.

Moving GP to the cloud (Azure or AWS)

You can also move the SQL database and Dynamics GP environment to Azure or AWS. This makes the data a little easier to access and generally safer than a box in a closet. Just be careful with operating system versions — older versions of SQL Server and Dynamics GP aren’t always supported on newer OS releases, so you’ll want to confirm compatibility before you migrate.

The best-of-both-worlds option: archive to Azure Data Lake + query inside BC

This is the approach I tend to like most. (For the record, I’m not affiliated with eOne — but their PopDock tool is a good example of how this works.)

The idea is that an add-on or standalone application pushes your historical GP data, via a fairly simple wizard, into Azure Data Lake, which offers relatively cheap storage. Then a query tool — built by the same folks behind SmartList Builder — sits inside D365 Business Central (or runs as a standalone app) and lets you combine and query data from the Azure Data Lake alongside your live Business Central data.

So, for example, a customer transaction list could show your historical Dynamics GP data (pulled from the Data Lake) and your current Business Central data together in one view, with a column marking where each record came from. It’s a really handy way to get historical context without cramming all that old data into your new system.

The trade-offs: there’s a cost for both the Azure Data Lake storage and the PopDock application, and I’ve heard some concerns about query performance when you’re pulling very large volumes of data. Worth testing with your own data volumes before you rely on it.

So what’s the right answer?

As with every solution, there’s no one-size-fits-all here. Each option carries its own pros and cons, and the right choice comes down to what matters most to your business — cost, convenience, compliance, or reporting.

If you’d like to talk through the best option for your Dynamics GP historical data, reach out to ArcherPoint. We’re always happy to help you weigh the options.

The post Moving From Dynamics GP to Business Central? Here’s How to Handle Years of Historical Data appeared first on ArcherPoint.

In recent years, that balancing act has grown considerably more demanding. Supply chain disruptions, labor shortages, rising transportation costs, heightened food safety requirements, and rapidly shifting customer expectations have introduced a level of operational complexity that many distributors have not encountered before.

For executives, operations leaders, and finance teams, the challenge is no longer just about moving product from supplier to customer. It is about maintaining real-time visibility and control while protecting margins and building a foundation for sustainable growth.

Modern food distribution ERP systems address these pressures by unifying inventory, finance, operations, and supply chain data within a single connected platform. Below, we examine the most significant challenges facing food distributors today and how purpose-built ERP functionality delivers practical, measurable solutions.

1. Managing supply chain disruptions in food distribution

Food distributors operate in an environment where disruptions carry immediate consequences. Delayed shipments, supplier shortages, weather-related events, transportation bottlenecks, and unpredictable demand swings can affect product availability and customer service levels with little to no warning.

Unlike manufacturers, which have weeks or months to adjust production schedules, distributors often work on compressed timelines. When inventory is unavailable, both revenue and customer relationships are at risk.

Distribution leaders need timely, accurate information across inventory availability, supplier performance, inbound shipments, demand trends, and purchasing requirements. Without that visibility, organizations become reactive, responding to problems after customers have already been affected. The ability to anticipate disruptions early and act on reliable data has become a measurable competitive advantage.

Business Central Solution: Business Central provides real-time purchase order tracking, demand forecasting, and supplier lead time visibility — all within a single platform. Planners can monitor inbound shipments, evaluate alternate vendors, and trigger replenishment workflows before stockouts occur. Inventory availability is visible across locations, giving procurement and operations teams the information they need to respond quickly and confidently.

2. Improving inventory management without increasing costs

Inventory represents one of the largest assets on a food distributor’s balance sheet — and one of the most difficult to manage effectively. Many products carry limited shelf lives, meaning excess inventory does not simply become obsolete; it becomes unsellable, resulting in direct financial losses. Too much inventory increases storage costs, consumes warehouse capacity, and ties up working capital. Too little results in stockouts, missed revenue, and dissatisfied customers.

This creates a constant balancing act. Distributors need accurate demand forecasting, real-time visibility into inventory movement, and the ability to make purchasing decisions based on current conditions rather than historical assumptions. As product portfolios expand and customer expectations evolve, sustaining that balance without modern, integrated technology becomes increasingly difficult.

Business Central Solution: Business Central delivers integrated demand forecasting, item replenishment planning, and real-time inventory valuation. With lot tracking and expiration date management built in, distributors can enforce first-expired, first-out (FEFO) picking strategies to reduce waste and protect margins. Reorder point alerts and automated purchase suggestions ensure procurement teams stay ahead of demand without overstocking.

3. Reducing transportation costs while maintaining service levels

Transportation has become one of the largest operational expenses for food distributors. Fuel costs fluctuate unpredictably. Driver shortages persist across most markets. Equipment maintenance expenses continue to climb. And customer delivery expectations continue to accelerate.

Customers increasingly expect faster delivery windows, greater shipment visibility, and consistent on-time performance. The combination of rising costs and rising service expectations compresses already narrow margins.

Distributors need complete visibility into warehouse operations, inventory availability, and route efficiency to assess customer and order profitability accurately. What appears to be a profitable customer relationship on paper can look very different once transportation and service costs are fully allocated. Organizations that connect operational and financial data are far better positioned to make informed decisions about pricing, route design, and service commitments.

Business Central Solution: Business Central connects sales order management, warehouse operations, and financial reporting within a single environment, enabling distributors to evaluate the true cost to serve at the customer and order level. Integration with transportation management systems (TMSs) provides end-to-end visibility into freight costs. Shipping and logistics costs can be tracked against each order, giving finance and operations teams the information they need to price accurately and manage delivery profitability.

4. Addressing labor shortages through automation and real-time visibility

Labor shortages and rising wage pressures continue to affect every facet of food distribution, from warehouse operations to delivery, planning, inventory management, and customer service. Recruiting and retaining qualified personnel remains difficult across most markets, and that challenge is not expected to ease in the near term.

The issue extends beyond headcount. Many organizations still depend on spreadsheets, disconnected systems, and manual data entry, requiring employees to spend time gathering information, resolving discrepancies, and managing exceptions that should be handled automatically. As labor becomes more expensive and harder to source, the cost of operational inefficiency increases proportionally.

Distributors that can streamline workflows, reduce manual touchpoints, and equip their teams with accurate information on demand are better positioned to maximize the productivity of their existing workforce.

Business Central Solution: Business Central eliminates manual handoffs and redundant data entry through workflow automation, role-tailored dashboards, and real-time exception alerts. Warehouse staff benefit from directed put-away and pick workflows that reduce errors and improve throughput. Approval workflows for purchasing, pricing, and credit reduce administrative burden on management. And because Business Central integrates natively with Microsoft 365 — including Teams, Outlook, and Excel — employees can access the information they need directly within the tools they already use without switching systems.

5. Improving food safety, traceability, and regulatory compliance

Regulatory compliance has always been a non-negotiable requirement in food distribution, but traceability has become an operational priority that extends beyond regulatory obligations. Customers, retail partners, and auditors increasingly expect distributors to demonstrate end-to-end product accountability.

Distributors must be prepared to respond quickly and accurately to product recalls, supplier inquiries, regulatory audits, and customer documentation requests. The ability to identify where a product originated, how and where it was stored, and where it was shipped is no longer a best practice — it is a baseline expectation.

As supply chains grow more complex and sourcing relationships span multiple vendors and geographies, maintaining accurate traceability records becomes significantly harder when that information lives across disconnected systems or in manual records.

Business Central Solution: Business Central includes robust Item Tracing functionality that supports both origin-to-destination and destination-to-origin traceability, enabling distributors to trace any item or lot forward through the supply chain to its final delivery point or backward from a customer complaint to the original vendor shipment. Item tracking is configurable at the serial-number or lot-level. Distributors can capture vendor-specific information alongside internal business-process identifiers, allowing them to maintain their own unique inventory identification practices while preserving full vendor traceability. In the event of a recall or audit, Business Central can generate a complete chain of custody, from inbound receipt through warehouse handling to outbound shipment, in minutes.

6. Why real-time financial visibility matters in food distribution

One of the most persistent challenges in food distribution software is measuring profitability in real time. Commodity prices shift frequently. Transportation expenses vary by lane, carrier, and season. Inventory carrying costs fluctuate with volume and storage conditions. Without timely financial visibility, management teams make critical decisions based on outdated information.

Many distributors still rely on month-end closing cycles that confirm what happened in the past, not what is happening right now. Finance teams are increasingly asked to move beyond historical reporting and actively support operational decision-making with forward-looking, real-time data.

Leaders want to understand customer profitability, product margin contribution, inventory carrying costs, and operational performance on demand—not 30 days after the fact. The ability to connect operational data with financial outcomes is becoming a defining characteristic of high-performing food distributors.

Business Central Solution: Business Central eliminates the gap between operational activity and financial reporting. Inventory transactions, purchase orders, sales orders, and warehouse movements are posted directly to the general ledger in real time, so financial statements reflect current operations, not last month’s activity. Dimensions and cost accounting features allow finance teams to analyze profitability by customer, product line, warehouse location, or business segment without running separate reports or waiting for period-end consolidations. Power BI integration provides interactive dashboards that put margin, cost, and performance data directly in the hands of decision-makers.

Building a more resilient food distribution operation

The food distribution industry will continue to face pressure from evolving customer expectations, supply chain volatility, labor market challenges, and expanding regulatory requirements. The organizations that succeed will be those that can act on accurate information, respond to disruption quickly, and maintain visibility across every dimension of their operations.

Microsoft Dynamics 365 Business Central is a modern, cloud-based ERP purpose-built to address these challenges. By connecting finance, inventory, purchasing, warehousing, sales, and supply chain processes into a single, unified platform, Business Central provides food distributors with the operational and financial visibility they need to protect margins and support growth.

Because Business Central is part of the Microsoft ecosystem, distributors can extend its capabilities through Microsoft 365 (Teams, Outlook, Excel) and the Power Platform (Power BI, Power Automate, Power Apps). Business Central also integrates with most modern business applications, including CRM, WMS, payroll, and TMS systems, creating a connected operating environment that improves collaboration and decision-making across the organization.

Technology alone does not solve every challenge, but the right platform provides the foundation for managing complexity, making better decisions, and building a distribution operation that is both resilient and profitable.

Ready to learn more? Contact ArcherPoint by Cherry Bekaert to explore how Microsoft Dynamics 365 Business Central can help your distribution operation manage today’s challenges and position for tomorrow’s growth. Visit our case study on Nissin Foods USA to see real-world results in food distribution.

The post The Biggest Challenges Facing Food Distributors – And How Business Central Helps Solve Them appeared first on ArcherPoint.

Performance reviews. Strategic planning cycles. Compliance training. Budget reconciliation rituals. The annual or recurring processes that consume enormous time and energy while everyone involved quietly acknowledges they are not producing what they are supposed to produce.

We complain about them. We roll our eyes. We go through the motions. Then we do it all again next year, often in almost exactly the same way.

Last week, I shared the paradigm shift behind the AI career development system I started building: what if performance evidence was collected by you throughout the year instead of about you at year-end? This week, I want to share what happened when I actually tried to build it.

The implementation taught me lessons at two levels. There were practical insights about building AI tools for organizational use, but there was also a broader realization about why we accept broken processes as permanent in the first place.

The tax we’ve all agreed to pay

Performance management at most organizations is a tax.

I do not mean that metaphorically. It is a real cost: hours multiplied by people multiplied by fully loaded labor rates. In my organization alone, the annual process consumes thousands of hours across Career Advisors and advisees.

If that investment consistently produced what it was supposed to produce, such as genuine development, fair evaluation, motivated employees, and better career conversations, it would be worth every hour. But most of us know it does not work that way, at least not consistently or reliably.

Instead, we get the year-end scramble. The reconstructed accomplishments. The carefully crafted language is designed for an audience rather than for reflection. The ratings that can feel like conclusions in search of justification.

I covered the philosophy last week: the paradigm inversion, the “Start at Developing” principle, and why accountability needs to shift more toward the individual. This week is about what happened when that philosophy met reality.

What building taught me

I spent the better part of a week creating an AI-powered career development system and most of a weekend debugging it. What I learned went well beyond performance management.

The first thing I ran into was the gap between an elegant idea and a messy reality. My original design assumed Microsoft’s Custom Copilot Studio agents could search email and Teams data the same way M365 Copilot does. They could not, at least not with my licensing, in my environment, at the moment I was building. I spent hours designing toward a capability that was theoretically possible, but not actually available to me.

That distinction matters. Infrastructure literacy is not just knowing what the technology might be able to do someday. It is knowing what is available to you right now, with your current tools, licenses, policies, and constraints.

Once I realized seamless automation was not going to work, I had to redesign the system. Evidence collection would happen through M365 Copilot, which had the search capabilities I needed, while the coaching and analysis layer would run in a separate approved LLM.

At first, that felt like a compromise. But the more I worked with the design, the more it started to look like an improvement.

The separation meant that advisees had to review their evidence before analysis. They could add context that the AI missed, remove noise, and understand what was happening, rather than trusting invisible magic. It also meant the analysis layer was not locked to a single platform, so an organization could use whichever approved LLM best fit its environment.

In other words, the compromise produced a system that was more trustworthy and flexible than my original seamless vision probably would have been.

Moving from prototype to production

The next lesson came when I moved from prototype thinking to production thinking. When I tested the same prompt with different LLMs, I got wildly different outputs. Dimension names varied. Template structures changed. Critical checkpoints were skipped. For personal use, that kind of variability is annoying. For organizational deployment, it is a dealbreaker.

If advisees are producing reports with different terminology and inconsistent formats, the system creates confusion rather than clarity. Making AI reliable for repeatable use required prompt engineering that felt almost comically explicit. It was not enough to say, “Use the official dimension names from the framework.” I had to embed the exact names in a table and add language like, “Do not rename these dimensions, create practical buckets, or substitute alternative categories.”

Back in Week 8, I wrote about conversational, human-centered prompting and treating AI as a collaborator rather than a code executor. That approach still works beautifully for exploration and ideation. But production workflows need something different. They need explicit constraints, embedded definitions, verification checklists, and enforcement language.

Both approaches are valid. The mistake is assuming one prompting style works for every use case.

The final lesson came from early user feedback. Some advisees testing the system said, “This is really cool.” That was nice to hear, but novelty fades quickly. The more important feedback was, “It has helped me think about my work in a different way and how it connects to different development dimensions.”

That second reaction matters because it points to value. Advisees were not just impressed by the tool. They were seeing their own work through a development lens and building awareness that they could bring into monthly conversations with their Career Advisors.

“Cool” does not justify the investment. “This changes how I think about my work”, does.

The broader pattern

Each of those lessons applies to anyone building AI tools for team use rather than personal productivity. Platform realities matter. Constraints can improve design. Production consistency requires more rigor than prototypes. And the real measure of value is not whether people are impressed, but whether the tool changes how they think or work.

But building this system also surfaced something I had not expected: a question about why it took me so long to try. I almost did not build it. Not because it was technically difficult. Not because I lacked the skills. I almost did not build it because I had accepted, like everyone else, that performance management was simply what it was.

A tax we pay. A process we comply with. An annual ritual we endure.

The only reason I built something different is that I finally did the math on the cost and could no longer justify continuing to pay it for something that was not working. That made me wonder how many other “required” activities we are accepting without question.

The weekly status reports nobody reads. The approval workflows that add days without adding value. The compliance processes designed for auditability rather than actual compliance. The meetings that exist because they have always existed.

We complain about all of them. We feel powerless to change them. And often, that feeling of powerlessness is wrong.

What makes “required” feel unchangeable

I have been thinking about why broken processes can feel so permanent. Sometimes it is because someone else designed them. The process came from HR, Legal, Corporate, Finance, or “the system,” and challenging it can feel like challenging authority. Even when the process is clearly flawed, it feels safer to comply than to question. Sometimes the issue is that the cost is distributed. No single person bears the full burden. Everyone loses a little time, so nobody owns the total cost. Death by a thousand cuts does not feel like death until someone adds up the cuts.

Improvement can also feel presumptuous. Who am I to redesign performance management? Who am I to question the compliance process? Who am I to change the approval workflow? It is easy to convince ourselves that our job is to participate, not to redesign.

The switching cost can also seem higher than the status quo cost. Learning something new, getting buy-in, managing change, and handling resistance all feel harder than just doing the same thing again.

And finally, we normalize the frustration. We complain about the process for so long that complaining becomes the response. We confuse acknowledging the problem with addressing it.

Every one of these barriers is real. But none of them automatically means the process is unchangeable.

The question worth asking

The question is not, “How do I make this required activity less painful?”

That question accepts the activity as given and optimizes around the edges. It might lead to a better form, a cleaner template, a shorter meeting, or a slightly improved workflow. Those improvements can help, but they rarely change the underlying experience.

A better question is, “What would this look like if it actually worked?”

That question challenges the premise. It creates space for redesign instead of refinement. It forces you to define the outcome the process was supposed to create before you start improving the mechanics.

When I asked that question about performance management, the answer became much clearer. Evidence would be collected continuously rather than reconstructed annually. The trajectory would be visible to the advisee throughout the year rather than revealed at the end. Development conversations with Career Advisors would be driven by insight rather than obligation.

The technology to enable that already exists. The real barrier was not capability. It was the assumption that meant unchangeable.

Your Week 28 Challenge: Audit your required activities

This week, look at the mandatory processes you participate in and identify the organizational taxes you have been quietly paying.

Start by making a list. What are the required activities that consume significant time without producing proportional value? Performance reviews, status reporting, approval workflows, compliance rituals, recurring meetings, budget processes, planning cycles, or anything else that fits your context.

Then pick one and do the math. Choose the process that frustrates you most and calculate the real cost. How many people participate? How much time does each person spend? How often does it happen? What is the organization actually investing?

Once you see the cost, ask what “actually working” would look like. Do not start with incremental improvement. Ask what the process would feel like if it delivered the outcome it was supposed to deliver. What would participants experience differently? What decisions would be better? What value would be created?

Then notice where you feel powerless. What is stopping you from building toward that better version? Is it technical capability? Authority? Buy-in? Risk? Or is it simply the assumption that because the process is required, it cannot be changed?

Finally, challenge one assumption. Do not start with “redesign performance management.” Start with something smaller, like, “What if I tracked my own development evidence for a month and saw what that revealed?” The goal is to begin where you have control.

You do not need to fix every broken process this week. You just need to notice how many processes you have been accepting as unchangeable that are actually just unchanged.

The Bottom Line

I spent a week building an AI career development system. Along the way, I learned about platform limitations, constraint-driven design, production prompt engineering, and the gap between prototype and deployment. Those lessons will shape how I approach the next organizational AI tool I build.

But the deeper lesson was how long I had been complaining about performance management without seriously questioning whether I could change it. For years, I treated “required” as if it meant “permanent.” It was easier to participate and criticize than to build something better.

AI did not give me permission to redesign a broken process. It gave me the capability. The permission was always mine to take.

What required activity have you been treating as unchangeable? What would it look like if it actually worked? And what is really stopping you from building toward that: capability, authority, or assumption?

The things we are required to do do not have to stay the way they are. Someone designed them. Someone can redesign them. Why not you?

This post is part of the “AI Over 40” series. It first appeared on LinkedIn: AI for the Over 40 [Week 28]: When “Required” Doesn’t Mean “Unchangeable”

Read more AI and Copilot blogs.

The post AI for the Over 40 – Week 28: When “Required” Doesn’t Mean “Unchangeable” appeared first on ArcherPoint.

Boltrics 3PL Software System for Microsoft Dynamics 365 Business Central includes Status Templates and Status Steps that help standardize warehouse processes while supporting automation and accountability.

In this walkthrough, Daniel Feltham-Lauzon demonstrates how status steps work within Boltrics, how they can be used as checklist items during warehouse operations, and how they can trigger automated actions such as overage, shortage, and damage notifications.

What are status steps in Boltrics?

Status steps are configurable actions that support warehouse workflows as documents progress through various statuses.

A status step can serve as:

• A required checklist item
• A trigger for automated processes
• A method for documenting completed tasks
• A control point within a warehouse workflow

Because status steps are tied to status templates and status processes, organizations can create standardized procedures that help ensure critical tasks are completed consistently.

Understanding status templates and status processes

Boltrics uses status templates to define the progression of documents through operational workflows.

Within each status, administrators can assign one or more status steps that users must complete or acknowledge as part of the process.

For example, when a receipt reaches a Received status, warehouse personnel may be required to:

• Verify quantities
• Check for damages
• Document exceptions
• Send customer notifications

This structure helps create repeatable operational procedures across warehouse teams.

Using status steps as checklist tasks

One of the simplest uses for status steps is as a digital checklist.

Rather than relying on memory or paper-based procedures, warehouse users can complete designated tasks directly within the system.

Examples might include:

• Inspecting inbound freight for damage
• Verifying pallet labels
• Confirming packaging requirements
• Reviewing customer-specific receiving instructions

These checklist-style steps improve process consistency while creating an auditable record of completed actions.

Automating warehouse notifications

Status steps can also trigger automated workflows.

In the video, Daniel demonstrates how a status step can generate an OSD (Overage, Shortage, and Damage) email.

Using configured templates, Boltrics can:

• Pull information from warehouse receiving documents
• Populate email content automatically
• Notify customers or stakeholders about receiving exceptions
• Reduce manual communication effort

This capability helps warehouse teams respond more quickly when discrepancies occur during receiving.

Tracking activity through the status log

Every completed status step is recorded within the status log.

The log provides visibility into:

• Which steps were completed
• When they were completed
• Which user performed the action
• The overall progression of the workflow

This creates accountability while providing supervisors and administrators with a clear audit trail of warehouse activities.

Associating functions with status steps

A single status step can perform multiple actions.

Administrators can associate functions that:

• Trigger notifications
• Update workflow statuses
• Launch automated processes
• Support exception handling procedures

Because multiple automations can be linked to a single step, organizations can streamline complex workflows without requiring additional manual intervention.

Creating a new status step

The video also walks through the process of creating a new step from scratch.

This includes:

1. Creating a new step code
2. Defining the step description
3. Assigning functions and automations
4. Associating the step with a status
5. Initializing the step on existing documents
6. Testing the workflow

Daniel demonstrates this process by creating a Check Damages step and adding it to the Received status.

This provides a practical example of how warehouse teams can extend existing workflows to support operational requirements.

Status changes versus step-triggered automations

An important distinction in Boltrics is the difference between status changes and status step actions.

A status change controls where a document sits within a workflow.

A status step controls what happens within that status.

This separation provides flexibility by allowing organizations to:

• Maintain consistent workflow structures
• Add new operational requirements
• Introduce automation without redesigning status processes
• Adapt workflows to customer-specific needs

As warehouse operations evolve, this flexibility can significantly reduce administrative effort.

Bringing it all together

Status templates and status steps are powerful tools for managing warehouse workflows in Boltrics 3PL Software System.

By combining checklist tasks, workflow controls, automated notifications, and audit logging, organizations can create more structured and repeatable warehouse processes.

For 3PL providers and warehouse operators using Microsoft Dynamics 365 Business Central, status steps offer a practical way to improve process control, support compliance requirements, and automate critical operational tasks without adding unnecessary complexity

The post How to Create Status Templates and Steps in Boltrics 3PL for Business Central appeared first on ArcherPoint.

The Dynamics 365 Business Central community, consisting of developers, project managers, and consultants, collaborates across various platforms to share valuable insights. At ArcherPoint, we greatly value their dedication and expertise. To ensure widespread access to this technical knowledge, we created Developer Digest.

Using AL MCP Server with CLI agents

The AL MCP Server is a command-line tool packaged within ALTool that exposes core Dynamics 365 Business Central AL development capabilities directly to autonomous AI coding agents and command-line interfaces (CLIs). The server implements the open-standard Model Context Protocol (MCP) and serves as a standardized bridge, enabling your LLM-driven CLI agent to interpret and act on your AL workspace.

It allows agentic tools to build, compile, perform diagnostics, and publish AL extensions without requiring the full Visual Studio Code desktop interface. This can be useful when automating various AI scenarios, such as CI/CD pipelines, chat-based agent workflows, and AppSource validation.

Several blogs that cover the practical application of this feature are worth checking out:

• Stefano Demiliani’s Dynamics 365 Business Central: using AL MCP Server from GitHub Copilot CLI provides a good tutorial on getting up and running.
• And Volodymyr Dvernystskyi’s series on CLI Agents covers the topic in more detail.

Debugging MCP Server

Speaking of MCP Server…

Troubleshooting Model Context Protocol (MCP) Server is a debugging tool integrated into Visual Studio Code for Business Central. It allows AI coding agents to access live runtime data during an active AL debugging session and:

• Analyze your call stack
• Inspect variable values
• Review relevant source code
• Help explain why something broke (and maybe even suggest a solution!)

Tonya Bricco-Meske discusses how this tool can help with faster debugging and root cause analysis in her blog, Troubleshooting MCP Server.

When AL slows you down

For the most part, executing AL code has minimal effect on system performance. Unfortunately, this can lead to bad habits that can severely bog down performance or, in some cases, crash the system.

Erik Hougaard covers some of the most problematic AL performance “gotcha’s” and how to avoid them. His short list is worth remembering:

• Minimize boundary crossings — bulk stream ops, 4-bytes-per-call I/O, TextBuilder accumulation.
• Turn per-byte computation into table lookups — precompute once, index in the loop.
• Inline and hoist the proven hot spots, and only those.
• Cache decoded data instead of re-reading and re-parsing it.
• Fuse pipeline stages so intermediate data never round-trips through a buffer.

To learn more, read his blog, Writing Fast AL Code: Lessons from a Byte-Crunching Hot Path.

Why is my page missing an Action?

Users who have recently moved to Business Central v28 are missing some actions on their page extensions.

This is not a bug. Instead, this behavior results from pages being migrated to the Modern Action Bar in BC v28, which ignores legacy promotion properties (Promoted and PromotedCategory).

Stefan Šošić explains the problem and how to fix it in his blog, Missing Actions on Pages After Upgrading to Business Central 28 ???.

Are you interested in Dynamics NAV and Business Central development? Check out our collection of NAV/BC Development Blogs.

Read “How To” blogs from ArcherPoint by Cherry Bekaert for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.

The post Dynamics Business Central / NAV Developer Digest – Vol. 556 appeared first on ArcherPoint.

For most warehouses running mobile WMS solutions, Wi-Fi instability is not a hypothetical edge case. It is a daily operational variable. The question is not whether your connectivity will be perfect. The question is what happens when it isn’t.

An offline-capable warehouse management system (WMS) for Microsoft Dynamics 365 Business Central helps warehouse teams continue picking, receiving, put-aways, and inventory counts even when wireless connectivity is unavailable. For operations that depend on mobile barcode scanning, this capability can significantly reduce downtime and improve inventory accuracy.

Why warehouse Wi-Fi is harder than it looks

Warehouses are difficult radio frequency environments. Metal racking, forklifts, concrete walls, and high ceilings all interfere with wireless signal propagation. Facilities that were designed before mobile WMS became standard often have coverage gaps that are expensive to remediate. Coverage that looks adequate on a heat map can perform very differently when a forklift is parked in an aisle, when a loading dock door is open, or when a team of workers is clustered in a single area during a cycle count.

Add to this the increasing density of connected devices competing for access points (handheld scanners, tablets, label printers, mobile computers, and IoT equipment), and what looked like sufficient bandwidth during a site survey can become unreliable under real production conditions.

Infrastructure improvements help, but they take time, require capital, and do not solve every scenario. A warehouse in a leased facility may have limited ability to install additional access points. A multi-site operation may have well-covered locations and poorly covered ones. A distribution center that processes high volumes in a compressed window simply cannot afford to wait for IT to troubleshoot a coverage issue before shipments go out.

Any serious warehouse management system needs to have an answer for this. And not all of them do.

The problem with “online-only” WMS design

Some warehouse management solutions assume the device is always connected. Every scan triggers a live transaction. Every lookup calls the server. Every posting requires an active session. When that works, it works fine. But when connectivity drops, even briefly, the consequences can be significant.

Workers may get error messages mid-task and lose their place in a multi-step pick or receiving flow. Partial transactions can leave inventory in an ambiguous state. A pick started but was not committed, a receipt was scanned but not posted. Workers learn workarounds quickly. They wait. They restart. They write things down and enter them later. These workarounds introduce the exact errors that a WMS is supposed to prevent.

Some solutions offer what might be called “graceful degradation” under poor connectivity, where the app stays open and queues data locally, but the user experience becomes unreliable and error-prone. The distinction matters: there is a significant difference between a system that tries to stay operational when connectivity drops and one that is genuinely built to operate offline from the start.

Offline-first WMS for Business Central warehouses

The right approach flips the model. Rather than requiring a constant connection and struggling to cope when it’s lost, an offline-first WMS stores the data it needs locally on the device and syncs with the ERP when connectivity is available. Workers perform their tasks continuously, including picks, put-aways, receipts, counts, and shipments, without depending on a live connection at the time of the transaction. When the device reconnects, data syncs automatically. The warehouse floor keeps moving.

This is not the same as simple caching. A well-implemented offline WMS synchronizes full transaction data to the device, intelligently resolves conflicts when multiple workers operate in the same area, and maintains a consistent view of inventory state across sessions. The sync mechanism needs to be reliable and transparent so that warehouse supervisors and ERP administrators have confidence in data integrity.

How Warehouse Insight and WMS Express handle offline operations

This is exactly the architecture that both Warehouse Insight and WMS Express, from Insight Works, are built on. Both applications store data locally on the mobile device and support full offline operation, including picking, receiving, put-aways, inventory counts, and other core warehouse tasks, without requiring a live connection to Dynamics 365 Business Central at the moment of each transaction. When connectivity is restored, transactions are automatically synced back to Business Central.

For operations teams, this has practical consequences that go well beyond avoiding downtime. Workers in low-signal areas can complete their tasks without interruption. Cycle counts in dead zones do not have to be rescheduled or handled on paper. Loading dock receiving does not stall when a door is open, and the signal is weak. The warehouse operates as designed, regardless of what the wireless environment is doing at any given moment.

Warehouse Insight is the full-featured solution for mid-market and larger operations, supporting complex warehousing configurations, including bin management, lot and serial number tracking, license plating, wave planning, custom workflows via the Application Designer, and a broad add-on catalog. WMS Express provides core receiving, picking, and counting functionality at no cost and serves as an effective starting point for operations new to mobile WMS or working with simpler setups.

Both are compatible with the rugged Android mobile devices that warehouses typically run, including purpose-built scanners from manufacturers like Zebra, Honeywell, and Datalogic. These are not consumer smartphones. They are devices designed to handle drops, dust, temperature extremes, and all-day scanning under production conditions. When you pair reliable hardware with an offline-capable WMS, you eliminate an entire category of operational risk.

What this means for distributed and multi-site operations

For companies running multiple warehouse locations, offline capability is especially important. Not every facility has the same IT maturity or infrastructure investment. A company’s primary distribution center may have excellent wireless coverage; a secondary facility or a third-party warehouse may not. An offline-capable WMS performs consistently across all of those environments without requiring infrastructure to be brought up to a uniform standard before the system can go live.

It also simplifies phased rollouts. Teams can be brought online in stages, and operational continuity does not depend on every access point being perfectly configured before the first scan happens.

How to evaluate offline WMS solutions for Business Central

If your organization is currently evaluating warehouse management systems for Business Central, or if you are reconsidering a solution that has caused problems in the past, connectivity resilience is worth probing specifically. The questions to ask include:

• Does the application store transaction data locally on the device, or does it require a live connection for each scan?
• What happens to an in-progress task if the device loses connectivity mid-flow?
• How does the sync mechanism handle conflicts when multiple devices have been operating offline?
• What is the data integrity model? How do you know that what is on the device matches what posts to Business Central?

Not every solution answers these questions the same way. The distinction between an offline-capable system and one that is merely tolerant of brief interruptions is significant, and it becomes visible quickly once a system is live on the floor.

Frequently asked questions about offline WMS

How ArcherPoint can help

ArcherPoint by Cherry Bekaert works with manufacturers and distributors across the country who are navigating the very same operational challenges. We have deep experience implementing Microsoft Dynamics 365 Business Central with warehouse management solutions for clients whose environments range from well-connected modern facilities to older buildings with significant infrastructure limitations. We understand that no two warehouse configurations are alike, and we take time to understand yours before recommending an approach.

If unreliable warehouse Wi-Fi has been a recurring frustration, or if you are building a business case for a more resilient WMS implementation, we would be glad to talk through your situation. Reach out to us and let’s start the conversation.

A well-run warehouse does not stop when the signal drops. With the right architecture, it never needs to.

The post When Warehouse Wi-Fi Fails: How Offline WMS Keeps Business Central Moving appeared first on ArcherPoint.

At ArcherPoint by Cherry Bekaert, we’ve found that Monday.com provides an effective platform for managing this balance. Supporting both executive-level project governance and Agile team execution helps organizations maintain visibility, accountability, and momentum throughout the implementation lifecycle.

Why Hybrid ERP implementations deliver better results

ERP implementations are complex because they span multiple workstreams with fundamentally different needs. In most implementations, holistic thinking stops at the preliminary conversations; it rarely extends to how the project is actually run. Instead, this mindset should be utilized throughout project delivery to avoid consequences in other departments. For instance, if a change to inventory is made without consulting finance, what is the downstream impact on the GL? Using Monday.com to improve cross-department visibility helps ensure these impacts do not fall through the cracks.

A waterfall approach gives you a detailed phase-gate timeline but does not easily accommodate change. An agile approach gives you flexibility but lacks anchor points for leadership to track progress against the budget and timeline. Hybrid gives you both. You apply the waterfall methodology for major phases, gate reviews for go/no-go decisions, and milestone dates. You run agile in each of these phases, letting SMEs “sprint” through their deliverables iteratively. This gives the team autonomy to adapt as they learn.

The trick is having a platform that can hold both views without creating two separate systems. This is where Monday.com comes into play.

Building a Hybrid ERP project framework in Monday.com

Creating the executive-level ERP Waterfall board

When building your Monday.com board, start with a high-level board that serves as the backbone. This backbone is your waterfall board (Figure 1). It will be used with your steering committee to represent phase and milestone progress.

You create groups for each major ERP phase:

• Discovery
• Design
• Build
• Test
• Deploy
• Hypercare

Within each group, add items that reflect key milestones and next phase gate reviews. Use the timeline column to map dependencies and durations. Add a status column for approvals with tags like Not Started, In Progress, Pending Approval, and Approved. Ensure that this board stays lean – no more than 50 items at most. The intent is to lack granularity and speak at a high level. This board will be your source of truth for the “big picture”. It’ll answer the question every executive asks: Are we on track?

A helpful tip: Set up automations for your key decision makers to mitigate approval delays.

Managing requirements and sprints with an Agile delivery board

Now let’s build our Agile board (Figure 2). Create a separate board that breaks down your requirements into categories, and label it ‘requirements’ or ‘user stories’. For example, these categories might read: Finance, Inventory, POS, Hospitality, Warehousing, and Data Migration. Each category will include a set of items to be addressed.

We recommend the following columns at a minimum within this board:

• Task: This lists out the requirements
• Sprint: Sprint 1, Sprint 2, Sprint 3, etc.
• Timeline: Broken down into 3–4-week time blocks
• Hours or Story Points: Effort assigned for each requirement
• Whether you choose hours or story points will depend on the style your client prefers. Hybrid means adaptable. The cookie-cutter approach doesn’t work for every project.
• Status: TBD, Ready, In Progress, Complete, Client in Review, and Accepted

Once the board is set up, you can start assigning what requirements can be met within the 3–4 week time block. Both parties must agree upon this assignment. The SMEs who are doing the configuration, testing, and documentation are on the agile board. Collectively, we run through requirements from start to finish within these sprint cycles. Throughout the project, we will measure velocity using these data points.

Taking the next step

Successful ERP project management requires both structure and flexibility. Organizations need executive-level visibility into milestones, budgets, and risks, while also enabling project teams to adapt as requirements evolve. A hybrid methodology provides that balance, and Monday.com offers a practical way to manage both perspectives within a single platform.

Contact ArcherPoint by Cherry Bekaert to learn how we can help with your Microsoft Dynamics 365 Business Central implementation, upgrades, and updates.

In a future article, we’ll explore how to connect these boards, measure project velocity, and use data-driven insights to keep ERP implementations on track.

The post Combining Agile and Waterfall for ERP Implementation Success with Monday.com appeared first on ArcherPoint.