Harpy Glossary

EDD (Estimated Delivery Date)

Amazon & D2C glossary · Harpy Media

EDD (Estimated Delivery Date) is the arrival promise shown to the customer — on the product page, at checkout, and in order history. It’s computed from fulfilment method, location, carrier performance, and lead-time buffers, and it is one of the most consequential sentences on the page: shoppers filter, compare, and abandon on it.

What is EDD?

On Amazon, the delivery promise is both a conversion lever and a performance contract. A fast, credible EDD wins the click and the cart; breaking it damages metrics (late shipment rate for sellers, delivery estimate accuracy for the system) and sends the buyer straight into the arms of the review box.

Why EDD steers so much behaviour

Three reasons. Filter effects: shoppers sort and filter by delivery speed — a Monday promise loses to tomorrow before the page even gets read. Conversion weight: Prime-speed expectations have become the category default; listings with slow promises convert materially worse on identical products and prices. And the trust loop: an EDD that’s met or beaten earns the best thing a buyer can give — belief in the next promise; an EDD missed teaches them to check a competitor next time. On the operations side, the same date is a scoreboard: seller-side late shipment metrics, FBM handling times, and carrier quality all resolve into whether the promise held.

Managing the promise you make

The levers: fulfilment method (FBA’s network versus self-shipped FBM — each yields different promise profiles), handling time settings (honest or optimistic — the fastest settings that you can sustain, not the fastest that score well), regional stock placement (customers buy the promise; inventory sitting far from the buyer makes a weaker promise), and carrier reliability (the EDD inherits your carrier’s bad weeks). The management habit with teeth: audit your own promises quarterly — order your product from three regions and read exactly what a real shopper is told. The gap between the promise your dashboard assumes and the promise the customer sees is always informative, occasionally shocking.

Promise accuracy = orders delivered within EDD ÷ total orders · Conversion and Buy Box both read this scoreboardManage the promise you can keep, then keep the promise you made.

In practice

A seller switches a slow region from FBM to FBA placement and watches a single change cascade: EDD on the page drops from 5–7 days to next-day, conversion in that region rises 19%, and the campaign’s cost per order falls because the same clicks now close better. The quickest conversion improvement of the quarter came from moving boxes closer to buyers, not from touching the listing at all.

⚠️ Watch out. A seller pads handling time to protect metrics and ignores the page consequences: the padded EDD reads slow, shoppers filter it out, and conversion falls — so they cut ad bids to “fix” an efficiency problem caused entirely by a delivery promise nobody needed to make. The buffer protected a metric and cost the sales the metric was proxying for.

💡 Harpy tip. Once a quarter, buy your own product as a customer in your three biggest regions. Compare the EDD the customer sees with the one you believe you’re offering. That test has never once failed to find something.

How Harpy Media helps

Delivery-promise management — placement, handling settings, and the EDD-vs-conversion link — is part of how we tune accounts, because speed converts before copy does.

EDD FAQ

What is EDD on Amazon?

Estimated Delivery Date — the arrival promise shown to shoppers on the product page, at checkout, and in order history.

What sets my EDD?

Fulfilment method, your handling time settings, inventory proximity to the buyer, and carrier performance — plus the buffers built into the system’s estimates.

Does EDD affect sales?

Significantly — shoppers filter and abandon on delivery speed, and Buy Box eligibility and conversion both read promise reliability.

Want these numbers watched for you, every week?

Book Free Consultation