Cloud connected label printing

Expedy's Cloud Print lets a shipment trigger a label at a connected printer without a driver installed on that machine, which fits how the tool bills itself as an IoT enabled print layer. A Beam agent can trigger a print job once a shipment record is marked ready, sending it to the printer tied to that location rather than waiting on someone to open a queue. Failed print jobs, or ones aimed at a printer the account does not have permission for, get routed to a person to resend rather than retried silently by the agent.

Transport management records

The TMS side of Expedy holds shipment and carrier records that a logistics team works from, covering bookings and the automation built on top of them through its API. A Beam agent reads a shipment once it is created, applies the carrier or routing rule the team has approved, and updates the record with the booking result where the connector and account permissions allow it. Shipments with missing carrier details, or ones outside the routing rule the team has set, are left for a logistics coordinator to place manually.

API driven shipment automation

Expedy exposes its cloud print and transport functions through an API, which is how its automation layer connects a shipment event to a label or a booking without someone opening the software directly. A Beam agent calls that API when a workflow reaches a shipping step, passing along the shipment details already confirmed elsewhere and reading back whatever confirmation the API returns. Where the API call fails, times out, or returns a result the agent cannot match to an open shipment, the case is handed to a person rather than retried indefinitely.