Direct answer: how to find which first-purchase products create repeat customers

To find which first-purchase products create repeat customers, start with an order export and rebuild the customer journey from the first order forward. For each customer, identify the first order, assign the first-purchase SKU, product, bundle, or category, then flag whether that customer placed a second order. From there, calculate the second-order rate, days to second order, second-order AOV, refund exposure, and the product or category bought next.

The operator question is not just, “What is my repeat purchase rate?” It is, “Which products are creating customers who come back, and which ones are only creating first orders?”

The practical workflow is:

  1. Export orders for a cohort of customers whose first purchase happened far enough in the past to allow a realistic second order.
  2. Group orders by customer ID or email hash.
  3. Find each customer’s first completed order.
  4. Assign the first-purchase product, SKU, category, or basket type.
  5. Check whether that same customer placed a second completed order.
  6. Calculate days between first and second order.
  7. Compare first-order AOV to second-order AOV.
  8. Separate refunded, cancelled, or partially refunded first orders.
  9. Rank first-product cohorts by repeat behavior and commercial quality, not just sales volume.

The output should tell you which first products deserve more acquisition support, which ones need a better post-purchase journey, which ones should be bundled differently, and which ones may be creating low-quality first-time buyers.

Direct rule: judge a first-purchase product by the customers it creates, not only by the revenue it produces on the first order.

Why storewide repeat purchase rate hides first-product quality

A storewide repeat purchase rate can look acceptable while specific first-purchase products are quietly weakening retention. One product may drive a large number of new customers through ads or discounts but produce very few second orders. Another product may bring in fewer first-time buyers but lead to faster repeat purchases, better follow-up AOV, or more predictable replenishment.

That is why first-purchase product cohorts matter. They show the quality of customers created by the first product, not just whether the store has repeat buyers overall.

TermWhat it meansWhy operators use it
First-purchase product cohortCustomers grouped by the SKU, product, bundle, or category they bought on their first order.Shows which entry products create better or worse customer behavior.
Second-order rateThe share of first-time customers in that cohort who placed another order.Measures whether the first product is creating repeat customers.
Days to second orderThe time between a customer’s first order and second order.Guides replenishment, education, cross-sell, and winback timing.
Second-order AOVThe average or median value of the customer’s second order.Shows whether repeat behavior is commercially meaningful or low-value.
Refund-adjusted repeat behaviorRepeat behavior reviewed alongside refunds, cancellations, and partial refunds.Prevents a product from looking strong when the first order has poor customer experience or weak margin.

The commercial risk is simple: if you scale first-order ROAS without checking first-product retention, you can buy more one-time customers. That can make acquisition dashboards look healthy while returning-customer revenue, contribution margin, and LTV stay weak.

This is especially important for hero products, discounted starter items, influencer-driven SKUs, bundles, seasonal products, and products with sizing, quality, or expectation issues.

Order export fields you need before building the cohort table

You can run a first-purchase product cohort analysis from Shopify, WooCommerce, or most ecommerce order exports if you have customer, order, product, revenue, and refund fields. You do not need a perfect data warehouse to start. You do need clean enough order data to identify customer sequence and product purchased.

Minimum fields to export

FieldUse in the analysis
Customer ID or email hashGroups orders from the same customer without relying only on order-level totals.
Order IDIdentifies each transaction and prevents duplicate counting.
Order dateSorts each customer’s first, second, and later orders.
Order number or order sequenceHelps confirm whether the order is the customer’s first order.
Product titleCreates readable product cohorts.
SKUSeparates variants, bundles, sizes, formulas, or product versions when needed.
VariantHelps diagnose size, color, flavor, pack size, or format differences.
Category or product typeAllows category-level cohorts when SKU-level samples are too small.
QuantityIdentifies multi-unit first orders and bundle-like behavior.
Order revenueCalculates first-order and second-order AOV.
DiscountShows whether retention changes when the first order is heavily discounted.
Shipping and taxLets you choose whether AOV should include or exclude these amounts consistently.
Refund amountFlags products where repeat behavior may be overstated by poor first-order outcomes.
Fulfillment statusExcludes cancelled, failed, or unfulfilled orders when appropriate.
Acquisition sourceHelps separate product quality from channel quality when the data is available.
Customer tagsHelps isolate wholesale, subscription, VIP, influencer, marketplace, or support-created orders.

How to handle multi-SKU first orders

Multi-product first orders are common, and they can distort the analysis if you assign the cohort randomly. Choose one rule and document it before reading the results.

  • Primary product rule: assign the cohort based on the highest-revenue item in the first order.
  • Hero SKU rule: assign the cohort based on a known acquisition product or featured product in the basket.
  • Category cohort rule: group the first order by category when several related SKUs appear together.
  • Bundle rule: treat curated bundles, starter kits, discovery sets, or build-a-box purchases as their own first-purchase cohort.
  • Basket combination rule: analyze common combinations separately if the combination is strategically important.

The goal is not to create a perfect academic model. The goal is to make product-level retention visible enough to guide acquisition, merchandising, and lifecycle decisions.

The first-product cohort report map: SKU, second order, timing, AOV, and refunds

Your report should be built around the first product purchased, then enriched with second-order behavior. A useful cohort table does not stop at “repeat purchase rate by product.” It also shows timing, order value, refund risk, and what customers bought next.

ColumnWhat to calculatePlain-English formula
First-purchase product or categoryThe SKU, product, bundle, or category assigned to the customer’s first order.For each customer, sort orders by date and use the product rule chosen for order one.
First-time customersNumber of customers who entered through that product cohort.Count unique customers whose first order belongs to the cohort.
Customers with second orderNumber of those customers who placed another completed order.Count unique customers in the cohort with an order after their first order.
Second-order rateShare of the cohort that bought again.Customers with second order divided by first-time customers.
Median days to second orderTypical time from first order to second order.For customers who repeated, subtract first order date from second order date and take the median.
Average or median first-order AOVTypical first purchase value for the cohort.Total or median first-order revenue for customers in the cohort.
Average or median second-order AOVTypical second purchase value for customers who repeated.Total or median second-order revenue among customers with a second order.
Refund rate on first orderShare of first orders in the cohort with refunds.First orders with any refund divided by first orders in the cohort.
Second-order product or categoryMost common product or category bought on the second order.Group second orders by product or category and identify the most frequent next purchase.
NotesCommercial interpretation.Add observations about discounting, channel mix, seasonality, CX issues, or lifecycle exposure.

Use a fixed first-purchase cohort window. For example, analyze customers whose first purchase occurred far enough in the past that they had a fair chance to place a second order. If your product usually takes weeks or months to replenish, do not compare last week’s new customers to customers acquired six months ago.

Simple spreadsheet logic

  • First order: the earliest completed order date for each customer.
  • Second order: the next completed order after the first order for the same customer.
  • Second-order flag: yes if the customer has at least one order after the first order; no if not.
  • Days to second order: second order date minus first order date.
  • Second-order rate by first product: repeat customers in the first-product cohort divided by all first-time customers in that cohort.
  • Refund-adjusted review: compare the same product cohorts after flagging refunded or cancelled first orders.

If you have margin data, add contribution margin to the table. If you do not, still separate gross order value from refunds and discounts so you do not mistake inflated revenue for high-quality retention.

Analyze your order export before changing spend

Before you scale a first-order offer, rebuild a post-purchase flow, or move a product into your hero placement, track which first products actually create second orders.

Analyze your order export

How to read the results without overvaluing top sellers

Once the table is built, avoid sorting only by first-time customer count. High-volume products are not automatically good entry products. Low-volume products are not automatically unimportant. The useful patterns are in the relationship between volume, repeat behavior, timing, AOV, refunds, and next product purchased.

Pattern 1: high volume, low repeat

This product creates many first-time buyers but few second orders. It may be an acquisition trap, especially if it is heavily discounted, low-margin, seasonal, or promoted to broad audiences.

Operator response: check channel mix, discount depth, first-order expectations, product education, and whether the next-best product is obvious after purchase.

Pattern 2: low volume, high repeat

This product does not bring in the most new customers, but the customers who start here come back at a stronger rate.

Operator response: test more traffic, improve collection placement, feature it in quizzes or buying guides, and consider using it as an entry product if margin supports it.

Pattern 3: fast second order

Customers who start with this product place another order quickly. This often signals a strong replenishment, accessory, refill, add-on, or discovery path.

Operator response: build the email/SMS timing around the median days to second order. Do not wait for a generic winback window if this cohort usually buys again sooner.

Pattern 4: slow second order

The cohort eventually repeats, but not quickly. These customers may need education, usage support, seasonal reminders, or a longer consideration cycle.

Operator response: avoid pushing aggressive discounts too early. Use product education, proof, comparisons, and timing based on the actual second-order interval.

Pattern 5: high refund, high repeat

A product can appear to create repeat customers while also producing refunds, support tickets, exchanges, or margin pressure. That does not make it a bad product automatically, but it does mean retention should be reviewed with CX and profitability.

Operator response: inspect product page expectations, sizing, quality, fulfillment timing, packaging, onboarding, and support reasons before scaling.

Pattern 6: high repeat, lower second AOV

A lower second-order AOV is not always bad. The cohort may still be valuable if customers continue into later orders, buy high-margin consumables, or enter a subscription path. But if the second order is both lower value and low margin, the first product may be weaker than the repeat rate suggests.

Operator response: compare second-order product mix and margin where possible. Then test bundles, thresholds, subscriptions, or cross-sells that improve the follow-up order.

Safeguard: do not crown a winner from a tiny sample. A SKU with ten first-time customers and five repeat buyers may show a high repeat rate, but it is not as reliable as a product cohort with a larger base and consistent behavior across multiple months.

Decision matrix: what to do with each first-purchase product cohort

The purpose of the analysis is action. Once you know which first-purchase products create repeat customers, map each cohort to acquisition, merchandising, lifecycle, offer, and measurement decisions.

First-product cohort findingAcquisition actionMerchandising actionEmail/SMS actionOffer actionMeasurement follow-up
High-repeat and profitableTest more budget if CAC and margin allow.Give stronger placement in collections, landing pages, quizzes, or starter paths.Build a dedicated post-purchase path based on the common second order.Protect margin; avoid unnecessary discounting if customers already return.Track second-order rate, second-order AOV, and later-order value by month.
High first-order volume, low repeatSlow scaling until customer quality is understood.Review whether the product is overused as the entry offer.Add education, use-case support, social proof, and next-step recommendations.Test a different welcome offer, bundle, or threshold instead of deeper discounting.Compare by channel, discount, and landing page to isolate the issue.
Slow-repeat productDo not judge too early against faster-cycle products.Add content that explains usage, replenishment, or complementary products.Extend the nurture window and time reminders to actual repurchase behavior.Use delayed incentives or value-add offers instead of immediate discounts.Measure repeat behavior over a longer, consistent window.
Refund-heavy productPause aggressive scale until refund causes are reviewed.Improve product page clarity, sizing, expectations, shipping notes, or variant guidance.Send onboarding, care, fit, setup, or usage guidance immediately after purchase.Avoid offers that push poor-fit buyers into the product.Track refund rate, support reasons, exchanges, and repeat behavior together.
Leads to higher second-order AOVConsider using it as a higher-quality acquisition product.Place it near complementary products that support the second order path.Promote the most common upgrade, replenishment, or bundle in the next flow.Test bundle thresholds or loyalty credit that increases order depth.Monitor second-order AOV, contribution margin, and bundle attach rate.
Leads to a specific second-order categoryTarget acquisition to audiences likely to need that product path.Make the second category easier to discover after the first purchase.Send category-specific cross-sells instead of generic best sellers.Offer a focused next-product incentive only if margin supports it.Track category transition rate from first order to second order.

This matrix is where the report becomes operational. It prevents the team from responding to every product cohort with the same generic discount, winback, or email sequence.

How to turn the analysis into lifecycle, merchandising, and acquisition actions

The cohort table should change what you do next. Use the first product to decide the post-purchase journey, the next product recommendation, the acquisition rule, and the measurement window.

Workflow: replenishable first product

If customers who start with a replenishable item tend to buy again after a predictable number of days, build the journey around that timing. Send product education first, usage reminders next, then replenishment prompts before the typical second-order point.

  • Use median days to second order as the starting timing reference.
  • Feature the same product, refill, subscription, or larger pack if that is the common second order.
  • Measure whether the flow improves second-order rate without relying only on discounting.

Workflow: discovery bundle or starter kit

If a discovery bundle leads customers into a specific second-order category, use that behavior to personalize the follow-up path. The bundle is not the end of the journey; it is a signal of what the customer should see next.

  • Identify the most common second-order category after the bundle.
  • Create segmented follow-ups based on what was included in the first basket.
  • Move customers toward full-size products, refills, subscriptions, or complementary categories.

Workflow: low-repeat discount product

If a discounted first product creates many first orders but weak repeat behavior, the problem may be the entry offer, the audience, the product-market fit, or the next step after purchase.

  • Compare discounted and non-discounted first orders for the same product.
  • Check whether one paid channel is driving most of the low-repeat customers.
  • Test a different welcome offer, bundle composition, or landing page promise before scaling.

Workflow: refund-heavy SKU

If a first-purchase SKU has meaningful refund exposure, do not treat repeat rate in isolation. Refunds may point to mismatched expectations, product fit issues, fulfillment problems, unclear sizing, or quality concerns.

  • Review refund reasons and support tickets for the SKU.
  • Improve product detail pages, variant guidance, delivery expectations, and onboarding.
  • Hold back acquisition scale until the customer experience issue is understood.

Workflow: product that leads to higher second-order AOV

If a first product reliably leads to larger second orders, it may be a better acquisition product than a higher-volume SKU with weaker follow-up behavior. Review margin and later-order behavior before making it a hero product, but do not ignore it just because it is not the top seller today.

  • Promote it in starter collections or product recommendation paths.
  • Build cross-sells around the second-order products customers already buy.
  • Measure whether added traffic preserves the same repeat and AOV pattern.

Common mistakes when measuring repeat customers by first product

Product-level retention analysis is only useful if the cohort logic is clean. The most common mistakes usually come from mixing customer stages, comparing unfair windows, or ignoring commercial quality.

MistakeWhy it misleads the teamBetter approach
Using all orders instead of first ordersYou end up measuring product popularity, not which product created the customer.Assign cohorts based only on each customer’s first completed order.
Counting multiple orders from the same customer incorrectlyHeavy buyers can distort product-level results.Count unique customers for second-order rate, then analyze later order depth separately.
Ignoring refunds and cancellationsA product can look strong while producing poor customer experience or weak economics.Flag refunded, cancelled, and partially refunded first orders in the cohort table.
Mixing customers with different follow-up windowsRecent customers have had less time to repeat than older customers.Use a fixed first-purchase window and a realistic repeat window for your product cycle.
Comparing tiny SKU samples to large product cohortsSmall samples can make repeat rates look unusually high or low.Set a minimum customer count or group small SKUs into product type, category, or bundle cohorts.
Ignoring bundles and variantsA starter kit, size, flavor, or variant may behave differently from the parent product.Separate strategically important bundles and variants when they have enough volume.
Using revenue when margin data existsHigh AOV does not always mean high contribution margin.Add margin, COGS, shipping cost, or contribution profit where available.
Assuming the product caused the repeat purchaseChannel, discount, seasonality, and lifecycle exposure may influence behavior.Review product cohorts alongside acquisition source, offer, and post-purchase flow exposure.

The best first-purchase product is not always the top seller. It is the product that creates profitable customers who come back, buy again within a sensible window, produce healthy follow-up value, and do not create avoidable refund or support pressure.

Once you can see that by SKU, bundle, or category, the next decisions become clearer: where to spend, what to feature, what to bundle, when to send replenishment or cross-sell messages, and which products should stop being scaled just because they generate first orders.