Infor Factory Track Installation and Go-Live Checklist (CSI / SyteLine)
A practical checklist for installing on-premises or enabling Infor Factory Track with CloudSuite Industrial (SyteLine), covering prerequisites, configuration, BarTender labels, devices and Wi-Fi, data readiness, pilot and go-live. Use it alongside the Factory Track administrator documents for your release.
0 of 37 items complete
8 critical items still open - these are the highest-risk gaps.
1. Prerequisites
2. Install and configure
3. Labels and printing
4. Devices and network
5. Data readiness
6. Pilot and go-live
Critical items are the ones that most often delay a Factory Track go-live or create inventory errors afterwards. Do not switch off paper until every critical item is complete.
Get your Factory Track go-live plan checked
Send us your scope, CSI version and site list and we will return a reviewed go-live plan with the critical items and owners marked.
Optional. The tool and every export work without this. No spam.
How to use it
Work through the six groups in order and tick items as you finish them; export the list for the project file or steering meeting. Groups 1 and 2 belong to IT and the Factory Track administrator, group 3 to whoever owns labels, group 4 to infrastructure, and groups 5 and 6 to the warehouse and production leads. The critical items are the ones that most often delay go-live or cause inventory problems after it. A Factory Track project fails less often on software than on missing location labels, untested Wi-Fi and users who do not know what each scan posts to CSI.
- Assign an owner and date to every critical item.
- Keep a list of open questions for Infor support by item number.
Where to find the official documentation
Infor publishes Factory Track documentation on docs.infor.com under Factory Track, split into administrator and user documents. The ones that matter for this checklist are Infor Factory Track Supported Backend Versions (which CSI versions each release supports), the administrator documents for installation, technology and BarTender label configuration, the administrator guide for the Android app, the Database Validation and Prep Tool user guide, and the CSI Warehouse Mobility and Time Track user guides. Use the versions that match your Factory Track release; steps and parameters change between releases.
Labels and BarTender
Factory Track prints labels through a BarTender integration, so label design and printer mapping are a workstream of their own. Agree templates for item, lot, serial and container labels early, because warehouse staff will scan them for years. Test print quality and symbology with the actual scanners at working distance, in the real lighting. Map printers to warehouses and work areas so Job Receipt and Purchase Order Receipt print where the material is, and teach users Change Printer and Label Reprint before go-live, not during it.
Pilot, cutover and the first week
A conference room pilot should run every transaction in scope with real barcodes and then check the result in CSI forms: the PO line received, the job material issued, the stock moved, the count posted. Then cut over from paper on a clear date, with a known last paper transaction. During the first week, staff the floor on every shift. At the end of week one, count a sample of locations, compare labor hours from Time Track or Labor Reporting with expectations, and fix the root cause of each variance, which is usually training or a missing label rather than the software.
Frequently Asked Questions
Where is the Infor Factory Track installation guide?
On docs.infor.com under Factory Track, in the administrator documents for your release. Check the Supported Backend Versions document first to confirm your CSI version is supported, then follow the installation and configuration guides for that same release.
How is BarTender configured for Factory Track?
Factory Track uses BarTender for label printing, and Infor provides a BarTender configuration guide for Factory Track in the administrator documents. It covers connecting BarTender to Factory Track, label templates and printer setup. Follow the version that matches your Factory Track release.
Why can a user not log in to Factory Track?
Common causes are a Factory Track user not linked to a CSI user or employee, a missing role or menu, an expired password, the wrong site or warehouse selected, or a device that cannot reach the server over Wi-Fi. Test the same user on a desktop browser to separate account problems from network ones.
How long does a Factory Track go-live take?
For one warehouse with Warehouse Mobility only, a few weeks to a few months is typical, driven by labels, Wi-Fi and training. Adding Time Track brings payroll rules and union or works council review, which often sets the timeline.
Once Factory Track is live, we can add a private AI layer so supervisors can ask what was received, issued or clocked in plain English, on your own servers.
Related Tools
Infor Factory Track Scanner Device and Wireless Coverage Sizing Calculator
Plan a Factory Track Warehouse Mobility and Time Track rollout: access points, devices with spares, peak transaction load and kiosks for shift change.
Infor M3 & CloudSuiteInfor Factory Track Warehouse Mobility and Time Track Transaction Reference (CSI / SyteLine)
Every common Factory Track Warehouse Mobility transaction for CloudSuite Industrial and SyteLine, with what the user scans, what it does and the usual gotcha.
More Infor M3 & CloudSuite tools
See all- Infor M3 Program Reference (MMS001, OIS100, PMS100)
- Infor M3 MI API Transaction Call Generator
- Infor M3 Customer Order Status Tracking Worksheet
- Infor M3 Item Master Upload Worksheet
- Infor M3 MEC Mapping Design Template
- Infor M3 H5 Script Review Checklist
- Infor M3 Upgrade Test Checklist
- Infor M3 Facility and Warehouse Structure Worksheet
- Infor M3 Fit-Gap Analysis Worksheet
Keep exploring
Free tools
- Infor Factory Track Warehouse Mobility and Time Track Transaction Reference (CSI / SyteLine)Every common Factory Track Warehouse Mobility transaction for CloudSuite Industrial and SyteLine, with what the user scans, what it does and the usual gotcha.
- SyteLine ION BOD Integration Go-Live ChecklistSetup, scope, testing, cutover and hypercare checks for BOD based integrations between SyteLine or CSI 10 on-prem and Infor ION.
- Infor Factory Track Private AI Layer Blueprint GeneratorFill in your Infor Factory Track version, database, hosting and use cases and get a shareable architecture plan for a private AI layer.
ERP fixes and how-tos
- Infor XA Factory Track: What It Does and How to Plan Shop Floor Data CollectionWhat Factory Track does for Infor XA shop floor data collection, which transactions it captures, how to plan a setup, and alternatives when it is aging.
- SyteLine or CloudSuite Industrial: how to decide in 2026How CIOs on Infor SyteLine should decide between staying on-prem, moving to CloudSuite Industrial, or holding at the current version in 2026. Practical decision framework.
Runs with your ERP
- Infor Factory Track Shop Floor with SyteLine: paperless labor, job and WIP reportingHow Factory Track Shop Floor kiosks record labor, job operations and WIP in SyteLine, with setup steps, common pitfalls and where a private AI layer helps.
- Infor Factory Track Time Track with SyteLine: attendance and labor captureHow Infor Factory Track Time Track captures clock-ins, breaks, absences and labor for SyteLine, applies attendance rules and prepares payroll data.
- Infor Factory Track Warehouse Mobility with SyteLine: receiving, moves, counts and issuesHow Factory Track Warehouse Mobility uses Mongoose and barcode scanning for receiving, moves, counts and material issue in SyteLine, with setup and pitfalls.
Guides
- CloudSuite Industrial 10 to 11 Migration GuideStep-by-step migration guide for upgrading Infor CloudSuite Industrial (CSI) from version 10 to 11, including ION integration, form updates, and testing.
- CloudSuite Industrial Cloud Security ArchitectureUnderstand CloudSuite Industrial cloud security architecture including identity management, encryption, network security, and compliance for CSI deployments.