Freight Run Sorting: Export Completed Stops & Push POD
Freight run sorting made easy: export completed stops with proof of delivery to TransVirtual or other TMS tools, and auto-push POD events via webhook.
The daily grind of closing out a freight run
You've finished the last drop. The truck's empty, the driver's done. But for the fleet controller, the day is far from over. Now comes the paperwork: matching paper PODs to consignments, typing notes into the TMS, chasing drivers for missing signatures or photos. It's hours of admin that adds no value — and it's error-prone.
If you're still doing this manually, you're not alone. Many freight operators run on a mix of paper, phone calls, and spreadsheets. But there's a better way. This article shows you how StopSorted's freight export and POD push can hand off completed stops automatically, so your team can go home on time.
How it works: from driver's tap to TMS record
StopSorted already handles the hard part: sorting your run into a sensible pallet delivery sequence, giving drivers numbered stops, and capturing proof of delivery at the door — signature, photo, or both.
What's new is the handoff. Once a stop is completed, StopSorted can package that stop's data — address, time, consignment details, POD images — into a format your freight or transport management system understands. You can either pull that data on demand via an API, or have StopSorted push it automatically to a webhook on a schedule you set.
No more double entry. No more lost paperwork.
Setting it up: a step-by-step walkthrough
- Sign in to StopSorted as a fleet user with Routes access.
- Go to Fleet Settings → Freight.
- Under Export format, choose the shape that matches your TMS: TransVirtual-compatible, MachShip-compatible, Onfleet-compatible, CargoWise/EDI-friendly, or Generic.
- If you want automatic pushes, enter your POD webhook URL (must be HTTPS).
- Optionally, set a Webhook signing secret — StopSorted will send an HMAC-SHA256 signature in the
X-StopSorted-Signatureheader so you can verify the data is genuine. - Turn on Auto-push POD to webhook.
- Set the Push interval — default is 5 minutes, adjustable from 5 to 120.
- Save.
That's it. The platform checks about once a minute and fires when your interval has elapsed. You can also hit Push POD now to send immediately.
If you prefer to pull data instead, use the export API:
GET /api/fleet/{fleetId}/exports/stops?format=transvirtual
Optional query params: from, to (dates), completed_only=1. Other format values: stopsorted, machship, onfleet, cargowise, generic.
What the driver sees vs what the office sees
The driver's world stays simple. They open the StopSorted app, see their numbered stops in sorted order, and at each drop they capture a signature or photo. They tap 'complete' and move on. No extra screens, no fiddling with exports.
The office sees the payoff. In the fleet login, completed stops appear with all POD attached. If auto-push is on, those stops flow into your TMS or webhook without anyone touching a keyboard. The controller can monitor progress, but the handoff is automatic.
Your customer? They just get their freight. But if you share PODs with them, you can do it faster because the data is already digital and organised.
A realistic scenario: from 2 hours of admin to 10 minutes
Meet Sarah, a fleet controller for a mid-sized freight company. Every afternoon, she waits for drivers to return with paper PODs. She then manually enters each consignment into the TMS, scans signatures, and emails photos to customers. It takes her two hours daily, and mistakes happen — a missing signature here, a wrong consignment number there.
Now imagine Sarah's company uses StopSorted with TransVirtual export and auto-push POD turned on. Drivers capture PODs on their phones. As each stop completes, StopSorted pushes the data to their webhook every 15 minutes. Sarah opens the TMS and sees completed stops already populated with POD images and signatures. She spends 10 minutes reviewing exceptions, then goes home on time. No manual entry, no lost paperwork.
Frequently asked questions
Do I need a private API key from my TMS vendor? No. StopSorted matches common field names used by popular freight systems. Your TMS may still need a small mapping on their side, but we don't require a private vendor key.
Can I turn off auto-push and just use the API? Yes. Turn auto-push off anytime; the export API still works for pull. You can also use 'Push POD now' for one-off sends.
What if a push fails? StopSorted retries on failure. Each completed stop is pushed once, but if the webhook doesn't respond, it will try again. You can monitor and adjust in settings.
How do I get POD photos into the export? First, turn on proof of delivery photos in your StopSorted settings. Then choose an export format that includes POD fields — most do. The photos will be included as URLs or base64, depending on the format.
Ready to streamline your freight handoff?
StopSorted's freight export and POD push are built to save you time and reduce errors. It's available now for fleets. To see how it fits your operation, visit our pricing page or read the full freight export and POD push guide.
If you're new to StopSorted, start with a free account and explore the fleet features. When you're ready to activate paid phones, you can add a card and scale as you grow. Coverage is expanding — Australia is live today, and we're adding more countries as requests come in. We welcome every market and are happy to help you get started, wherever you are.
Ready to try this on your fleet?
Create a free fleet account, approve the phones that will run, and sort the first morning. You add a card only when you turn on paid seats. Pricing is by phone that runs, not by login.
Office staff start at the landing page. Solo drivers can get the Android app.
How-to
Step-by-step for this topic: fleet/freight export pod push.