Skip to content
DynaCargo DynaCargo Docs

Live tracking and waybills

Every trip has a live tracking link you can share with anyone, and a digital waybill for the driver to show at checkpoints. Only the tracking link works without a DynaCargo login — the waybill itself asks the viewer to sign in, so it’s the QR code on it, not the page, that a checkpoint official uses.

  1. Open the trip: Dashboard → Trips.
  2. Click Share tracking. Your device’s share sheet opens, or the link is copied and you’ll see “Link copied”.
  3. Send it on.

Live map next to it opens the same public page yourself, which is the quickest way to check what your recipient will actually see before you send the link.

The link points at /track/{token} and is public — anyone holding it can open it, with no login. Share it with the consignee, the receiving warehouse, your client’s operations desk. Treat it like any other link: whoever you send it to can forward it.

What the recipient sees

A page headed DynaCargo · Live tracking with:

  • An OpenStreetMap map showing Pickup (green), Delivery (red) and the Truck, plus a breadcrumb trail of where it’s been.
  • Status updates — the trip’s timeline as the driver logs each step.

The page refreshes itself about every 60 seconds, so it can be left open on a screen.

A token that’s invalid or expired shows “Tracking link unavailable” rather than an error.

How the position is reported

Position comes from the driver’s device while the trip is running, roughly every 5 minutes in transit, dropping to every 15 minutes when the truck hasn’t moved. If the driver denies the browser location prompt or has no signal, the map keeps the last known position and the timeline keeps working — status updates don’t depend on GPS.

While tracking is active the driver’s trip page says so: “Live tracking is on. Keep this tab open and your screen awake — mobile browsers pause location in the background.” That’s worth passing on to drivers, because it’s the usual reason a truck appears frozen on the map — the phone locked, not the signal dropped.

Both parties see the same map on the trip page itself, so shippers don’t need the share link for their own trips.

The waybill

Waybill on the trip opens /waybill/{bookingId} — a Digital Waybill on a full-white background, headed with the booking reference and date.

It lists Shipper, Transporter, Origin, Destination, Cargo, Weight and Vehicle. Any of those the booking doesn’t carry shows as a dash — an individual shipper with no company profile shows — against Shipper, and a trip with no truck assigned shows — against Vehicle. That’s the field being empty, not an error.

Below that is a Scan to verify QR code, then Download PDF and Print.

The waybill page needs a login. Sending its URL to a client or a border official will land them on the sign-in screen. What they can open is the QR code, which resolves to /verify/{token} — a public page needing no account. So the working pattern is: print it or show it on the driver’s screen, and let them scan.

The QR is rendered on the server, so it survives printing and appears even with JavaScript disabled — which matters when the person checking it is holding a sheet of paper at a weighbridge.

Where to go next