Operator surface
Tauri interface
Packing and receiving sessions show the task, the items, device feedback and proof.
Fixed station operations
Use scanners, printers and cameras from each workstation.
The application connects to Ysend for each session and uses the workstation’s scanners, printers and cameras. It can also exchange data with other devices on the local network when that option is enabled, without turning the workstation into a required warehouse application server.
Station anatomy
UI, device bridge and SaaS keep separate responsibilities
Local I/O
Bundled Go bridge
The per-station agent handles scanner, printer and camera access close to the hardware.
Authority
Direct SaaS backend
The authenticated backend remains the source of business state and accepted operations.
Secure session
Peripheral access stays inside the authenticated workstation session
Sign in
The station establishes an authorised SaaS session for the operator and site.
Proxy locally
The bundled bridge receives only the bounded device calls required by that session.
Capture
Scans, prints and camera proof stay attached to the current task and items.
Commit
SaaS validates the resulting operation before downstream state advances.
Peripheral loop
Every device action has an operational purpose
Scanner
Identifies order, LPN, carton, pallet, item or station context.
Printer
Produces the label selected by the active packing or receiving workflow.
Camera
Captures bounded proof associated with the task instead of an unscoped image folder.
Session proxy
Keeps local device access behind the authenticated desktop operation.
Local SQLite
Continuity state stays local and reconcilable
Session continuity
The station can preserve bounded local state through a short connection loss.
Queued evidence
Pending device events remain distinguishable from server-accepted warehouse work.
Reconciliation
The same operation identity supports safe retry when the SaaS path returns.
Optional mesh role
The station may be a peer or WAN relay
Mesh participation is an optional resilience function. Handheld peers continue to work without the desktop bridge.
-
Peer Exchange bounded LAN events
The station can participate in the signed warehouse peer mesh.
-
Relay Forward when WAN is available
It may help upload replicated work while SaaS deduplicates by event identity.
-
Direct Keep its own backend path
The station itself connects through the configured SaaS URL.
Station boundary
Bundled local agent does not mean on-premises business authority
Specify the station by workflow and peripherals
Bring packing or receiving steps, scanner and printer models, camera-proof needs and network constraints. We will map the per-station bridge and optional mesh role.