DEV Community: Insight_Works

How Does a Mobile WMS Handle Assembly Edge Cases in Business Central?

Insight_Works — Tue, 21 Jul 2026 23:15:27 +0000

Assembly work has a way of stalling for reasons that have nothing to do with the physical task. A worker finishes consuming components, but the software assumes a step the operation doesn't actually use, and now someone has to walk back to a desk to sort it out. In standard Microsoft Dynamics 365 Business Central, assembly behaves differently depending on location setup, whether picks are required, and how item tracking is configured, and not every mobile tool accounts for all three.

The four scenarios below are the edge cases that tend to break that flow on a handheld, and how a warehouse management tool built for Business Central handles each one without sending the worker back to a workstation.

Can lot or serial numbers be captured during assembly output, right on the device?

Traditionally, item tracking tied to assembly output meant a follow-up step away from the floor. A tool that records lot and serial details at the moment of output removes that gap entirely. For an operation running mixed tracking, lot-tracked in the warehouse but serial-tracked on outbound documents, the details get captured once, at the source, instead of reconciled later from a desk.

Does a label have to print from a browser, or can it happen from the same device?

Once assembly output is complete, the next step is usually a label, and looping back to a desktop browser to trigger that print job breaks the flow the same way a missed tracking entry does. Warehouse Insight supports printing item labels directly from the device as part of the output step itself, so the label comes off the printer before the worker has moved to the next task, not after.

What if picks and consumption don't happen in the same sequence?

Not every floor consumes components in lockstep with when they were picked. Recording assembly consumption independently of warehouse picks means a worker isn't forced into an order of operations that doesn't match how the physical work actually happens. A location running partial staging ahead of a shift, for example, needs that separation more than one where picks and consumption happen back to back.

What happens to assembly output at a location that doesn't use picks at all?

Some warehouse configurations skip picks during assembly entirely, which is a legitimate setup in standard Business Central but can trip up software that assumes picks always happen. Output still needs to complete correctly even when consumption is separately configured as pick mandatory. The order posts and the worker moves to the next task without the mismatch surfacing as an error on the screen.

None of these scenarios are edge cases in the sense of being rare. They're the everyday reality of a floor where location setup, pick requirements, and tracking configuration don't all match the same template, and the tool is built to hold that variation instead of forcing the workflow to conform to one assumption.

Read the full blog: https://dmsiworks.com/blog/warehouse-insight-assembly-output-business-central

Disclaimer: This content is shared for informational purposes and is not promotional.

Which Mobile WMS View Fits Which Warehouse Worker in Business Central?

Insight_Works — Wed, 15 Jul 2026 22:55:45 +0000

A receiving clerk on a compact handheld, a forklift operator on a vehicle-mounted tablet, and a picker wearing a ring scanner are not doing the same job, and they should not be looking at the same screen layout. Most mobile warehouse interfaces for Microsoft Dynamics 365 Business Central hand every one of those workers an identical view regardless of device or task.

That mismatch is where scanning slows down and mistakes creep in: a dense list that works for an experienced picker on a handheld crowds a forklift tablet meant for one pallet at a time, and a single-record screen built for a wearable wastes space on a bigger display. The questions below cover how a mobile WMS tool with three configurable views addresses that, and where the configuration for each one actually lives.

What's the best mobile view for a worker scanning a long pick list on a small screen?

A high-density grid listing every document line at once suits smaller scanner screens and workers who already know the workflow. A footer panel expands detail for whichever row is selected, and workers can sort by any column or add and remove columns themselves without needing an administrator involved. A night-shift picker working a 40-line order benefits most from this density.

Does a mobile WMS view need to show item images, or is that just extra clutter?

For picking, receiving, and shipping on Android handhelds, a tile-based layout that pulls the item picture directly from Business Central alongside description, bin, lot or serial, and quantity cuts down on mispicks before the scan even happens. Color rules per row let a supervisor flag priority lines or exceptions visually, which matters most when a receiving dock is running several purchase orders at once.

Where do you configure which mobile view each device uses?

Warehouse Insight keeps all of this inside Business Central itself: device configuration and device column pages control which view a device gets, which fields appear, color rules, and factbox setup. There is no separate interface designer or external tool to maintain, since the device reads its display logic from Business Central at runtime the same way it reads every other warehouse management setting.

What view makes sense for a forklift tablet or a wrist-worn scanner?

A one-record-at-a-time panel showing bin, item, quantity, unit of measure, lot, serial, description, and source document on a single uncluttered screen fits vehicle-mounted tablets and wearables paired with ring scanners. Configurable factboxes beside the panel can surface the item picture or pick instructions. The focused layout matches the physical, step-by-step motion of forklift and hands-free picking work, rather than asking an operator to scroll a dense list mid-lift.

Many mobile WMS tools for Business Central offer one fixed layout regardless of device. Matching three purpose-built views to a mixed hardware fleet, all managed from inside Business Central, is a practical difference when the floor runs more than one kind of scanner or device.

Read the full blog: https://dmsiworks.com/blog/mobile-wms-views-business-central

How the Order Fulfillment Worksheet Answers "What Can I Ship Today?" in Business Central

Insight_Works — Wed, 08 Jul 2026 23:03:00 +0000

Ask any warehouse supervisor what they can ship today, and the honest answer usually starts with "give me an hour." Standard Business Central sales order screens sort on one column at a time and don't deduct availability across competing orders, so the only way to find out what's really shippable is to check each order by hand.

That manual check is where double-promised inventory comes from: two orders both look fine on paper, but there's only enough stock to cover one of them. The questions below cover how a purpose-built worksheet approach closes that gap, from allocation logic to automated status updates.

Why do two sales orders both look shippable when there's only enough stock for one?

Standard order screens don't deduct availability as they display it, so if ten units cover order A and order B each needs ten, both look fully stocked. Only when picking starts does the shortage surface. A worksheet that calculates availability top-down instead allocates each unit once, showing accurately which order gets it and which one waits.

Can shipping priorities be automated instead of decided order by order?

Not every order should ship on the same logic. Filtering and sorting by planned ship date, customer value, shipping agent, or order size lets a supervisor define the priority once instead of re-deciding it daily. Picture a distributor that runs one filtered pass for same-day carrier pickups and a separate one for next-week freight consolidation, both against the same open order list.

What happens to back orders once new stock finally arrives?

Back orders usually sit on a spreadheet until someone remembers to check them against a new purchase order receipt. A worksheet that recalculates automatically flags previously blocked orders as ready the moment inventory posts, without a person cross-referencing anything. For a plant receiving several inbound trailers a day, that removes a recheck step that used to happen at the end of every shift.

How do I know an order's status changed without re-scanning the whole backlog?

Every order carries a live status such as fully available, partial, or unavailable, and a recalculation refreshes all of them at once. Instead of rereading every line to spot what moved, the status itself tells the story. Running this on a schedule, for example every 30 minutes for orders shipping within two days, means the backlog stays current without anyone opening the screen.

The Order Fulfillment Worksheet works across warehouse setups, including locations with no bins, and can generate shipments and picks directly from the orders selected.

Read the full blog: https://dmsiworks.com/blog/stop-double-promising-stock-business-central

Keeping Business Central Warehouse Scans Moving Through Wi-Fi Dead Zones

Insight_Works — Fri, 03 Jul 2026 17:42:25 +0000

Loading docks with weak signal. Corners of the floor a router never quite reaches. Peak shift hours when the network bogs down under load. Every warehouse runs into some version of this, and when a worker is mid-scan and the connection drops, it's not a question of if productivity takes a hit, only how much.

What stops a mid-count scan from getting blocked?

Inventory counts can hit a wall when the system flags a license plate that's already tied to another active count session, a common friction point during cycle counts run across multiple zones at once. Advanced Inventory Count removes that blocker: license plates assigned to other active counts no longer stop scanning from continuing. The count keeps moving, and any conflicts get sorted out afterward through the normal process instead of halting work on the floor.

How do custom workflows avoid acting on unconfirmed data?

Custom workflows built in App Designer for warehouse operations sometimes depend on data being confirmed in Business Central before the next step can run safely, such as a shipment confirmation that shouldn't fire until inventory is updated. A Wait for Network Queue block pauses the workflow until pending network operations finish, rather than letting it move ahead and risk timeouts or inconsistent results. The pause protects data integrity instead of forcing a race against the network.

What keeps scanning going when the network can't keep up?

Busy receiving windows and large inventory counts put real strain on the connection between handheld devices and Business Central. Under that strain, workers end up waiting on confirmations instead of scanning. Warehouse Insight's Store & Forward option changes that: scan data gets queued locally on the device and sent through once the connection stabilizes. Workers keep working while the data catches up behind them, whether that's a single dropped signal or an extended outage across a shift.

Why would compression settings matter for two warehouses running the same app?

No two warehouse networks are built the same. Bandwidth, device age, and infrastructure vary enough that a single fixed setting won't perform well everywhere, a facility running older handhelds on a congested Wi-Fi network has different needs than one with newer devices and dedicated access points. Warehouse Insight lets administrators switch data compression on or off for device-to-server communication, so performance can be tuned to match the environment it's actually running in.

Wi-Fi dead spots and network strain aren't rare in warehouse environments. Handling them well is part of what keeps a Business Central-connected floor operation running without interruption.

Read the full blog

Why Business Central Quotes and Production BOMs Don't Match

Insight_Works — Wed, 24 Jun 2026 20:48:02 +0000

In configure-to-order manufacturing, a quote leaves sales and something different arrives on the shop floor. The production BOM reflects the standard item, not the configured one the customer ordered. Someone reconciles the gap manually, after the fact, under pressure. Here is why it happens and what a connected system does differently.

Why do Business Central quotes and production BOMs end up out of sync?

The missing link is the handoff between sales and production planning. Configure-to-order breaks the standard assumption — the finished product doesn't exist yet as a standard item. Its BOM and routing have to be assembled from the selections made during the sales process.

Without a formal configuration tool, that assembly is manual. The same customer conversation gets interpreted twice, by different people, with different results:

The BOM reflects the base item, not the configured item. Manufacturing builds the standard product. The customer receives something different from what they ordered.
The quote and BOM were built independently. Both are internally consistent. They don't match each other.
A rule that should have caught an incompatible combination didn't. The error reaches production.
Costs on the quote don't match costs in the system. Finance reconciles the difference at month end.

What does this misalignment actually cost?

Rework is the visible cost. The invisible cost is larger. It lives in engineering time spent rebuilding BOMs from quotes that should have generated them automatically. It lives in the informal rule requiring sign-off on complex orders because the team has learned not to trust the handoff. It lives in quotes delayed because the salesperson is waiting on confirmation that a proposed configuration is actually buildable.

None of this shows up as a line item. All of it shows up in capacity, throughput, and margin.

What changes when sales configuration connects directly to production output?

When option selection, BOM generation, and configuration rules operate as a single workflow, manual reconciliation disappears. The salesperson selects options. The system validates the combination in real time. The BOM and routing generate automatically. The production order is created with the correct configuration already embedded.

Quote accuracy improves because invalid combinations are excluded during selection, not discovered on the shop floor. Cost accuracy improves because the BOM derives from the same selections as the quote. Manufacturing receives exactly what sales produced — not a reconstruction of it.

What should a Business Central configure-to-order tool actually do?

Rule enforcement during selection, not after submission
Automatic BOM and routing generation from selected options, covering both production and assembly BOM types
Cost calculation from the configuration itself, consistent between quote and BOM
Support for nested configurations where parent settings propagate correctly to sub-assemblies
Integration with Business Central MPS and MRP from the moment the order is created

Product Configurator handles both BOM types, enforces rules at the point of selection, generates BOMs and routings automatically, and connects to standard Business Central planning functions.

Read the full blog: Business Central Quotes and Production BOMs: Why They Don't Match

Why Is Business Central Data Migration So Painful — And What Actually Fixes It?

Insight_Works — Thu, 11 Jun 2026 16:05:41 +0000

Business Central's built-in RapidStart Configuration Packages were designed for structured, one-time setup migrations, not for the messy, iterative work that consultants, developers, and power users actually face: opening balance loads, sandbox-to-production copies, inter-company moves, history imports, and bulk record corrections.

RapidStart requires Excel, demands that every field be explicitly defined in a configuration package, moves slowly on large datasets, and offers no mechanism to write directly to protected tables like item ledger entries. When the tool you have is slow and rigid, the work piles up.

Why does bulk data migration break down in Business Central?

The problem is not the data. It is the tooling.

Research on ERP implementation projects consistently identifies data migration as the leading source of delays and cost overruns, and Business Central implementations are no exception.

The change log problem compounds it. Run a bulk update on customers using standard methods, and Business Central faithfully logs every field change on every record. Import 50,000 items, and you may generate more change log noise than the system produces in months of normal use. None of that data is useful. All of it costs performance.

What does Import Export PowerTool do differently?

Import Export PowerTool installs directly from Microsoft AppSource and sits inside Business Central as a native extension. It handles imports, exports, bulk updates, and targeted deletions across any table in the system, including protected tables such as item ledger entries, G/L entries, and VAT entries, at speeds that are not in the same league as RapidStart.

The output of an export is a plain tab-delimited text file. You can open it in Excel, edit it, add columns, remove columns, and import it back. There is no requirement to predefine a schema in a configuration package. Multiple tables export into a single file. If you are moving data from a legacy NAV environment, you can run the included NAV export report, take the resulting text file, and load it straight into Business Central without a staging database.

How does the app handle change log noise, lot numbers, and protected tables?

The app validates data against Business Central's table and field rules, runs field-level business logic selectively based on which fields are flagged for validation, and gives you control over whether the change log fires during the operation. When you are loading 10,000 records, disabling the change log for that session is the difference between a clean system and thousands of audit entries that describe nothing of value.

The two-step insert option handles tables where Business Central's own triggers would otherwise overwrite incoming field values before the record is fully written.

Lot numbers and serial numbers in item journal imports are handled automatically, removing one of the more tedious manual steps in initial inventory loads. Dimensions, including both shortcut and non-shortcut dimensions as well as default dimensions, can be imported and exported directly. Record links and record notes travel with the data. For consultants who need to import historical item ledger entries without posting through journals, the app writes directly to the ledger table, leaving no spurious G/L entries or value entries behind.

What controls prevent accidental changes to sensitive tables?

The update and delete operations follow the same logic. You specify a table, set filters to scope the records you want to touch, review exactly which records will be affected, and then confirm.

Enhanced confirmation prompts are available for operations on protected tables, giving users a moment to reconsider before committing to an irreversible action. Permission sets control who can access those tables, so end users with standard Business Central access cannot do anything the tool would not otherwise allow.

Explore the Full Migration Guide

Why Inventory Counts Take So Long in Business Central (And What to Do About It)

Insight_Works — Wed, 03 Jun 2026 20:08:14 +0000

Your team shuts down receiving, locks the warehouse doors, and spends the next two days counting everything from raw materials to half-finished production orders. When it's over, the numbers don't reconcile. The accounting department is waiting. Someone finds a pile of uncounted items behind a rack. The process restarts.

Business Central's built-in counting tools were designed for straightforward scenarios. If your warehouse is anything but simple, you start running into walls quickly.

Why Does Inventory Counting Break Down in Business Central?

The Physical Inventory Journal generates a list of items, lets you fill in quantities, and posts adjustments. That works for simple warehouses. The constraints that surface in more complex ones are real, not workarounds:

Items across multiple shelf locations with no bins enabled cannot be counted separately by location — you end up tracking sub-totals on paper and entering a single figure, which is exactly the kind of manual math that introduces errors
Microsoft's own documentation acknowledges that without bins, an item can only be counted once per location, and the document-based approach still requires separate reconciliation steps for warehouse entries
Lot and serial number reconciliation is fragile — a misconfigured line, a missing tracking entry, or an item in an unexpected bin can break it entirely

The standard journal also does not handle multiple teams entering counts simultaneously. Research published in the journal Production found that inventory inaccuracies affect picking productivity, lost sales, and warehouse capacity utilization across every warehouse category studied, and that implementing cycle counts alone is often insufficient to resolve the underlying problem.

How Does Advanced Inventory Count Fix the Problem?

Advanced Inventory Count is a Business Central app that replaces manual workarounds with a structured counting framework. It installs from the Microsoft Marketplace and layers onto Business Central's existing journal and posting infrastructure — no custom development, no disruption to existing workflows.

Each count is organized around an Inventory Count Card, typically one per location. Within each card, Count Sheets group items by zone, filtered by shelf range, posting group, vendor, or any item card field, so each team sees only what is relevant to their area. The As-of-Date field lets you generate and print sheets before count day while ensuring differences calculate against the correct transaction date — teams can prepare a week in advance without locking the system.

What Does the Counting Process Actually Look Like?

Paper, scanner, and hybrid data entry are all supported simultaneously, and multiple users can enter counts into different sheets at the same time. For bin and directed put-away configurations, the app works with the Warehouse Physical Inventory Journal and populates both journals automatically when count data is transferred.

After entry:

The Count Difference Analysis report sorts discrepancies by absolute dollar value, flagging the biggest exposures first
Generate Recount Sheets flags items exceeding a set threshold and creates a new sheet — original count lines lock, keeping the audit trail clean
Copy Count to Journals transfers everything to the Physical Inventory Journal, including item tracking lines, lot and serial number reclassifications, and dimension values
A pre-posting test report checks every line for blocked items, missing tracking, and missing posting groups before anything posts

What Are the Results?

One customer went from a four-day serial-number-heavy count to a single day, with half a day of reconciliation.

Read the full blog

Disclaimer: This content is shared for informational purposes and is not promotional.

When Your Equipment Has No Voice in Business Central

Insight_Works — Thu, 28 May 2026 14:02:29 +0000

Why Does Maintenance Fall Through the Cracks in Business Central?

The gap is not a software flaw; it is a scope decision. Business Central is built to manage production, inventory, purchasing, and finance. Maintenance is treated as a capacity absence at best: you can register a work center as unavailable, block off time on a calendar, and bury a note in a comment field. What you cannot do natively is define a recurring inspection interval, track runtime against a machine center, store parts requirements for a specific asset, or give a technician a mobile job card with attached manuals and step-by-step work instructions.

The result is familiar: maintenance lives in spreadsheets, paper binders, or a standalone CMMS with no connection to the production schedule
Across U.S. manufacturing alone, unplanned downtime costs an estimated $50 billion annually
The average large manufacturing operation loses roughly $260,000 for every hour a critical line sits idle
Business Central's fixed asset register can record equipment existence and track depreciation, but provides no native way to assign maintenance intervals, build service bills of materials, or trigger work orders when a runtime counter hits a threshold

Closing that gap has traditionally required a separate enterprise asset management (EAM) platform, which adds its own integration burden, licensing costs, and a learning curve your millwrights and maintenance technicians have to climb.

How Does Maintenance Manager Solve the Problem?

Maintenance Manager is a maintenance management system (CMMS) that runs natively inside Business Central. Rather than building a parallel data structure, it uses production orders as its foundation for maintenance work orders. That one architectural decision means every existing Business Central capability, including warehouse functions, shop floor execution, planning worksheets, and third-party ISV apps, works with maintenance orders exactly the same way it works with production orders.

How Does Maintenance Manager Work in Practice?

Setup is intentional in its simplicity. An installation wizard applies default data, numbering series, and posting groups, so the system is usable almost immediately.

Equipment items are created as standard Business Central items with a maintenance designation and can be linked to existing fixed assets or set up independently for tooling, vehicles, or any asset that does not require a fixed asset record
Each piece of equipment is assigned maintenance tasks with intervals defined by duration (weekly, monthly, annual), runtime (every 500 machine hours), output count (every 100,000 cycles), or distance (every 10,000 miles)
For production assets linked to work centers or machine centers, runtime and output count updates automatically whenever a production order posts against that resource
When maintenance is due, the planning worksheet generates work orders complete with bills of materials for spare parts and labor routings
Those parts become live demand signals in Business Central, so the standard planning run will recommend purchasing them if stock is insufficient
When a work order is released for a production asset, that capacity is consumed in the schedule

Read the full blog

This content is shared for informational purposes and is not promotional.

Enhanced License Plate Packaging in Dynamic Ship for Dynamics 365 Business Central

Insight_Works — Fri, 15 May 2026 17:56:51 +0000

License Plate management is one of the most powerful tools available in advanced warehouse operations inside Dynamics 365 Business Central. Yet for many users, packing with License Plates can still feel slow, clunky, or overly complicated.

Dynamic Ship from Insight Works now delivers a significantly improved License Plate packaging experience. The new License Plate Packaging page provides a cleaner, more intuitive interface that streamlines packing of both flat and embedded License Plates while making EDI label creation faster and more reliable.

Why is License Plate packaging critical in Business Central?

Modern warehouses using License Plates need to:

Build or unpack complex shipments quickly
Maintain clear visibility of contents at every level
Generate accurate EDI-compliant labels without extra manual work
Minimize errors during high-volume packing

Many basic shipping tools included with warehouse management apps fall short in this area. They often require too many clicks, offer limited visibility, or force users into rigid workflows that slow down the packing station.

What limitations exist with basic License Plate packing tools?

Basic Pack and Ship features found in many warehouse management solutions often:

Require too many clicks and unnecessary steps
Offer limited visibility into License Plate hierarchy and contents
Force users into rigid workflows that slow down the packing station
Make EDI label creation a manual process prone to corrections

Split quantity lines and item matching on scanning can also introduce packing errors when the interface does not provide clear status indicators or feedback.

How does Dynamic Ship improve License Plate packaging?

Dynamic Ship was built to solve these real-world challenges directly inside Business Central. Key improvements include:

A dedicated, streamlined License Plate Packaging page that reduces unnecessary steps and gives packers a clearer view of what needs to be done
Enhanced Quick Label that intelligently matches order options and includes a new "Copy Last Package" action, allowing users to quickly replicate package data across multiple boxes or pallets
Improved packaging flow that simplifies the generation of accurate, EDI-ready labels with full License Plate hierarchy and contents, especially helpful for companies that exchange Advanced Shipping Notices (ASNs) with trading partners
Better item matching on scanning, refined handling of split quantity lines, and clearer status indicators that reduce packing errors and improve overall process visibility

What are the real-world benefits for your warehouse team?

Faster packing cycles, allowing you to move more volume through the dock each day
Fewer mispacks thanks to improved scanning logic and clearer feedback
Smoother EDI compliance with fewer manual corrections of labels and data
A more natural workflow, whether you are packing individual boxes or building complex nested pallets

Getting started is straightforward:

Update Dynamic Ship through the Business Central Extension Management page
Test the new License Plate Packaging features on your next shipment

These enhancements make License Plate handling noticeably more efficient and user-friendly directly inside Dynamics 365 Business Central.

Read the full blog

Disclaimer: This content is shared for informational purposes and is not promotional.

How to Simplify Returns and Reverse Logistics in Dynamics 365 Business Central

Insight_Works — Mon, 04 May 2026 21:15:54 +0000

Returns and reverse logistics are among the most frustrating parts of shipping, especially when your warehouse management system only offers basic outbound tools. Many businesses struggle with limited return-label options, manual re-entry of addresses, and poor visibility into goods returned by customers or vendors.

Dynamic Ship from Insight Works now handles reverse logistics efficiently and accurately, all directly inside Dynamics 365 Business Central, with major improvements to return label generation, inbound shipping support, and greater flexibility.

Why are returns so painful in many systems?

Basic shipping modules in warehouse apps often treat returns as an afterthought. You might be forced to:

Manually recreate labels from scratch
Link every return to an original shipment
Handle only one package at a time
Re-enter addresses and customs data repeatedly

These limitations waste time, increase errors, and frustrate both warehouse staff and customers.

What return and inbound shipping limitations do teams face?

Many businesses are forced to link every return to an original shipment. When you need to send a replacement item quickly or handle a return independently, this slows the process down.

Multi-package return label support is limited, forcing you to handle only one package at a time. There is no easy way to specify different return addresses for directing goods to repair centers, warehouses, or third-party locations.

Creating original shipping labels for goods coming into your Business Central locations from customers or vendors requires manual work. Replicating package data for multiple returns is slow without a way to quickly copy previous entries.

How does Dynamic Ship address these limitations?

Dynamic Ship was built to solve real-world shipping challenges and takes returns and inbound shipping to a new level:

Generate return labels without linking to the original shipment. This is useful when you need to send a replacement item quickly or handle a return independently
Choose to create return labels for a single package, or all packages in a multi-package shipment. This flexibility saves time when dealing with partial returns or complex orders
Easily specify different return addresses, perfect for directing goods to repair centers, warehouses, or third-party locations
Create original shipping labels for goods coming into your Business Central locations from customers or vendors. This full reverse logistics support makes it easy to manage vendor returns, customer returns, and internal transfers
The enhanced Quick Label now includes a "Copy Last Package" action, letting you quickly replicate package data for multiple returns, dramatically speeding up the process

Country-specific address validation helps ensure returns meet regional requirements.

What are the real-world benefits?

Less manual work: generate accurate return labels in seconds instead of minutes
Better accuracy: reduce errors with clearer options and automatic data handling
Improved customer experience: faster processing means quicker resolutions and happier customers
Stronger compliance: country-specific address validation helps ensure returns meet regional requirements

Getting started is straightforward:

Update to the latest version of Dynamic Ship via the Business Central Extension Management page
Test the new return label options on your next inbound or customer return

Whether you handle occasional customer returns or manage high-volume reverse logistics, these improvements make Dynamic Ship significantly more powerful. Reverse logistics becomes faster, more accurate, and far less painful directly inside Business Central.

Read the full blog

Disclaimer: This content is shared for informational purposes and is not promotional.

Streamlining Time Tracking on the Shop Floor: From Clock-Ins to Operation Timings in Dynamics 365 Business Central

Insight_Works — Mon, 27 Apr 2026 17:31:26 +0000

In manufacturing, accurate time tracking is critical for operational efficiency. Recording staff clocking in and out, tracking time on production lines, and capturing start and end times for operations are common priorities. Manual processes introduce errors, delays, and incomplete data that inflate costs and hinder decision-making.

Dynamics 365 Business Central provides built-in Shop Floor Data Collection features for basic time capture. However, native capabilities have limitations in more complex or high-volume environments.

Why does manual time tracking create problems in manufacturing?

Manual time tracking through paper timecards or spreadsheet entries remains a common bottleneck in many shops using Business Central.

These methods introduce significant risks:

Employees may forget to log times, round hours incorrectly, or make simple entry mistakes
Underreported or inflated hours distort labor costing, job profitability, and regulatory compliance
Data is typically entered hours or even days after the fact, preventing supervisors from identifying downtime, bottlenecks, or productivity gaps in real time
Manual reconciliation with payroll systems requires chasing down missing entries, correcting errors, and double-checking records

Without shop-floor-optimized mobile support, workers remain tethered to fixed stations or paper-based processes, reducing flexibility in dynamic environments where operators move between machines or handle variable shifts.

What are the limitations of native time tracking in Business Central?

Business Central offers foundational tools for shop floor time tracking. Using the Production Journal or Time Sheets, you can manually log employee attendance, start and end times for operations, and time spent on production orders or jobs. This integrates with capacity planning and resource management.

However, in more complex or high-volume environments:

Time entries often require keyboard input, leading to errors and slowdowns
There is no built-in barcode scanning or touchscreen optimization for shop floor use
Overtime calculations, break deductions, and exception approvals are not fully automated
Setup can be cumbersome without easy device support for multiple terminals or mobile needs
Real-time downtime or rework tracking is basic at best
The interface is not tailored for shop floor workers, slowing adoption

While Business Central connects to payroll systems, custom formats often require development work.

How does Shop Floor Insight address these gaps?

Shop Floor Insight from Insight Works integrates with Dynamics 365 Business Central, adding barcode technology, touchscreens, and mobile devices to automate time capture.

It enables manufacturers to:

Scan badges or production orders to clock in and out instantly, eliminating manual entry
Automatically calculate overtime, shift differentials, and breaks when scanning barcodes for setup and runtime
Review timecards with multi-level approvals, flagging anomalies like excessive overtime
Export data to any payroll provider with configurable formats, cutting double-entry and errors
Schedule shifts with recurring patterns and visual calendars for tracking indirect tasks like meetings or cleaning
Track non-productive time, rework, and downtime through real-time reporting

Workers can use smartphones or tablets for swipe-on and swipe-off functionality, making it suitable for roving roles or break tracking. Fixed terminals such as Chromebooks or tablets as well as personal devices ensure secure access in challenging environments.

What does implementation look like?

The solution is priced per employee, with implementation typically taking four to six weeks on a fixed-price basis including training and support.

Savings come from:

Eliminating manual validation
Cutting rework
Optimizing payroll through automated overtime calculations

The payback period is often just a few months, with first-quarter savings frequently covering the annual subscription. Efficiency gains can reach twenty to thirty percent for a mid-sized shop.

Streamlining time tracking is not about replacing the team but about empowering them with accurate, real-time data. From clock-ins to operation timings, these tools address key limitations that hold manufacturers back.

Read the full blog

Disclaimer: This content is shared for informational purposes and is not promotional.

Barcode-Free Scanning for Business Central: How OCR Text Recognition Simplifies Warehouse Operations

Insight_Works — Mon, 20 Apr 2026 22:28:52 +0000

Warehouse operations in Microsoft Dynamics 365 Business Central typically rely on barcode scanning for speed and accuracy. But barcodes are not always available. Vendors ship without labels, existing bin racking has only printed text, and lot numbers on packaging lack barcodes.

Teams face a difficult choice: spend time and money printing and applying new labels everywhere, or fall back to slower manual entry that risks errors.

Why is barcode dependency a problem in warehouse operations?

Most warehouses start with the ideal situation: vendor or manufacturer barcodes already on incoming product. These scans are instantly processed and cross-referenced in Business Central via item references, GTIN fields, or custom mappings.

When vendor barcodes are unavailable, the next step is often to print your own. Yet printing labels for every item, every lot, or retrofitting hundreds of existing bin locations is not always practical.

This means:

Teams must choose between relabeling costs or manual data entry
Items without barcodes slow down receiving, counting, and movement
Manual entry introduces typing errors and delays
Partial barcode coverage creates inconsistent workflows across the warehouse

Without a way to capture data from existing printed text, warehouses are forced into workarounds that reduce speed and accuracy.

What gaps exist when barcodes are not available?

Standard barcode scanning assumes labels are present on every item, lot, and bin location. When they are not, the process breaks down at several points:

Receiving goods without vendor barcodes requires manual lookup and entry
Lot and serial numbers printed on packaging cannot be scanned directly
Bin locations with only printed text codes require new barcode labels
Mixed environments with partial barcode coverage lack a consistent capture method

This often leads to:

Slower receiving and put-away processes
Increased data entry errors
Delayed inventory updates in Business Central
Additional cost and labor for printing and applying labels

How does OCR text scanning address these limitations?

Optical character recognition lets rugged Android devices read legible printed text such as item numbers, vendor product codes, lot numbers, serial numbers, expiration dates, or bin codes almost as fast as scanning a barcode.

Warehouse Insight from Insight Works now supports barcode-free scanning through OCR on compatible devices from manufacturers like Honeywell and Datalogic.

This enables warehouses to:

Receive goods by scanning printed item numbers or vendor codes directly from packaging
Capture lot and serial numbers from human-readable text without manual typing
Scan existing printed bin codes on racking without applying new barcode labels
Use barcodes where available and fall back to OCR text scanning where they are not

Every scan, whether barcode or text, updates Business Central in real time. Once captured at receiving, a proper barcode label can be printed immediately for downstream processes like picking, shipping, and counts.

How do you get started with barcode-free scanning?

Getting up and running follows these steps:

Install Warehouse Insight from Microsoft Marketplace
Use the assisted setup to connect to your location and configure scanning behaviors
Pair with compatible devices — many modern Honeywell and Datalogic models support OCR capture alongside traditional barcodes
Leverage the Barcode Generator PowerTool for label creation where needed

Barcode-free scanning works best when teams need to start scanning without waiting for a full relabeling project. OCR text recognition removes a major friction point, making mobile warehouse management more accessible without forcing changes to existing processes.

Read the full blog

Disclaimer: This content is shared for informational purposes and is not promotional.