The Weekly Report Problem
Most Amazon Relay carriers have some version of the same problem: every week, someone on their team downloads the settlement CSV, opens it in Excel, does some manual cleanup, writes some formulas, maybe copies data into a template, and produces a report that looks slightly different from the one they made last week. It works, but it's fragile, slow, and dependent on whoever built the template knowing what they're doing.
When that person is out, the report either doesn't get done or someone else has to figure out the spreadsheet from scratch. When Amazon changes a column name in the export format, formulas break. When you add a new truck to the fleet, the template needs to be updated. It's a maintenance burden that compounds over time.
What a Good Weekly Report Actually Needs
For Amazon Relay operations, a useful weekly report contains:
- KPI summary — total revenue, total miles, trip count, average revenue per mile for the week
- Per-truck breakdown — revenue and miles by tractor ID, so you know which units earned what
- Per-driver breakdown — loads completed, miles, and revenue by driver name
- Load-level detail — the underlying trip data with pickup/dropoff dates, origin, destination, load pay, and status
- Totals row — summed at the bottom for quick verification
That's the structure. Getting from a raw Relay CSV to a formatted report with all of those sections is the part that takes time when you're doing it manually.
What Relay Dashboard Exports
When you export from Relay Dashboard, you get a styled multi-sheet Excel workbook. The first sheet is a summary of all trips — revenue, miles, status, driver, tractor, origin, destination, and load ID — with a formatted header row, alternating row colors for readability, and a totals row at the bottom. If you're viewing All Trucks, the workbook includes one sheet per tractor automatically, so your accountant or fleet manager can go directly to the sheet for a specific unit without filtering.
The report also includes a KPI banner at the top showing total revenue, miles, trip count, and average per mile — the four numbers most people are looking for first. These are calculated from whatever data is currently filtered in your dashboard, so if you've filtered to a specific week or a specific truck, the export reflects that exact view.
Filtering Before You Export
The most useful feature for weekly reporting isn't the export itself — it's the filtering. Before you export, you can filter by date range and by truck. Filter to the current week, select a specific tractor, and export. That Excel file is the weekly report for that truck. Do it for each truck, or export all trucks at once with per-truck sheets. Either way, it takes about 30 seconds per report once the CSV is uploaded.
You can also export as CSV instead of Excel if your accounting software or payroll system prefers CSV input. The CSV export is a flat file with all the same data in plain comma-separated format — no formatting, just the rows and columns, clean and ready to import wherever it needs to go.
Sharing With Your Accountant or Payroll Team
One of the practical benefits of having a clean, consistently formatted Excel export is that it's shareable without explanation. Your accountant doesn't need to know what Amazon Relay is or how to read a raw settlement CSV. They get a formatted spreadsheet with labeled columns, a totals row, and a KPI summary at the top. That's a file they can work with immediately.
The same applies to your payroll team. If you're paying drivers based on loads completed or miles driven, the per-driver breakdown in the export gives payroll the numbers they need in a format they can actually use — without having to ask you to pull anything manually from the portal.
Upload Once, Report in Seconds
The workflow is: download your Relay CSV, upload it to Relay Dashboard, filter to the period you're reporting on, click Export. Done. The report is the same structure every week — same column order, same formatting, same KPI banner — so whoever receives it knows exactly where to look. No rebuilding, no formula maintenance, no one-off cleanup.