One platform.Four ways in.
Hand us the whole flow, build it yourself, ask an AI teammate, or call the API. Every route runs on the same live network of 3,400+ connections.
01 · Managed Flows
Custom integrations, built and run for you.
Tell us what needs to move and where. Our specialists scope the flow, build it against your real bookings, launch it with your team and watch it every hour after.
- A named solutions engineer and a 24/7 operations desk
- Built and tested against live bookings in a sandbox first
- Monitoring, alerts and fixes included, not billed per incident
- Booking received from carrier0.4s
- Mapped to the purchase order0.9s
- Customs entry filed with broker2.1s
- Gate slot booked at the terminal1.3s
- Warehouse told the new ETA0.6s
- Proof of delivery matched to invoice0.8s
02 · Flow Studio
Design and automate flows visually.
Drag in a trigger, map the fields, add rules for the exceptions. Flow Studio shows every step running live, so your ops analysts can build and change flows without waiting on IT.
- 400+ prebuilt steps for carriers, ports, brokers and ERPs
- Every change versioned, with one-click rollback
- Test runs on real data before anything is published
03 · Pilot
An AI teammatefor daily ops.
Pilot connects to your ops tools, learns how your team works and handles the repetitive tasks in plain language: chasing carriers, checking holds, rebooking slots and drafting customer updates.
- Answers from live shipment data, not guesses
- Acts only within the permissions you set
- Hands anything unusual to a person on our ops desk
04 · Open API
One connection to 3,400+ carriers and systems.
One key reaches every carrier, port, broker and system in the Quayside network. Scope it read-only, run-flows or full access, and get the same clean shipment model everywhere.
- REST endpoints and signed webhooks on one shipment model
- Keys scoped read-only, run-flows or full access
- 99.98% API uptime over the last twelve months
POST /v2/flows/run Authorization: Bearer qs_live_••••7f3a { "flow": "bookings-to-erp", "lane": "RTM-CHI", "booking": "QS-48213" }
{
"status": "delivered",
"erp_order": "PO-118204",
"eta": "2026-10-23T09:00Z"
}Which way infits your team?
Most customers start with one and add another within a year. All four run on the same network, the same shipment model and the same ops desk.
How a flow runs
Five steps,every single time.
Whichever way you come in, every update follows the same path, and every step is logged so you can see exactly what happened to a shipment and why.
- 01
Trigger
A booking, EDI message, email or API call starts the flow.
- 02
Normalise
Every source is mapped into one clean shipment model.
- 03
Check
Rules catch missing documents, holds and mismatches early.
- 04
Deliver
Updates land in your ERP, warehouse system and customer portal.
- 05
Watch
Our ops desk monitors every run and handles the exceptions.
