Does Business Central Have a Mobile Scanner?
Yes — with an important distinction. Business Central’s native scanning support is a capability built into its general-purpose mobile app and its AL extensibility framework, not a separate, purpose-built warehouse-floor scanning application. Understanding exactly what that means is the honest starting point before evaluating any third-party scanning tool, including ours.
What Business Central ships natively
The standard Business Central mobile app for iOS and Android has had native barcode scanning support since the app’s version 4.0, on Business Central 2023 release wave 2 (platform 23.0) and later. It reads barcodes two ways: through the device’s own camera, on both iOS and Android, or through a paired dedicated hardware scanner — the kind of professional device sold by brands like Zebra or Datalogic — but that second path is Android-only, requiring Android 11 or later, because it works over Android’s own intent-broadcast mechanism, an OS-level messaging channel iOS doesn’t have an equivalent of.
| Scan method | iOS | Android |
|---|---|---|
| Device camera | Supported | Supported |
| Paired dedicated hardware scanner | Not supported | Supported (Android 11+) |
Scanning covers a wide set of common 1D and 2D barcode formats out of the box — QR code, Data Matrix, UPC-A, UPC-E, EAN-8, EAN-13, Code 39, Code 93, Code 128, PDF417, AZTEC, and (Android only) Codabar, RSS-14, and RSS Expanded.
There are, mechanically, three distinct ways a developer can wire this capability into a given Business Central page, and they matter because they represent genuinely different amounts of built-in behavior:
- A scanning button on a field. The simplest option — a barcode icon appears next to a field, the user taps it, the device camera opens, and the scanned value drops straight into that field. This is a one-line property on the field (
ExtendedDataType = Barcode) and needs essentially no custom logic. - AL-invoked scanning. A page can trigger the camera scanner programmatically — when it opens, or when a custom action runs — and process whatever comes back in code. This requires an actual AL control add-in and event-handling logic, not just a property flip.
- Dedicated hardware scanner integration. A paired Android scanner is configured to broadcast an Android intent every time it reads a barcode, and a page can be built to listen for that broadcast and act on it — the design aimed specifically at high-volume users, like warehouse staff, who need to scan a rapid sequence of items without touching the screen between scans.
The three scenarios represent genuinely different amounts of development effort, not just three configuration checkboxes. The first — a scanning button on a field — is close to free: a single property set on a field definition, no custom code required. The second and third are real AL development: a control add-in has to be declared on the page, event triggers have to be written to receive a scanned value and decide what to do with it, and for the hardware-scanner path, the physical scanner itself has to be configured to broadcast in the format the mobile app listens for. None of that is exotic engineering, but it’s also not “just turn it on” — a business wanting a guided, purpose-built receiving or picking screen beyond what a bare scan-into-a-field can offer is looking at a real, ongoing AL customization project, maintained release over release as Business Central itself updates.
Where scanning is already wired in, out of the box
This is the part worth being specific about, because “Business Central can scan a barcode” undersells how much is already built. A defined, documented set of standard pages already have scanning enabled by default, with no extension required:
- Item Tracking Lines and Warehouse Item Tracking Lines — serial, lot, and package number fields, both original and “new,” on the page described in item tracking in Business Central, explained.
- Item Tracing — filtering a trace by serial, lot, or package number.
- Item Journal — serial, lot, and package number entry on journal lines.
- Warehouse Activity Line — the shared page behind warehouse pick, put-away, and movement subforms, and their inventory-level (order-by-order) equivalents — meaning scanning is already available across put-away, pick, and movement regardless of which rung of the warehouse topology ladder a location is running at.
- Warehouse Physical Inventory Journal — serial, lot, and package number entry during a directed-location count.
On the Item Tracking Lines page specifically, a Scan multiple action exists precisely for the case of scanning a run of serial, lot, or package barcodes in sequence, advancing to the next quick-entry field automatically after each one — a small but telling sign that Microsoft has already designed for exactly the rapid-fire scanning pattern a warehouse floor needs.
What it assumes
Native barcode scanning in Business Central is a capability of the platform’s extensibility framework, not a ready-made warehouse-floor workflow handed to a worker out of the box. Turning it on for a field Microsoft hasn’t already wired is a configuration or development task: someone has to decide which pages get a scan button, which ones listen for a paired scanner’s broadcast, and how the surrounding screen behaves once a barcode value actually lands. For the pages listed above, that work is already done. For anything else — a custom receiving screen, a guided put-away sequence, an operator-facing summary of what just got scanned — it’s a building block, not a finished floor app.
It’s also worth remembering, from warehouse topology, explained, that Business Central’s own warehouse features scale from “no dedicated warehouse activity” up through fully directed put-away and pick. A location running at the simplest end of that ladder doesn’t have much of a receiving-to-shipping flow to scan through in the first place — the value of any scanning tool, native or otherwise, tracks a warehouse’s actual operational complexity, not just whether a camera can read a barcode.
The honest “so when would I want more”
None of this is a criticism. A general-purpose business application with an extensible, well-documented scanning framework, already wired into the exact pages a tracked-inventory workflow touches, is a reasonable and genuinely useful design for a platform that has to serve every kind of business, not just warehouses. It does mean the real question for a warehouse-heavy operation isn’t “can Business Central scan a barcode” — it clearly can, on a defined and fairly broad set of pages already — but “who is going to build and maintain the specific screens, prompts, sequencing, and validation a particular warehouse floor actually needs, on top of that framework.” That’s the gap a purpose-built scanning app is meant to fill, and it’s the honest starting point for the evaluation checklist on the next page.
Where this goes next
See choosing a warehouse scanning app for Business Central for the questions worth asking any vendor building on top of this native framework, including us.
Further reading — Microsoft Learn
Barcode Scanning in Mobile App — the native capability, supported formats, and the three implementation scenarios described above. Track Items with Serial, Lot, and Package Numbers — confirms exactly which standard pages already support scanning for item tracking.