HTTPS operations
Signed-in reads and changes go through the Ysend API, limited to the right account, warehouse, device and user.
Connectivity and continuity
Cloud first. Peer capable. Local components only when they earn their place.
Supported applications connect directly to Ysend over HTTPS and realtime hubs. Offline queues and the handheld peer mesh preserve bounded work; desktop bridge, equipment tunnel and store-and-forward edge remain distinct optional components.
Default route
The application talks to SaaS directly
A warehouse application server is not a prerequisite. Each enrolled client keeps its own identity, scope and cloud session.
Realtime state
Hubs carry fresh operational updates without transferring business authority to a local relay.
Direct fallback
When no local bridge is configured or reachable, the handheld continues with its direct cloud path.
Device custody
Offline acknowledgement is not cloud confirmation
-
Capture The origin device records its own operation
Each event gets a unique ID so it is never recorded twice, and the related task details are stored locally.
-
Acknowledge Local storage confirms only receipt on the device
The interface does not call the operation cloud-accepted yet.
-
Upload The device sends directly when connectivity returns
Retries keep the same event identity so duplicate delivery is safe.
-
Confirm SaaS validates and records the outcome
The device’s record does not replace confirmation by Ysend.
Warehouse peer mesh
Handhelds can converge work across the LAN without a server
Supported handheld instances listen for peers, discover one another and exchange operation events plus signed reference records.
Disconnected work
Peers exchange bounded events while cloud access is unavailable; a desktop station may join as an optional peer.
Origin responsibility
When the WAN returns, each device normally uploads its own work directly to SaaS.
Dark-origin recovery
An idle peer may upload a replicated event for an origin device that is no longer available.
Fail-closed envelope
Account, warehouse, device, key period, signature and expiry are checked; reusable logins or API keys are never accepted in messages between devices.
Optional local components
Three local roles, none of them a mandatory warehouse server
Per station
Desktop device bridge
The bundled station agent connects scanners, printers and cameras and may act as a mesh peer or WAN relay.
Per equipment site
Outbound equipment bridge
A vendor-enrolled agent carries authorised TCP adapter streams through outbound-only cloud tunnels.
Per warehouse, opt-in
Store-and-forward edge
The separate local edge software is off by default and must be configured and installed for each warehouse.
NAT-behind equipment
Reach local equipment without opening an inbound port
Agent opens control channel
The enrolled site agent establishes an outbound WebSocket to SaaS.
Cloud authorises equipment
The site allowlists exact endpoints and pairing credentials are stored as hashes.
A data channel opens
Each authorised equipment connection receives a separate duplex binary channel.
Existing adapter runs
TCP machine or robot traffic crosses the tunnel while SaaS remains authoritative.
Cloud reconciliation
Redundant delivery converges on one event identity
Origin uploads, peer rescue and local relays can overlap. The SaaS validates identity and deduplicates rather than asking the warehouse to choose a winner.
Identity
The same operation keeps the same unique ID through retries and copies, so it is never applied twice.
Validation
Scope, sequence, age, signature and workflow state are checked before acceptance.
Outcome
The cloud response establishes accepted, rejected or already-recorded state.
Fleet supervision
Enrol, monitor and update each device from one place
Enrollment
Device identity and warehouse assignment are explicit and revocable.
Telemetry
Connectivity, version, health and workflow signals support remote diagnosis without granting unlimited control.
Self-update
Managed devices can receive approved app updates and keep their access limits.
Retirement
A removed or expired identity fails closed across cloud, mesh and bridge paths.
Draw the topology before choosing edge components
List applications, equipment endpoints, WAN failure modes and custody requirements. We will keep direct SaaS, peer mesh, equipment bridge and optional edge separate.