Amazon reported third-quarter 2026 net sales of $201.9 billion, up 12% from a year earlier, in its October 29 results. The release also identifies a calendar change: Prime Day occurred in Q2 for most large countries in 2026, while the 2025 event occurred entirely in Q3. That matters when reading the year-over-year comparison.

Amazon’s October 29 third-quarter results and timing explanation

Put the promotion in the quarter where it happened

Amazon’s earlier U.S. announcement scheduled Prime Day for June 23–26, 2026. Those dates fall in the second calendar quarter. A reader comparing July–September sales across years should therefore check whether the same major promotion sits inside both periods.

Amazon’s official June 23–26 Prime Day announcement

Check marketplace coverage before applying the U.S. dates elsewhere; the earnings release’s timing statement concerns most large countries.

Keep reported results and the timing estimate separate

Amazon says Q3 year-over-year growth would have been approximately 400 basis points higher excluding the timing shift. That is the company’s estimate for a different comparison, not a replacement for reported sales. Four hundred basis points means four percentage points; adding that to the rounded 12% headline gives approximately 16%, retaining the estimate and rounding limitations.

Build a small comparison worksheet

For your own retail review, create one row per reporting period with its start date, end date, sales measure, geographic scope and promotion dates. Add a separate field for any company-provided timing adjustment, including its source and wording. This preserves the reported result while making the calendar issue visible.

Imagine a fictional retailer whose internal worksheet uses calendar quarters and tags sales by transaction date. It moves a promotion from July 1 one year to June 30 the next. The dates are only one day apart on the calendar, but they belong to different quarters. Under this exercise’s stated tagging rule, the promotion’s dated sales would appear in different quarterly rows.

That example illustrates a boundary; it does not prove the retailer would have sold the same amount on either date. Customers might change when or what they buy, and other conditions can change too. A calendar annotation alone cannot calculate the hypothetical sales that would have occurred under a different schedule.

Ask what evidence supports a further adjustment

If your team wants to compare promotion performance, define the question first: the same calendar quarter, the full event window, or a particular marketplace. Request the records needed for that question and document any assumptions. Do not silently switch from one comparison to another because a preferred headline looks stronger.

When sharing a retail growth comparison, include the reporting window, promotion calendar, source and any stated adjustment. Preserve the distinction between an observed outcome and an estimate for a different schedule.

Read the promotion calendar

Conceptual illustration of a retail analyst comparing promotion dates on adjacent calendar pages; not an Amazon interface.
Conceptual illustration of a retail analyst comparing promotion dates on adjacent calendar pages; not an Amazon interface.