Most Amazon DSP owners review one number every month, the bottom line of the profit and loss (P&L) statement. That number arrives too late to act on, and it is too aggregated to guide any real decision. If your March P&L shows lower net income than February, the number itself will not tell you whether the drop came from overtime, chargebacks, fuel, or a scorecard tier lag. All four of those issues look identical inside a topline income figure.
A monthly KPI dashboard fixes both problems. Ten specific numbers, tracked in the same format every month, tell you where the margin came from, where it went, and where the biggest opportunity for improvement is sitting. The dashboard sits on top of the P&L, not in place of it.
This post covers the 10 KPIs that matter most for a DSP, why each one matters, what the target range looks like, and what to do when a number drifts.
The signs are already familiar if you have read our other posts in this series: monthly close slipping past day 10 is exactly what we cover in How Amazon DSP Owners Can Speed Up Month-End Close, and stacking dispute deadlines are one of the errors detailed in 7 Costly Amazon DSP Settlement Mistakes. Both point to the same root cause this post addresses directly: a process that worked at 10 routes does not scale to 30.
Key Takeaways
- A monthly P&L is not a dashboard. Ten numbers tracked in the same format every month give you the trend visibility a P&L alone cannot.
- Two KPIs predict DSP net margin better than any others: incentive attainment on a 13-week rolling basis, and labor cost as a percentage of revenue. When both are on target, net margin usually follows.
- Chargeback rate matters less than recovered chargeback rate. A 4% chargeback rate with 40% of disputes recovered is healthier than a 2% rate with 0% recovered, because it means you actually have a dispute process working.
Why a P&LStatement Is Not a Dashboard
A P&L answers one question well: did we make money last month? That is the wrong question to run a DSP on. The questions that actually run the business are different from that.
Where did the margin come from this month, and is that source repeatable next month? Which cost lines are trending in the wrong direction, and by how much? Where is the biggest lever for improvement, and how much money is that lever actually worth? A P&L cannot answer any of these because it does not carry trend data, target thresholds, or ratios between line items.
A dashboard does. The same 10 numbers, calculated the same way every month, compared against the same target ranges. That structure surfaces trends the P&L hides and attaches a specific action to every drift.
Profitability KPIs
1. Net Margin
Net margin is net income divided by gross revenue, expressed as a percentage. A well-run DSP should sit somewhere between 5% and 12%, with anything above 12% considered exceptional and anything below 3% pointing to a structural problem rather than a one-off month. This is the KPI that tells you whether everything else is working together, since it’s really the roll-up of every other number on the dashboard. If net margin falls below 3% for two consecutive months, or drops more than 2 percentage points year-over-year, don’t try to fix it directly. Check every other KPI on the dashboard first to find the specific leak, then fix that.
2. Gross Margin
Gross margin is revenue minus direct operating costs (driver wages, fuel, chargebacks), divided by revenue. The healthy range runs from 18% to 28%, and anything under 15% means the operational math doesn’t support profitability no matter what happens at the overhead layer. This number tells you whether the basic route economics are working; a DSP with weak gross margin can’t fix the problem by cutting insurance or admin costs. If gross margin stays below 15% for a full quarter, the fix is almost always a labor or fleet issue rather than a revenue issue, so start by looking at overtime and fuel cost per route.
Labor Efficiency KPIs
Driver payroll is 55 to 65 percent of gross revenue for a typical DSP, which makes it both the biggest cost lever and the biggest source of leakage. Two KPIs cover this cleanly.
3. Labor Cost as Percentage of Revenue
This is total driver payroll (wages plus taxes plus benefits) divided by gross revenue, and it should land between 55% and 62%. Anything above 65% means the payroll structure is out of line with route economics, and the gap will eat every operational improvement you make elsewhere. It tells you whether your overall payroll cost per route is sustainable at your current pay structure. If it climbs above 65% for two consecutive months, break the number apart to find the source: check overtime as a percentage of payroll first, then driver retention costs, then rescue-pay leakage.
4. Overtime as Percentage of Payroll
Overtime as a percentage of payroll is the overtime premium (the extra half-rate paid on hours over 40) divided by total driver wages. Keep it under 18%; above 22% is a real staffing problem. This number tells you whether you’re staffed at the right level. Some overtime is normal, since Amazon routes typically run 9 to 10 hours across 5 to 6 days a week, but excessive overtime is really understaffing dressed up as a payroll problem. Above 22%, or a jump of 3 percentage points month-over-month, usually means the fix is hiring 2 or 3 more drivers rather than continuing to pay overtime, since a fully loaded new driver costs less per hour than the OT premium.
Fleet Economics KPIs
Fleet is the second-largest cost bucket after payroll, typically 15 to 22 percent of gross revenue. Two KPIs cover the fleet story clearly.
5. Fuel Cost Per Route
Fuel cost per route is total fleet fuel spend divided by routes dispatched. It varies by market, but typically falls between $20 and $35 per route dispatched, and anything above $40 in most markets signals a real issue. It tells you whether fuel is under control, since fuel is one of the easiest costs to leak through, whether from personal use of the fuel card, inefficient route sequencing, or drivers taking longer routes than necessary. A 15% jump month-over-month with no matching change in volume or gas prices should send you to the fuel card transactions first to check for anomalies, then to route sequencing and driver-level fuel spend.
6. Fleet Cost Recovery
Fleet cost recovery is total monthly fleet cost (leases plus maintenance plus insurance) divided by Amazon’s fixed monthly vehicle payment. Keep this at or below 100%; above 105% means Amazon’s fleet supplement isn’t covering your actual fleet cost. It tells you whether the fleet side of your P&L is balanced against what Amazon actually pays for the fleet, and when it runs high, that usually points to missing Amazon Freight Supplement (AFS) payments or unrecovered maintenance charges. If it stays above 105% for two consecutive months, audit AFS eligibility across your active vans against what Amazon actually paid for the month; the gap is usually where missing supplements hide.
Amazon Revenue Health KPIs
Two Amazon-specific KPIs matter more than any single revenue metric alone.
7. Incentive Attainment Percentage (13-Week Rolling)
This is actual incentive pay earned divided by maximum possible incentive pay, averaged across the last 13 weeks. Aim to stay above 90%; below 80% means you’re consistently leaving money on the table. It tells you how well the scorecard is being managed, and the 13-week window smooths out one-off bad weeks to reveal the underlying pattern. If attainment drops below 80% for two consecutive months, or trends downward across a full quarter, dig into the individual scorecard metrics to find the specific ceiling. On most DSPs that’s Safety and Compliance, which caps the entire rating.
8. Chargeback Rate
Chargeback rate is total chargebacks divided by gross revenue, expressed as a percentage. A well-run operation stays under 3%; above 4% is a real problem, though the number alone doesn’t tell you what kind. It only tells you half the story, since the other half is whether disputes are being filed and won, so pair chargeback rate with dispute recovery before drawing any conclusions. If the rate climbs above 4%, or the chargeback dollar amount doubles without a matching volume increase, split the chargebacks by type first. A spike in concession charges is a different problem than a spike in POD failures.
Cash and Reconciliation KPIs
The last two KPIs cover cash management and whether the reconciliation process is actually recovering money owed to you.
9. Cash Reserve in Weeks
Cash reserve in weeks is available cash divided by average weekly operating expenses. Aim for a minimum of 2 to 3 weeks; below 1.5 weeks is a real risk, and above 6 weeks is possibly over-conservative for capital allocation. It tells you whether you can survive a slow payment week, a peak season hiring ramp, or an unexpected repair bill without needing emergency financing. If it trends down for three consecutive months, or drops below 1.5 weeks in any single month, secure a line of credit before you need it, since emergency financing runs 3 to 5 times more expensive than pre-arranged credit.
10. Reconciliation Exceptions and Recovered Dollars
This is the number of open disputes at month-end plus total dollars recovered through disputes filed and won during the month. For a 25-route DSP, a healthy target is recovering $2,000 to $5,000 per month through the dispute process; zero recoveries almost always means disputes aren’t being filed, not that there was nothing to dispute. It tells you whether the reconciliation process is actually working. A high chargeback rate with high recovery is a functioning system, while a high chargeback rate with no recovery is a broken one. Zero recoveries in a month, or a growing backlog of open disputes past the 7 to 14 day dispute window, means you should audit whether disputes are being filed inside the window on each chargeback and fix the process before chasing the numbers.
How to Build the Dashboard
The 10 KPIs above require a specific chart of accounts and transaction tagging strategy in QuickBooks or your accounting system.
Every payroll transaction should be tagged by route, driver, and vehicle. Every fuel purchase should be coded by vehicle. Every settlement should be split into base pay, per-package pay, incentive pay, and chargebacks as separate lines. Chargebacks should sit in a contra-revenue account, not a cost of goods sold account, so the chargeback rate calculation stays clean and comparable across months.
Once the underlying data is structured properly, the dashboard itself is straightforward. A Google Sheets or Excel workbook with one tab per KPI category works fine for most DSPs. Pull the data from QuickBooks by the 5th of the following month, populate the dashboard by the 10th, and review it against last month’s numbers before making any operational decisions for the current month.
The dashboard is a decision tool, not a report. If you never act on a KPI after refreshing it, drop that KPI from the dashboard. Ten specific numbers you actually use to make decisions is a real dashboard. Twenty numbers nobody looks at twice is a distraction.
Where Manual Tracking Falls Short
Four of the 10 KPIs above require weekly cross-referencing across multiple Amazon portals to produce accurate monthly numbers. Manual tracking of these four is where DSPs lose the most reporting accuracy at scale.
Incentive attainment percentage needs the DSP Console tier compared against the actual incentive pay on each settlement, every week, without exception. Chargeback rate and dispute recovery need every chargeback tracked from settlement date through dispute filing to outcome. Reconciliation exceptions need cross-referencing across dispatch data, four separate settlement reports, and Payee Central. Fleet cost recovery needs AFS eligibility tracked by van by week and compared against actual supplement payments landed.
BeanSquad’s Route Recon AI™ produces the underlying data for all four of these KPIs automatically. The platform cross-references all six Amazon portal data sources every week, flags exceptions with dollar amounts, tracks dispute windows with countdown alerts, and delivers monthly outputs in a format that feeds directly into a KPI dashboard. Based on BeanSquad’s data across onboarded DSPs, the average fleet recovers $62,400+ per year in chargebacks alone.
Book Your Free Reconciliation Assessment →
Conclusion
The gap between a DSP that grows and a DSP that bleeds cash is not effort. Most owners work equally hard. The gap is visibility. Ten numbers, tracked in the same format every month, is what turns operational effort into operational insight.
Whether you build the dashboard yourself in a spreadsheet or feed it with data from an automated tool like Route Recon AI, the value is in the discipline of monthly review. BeanSquad is currently accepting the first 50 DSPs into the Founding Partner program at $499/month with the first two months free. Claim your spot →
Frequently Asked Questions
How often should DSP financial KPIs be reviewed?
The full dashboard should be reviewed monthly, with the four Amazon-facing KPIs (incentive attainment, chargeback rate, dispute recovery, fleet cost recovery) checked weekly. Monthly review drives operational decisions, while weekly review catches the leaks before they age into permanent losses.
What are the most important KPIs for a DSP owner to track?
Net margin and labor cost as a percentage of revenue are the two that most directly predict whether the business will grow, break even, or bleed cash. When both are inside their target ranges, most other KPIs are usually in range too.
What is a good net margin for an Amazon DSP?
Five to twelve percent is the well-run range, with above twelve percent considered exceptional performance. Below three percent is a structural problem that no single operational change will fix on its own.
How do I know if my chargeback rate is a real problem?
Look at chargeback rate together with dispute recovery, not chargeback rate alone. A 4% rate with 40% of disputes recovered is healthier than a 2% rate with zero recoveries, because at least the money is coming back into the business.
What is Hours to Budget and does it belong on a monthly dashboard?
Hours to Budget is a weekly labor efficiency metric comparing hours actually worked to hours Amazon pays you for. It belongs on your weekly operational dashboard, not the monthly financial dashboard, because it needs weekly action to be useful.
Can I build this dashboard in QuickBooks alone?
QuickBooks handles the data collection but not the monthly presentation cleanly. Most DSPs pull the underlying numbers from QuickBooks and populate a Google Sheets or Excel dashboard for the actual monthly review and decision-making.