Why Your DD+7 Payout Is Frozen (And Amazon Isn't Going to Tell You)

If you've been selling FBM on Amazon for any length of time, you've probably noticed that your disbursements don't always land when you expect them to. Since Amazon's DD+7 reserve policy went universal in March 2026, a lot of FBM sellers are now asking a version of the same question: why is my payout delayed, and where exactly is my money?

The honest answer is more specific — and more actionable — than most of what's being written about DD+7 right now. This article explains the actual mechanism behind delayed DD+7 payouts, why carrier tracking is the variable Amazon doesn't talk about, and what you can realistically do when things go wrong.

What DD+7 Actually Means

DD+7 stands for Delivery Date plus 7 days. Under the policy, Amazon holds your funds until 7 days after confirmed delivery of the order. The intent is straightforward: Amazon wants to ensure the buyer has received their item before releasing the seller's payment.

Under normal conditions — package shipped, carrier scans it at delivery, confirmation transmitted to Amazon — this works as designed. Your funds release 7 days after the delivery date and you move on.

The problem is that "confirmed delivery" is not as simple as it sounds.

The Variable Amazon Doesn't Control: Carrier Scanning

Amazon's DD+7 clock starts when a carrier transmits a delivery confirmation. Amazon does not scan packages. Amazon does not deliver packages. Amazon receives data from carriers — USPS, UPS, FedEx, and others — and uses that data to determine when your funds are released.

When that carrier data is missing, delayed, or incorrect, your DD+7 clock either starts late or doesn't start at all.

This happens more often than most sellers realize, in several distinct ways:

Ghost shipments. You create a label and drop the package at the post office. The package is accepted, but the carrier never scans it at pickup. From Amazon's perspective, the label exists but the shipment hasn't started. The DD+7 clock has no delivery event to wait for, because as far as Amazon's data is concerned, the package was never handed to the carrier.

Stalled packages. The package enters transit and carrier scans are transmitted normally for a day or two — then go silent. The package is somewhere in the carrier network but tracking has stopped updating. Your DD+7 clock is waiting for a delivery event that may never come, or may come weeks late.

EDD breach. Your estimated delivery date passes without a delivery confirmation. Amazon's clock was expecting a delivery event by a certain date. That date has passed. The funds are in a holding pattern.

Incorrect terminal scans. A carrier scans a package as undeliverable, returned to sender, or damaged — even when the package was actually delivered. The buyer has their item, but Amazon's data says otherwise, and your DD+7 clock reflects Amazon's data, not reality.

One seller described the situation plainly in a recent forum thread:

"What if the post office forgets to scan it upon delivery? Do we now have to worry that we won't get paid if the post office forgets to scan it?"

The answer, unfortunately, is yes — that's exactly the risk. And at meaningful FBM volume, it's not a hypothetical.

What Actually Happens When the Scan Is Missing

Here's where it's important to be precise, because there's a lot of confusion on this point.

Amazon does have a fallback mechanism. If a tracked order never receives a delivery confirmation, Amazon will release the funds 7 days after the latest estimated delivery date. This is documented policy and it generally works as described.

But "generally works" is doing a lot of work in that sentence. The fallback requires Amazon's systems to correctly identify the order as stuck, apply the EDD correctly, and process the release on schedule. Sellers in active forums report cases where this didn't happen automatically and required a Seller Support case to resolve. Some have described packages under USPS investigation for over a year with no automatic resolution.

More importantly, even when the fallback works perfectly, you are still waiting longer than you should be. If your package was expected to deliver on day 6 and the fallback triggers on the latest EDD — which may be several days later — you've lost days of cash flow on every order this happens to. At 500 orders per month, a 1-2% carrier scan failure rate means 5 to 10 orders every month where your funds are delayed, sometimes significantly.

And unless you are manually reviewing every in-transit order against your expected delivery dates, you don't know which ones they are.

One seller described the scale of this problem clearly:

"Unless a seller performs regular forensic audits of shipped-but-undelivered orders, Amazon keeps the funds by default. Multiply this across millions of FBM shipments and thousands of sellers, and the result is not 'risk management' — it's systematic float capture."

That framing is harsh, but the underlying mechanics are accurate. The funds don't disappear — but they don't move until someone takes action, and Amazon's systems don't proactively alert you when an order is stuck.

The Manual Audit Problem

The traditional response to this problem is exactly what it sounds like: sellers manually reviewing their open orders, checking tracking on each one, identifying which packages have gone silent or missed their EDD, and opening cases or contacting carriers as needed.

Sellers who do this describe spending 10 to 12 hours per week on this work alone. At a certain order volume, it becomes genuinely impossible to do thoroughly. Individual orders fall through the cracks. Deadlines pass. The funds sit.

"Lost or stalled packages dissolve into operational noise."

That's the core problem. Not that the tools don't exist to resolve these situations — they do. But the volume of orders makes it impossible to catch every one manually, and Amazon provides no consolidated view of which orders are currently at risk.

What You Can Actually Do

For ghost shipments: The window to act is widest in the first 48 to 72 hours after label creation. If a package has no carrier scan after two days, contacting the carrier to confirm pickup — or reshipping — while the buyer is still expecting normal delivery gives you the best chance of meeting the original EDD and having the DD+7 clock start on schedule. Waiting until day 7 or 10 leaves you managing a buyer complaint alongside a carrier problem.

For stalled packages: Five days of tracking silence in transit is a reasonable threshold for concern. At that point, contacting the carrier for a status update and beginning to prepare for a possible reship gives you options. Waiting for the buyer to file an INR claim removes most of those options.

For EDD breaches: The moment an estimated delivery date passes without a delivery confirmation, contacting the carrier is the most direct path to resolution. In many cases, the package has been delivered but the scan was delayed or missed. Getting confirmation from the carrier — even informally — gives you information to share with the buyer and with Amazon if needed.

For incorrect terminal statuses: If a package is marked undeliverable or returned when you have reason to believe it was delivered, opening a Seller Support case with the order ID and carrier documentation is the appropriate path. These cases resolve more quickly when opened early.

The common thread across all of these is timing. Every one of these situations is more resolvable at 48 hours than at 7 days, and more resolvable at 7 days than at 14. The earlier you know, the more options you have.

A Note on Scale

Everything described above is manageable at low order volumes. At 50 orders per month, manual review is feasible. At 500 orders per month, it isn't — not without dedicated staff or dedicated tooling.

The DD+7 policy change has made carrier tracking failures directly expensive in a way they weren't before. Previously, a ghost shipment was an operational inconvenience that resolved itself one way or another. Now, a ghost shipment is a cash flow event. That shift in stakes justifies a corresponding shift in how seriously sellers monitor their shipments.

DD7 Radar was built specifically for this problem. It monitors every FBM order continuously, flags ghost shipments within 48 hours of label creation, surfaces stalled packages before EDD breach, and alerts on EDD breaches the day they occur — giving sellers the information they need to act while acting is still useful.

If you're shipping FBM at meaningful volume and want to stop doing manual tracking audits, get started with DD7 Radar today.