# RF Plus (Portable Intelligence) with Infor SyteLine: barcode receiving, production, counts and shipping > Source: https://netray.co/stack/rf-plus-barcode-scanning-infor-syteline > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Stack ## Short answer RF Plus is Portable Intelligence's warehouse barcode suite, offered in an edition built for SyteLine / CloudSuite Industrial. Handheld scanners post receiving, production, count and shipping transactions into SyteLine through a vendor-built ERP connector, so inventory is updated at the moment of the scan instead of at the keyboard. ## Erp Infor CloudSuite Industrial (SyteLine) ## Erp Key syteline ## On Prem true ## Product RF Plus for SyteLine/CSI ## Vendor Portable Intelligence ## Category RF and WMS ## Integration **Method:** Vendor-built ERP connector **Detail:** Portable Intelligence ships a SyteLine/CSI edition of RF Plus, so the scanner screens map to SyteLine transactions without custom development on your side. The exact transport (IDO calls, stored procedures or direct SQL) is a vendor implementation detail you should confirm in writing during scoping, because it decides how upgrades and the SyteLine database behave. **Method:** Wi-Fi handhelds against an on-prem server **Detail:** In a typical on-prem install the RF application runs on a server in the plant and talks to the SyteLine application and database tier over the LAN. Handhelds connect over the warehouse Wi-Fi, which is why coverage and roaming matter as much as the software. ## Data Flows **From:** SyteLine **To:** RF Plus **Data:** Open POs, jobs, customer orders, items, locations, lot and serial masters **Trigger:** On scan or lookup, with cached master data refreshed on a schedule **From:** RF Plus **To:** SyteLine **Data:** PO receipts and putaway moves **Trigger:** Scan of PO line and location at the dock **From:** RF Plus **To:** SyteLine **Data:** Job material issues, labor and quantity completed **Trigger:** Operator scan at the work center **From:** RF Plus **To:** SyteLine **Data:** Cycle count and physical inventory counts **Trigger:** Count task completed on the handheld **From:** RF Plus **To:** SyteLine **Data:** Pick confirmation and shipment quantities **Trigger:** Scan of item and package during pick and pack ## Setup ### Scope the transactions **Detail:** List which flows you want on the scanner first: receiving, putaway, job issue, counts, shipping. Start with receiving and counts, which have the fastest payback and the least process change. ### Confirm the SyteLine version and edition **Detail:** Check with Portable Intelligence that your SyteLine release (on-prem or CloudSuite Industrial) is supported and how the connector is licensed per device or per user. ### Clean the item and location masters **Detail:** Barcodes only work if item numbers, UoM and warehouse locations are consistent. Fix duplicate or retired items and standardise location naming before go-live. ### Print and test barcode labels **Detail:** Decide what each label encodes (item, lot, PO line, location) and print samples. Test them on the exact scanner models you will deploy under real plant lighting. ### Configure users and permissions **Detail:** Create SyteLine users or a service account for the RF server and limit what each scanner role can post, for example receiving clerks versus production operators. ### Run a parallel pilot **Detail:** Run one warehouse area on scanners for a week while someone reconciles against SyteLine. Compare on-hand by location at the end of each day. ### Cut over and train **Detail:** Train by role on the handheld screens, set a cycle count schedule, and keep a written fallback procedure for when Wi-Fi or the RF server is down. ## Pitfalls - Unit of measure mismatch between the PO line and the stocking UoM produces receipts at the wrong quantity; test every UoM conversion on the scanner, not only in SyteLine. - Lot and serial controlled items need the right tracking flags and numbering in SyteLine before the first scan, otherwise receipts fail or create untraceable stock. - Weak Wi-Fi coverage causes half-posted transactions and duplicate scans; survey dead zones in racking aisles and freezers. - Scanner posts depend on the SyteLine data model, so a SyteLine upgrade or customised form can break a screen. Retest the RF flows in your test environment before every upgrade. - Negative inventory and location-less stock appear when operators issue material that was never received by scan. Decide your policy before go-live. - A shared service account hides who posted what; use individual operator IDs so SyteLine audit trails stay meaningful. ## Ai Layer ### Scan exception triage **Description:** A private assistant reading SyteLine transaction history and the RF error log can group failed or rejected scans by cause (UoM, closed PO line, missing lot) and list the likely fix for each, for a supervisor to approve. ### Count variance explanations **Description:** After a cycle count, it can pull receipts, issues and moves for the item and location and propose why on-hand differs, such as a receipt posted to the wrong location. ### Plain-language inventory questions **Description:** Planners and supervisors can ask where a lot is, what was received today without a putaway, or which jobs are waiting on material, answered from SyteLine data on your own servers. ### Draft label and master data fixes **Description:** It can find items with missing UoM conversions or duplicate locations and draft corrections for a person to review before anything is written to SyteLine. ## Alternatives - Infor Factory Track Warehouse Mobility is Infor's own Mongoose-based scanning module for SyteLine and avoids a third-party vendor if its screens fit your process. - A broader WMS is a better fit if you need wave planning, directed putaway or multi-site slotting, which a transaction-capture scanner suite does not aim to cover. - For very small operations, keyboard entry plus weekly cycle counts in the standard SyteLine inventory forms may be enough. ## Faq ### Does RF Plus replace SyteLine inventory screens? **Answer:** No. SyteLine remains the system of record. RF Plus is a data collection layer that posts receiving, issue, count and shipping transactions into it from handheld scanners, so users still use SyteLine for setup, reporting and exceptions. ### Is RF Plus the same as the generic RF Plus product? **Answer:** Portable Intelligence describes it as the same RF Plus warehouse barcode suite offered in a SyteLine/CloudSuite Industrial edition. The ERP-specific edition is the part that talks to SyteLine, so ask the vendor which version and connector you would receive. ### Can it run fully on-prem? **Answer:** Barcode data collection is commonly deployed on a server inside the plant with handhelds on local Wi-Fi, but deployment options are the vendor's to confirm. For SyteLine on-prem, ask for the server requirements and whether any cloud component is mandatory. ### Where does AI fit in? **Answer:** Not in the scan itself. A private AI layer sits beside both systems and helps with exceptions, count variances and questions in plain language, read-only by default, with human approval for any write back. ## Source https://www.portable-intelligence.com/ ## Search terms rf plus syteline barcode scanning, portable intelligence syteline, syteline barcode receiving, syteline cycle count scanner, csi rf data collection, syteline handheld scanner --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json