Mobile scanning
Connect scanner hardware
Use the YiTaiCOS Mobile App camera, PC-connected keyboard scanners, or Android handheld scanner output without creating a second picking workflow.
Where this page belongs
Publish this operator guide on docs.yitaicos.cn. Use dev.yitaicos.cn only when a developer is building a native scanner bridge, vendor SDK plugin, or API contract.
The app is already a scanner
The YiTaiCOS Mobile App camera path needs no external scanner hardware.
Hardware connects to the working device
USB or Bluetooth scanners should connect to the PC, tablet, or handheld that runs YiTaiCOS.
One scan bridge
Camera and hardware input feed the same YiTaiCOS scan processing path.
Connection model
A scanner is only an input device. The device that runs YiTaiCOS receives the scanned text, then YiTaiCOS resolves products, orders, labels, picking, inventory, and stage movement on the server.
Mobile app camera
No external scanner is attached. The phone or tablet camera scans directly inside the YiTaiCOS Mobile App.
PC packing station
Connect a USB or Bluetooth scanner to the PC. Configure it as HID keyboard input so it types the scanned code into the focused YiTaiCOS scanner input.
Android handheld
Run the YiTaiCOS Mobile App on the handheld. Zebra DataWedge, Honeywell, or similar tools should output keyboard text into the app.
Custom native bridge
Use only when keyboard output is not possible. The bridge still hands the normalized scan value to YiTaiCOS server APIs.
Supported paths
Choose the path based on where the operator works. A scanner connected to a PC is correct for a packing station; the mobile app camera is correct when the phone or tablet itself is the scanner.
| Mobile scanning | Connected to | YiTaiCOS profile | Notes |
|---|---|---|---|
| YiTaiCOS Mobile App camera | Phone or tablet camera | Camera | Primary mobile scanning path. No external hardware required. |
| Generic USB or Bluetooth scanner | PC, tablet, or handheld | Generic keyboard wedge | Use HID keyboard mode and send Enter, CR, or LF after each scan. |
| Zebra DataWedge | Zebra Android handheld | Zebra DataWedge | Configure barcode input with keyboard output into the foreground YiTaiCOS app. |
| Honeywell keyboard scanner | Honeywell handheld or PC | Honeywell keyboard | Use keyboard wedge or HID mode with an Enter, CR, or LF suffix. |
Setup steps
Use this checklist for own hardware scanners. Camera scanning in the mobile app does not need these steps.
- Connect or pair the scanner with the PC, tablet, or handheld that runs YiTaiCOS.
- Set the scanner to HID keyboard input or keyboard wedge mode.
- Configure an Enter, CR, or LF suffix after every scan.
- Disable hidden prefixes when possible. YiTaiCOS normalizes common AIM prefixes such as ]C1, but plain text is easier to support.
- Open YiTaiCOS and go to the scanner workspace.
- Select the required work area, such as Dispatch or Inventory.
- Focus the hardware scanner input and choose the matching hardware profile.
- Scan a known SKU, barcode, tracking number, or shipment label and confirm the expected result.
Stage scanner behavior
Configure Dispatch stage automation in Orders -> B2C fulfillment -> Stage Editor -> Execution logic -> Warehouse picking -> Scanner behavior.
Shipping label / tracking number
Move the matched order when a label, shipment, or tracking code is scanned.
SKU
Move the active order when the scanned SKU matches an order line.
Barcode
Move the active order when the scanned product or variant barcode matches an order line.
Custom bridge
A custom bridge is developer work. Keep this operator page focused on setup, and document implementation details on dev.yitaicos.cn.
- Do not call Dispatch stage APIs directly from scanner firmware.
- The bridge should normalize the scan value and hand it to the same YiTaiCOS scanner workflow.
- Tenant scope, permissions, validation, and audit events remain server-side in YiTaiCOS.
- Do not expose vendor SDK payloads, credentials, request bodies, or database details to operators.
Testing
Run these checks before using scanner hardware in production.
- A SKU scan resolves the expected product or variant.
- A product barcode scan resolves the expected product or variant.
- A tracking or shipment-label scan selects the expected Dispatch order.
- A Dispatch product scan picks against the active order when picking is enabled.
- Configured scanner behavior moves the matched order to the next stage.
- An unknown code shows a safe no-match result and does not mutate data.
- Repeated scans do not create unintended duplicate work.
- The activity or audit trail reflects every server-side mutation.
Troubleshooting
Most scanner issues are input-focus, suffix, profile, or permission issues.
| Nothing happens after scanning | Confirm the scanner input is focused, the scanner is in HID or keyboard wedge mode, and an Enter/CR/LF suffix is configured. |
|---|---|
| Characters look wrong | Check keyboard layout, hidden prefixes, and the selected hardware profile. YiTaiCOS normalizes common full-width Latin letters and digits, but the scanner should still output plain text. |
| The wrong workflow runs | Confirm the selected work area and the Stage Editor scanner behavior settings. |
| Dispatch stage does not move | Confirm that the stage has scanner behavior enabled, the order is matched, SKU/barcode scans have an active order, and a next stage exists. |
Safety rules
Scanner hardware must not become a trusted actor. It only supplies text input.
- Do not bypass YiTaiCOS login, tenant context, permission checks, or audit paths.
- Do not maintain a second desktop scanner workflow for the same picking or Dispatch operation.
- Do not send raw provider or device diagnostics to browser copy.
- Use dev.yitaicos.cn for bridge implementation contracts, not for operator setup steps.