Scan2Flow captures barcodes in the browser and routes them to your REST API or webhook. It is not a WMS, TMS, or FSM. Use it when your system owns the data and you need scan stations without deploying the full vendor mobile app.

Compatibility matrix

Workflow	Today
Single-item receive (1 scan → POST)	Yes
Single pick confirm	Yes
Lookup then confirm (GET → display → POST)	Partial
Bulk receive / pick (N scans → 1 POST)	No
Cycle count session	No
Task-guided picking from WMS	No
Offline scan queue	No
Two-way sync (WMS pushes tasks)	No
FSM work order confirm (1 scan → POST)	Yes
FSM asset lookup (GET → display → POST)	Partial
FSM parts consumption scan	Yes

What works today

Single scan POST/GET to your WMS, TMS, or FSM API with Bearer, Basic, or custom auth
Pattern and format rules to separate SKU, location, or shipment code types
Lookup workflows with display or HTML confirmation before update
USB/Bluetooth wedge scanners and audio pass/fail for scan stations
Field service asset and work order scans to FSM REST endpoints or middleware webhooks

Known gaps (roadmap)

Bulk scan buffer and batch send - scan many items, submit once
Offline queue and retry when connectivity returns
CSV export of scan history for audits
Session fields (operator, dock, task ID) across scans
Importable connector packs for common WMS API patterns

Verification checklist

One scan triggers one authenticated API request with expected payload
Pattern rules reject or accept the right barcode types
Lookup flow returns and displays record data before update
Bulk test: three scans today produce three API calls, not one batch
Offline test: scans are not queued automatically (expected until roadmap ships)
FSM test: asset lookup returns record context before work order or parts update POST

Building a WMS, TMS, ERP, or FSM integration? We partner with system vendors on connector packs.

Partner with us

Workflow guide