Read Stripe’s BFCM totals before forecasting merchant sales

A payment platform can report a record weekend while an individual merchant faces weaker sales. Both observations can be true. Stripe’s Black Friday through Cyber Monday reports are useful evidence about activity passing through Stripe. A merchant planning stock or staffing needs a comparison tied to its own business. The gap between those two uses is the denominator: whose activity is being counted, and what stayed comparable between years.

Looking back from November 2026, the practical lesson is to preserve the scope of a headline when carrying it into a planning spreadsheet. A platform total can inform a scenario. It cannot establish how a typical merchant performed, or what your next promotion will earn. Treating it as that forecast gives a precise-looking answer to a question the source never measured.

Keep the four-day window intact

Stripe’s report dated 2 December 2025 states more than $40 billion in payment volume and more than 578 million transactions over Black Friday through Cyber Monday. Its 3 December 2024 report states more than $31 billion and 465 million transactions for the corresponding four-day event. These are Stripe-wide figures with global activity, expressed in US dollars; the /gb/ page location does not make them British sales totals.

The event windows correspond to 28 November–1 December 2025 and 29 November–2 December 2024. Publication followed each window. Keep those dates separate from a local retailer’s differently scheduled Black Friday campaign. The releases do not specify a precise timezone cutoff or a constant-currency method for these headline totals, so neither should be supplied by inference.

There is also a rounding limit. Dividing 40 by 31 describes the ratio of two displayed thresholds. Because both values are reported as “more than”, that calculation does not recover an exact growth rate or even a guaranteed minimum growth rate. The unknown excess above either threshold matters. A planning document can quote the two reported amounts without manufacturing a percentage from them.

Platform composition can change

The relevant population is businesses processing through Stripe during each window. It is not a declared fixed panel of the same merchants, with unchanged coverage and payment share. A platform can gain businesses, lose others or process a different share of an existing business’s payments. Without a reconciliation of those changes, the difference between platform totals cannot be assigned entirely to growth inside continuing merchants.

Even a fixed merchant panel would leave several questions open. Larger merchants can dominate a value-weighted total. A rise concentrated in a few businesses need not describe the median merchant. To claim “typical growth”, define typical first: median business, average payment, total revenue per continuing merchant or another explicit measure. Those quantities can move differently without any arithmetic error.

Basket composition adds another distinction. A merchant can process more value because prices changed, because customers bought different products or because order frequency changed. Payment count and total payment value help describe activity, but neither directly measures units shipped or contribution after fulfilment. A larger basket can create more revenue and more cost together. The business decision determines which measure belongs in the forecast.

Geography belongs in that comparison too. Changes in customer location and currency mix can affect a dollar-denominated aggregate. A domestic merchant with a narrow product range has a different exposure from a platform serving several markets. The reports’ global reach is useful context; it is not evidence that a particular country or product category grew at the same rate.

Build a merchant comparison that answers a decision

Start with the decision the forecast supports. Stock purchasing needs product demand and replenishment timing. Staffing needs the distribution of orders and support contacts. Cash planning needs settlement expectations and outgoing obligations. One platform-wide payment-value headline cannot supply all of these inputs, even if its measurement is accurate for its stated scope.

For an internal sales comparison, define the campaign window and the merchants or stores included. Keep returns and cancellations consistent between periods, and document whether revenue is gross or net of those adjustments. If reporting coverage changed, show that separately. Otherwise a new checkout integration can appear as sales growth simply because more existing activity became visible in the dataset.

Separate observed history from assumptions about the next campaign. Repeat purchasing, promotional pricing and stock availability can be recorded as distinct assumptions rather than hidden inside one uplift factor. Where an input is missing, keep the uncertainty visible. There is no basis here for a universal break-even threshold, staffing multiplier or merchant growth benchmark.

Broad totals still have a planning use

The strongest counterargument is that a broad network sees demand pressure a small merchant cannot observe alone. That makes the totals relevant context for discussing seasonal readiness. A team can use them to justify examining peak-load exposure, payment failure handling and support coverage. Rejecting every aggregate because it is not a merchant panel would discard useful evidence about the environment.

That use still needs a local translation. Capacity depends on when requests arrive and what each request does, not just the sum of money processed elsewhere. A high-value transaction and many low-value transactions create different workloads. Choose local scenarios from your application’s observed traffic and business plans, then record which assumptions are merely informed by the broader event.

For custom software development, the useful reporting requirement is the ability to separate continuing-business performance from changes in coverage. Preserve campaign dates, currency treatment and adjustment rules beside the figures. A dashboard that explains its denominator gives owners a defensible planning input. A large number copied without that explanation only borrows the authority of somebody else’s measurement.