Publish Date :
Shopify's US$119bn Quarter: When Do Growing Brands Outgrow Spreadsheets?
A growing brand outgrows spreadsheets when separate channel plans repeatedly compete for the same stock or disagree about commitments. Merchmix Core, Core Plus and configured integrations connect the merchandise plan with a shared operational stock context.

THE MERCHMIX DECISION / Core + Core Plus + Integrations
One stock balance. Three competing requests.
Reconcile reservations before approving another channel commitment.
Worked retail example. Independent of the reported company records. Financial scenario amounts are USD.
Independent brand / new allocation requests
| Channel | Requested | Proposed |
|---|---|---|
| Online | 50 units | Under review |
| Stores | 40 units | Under review |
| Wholesale | 30 units | Under review |
Existing reservations are excluded once. New proposals share the remaining stock and require approval; no storefront update is asserted.
150 physical units less ninety already reserved leave sixty usable.
THE KEY IDEA
The planning limit is reached when teams cannot trust a shared starting position. Connect demand, reservations and proposed stock decisions before another channel multiplies the reconciliation work.
Read platform growth as context, not a merchant benchmark
Shopify’s 3 November 2026 results describe approximately $119 billion in third-quarter gross merchandise volume and revenue growth of 32%. Its quarterly filing reports GMV of $119.1 billion. GMV represents commerce facilitated through the platform, not Shopify’s own retail sales or the growth rate of every merchant.
The company’s comments about commerce across more surfaces underline a planning question for individual brands: can the team reconcile demand and stock across the channels it actually operates? The results do not establish a revenue threshold at which a merchant must replace spreadsheets.
The warning sign is a repeated reconciliation problem
A spreadsheet can support a small, controlled range. The problem grows when online, store and wholesale teams maintain different versions of what is available, due or already promised. A late export can look current long after another channel has consumed the stock.
Count the decisions that require manual reconciliation rather than judging the tool by the number of rows. If a buyer must rebuild the commitment position before every review, the team lacks a dependable starting point. Adding another sales channel will increase that coordination requirement even if total sales remain manageable.
Three channel requests cannot each own the same balance
An independent brand has 150 physical units. Ninety are already reserved: forty for online orders, thirty for stores and twenty for wholesale. That leaves sixty usable units for additional commitments, assuming these reservations do not overlap and there are no other exclusions.
New requests are fifty online units, forty store units and thirty wholesale units, a total of 120. They exceed the usable balance by sixty. A proposal of thirty, twenty and ten shares the sixty available units. The proposal does not execute orders, release reservations or establish that this split is commercially correct.
THE FIGURES BEHIND THE DECISION
| Channel | Existing reserved | New request | Proposal |
|---|---|---|---|
| Online | 40 | 50 | 30 |
| Stores | 30 | 40 | 20 |
| Wholesale | 20 | 30 | 10 |
| Total | 90 | 120 | 60 |
150 physical − 90 reserved = 60 usable / proposed split: 30 + 20 + 10 = 60
Keep the commercial forecast in Core
Core supports budgets, assortment decisions and MFP/WSSI. It gives the brand a place to review sales, stock and intake assumptions across the relevant merchandise scope and planning periods. A channel forecast is an expectation; a reservation is an existing operational commitment. They should not be substituted for one another.
Compare the proposed buy with the accepted forecast and the quantities already committed. A stronger online outlook does not automatically remove a store obligation. The planner needs to make the trade-off explicit instead of allowing separate channel spreadsheets to approve the same unit twice.
Use Core Plus for the stock-response decision
Core Plus supports inventory, allocation and replenishment decisions by location and size. For the example, the useful review starts with the shared sixty-unit balance and the reasons behind each new request. It then checks the correct product, source and timing before quantities are approved.
A style total alone can still conceal a size shortage. Likewise, a transfer on the way is not necessarily usable stock today. Keep those qualifications in the operational view so the allocation remains grounded in what the business can actually fulfil.
Treat integration scope as part of the operating design
Merchmix’s documented Shopify integration covers configured flows for orders, refunds, product data and stock, with supported decision hand-offs depending on setup. Confirm which system owns each record, the fields included, location mapping, update timing and the permitted write-back before relying on a connection.
An integration is not a promise that every channel, app or field synchronises instantly. Test the transactions that change the balance: a reservation, a cancellation, a return and a delayed receipt. The aim is a defined stock basis and accountable decisions, rather than an unexplained number copied into several tools.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| Channel forecasts disagree | Core / merchandise plan | Choose an accepted demand basis before changing the buy. |
| Requests exceed usable stock | Core Plus / allocation | Review one sixty-unit balance rather than separate channel totals. |
| Stock moves between systems | Integrations / configured flows | Confirm ownership, mapping and supported updates for each transaction. |
Choose the next system by the decision it must support
List the recurring failure first: conflicting stock promises, duplicate buying assumptions, delayed allocation or inconsistent range data. Then establish what Core plans, what Core Plus reviews and what the connected systems must record after an authorised action.
The worked proposal consumes the available sixty units only if approved. Until then, the existing reservations and requests remain distinct. That discipline matters more than announcing that the brand has reached a particular revenue size or replaced a spreadsheet with a more attractive screen.
BEFORE THE NEXT DECISION
- Planner
Keep forecasts and existing commitments distinct.
- Stock team
Reconcile reservations and available sizes before approving a split.
- Integration owner
Validate stock-changing transactions and record ownership.
Common questions
Is Shopify’s GMV its own retail revenue?
No. It measures merchandise value facilitated through its platform, distinct from Shopify’s revenue.
Is there a fixed revenue threshold for replacing spreadsheets?
The sources do not establish one. Assess the repeated planning and reconciliation problems in the business.
Why are only sixty units available?
The example has 150 physical units and ninety existing, non-overlapping reservations.
Does the thirty/twenty/ten proposal fulfil the requests?
It shares only the available sixty units and remains a proposal; it does not satisfy every request or execute orders.
Does every integration update every field instantly?
No. Confirm configured record ownership, fields, timing and supported hand-offs for the retailer’s setup.
FROM THE ARTICLE TO YOUR OWN RETAIL PLAN
Review the decision.
See the workflow.
Bring your planning questions to a demo, or explore a proof of concept on your own data.