Capture shipment codes
Scan shipment IDs, cartons, route labels, dock labels, or proof-of-delivery codes from a browser device.
Capture shipment, route, carton, or delivery barcodes in the browser and send the values to a TMS-connected endpoint.
Transport scan input for TMS handoff
Scan shipment IDs, cartons, route labels, dock labels, or proof-of-delivery codes from a browser device.
Use separate workflows for loading, dispatch, handoff, delivery confirmation, exception capture, or status checks.
Forward the scan value to a TMS API, webhook receiver, automation tool, or logistics middleware that owns shipment state.
A transport workflow can capture a shipment barcode and pass it to the system responsible for status, route, or delivery updates.
The receiving TMS or middleware endpoint should decide how to map the scan into shipment status or logistics records.
{
"barcode": "{{data}}",
"source": "scan2flow",
"workflow": "tms-shipment-status",
"operator_context": "browser-scan-station"
}No. Scan2Flow captures and routes scan input. Your TMS, logistics middleware, or backend remains responsible for shipment records and status updates.
Yes, if your receiving endpoint is configured to treat the scanned value as a delivery, handoff, or status event.
Yes. Workflows can use barcode format and pattern matching so different labels or prefixes route to different actions.
Scan2Flow runs in the browser and can use supported device cameras, scanner input, or manual entry. Suitability depends on the device, environment, and your operating process.
We partner with WMS and TMS vendors on connector packs (importable workflow templates plus setup docs). Contact us via the integrations partners section or the contact page.
Start with browser scan capture, then connect the workflow to the endpoint that owns shipment status.