Shopify Customer Lifetime Value: Calculate, Segment, and Act
Start with the decision, not the formula
“What is our Shopify LTV?” sounds like one question. It is usually several:
- How much have customers in a defined cohort spent so far?
- How much of that spend was refunded or discounted?
- When do customers tend to make a second purchase?
- Is there enough evidence to change an acquisition limit or prepare a retention review?
Those questions need a time window, a cohort definition, and a clear owner. A single all-time average can hide the fact that newer customers have had less time to return, or that one acquisition channel brought a different kind of buyer.
Shopify’s customer reports include cohort analysis, returning-customer information, and amount-spent measures. Shopify also warns that cohort projections are estimates, not guaranteed sales. That is the right starting point: use observed value for historical decisions, and keep any forecast visibly separate.
Define the version of LTV you need
There is no universal LTV number. Name the version before calculating it.
| Decision | Useful LTV view | Do not assume |
|---|---|---|
| Review a past acquisition cohort | Realized net spend per acquired customer through a named age | That every cohort has had equal time to mature |
| Decide when to re-engage customers | Repeat behavior and amount spent by cohort period | That high first-order revenue means high repeat value |
| Set a provisional acquisition guardrail | Realized value, contribution costs, and a stated payback period | That revenue alone is available to spend on acquisition |
| Plan with a forecast | Provider projection, labeled as an estimate | That an estimate is a promise or a benchmark |
For a basic realized customer-value view, use a consistent definition:
realized customer value = included customer revenue in the cohort and period
÷ included customers in that cohort
The hard part is not the division. It is documenting what included means. Decide whether the numerator is gross or net sales, how refunds are treated, which customer identity is used, and what happens to test, wholesale, or replacement orders. If those choices are unknown, stop at “needs evidence” instead of producing a confident value.
Build a cohort before you compare customers
Shopify’s customer cohort analysis groups customers by first-order date by default and lets a merchant change the cohort definition and metrics. That matters because a January cohort has had more time to repurchase than a June cohort.
Use this minimum cohort contract:
| Field | Example choice | Why it must be visible |
|---|---|---|
| Cohort entry | First paid order in one calendar month | Makes acquisition timing comparable |
| Observation age | 30, 60, or 90 days since first order | Prevents immature cohorts from looking weak |
| Value basis | Net sales after the business’s documented refund treatment | Keeps the number tied to the decision |
| Customer scope | Named store, market, and customer identity rule | Avoids mixing unrelated populations |
| Comparison | Same-aged cohort, prior period, or documented benchmark | Avoids comparing a partial period with a full one |
An illustrative example: a 60-day cohort contains 100 customers. The team has defined $8,000 as included net sales for those customers in the same 60-day window. Realized value is $80 per included customer. That does not say the customer will spend $80 forever, or that $80 is a safe cost to acquire every customer. It says what this one defined cohort has done so far.
Separate realized value from a forecast
Forecasts can be useful when they make their assumptions visible. Shopify explains that its cohort projections use a store’s prior data and can be higher or lower than actual future spending. Use a forecast to frame a planning question, not to erase uncertainty.
Ask these questions before using a projected value in a budget discussion:
- What cohort age and historical data does the estimate rely on?
- Is the current cohort comparable in product mix, offer, market, and acquisition channel?
- Does the decision need revenue, contribution after costs, or cash collected?
- What would make the team pause the decision and wait for more evidence?
For contribution decisions, connect the result to Shopify profit after ads, COGS, fees, and refunds. A revenue measure and a contribution measure answer different questions; neither should be silently substituted for the other.
Turn a customer-value finding into a safe action
LTV becomes useful when it changes a specific next review. Keep the proposal bounded.
| Finding | Reviewable next step | Evidence still needed |
|---|---|---|
| A mature cohort has stronger repeat value | Compare its acquisition source, offer, and product mix with a same-aged cohort | Whether the difference persists after refund and margin treatment |
| High-value customers have become inactive | Prepare a segment review using last order, past spend, consent, and product context | Whether they are eligible for the planned message or offer |
| A new cohort looks weak at day 14 | Wait for the defined observation point; check checkout, inventory, and measurement | Whether the cohort is mature enough to judge |
| Forecast and realized value diverge | Document the data and definition difference | Whether the forecast should be used for this decision |
BizSidekick can assemble authorized commerce and retention evidence into a reviewable segment or finding. It should not promise a predicted LTV result, silently change a bid, or send a customer message. The responsible operator still confirms the audience, offer, timing, and any provider action.
A prompt for a governed customer-value review
Compare customers whose first paid order was in the last complete quarter with the same-aged prior-quarter cohort. Show realized net spend per customer, repeat-order rate, refund treatment, cohort age, and missing evidence. Identify one retention question worth reviewing. Do not change an audience, bid, or message.
This prompt names the population, comparison, evidence, and stopping point. It also leaves a useful trail for someone who needs to approve the next step.
FAQ
Should refunds be included in Shopify LTV?
Use the treatment that matches the decision and document it. A commerce or contribution decision often needs refunds visible because they change the quality of realized revenue. Do not switch between gross and net figures without saying so.
Is LTV enough to choose a winning acquisition channel?
No. Compare same-aged cohorts and keep channel attribution, costs, product mix, and customer eligibility visible. For a cross-source comparison, use the cross-channel ROAS workflow rather than treating one reported number as complete.
What should I do when the data is incomplete?
Record the missing field, owner, and decision blocked. Waiting for a complete cohort or repairing measurement is safer than creating a precise-looking estimate from inconsistent inputs.
Use BizSidekick in your AI apps
BizSidekick can help prepare an authorized-data customer-value review in ChatGPT, Claude, WorkBuddy, and more. It separates measured evidence from inference and keeps consequential changes for human confirmation.
Keep reading
Continue with a guide that supports your next ecommerce decision.
