The weekly FBA recovery rhythm that protects margin

Most FBA leakage is not invisible. It is unowned. Fee changes, stranded units, missing reimbursements, returns, and removal discrepancies show up in different reports on different days. Without a weekly rhythm, nobody sees the whole queue until the month-end margin number disappoints everyone.

The cadence does not need to be complicated.

Monday: margin and fee variance

Review last week's contribution margin by SKU, size tier, marketplace, and fee category. Rank material changes. Assign owner actions for unexplained fulfillment fee movement, storage spikes, inbound charges, and low-inventory exposure.

Tuesday: inventory health

Review stranded inventory, days of supply, aged inventory bands, inbound delays, and reservation mismatches. The output should be a list of SKUs to replenish, recover, discount, remove, or stop buying.

Wednesday: reimbursement queue

Review claims opened, evidence missing, claims denied, claims paid, and expected recovery. Keep deadlines visible. Reimbursement work fails when it becomes a pile of cases with no next action.

Thursday: returns and removals

Match refunds to unit outcomes. Match removal orders to returned, disposed, reimbursed, or unresolved quantities. Escalate anything that is nearing a window or lacks evidence.

Friday: close the loop

Update pricing, purchasing, warehouse rules, and supplier feedback based on the week's findings. Recovery without prevention turns into permanent administration.

A weekly FBA recovery rhythm creates operating memory. The same problems may still appear, but they stop becoming surprises.

Keep the agenda tied to decisions

The rhythm fails when it becomes a status meeting. Each day should end with decisions: file, wait, replenish, remove, discount, update a rule, or accept the cost. If an issue is not ready for a decision, assign the missing research with a due date. That keeps the queue moving and prevents the same line from appearing every week with no progress.

Use dollar impact to keep the review grounded. A small unexplained fee may be batched for later. A high-confidence reimbursement near deadline should move immediately. A stranded SKU with large recoverable value deserves more attention than a low-margin tail unit. The cadence should spend operator time where it can change margin.

Measure closure, not activity

Track actions closed, dollars recovered, fees avoided, stockouts prevented, and repeat exceptions reduced. Do not celebrate the number of cases opened if cash is not recovered. Do not celebrate the number of reports reviewed if the same preventable errors keep appearing.

The Friday close-the-loop step is the control point. If the week revealed a bad prep rule, update the rule. If it revealed a supplier packaging problem, send feedback before the next purchase order. If it revealed a fee assumption change, update pricing and replenishment models. Recovery work protects the past; prevention protects the next margin cycle.

Keep a visible backlog

The weekly rhythm needs one backlog for open recovery work. Each item should show owner, dollar impact, due date, evidence status, and next action. If work lives in separate spreadsheets, support cases, and chat messages, the team will lose context and duplicate effort.

Review the backlog for aging. Items that sit too long without movement should be escalated, narrowed, or closed with a reason. A stale backlog is dangerous because it creates the impression of control while deadlines pass.

Teach the system from the week

At the end of the week, ask what rule should change. Maybe a prep instruction needs a required field. Maybe a reimbursement case needs a better evidence template. Maybe a low-inventory alert needs a bigger receiving buffer. The best rhythm makes the next week easier by changing the operating system, not just by clearing last week's queue. That is how weekly recovery work becomes a durable margin-control habit.