# Infor Factory Track and Infor M3: handheld scanning transactions > Source: https://netray.co/stack/infor-factory-track-barcode-scanning-infor-m3 > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Stack ## Short answer Infor Factory Track is a native Infor add-on that gives M3 handheld transactions for receive, putaway, move, physical count, pick and pack, shipment loading and package labels, plus mapping of barcode scan formats. It is the first thing to check before buying a third-party RF tool for M3. ## Erp Infor M3 ## Erp Key infor-m3 ## On Prem true ## Product Infor Factory Track ## Vendor Infor ## Category RF barcode data collection and warehouse mobility ## Integration **Method:** Native Infor add-on **Detail:** Factory Track is documented by Infor as a native add-on to M3, so scans become M3 transactions through the product rather than through a custom connector. Its documentation covers the M3 transaction set and barcode scan-format mapping. ## Data Flows **From:** Handheld scanner **To:** Infor M3 **Data:** Receipt against purchase order **Trigger:** Operator scans item and location at the dock **From:** Handheld scanner **To:** Infor M3 **Data:** Putaway and move transactions **Trigger:** Scan of item, from and to locations **From:** Handheld scanner **To:** Infor M3 **Data:** Physical count entries **Trigger:** Count task or cycle count **From:** Infor M3 **To:** Handheld scanner **Data:** Pick lists and pack tasks **Trigger:** Delivery released for picking **From:** Handheld scanner **To:** Infor M3 **Data:** Shipment loading confirmation **Trigger:** Packages scanned onto the vehicle ## Setup ### Choose the transaction set **Detail:** Decide which of receive, putaway, move, count, pick, pack and shipment loading you need first. Starting with receiving and counts is common. ### Define barcode scan formats **Detail:** Map each barcode on supplier labels and your own labels to the M3 fields it carries, using Factory Track's scan-format mapping. ### Prepare M3 master data **Detail:** Clean up item, warehouse, location and lot or serial setup. Scanning exposes any gaps immediately. ### Configure devices **Detail:** Select handhelds, connect them to the Factory Track environment, and set operator permissions and warehouses. ### Design package labels **Detail:** Specify what package labels contain and where they are printed from. ### Pilot in one warehouse **Detail:** Run real receipts and picks, compare inventory balances with M3 and record scan error causes. ### Train and roll out **Detail:** Train by role and add the remaining transactions after the first process is stable. ## Pitfalls - Supplier barcodes that do not match your scan-format mapping, causing rejected scans at the dock. - Locations not defined in M3 consistently, so moves fail or inventory lands in wrong bins. - Lot and serial capture treated as optional on the device while M3 requires them. - Counts posted without a review step, adjusting inventory from a bad count. - Network dead spots in the warehouse leaving operators with stalled sessions. - Label formats copied from another system that omit data downstream partners need. ## Ai Layer ### Scan failure triage **Description:** A private assistant reading Factory Track errors and M3 master data can say which rejected scans come from missing locations, unmapped barcodes or closed orders, and propose the fix for approval. ### Inventory variance explanations **Description:** Ask why a location shows a count difference and get the recent transactions behind it, in read-only form. ### Barcode mapping drafts **Description:** When a supplier changes label layout, the assistant drafts the updated scan-format mapping for a consultant to review. ### Warehouse performance questions **Description:** Supervisors ask which receipts are waiting for putaway or which deliveries are not yet picked, scoped to their warehouse. ## Alternatives - M3 standard warehouse functionality with a third-party RF client if you already own that tooling. - Spreadsheet-based counting and manual M3 entry for very small stockrooms, at the cost of accuracy. - A dedicated WMS where you need advanced slotting, waves or labour management beyond handheld transactions. ## Faq ### Is Factory Track an Infor product? **Answer:** Yes. Infor documents Factory Track for M3 as a native add-on with handheld transactions. That makes it the first option to evaluate for barcode scanning on M3, before comparing with third-party RF vendors. ### Which transactions does it cover? **Answer:** Infor's documentation lists receive, putaway, move, physical count, pick and pack, shipment loading and package labels, and scan-format mapping. Confirm the exact transaction names and version in the documentation for your release. ### Does it work with on-premises M3? **Answer:** It is positioned as an M3 add-on, so check the installation and architecture guide for your M3 release and deployment type. Network and device requirements are where on-premises projects most often need planning. ### What is scan-format mapping? **Answer:** It tells the system how to read a barcode, such as which part is the item, lot or quantity, so a scan fills the right M3 field. Getting it wrong is the most common cause of rejected scans. ## Source https://docs.infor.com/factorytrack/6.01.10/en-us/ftm3olh/lsm1455964686816.html ## Search terms infor factory track m3 barcode scanning, m3 rf scanning, infor m3 warehouse mobility, m3 handheld receiving putaway, factory track m3 physical count, m3 barcode scan format --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json