Skip to content
MergeGuard

    Start with

    Playbook

    No source defines discount dependency, so define it from your own orders: the share of a customer’s orders that used a discount code. Count it per person across profiles, choose the cut line yourself, and test it before you act. A high share is a reason to adjust your offers. It is not a finding about the customer.

    By MergeGuard team

    4 min read

    Key insight

    Discount dependency has no standard definition, so write down your own before you count anyone.

    4 words used here
    Discount shareThe share of a customer’s orders that used a discount code.
    Discount codeA code a customer enters at checkout to get money off.
    Orders fileA spreadsheet file of your orders that you can download from Shopify.
    Cut lineThe discount share above which you treat a customer as discount-led.

    Define it from your orders

    We found no primary source that defines a customer who depends on discounts. A working term fills the gap: a customer’s discount share is the number of their orders that used a discount code, divided by all of their orders.

    A share is simple to calculate and easy to explain to a colleague. It shows how often a code was used, not why or how large the discount was.

    Export orders and calculate the share

    The export’s Discount Code column leaves out automatic discounts, so a store that runs automatic sales will undercount.

    Worked example (made up)

    Customer A: 4 of 5 orders used a code: 80%; Customer B: 1 of 4 orders used a code: 25%.Customer A: 4 of 5 orders used a code80%Customer B: 1 of 4 orders used a code25%

    Discount share is the orders that used a code divided by all of the customer’s orders.

    Shopify’s customer segments page says nothing about filtering by discount use, so do this step in a spreadsheet.

    Count per person, not per profile

    A shopper with two profiles splits their orders, and the share changes with the split. Counted by profile, the person looks like one customer who always uses a code and one who rarely does. Counted as one person, the share is in the middle.

    MergeGuard’s Win-back lists count this per person: Uses discounts on several profiles and Buys on sale every time, where every order had a discount or a marked-down price. Every plan, Free included, sees each list’s count, and the people behind them appear on a plan that includes Win-back lists (win-back lists).

    The profiles are one person only when the evidence says so: the same phone number, or emails that differ only by a typo. A shared address alone is a reason to look and is no proof, because partners and flatmates share one. See how Shopify identifies a customer for a discount for why profiles split in the first place.

    Worked example (made up)

    Profile 1: 2 of 2 orders: 100%; Profile 2: 1 of 3 orders: 33%; One person: 3 of 5 orders: 60%.Profile 1: 2 of 2 orders100%Profile 2: 1 of 3 orders33%One person: 3 of 5 orders60%

    Counted as one person, the share sits between the two profiles.

    Worked example (made up)

    58 customers look like they only buy with a code → 49 only buy with a code once each person is counted once; 9 also pay full price on another profile

    Pick and test a cut line

    There is no right cut line. Our reasoning is that a high share means the customer has often seen a code before ordering, and that tells you about your offers as much as about them. Start with the question you want answered:

    • To find regulars, look at customers with several orders and a high share, such as the top tenth.
    • To find one-off bargain hunters, look at customers with one order that used a code.
    • To check your offers, compare the share across months and see whether it rises when sales run.

    Check ten customers on each side of the line by hand. If the list holds loyal customers who happened to order during a sale, move the line.

    Do not call it fraud

    A discount share describes a buying pattern. It does not describe intent. A customer who buys every Black Friday is a seasonal customer. Someone who joined through a welcome offer and then waited for the next sale is behaving as most price-aware shoppers do. Keep the label out of your notes and out of anything the customer sees.

    If your question is about reuse of a single welcome code on several profiles, that is a different check; see welcome discount reuse.

    What to do with the list

    Use it to change your offers, because that treats everyone the same:

    • Run a sale without a code for one group, and compare their orders with a group that got the code.
    • Hold back the discount in a win-back email for customers whose share is high, and test full price first.
    • Remove people who are still buying under another profile from a “come back” offer, as who should not get a win-back discount explains.

    Your own email tool sends the offer. MergeGuard sends nothing, and a list you export or sync never changes anyone’s subscription.

    Step by step

    1. Export your orders for a set period

      Use the Export button on the Orders page and choose a date range. Pick a period long enough for most customers to have ordered more than once.

    2. Mark each order that used a discount code

      The export has a Discount Code column. It covers codes and manually applied draft-order discounts, and it leaves out automatic discounts.

    3. Join the profiles that belong to one person

      Combine profiles that share a phone number or differ only by a typo, and count their orders together before you filter anyone out. Keep profiles that share only an address apart.

    4. Group the orders by person and calculate the share

      Divide each person’s orders with a code by all of their orders. Then leave out people with a single order, because their share is always 0% or 100%. Apply this filter per person, after the join, so a shopper with one order on each of two profiles stays in.

    5. Choose a cut line and test it

      Pick the share that counts as a regular for your store, such as the top tenth of customers by share. Check a few customers by hand before you rely on the line.

    6. Decide what to change in your offers

      Use the list to adjust discount timing and size for everyone, and leave individual customers alone unless the pattern is strong.

    How do I spot customers who only buy with a discount?

    Count the share of each customer’s orders that used a discount code, per person across all profiles, and define discount dependence from your own orders. Pick the cut line and test it before you act, because a high share is a reason to review your offers. MergeGuard for Shopify’s Buys on sale every time list needs at least 2 orders.

    Welcome discount reuse

    Question about this chapter? Email support@mergeguard.store.

    Keep reading (8 links: 2 Guides, 1 Help, 1 Term, 1 Feature, 3 Sources)

    0 of 4 readSaved in this browser only.