Standard scanner
Default on /scanner
App chrome with bottom nav, camera-first layout, workflow picker, and demo tools. Best for first visits, BYOD trials, and desk-side setup.
Workflow guide
Workflows tell Scan 2 Flow what to do after a scan. Choose one action, add optional filters, and test with the built-in demo flows.
Scan, match, act
What is a workflow?
A workflow runs one action when the active scan matches its rules. This is the core of barcode-first workflows: scan first, then trigger the configured action. Demo flows include tickets, inventory items, assets, and pharmacy products.
Scan
Capture with camera, scanner input, or manual entry.
Match
Use the active workflow plus optional format and pattern rules.
Act
Open a URL, call an API, render data, or show a page.
Barcode-first workflows
Barcode-first workflows start with a scan, not a form. The operator captures a barcode or QR code, Scan2Flow matches workflow rules, then triggers the configured action.
Two scanner usage modes
Scan2Flow has two ways to use the scanner page. Standard mode is the default for exploration and camera scanning. Terminal mode is the floor station layout for pinned devices and Flow Link QR deploy.
Terminal scan station
Settings, Flow Link, or ?mode=terminal
Full-screen station UX: workflow menu, wedge-first active task, large last-result feedback, and no marketing chrome. Best for warehouse lanes, docks, and MDM-pinned handhelds.
Flow Link and station QR
Deploy a scan station without typing URLs on the floor. Flow Link is a URL-only QR that opens terminal mode with one workflow selected.
1
Create the workflow on the device
Build and enable the workflow on the Flow page. Station URLs reference the workflow id stored in this browser.
2
Copy link or download QR
On each enabled workflow card, use Copy station link or Download QR. The URL looks like /scanner?mode=terminal&workflow={id}&source=external.
3
Pin or print at the station
MDM home-screen shortcut, printed QR at a dock, or emailed link to rugged Android in Chrome. Operators land in terminal menu or the linked task.
Flow Link vs Flow UI
Flow Link (Layer A) encodes only the station URL - not item barcodes and not workflow JSON. Flow UI (Layer B) is when that workflow uses show_iframe or api_call_display so your server renders the operator screen after each scan.
Build a workflow in three decisions
Decision 1
What codes should run it?
Choose whether the workflow catches any allowed format, only QR codes, only barcodes, or values matching a specific pattern.
Decision 2
Where should the value go?
Send the scanned value to a URL, an API, a webhook-style receiver, a rendered HTML card, or a trusted iframe.
Decision 3
What should staff see?
Decide whether the operator needs silent routing, visible returned fields, HTML output, iframe content, or success/failure audio feedback.
Open Scan, choose or create a workflow, and test it with a real code or manual entry.
Action types
Pick the action that matches the job. Configure URLs, API endpoints, display fields, and feedback behavior inside each workflow.
Open URL
Open a page or deep link after a scan.
API Call
Send the scanned value to an HTTP endpoint.
API Call & Beep on Status
Call an API and play a success or failure beep based on the response status.
API Call & Display
Show selected fields from an API response in the browser.
API Call & HTML/JS Render
Render a small HTML/JS view from API response data.
Load link in Iframe
Show a trusted web page in an iframe using the scanned value.
When does the selected workflow run?
Only the selected workflow runs. The scan still has to pass its format and pattern rules:
Format filter
Format: Limit the active workflow to specific barcode types (e.g. QR Code only) or "Any Format" for any type allowed in Settings.
Pattern match
Pattern: Enable "Pattern match" and enter a regular expression. The scan must match the regex for the selected workflow's action to run.
Developer APIs
Use the API docs to decode barcode images or generate QR code images from text.