Ecommerce dispatch and transit time statistics

Updated 26 source citationsSources checked 12 November 2026

On this page
  1. Quick answer
  2. Key Takeaways
  3. When does the delivery timeline start?
  4. How often did the wait before handoff exceed transit time?
  5. Can a typical delivery time support a promise?
  6. How do invalid timestamp sequences affect the sample?
  7. How should the answer reflect the order’s current stage?
  8. Which source figures support the findings?
  9. Why should stage percentiles not be added into a delivery promise?
  10. Methodology and Sources
Download study text

Quick answer

Across 96,281 delivered Olist orders with complete chronological timestamps, the median wait before carrier handoff was 2.20 days and the median carrier-to-customer time was 7.10 days. In 17.87% of eligible orders, the pre-carrier stage lasted longer than the transit stage. (Olist data, independent analysis, Nov 2026).

A delivery answer can become misleading when a carrier transit figure is presented as time from purchase. This analysis splits the journey at carrier handoff and retains only complete, chronological timestamp sequences. It compares the two stages and explains why their separate medians cannot simply be added. The source describes historical Brazilian orders, with no promise about a current store’s delivery time.

Key Takeaways

  • In 96,281 eligible delivered Olist orders, median purchase-to-carrier-handoff time was 2.20 elapsed days (Olist data, independent analysis, Nov 2026).
  • Median carrier-to-customer time was 7.10 elapsed days among the same 96,281 eligible Olist orders (Olist data, independent analysis, Nov 2026).
  • In 17,209 of 96,281 eligible Olist orders, the interval before carrier handoff was longer than the interval after it, or 17.87% (Olist data, independent analysis, Nov 2026).
  • A reanalysis found that 36,994 of 96,281 eligible delivered Olist orders took at least three elapsed days from purchase to carrier handoff, or 38.42% (Olist data, independent analysis, Nov 2026).

When does the delivery timeline start?

A shopper asking whether an order will arrive by Friday needs an end-to-end answer. A carrier’s transit estimate addresses the journey after handoff. The order may still need payment checks, picking, packing and collection before that journey begins.

Median dispatch is 2.20 days and transit 7.10 days. The 90th percentiles are 6.40 and 18.91 days.
Figure 1: Include the expected dispatch stage when answering an arrival-date question. Source: Olist data, independent analysis, Brazilian E-Commerce Public Dataset by Olist, Nov 2026. Original analysis of the cited source. Source periods and calculation limits appear in the text.

This study separates the two observed stages in the public Olist order file. For each eligible delivered order, it measures purchase to carrier handoff and carrier handoff to customer delivery. The analysis uses elapsed time, so a day means 24 hours. Weekends and holidays remain part of that elapsed time. (Olist data, independent analysis, Nov 2026).

How often did the wait before handoff exceed transit time?

The median pre-carrier stage lasted 2.20 days. The median transit stage lasted 7.10 days. Those figures describe the separate distributions. Adding the two medians would not produce the median total delivery time, because the middle order can be different in each distribution. (Olist data, independent analysis, Nov 2026).

For 17,209 eligible orders, the pre-carrier stage lasted longer than transit. That is 17.87% of the 96,281 orders. Another useful count is the 36,994 orders that took at least three elapsed days to reach the carrier, or 38.42%. A transit-only answer would leave out a substantial part of these recorded timelines. (Olist data, independent analysis, Nov 2026).

Can a typical delivery time support a promise?

At the 90th percentile, the pre-carrier interval reached 6.40 days and transit reached 18.91 days. The wider tail matters when the shopper has a deadline. A median gives a useful description of typical experience. A promised arrival requires the current order conditions and the reliability level the merchant can support. (Olist data, independent analysis, Nov 2026).

Consider a checkout offering three-day transit while the order will leave the warehouse in two days. The earliest useful explanation includes both stages and the applicable working-day rules. If dispatch is uncertain, the reply should say when it will be confirmed and offer the available delivery choices. The historical Olist figures provide a reason to inspect that gap; they cannot supply the promise for another store.

How do invalid timestamp sequences affect the sample?

The file contains 99,441 order records. The stage comparison excludes 2,963 orders with a final status other than delivered, nine delivered orders with a required timestamp missing, and 188 with timestamps outside the required purchase-to-handoff-to-delivery order. That leaves 96,281. (Olist data, independent analysis, Nov 2026).

Keeping these exclusions visible prevents a clean-looking average from absorbing negative durations or treating an unfinished order as delivered. The excluded records remain useful for a separate data-quality review. They require a definition of the problem before they enter a performance metric.

How should the answer reflect the order’s current stage?

A pre-purchase answer should distinguish the expected dispatch window from transit after dispatch. Once an order exists, a recovery or support reply can use its current status to explain the remaining stage. “Packed and awaiting collection” gives the shopper a different reason to wait than “the carrier has the parcel.”

A store can reproduce this analysis using its own purchase, handoff and delivery events, then split results by the conditions it actually uses to make promises. The published dataset includes state and item-count cuts for exploration. Their descriptive differences call for investigation of product, carrier and distance mix before a policy changes.

Which source figures support the findings?

The table retains the source measure and its population. Independent results in the next table use the stated formula; their precision follows the recorded inputs.

Source measureValue and unitPopulation or denominator
Eligible delivered orders96,281 orders (Olist data, independent analysis, Nov 2026)96,281 delivered orders with complete chronological timestamps
Median time before carrier handoff2.2 days (Olist data, independent analysis, Nov 2026)96,281 delivered orders with complete chronological timestamps
Median carrier-to-customer time7.1 days (Olist data, independent analysis, Nov 2026)96,281 delivered orders with complete chronological timestamps
90th percentile before carrier handoff6.4 days (Olist data, independent analysis, Nov 2026)96,281 delivered orders with complete chronological timestamps
90th percentile carrier-to-customer time18.91 days (Olist data, independent analysis, Nov 2026)96,281 delivered orders with complete chronological timestamps
Orders with a longer pre-carrier wait17,209 orders (Olist data, independent analysis, Nov 2026)96,281 delivered orders with complete chronological timestamps
Orders taking at least three days to reach carrier36,994 orders (Olist data, independent analysis, Nov 2026)96,281 delivered orders with complete chronological timestamps
Excluded not delivered2,963 orders (Olist data, independent analysis, Nov 2026)All 99,441 recorded orders
Excluded out of order timestamp188 orders (Olist data, independent analysis, Nov 2026)All 99,441 recorded orders
Excluded missing timestamp9 orders (Olist data, independent analysis, Nov 2026)All 99,441 recorded orders

How were the additional comparisons calculated?

These are calculations from the source inputs. Each retains its original unit and comparison population.

CalculationResultFormula
Longer pre-carrier wait, percent17.87 % (Olist data, independent analysis, Nov 2026)17209 / 96281 * 100
At least three days before carrier, percent38.42 % (Olist data, independent analysis, Nov 2026)36994 / 96281 * 100
Median-stage ratio3.22 ratio (Olist data, independent analysis, Nov 2026)7.100752314814815 / 2.2047916666666665
Delivered records excluded from stage calculation197 orders (Olist data, independent analysis, Nov 2026)188 + 9

Why should stage percentiles not be added into a delivery promise?

Adding the median pre-carrier time of 2.20 days to median transit of 7.10 days gives 9.31 days. The median complete journey in the same 96,281 orders was 10.23 days. Adding the two 90th percentiles gives 25.31 days, while the directly observed whole-journey 90th percentile was 23.11 days. These are our additional calculations from the eligible public timestamps. (Olist data, independent analysis, Nov 2026)

In the same Olist delivered-order cohort, the sum of stage medians is 9.31 days while the whole-journey median is 10.23 days. The sum of stage 90th percentiles is 25.31 days, while the whole-journey 90th percentile is 23.11 days.
Figure 2: A stage percentile describes a position within that stage's distribution. The parcels occupying that position need not be the same parcels in the next stage. Source: Olist public order archive, original calculations, Nov 2026. Original analysis of the cited source. Source periods and calculation limits appear in the text.

The distinction matters when a merchant turns an operational report into a customer-facing date. A label such as “typical dispatch plus typical transit” sounds like a typical total, but medians are not additive. The combined value can fall below the actual journey median, as it does here. The two errors also need not point in the same direction at other percentiles.

The source records allow a second check. Of the eligible orders, 1,080 exceeded both stage-specific 90th percentiles, while 18,176 exceeded at least one. The simple 25.31-day sum happened to cover 88,853 orders, or 92.29% of the cohort. That is an empirical coverage result for these historical journeys. It is not a 90% service guarantee and supplies no coverage guarantee for a different destination, stock policy or carrier. (Olist data, independent analysis, Nov 2026)

For a store with linked timestamps, calculate the distribution of complete eligible journeys directly. If only separate stage reports exist, the missing relationship between stages is a real information gap. Calling their summed percentiles an end-to-end percentile would conceal it. An estimate intended for a particular shopper also needs the matching route, service, dispatch schedule and current order state, rather than the entire archive's pooled value.

This analysis does not mean stage reports are unhelpful. They identify where time was spent and where an operation may need attention. The mistake is using those separate summaries as if they already describe the probability of the shopper's complete journey.

Methodology and Sources

Delivered orders with complete nondecreasing purchase, carrier-handoff and customer-delivery timestamps. Durations are exact elapsed days, not calendar dates or promised working days. Historical Brazilian marketplace data, not a representative DTC merchant sample. Recorded final states cannot identify authorization, refund, fraud or abandonment causes. No counterfactual or causal recovery effect is inferred. All available dataset dates are retained. Carrier-handoff time does not measure every fulfillment operation or the cause of delay. Group differences are descriptive. Derived percentages are rounded to two decimal places.

The source period is 2016 to 2018, all available Olist records. Independent calculations were completed in November 2026 and use the formulas shown above.

Glossary

  • Order ID: The key used to join records belonging to an order.
  • Payment record: One row describing a recorded payment amount or method.
  • Freight: The shipping amount recorded with an item.
  • Matched order: An order found in both files used for a comparison.
  • Denominator: The population used to calculate a share or rate.
  • Recorded final state: The status present in the historical export.
  • Payable balance: The amount currently owed after relevant payments and adjustments.
  • Reconciliation: A check that related financial records agree under stated rules.

Sources

Cite this page

Use the citation below when referring to this analysis. The original source and calculation scope accompany each finding.

Convo Rescue. "Ecommerce dispatch and transit time statistics." Convo Rescue, November 2026. https://convorescue.com/guides/ecommerce-dispatch-and-transit-time-statistics/
<a href="https://convorescue.com/guides/ecommerce-dispatch-and-transit-time-statistics/">Ecommerce dispatch and transit time statistics</a> (Convo Rescue, November 2026)