Why your true Amazon margin moves daily — and how to watch it

A monthly margin number is what FBA tools have always given you. Pull the month's revenue, subtract the month's COGS, subtract the month's fees, divide. Done. The number is comforting and mostly correct, and it is too late to act on by the time you see it.

The monthly cadence made sense when settlement reports were the only data source and operators ran small enough that monthly resolution was sufficient. Neither of those things is true anymore. Settlement reports arrive on a fortnightly cycle, the underlying data updates daily, and a single bad week of fee anomalies can compound into the kind of margin slip that takes a month to recover from.

This post is about why true margin is a daily metric, and what it takes to actually watch it.

The five fee dimensions, as a daily signal

There are five fee categories Amazon charges you on the FBA program:

1. Referral fees
2. Fulfillment fees
3. Storage fees
4. Returns and removals
5. Inbound and prep

Each one moves on its own cadence. Referral fees move with sales (daily). Fulfillment fees move with shipped units (daily). Storage fees update monthly, but the inputs — your on-hand inventory by cube — change every day. Returns and removals are event-driven; they spike on specific days. Inbound and prep fees follow your inbound shipment cadence.

A monthly margin report aggregates all five into a single rolled-up number. A useful daily margin view keeps them separate, because the action you take is different per category. A spike in fulfillment fees with no corresponding spike in shipped units is a dim-weight problem. A spike in returns is a listing-quality or product-quality problem. The aggregate hides both signals.

What "the day Amazon books it" means

Amazon doesn't release fee data instantly. There's typically a 24-hour delay between an order shipping and the fulfillment fee appearing in the financial events feed, and a 1–3 day delay before it shows up in the settlement report. We pull from both, so the margin number you see for yesterday is as fresh as Amazon's API allows.

The trade-off is that yesterday's margin is provisional. Some lines will correct in subsequent days as Amazon finalizes data. The dashboard shows you the provisional number with a confidence band, and the band tightens as older days finalize.

The threshold alert

A daily margin chart by itself isn't actionable. Most days look like the previous day. The signal you need is when something has shifted, and that needs to be a notification, not a chart somebody has to remember to open.

MarginLock's alert engine subscribes to per-category margin and per-SKU margin. The default thresholds:

• Workspace-level: alert if any single fee category moves more than one standard deviation from its 30-day baseline.
• SKU-level: alert if a top-50 SKU's contribution margin drops more than 10% week-over-week.
• Anomaly-level: alert if a single settlement line is more than 2× the category's median.

Operators can tune these. The defaults catch the cases worth interrupting your day for; the operator's job is to dial them so the rate of false positives is sustainable.

What to do when an alert fires

The same five-step playbook works for almost every margin alert.

1. 1

   Open the per-category drilldown

   The alert tells you which fee dimension moved. Drill into that one — not the rolled-up number.

2. 2

   Find the offending lines

   The drilldown shows the largest contributors. Three or four lines usually explain most of a category-level shift.

3. 3

   Tie the lines back to physical events

   A spike in fulfillment fees ties back to specific shipments. A spike in returns ties back to specific SKUs and reasons. The tie-back is the diagnosis.

4. 4

   Decide: dispute, fix, or accept

   Some shifts are unjust (file a dispute). Some are legitimate (your inbound costs went up; accept the new baseline). Some are fixable (relabel a SKU; update a manifest dimension).

5. 5

   Set a follow-up

   If the shift indicates a fix, schedule a check-in to confirm the fix held. If you accepted, update the baseline so the alert doesn't keep firing.

Why monthly isn't going to come back

Some operators we talk to push back: "I don't need daily — my volume is low enough that monthly is fine." We hear that and we don't fight it. The honest answer is: at low volume, monthly is fine. The breakeven where daily becomes worth the cognitive load is somewhere around the point where one bad week costs more than your most expensive employee for a day. That number is different per business, but it shows up sooner than most operators expect.

If you want to see what your business looks like at daily resolution, the sandbox import takes about three minutes: