
Fail to exclude customers from a loyalty program, and a staff-priced order can collect a second benefit while a wholesale replenishment order inflates consumer reward liability. To exclude customers from a loyalty program properly, separate staff, commercial, and partner relationships before changing a single customer record.
Short answer: Define whether an exclusion blocks earning, redemption, enrollment, communications, or all four. Then identify the account consistently in Shopify, confirm your loyalty platform can act on that identifier, and document the policy before applying it. A staff member, reseller, club coordinator, and sponsored athlete should not automatically receive the same treatment in a Shopify loyalty program.
How to exclude customers from a loyalty program: start with the rule
| Customer type | Default recommendation | Why | Earning | Redemption | Review trigger |
|---|---|---|---|---|---|
| Staff using employee discount | Exclude from consumer program | Staff pricing already changes order economics | Block | Block | Employment ends or discount is not used |
| Wholesale or B2B account | Separate policy | Commercial terms differ from DTC pricing | Usually block | Usually block | Account begins buying for personal use |
| Reseller | Exclude | Margin comes from resale | Block | Block | Resale status changes |
| Club or team coordinator | Review by order purpose | Group purchasing differs from personal shopping | Case by case | Case by case | Order is for members rather than inventory |
| Sponsored partner | Exclude from public program | Sponsorship benefits are separately agreed | Block | Block | Agreement expires |
| Ordinary DTC customer | Include | Consumer purchase economics apply | Allow | Allow | Fraud or account review |
The difference between a customer exclusion and a discount rule
A customer exclusion is an eligibility decision. A discount rule decides which orders qualify for a price reduction. They can overlap, but they solve different problems.
For example, excluding discounted products from earning may prevent points on a promotional order. It does not answer whether an employee should redeem a consumer reward after using staff pricing. Decide the relationship first, then configure the order-level rule.
The core test is practical: does this account buy under the same economics, customer relationship, and intended use as your DTC audience? If the answer is no, the public program may not fit.
Choose the behavior you want to block
Write down exactly what exclusion means for each category:
- Enrollment in the program
- Earning on purchases and actions
- Reward redemption
- Loyalty emails and messages
- Access to previously earned balances
Avoid a vague “excluded from loyalty” label. A former employee might retain a balance you agreed to honor while no longer earning on staff-discounted purchases. A reseller may need a complete block because consumer rewards undermine their resale margin.
A practical exclusion decision tree
Start with the transaction. Is the buyer purchasing for personal use at consumer pricing? If yes, include them unless there is a specific risk or agreement that says otherwise.
If the order uses staff pricing, wholesale terms, sponsored product, partner compensation, or resale inventory economics, create a separate policy. The decision should come from finance, ecommerce, and whoever owns the commercial relationship.
Exclude staff from rewards when the staff discount already does the work
Why staff discounts and points should not stack
A staff discount lowers the price paid today. Loyalty points or store credit create another benefit for a later order. Allowing both by default can reduce margin twice on the same customer relationship.
It can also distort reporting. Employee purchases can make member revenue, points issued, and redemption rates look healthier than consumer behavior really is.
That does not mean staff can never participate. A merchant can allow an employee to shop as a normal customer when they use a personal account, do not use staff pricing, and follow the same terms as everyone else. Treat that as a written merchant policy, not an assumption built into Shopify.
Set a clear employee policy
A workable default is to exclude current employees, contractors with purchase privileges, and shared internal accounts from both earning and redemption when a staff discount is applied.
Use a clear rule for support and store teams: “Your staff benefit already applies to this purchase, so consumer loyalty rewards are not added to the same order.”
Do not rely only on an employee email domain. Shopify provides a Flow example for tagging employee accounts by email domain, but employees may also shop with personal addresses. Use an internal onboarding and offboarding process to add or remove the relevant customer tag.
What to do with existing employee balances
Choose one policy and apply it consistently. You might freeze the balance, allow redemption until expiry, convert it to a separate staff benefit, or remove it after notice under your program terms.
Record the effective date and any manual adjustment so support can explain the outcome consistently. See the points and rewards framework below before changing balances.
Handle wholesale accounts, resellers, clubs, and bulk buyers by channel
| Account type | Typical economics | Exclude by default? | Alternative treatment | Owner of the decision |
|---|---|---|---|---|
| Wholesale or B2B buyer | Negotiated commercial pricing | Usually | Separate B2B retention policy | B2B lead and finance |
| Reseller | Buys inventory for resale margin | Yes | Partner or reseller agreement | Sales and finance |
| Bulk consumer buyer | Large order for personal or group use | No automatic exclusion | Review order purpose | Ecommerce team |
| Club, school, or team | Group purchases or member orders | Review | Separate coordinator policy | Partnerships lead |
| Sponsored athlete or coach | Free product, partner pricing, or compensation | Usually | Sponsorship agreement benefits | Partnerships lead |
Wholesale customers and B2B accounts
Wholesale buyers are not automatically bad loyalty candidates. They are commercial customers with different pricing, order patterns, and often a different relationship owner.
Shopify B2B customers must be associated with a company location to place B2B orders, and they use Shopify customer accounts for B2B purchasing. That structure gives you a clearer way to distinguish business purchasing from ordinary DTC activity.
If repeat ordering matters and you own the relationship, a separate B2B earn-and-redeem structure may be useful. The safer default is to avoid stacking DTC rewards on top of wholesale pricing. Read more about what changes between channels in B2B vs DTC loyalty programs.
Resellers and bulk buyers
Resellers should usually be fully excluded from the public program. Their economic benefit comes from resale margin, and consumer rewards can effectively subsidize inventory purchasing.
Bulk buyers need more care. Someone ordering ten units as gifts may still be a legitimate consumer. A buyer ordering ten cases for resale or for a recurring group purchase is operating under different economics. Use the purpose of the order, not just quantity, as the review trigger.
For replenishment-heavy categories, POS sales and repeat ordering can further complicate the decision. The right treatment may vary by channel, which is why loyalty programs by industry should reflect how customers actually buy.
Sponsored athletes, coaches, and partner accounts
Sponsored athletes, coaches, ambassadors, and partners should generally sit outside the public consumer program when they receive free product, partner pricing, commissions, or custom benefits.
Their arrangement already has terms. Put their benefits in the agreement, including what happens when the partnership ends, rather than trying to manage exceptions through customer-service discretion.
Use Shopify customer tags as your source of truth, not as the exclusion itself
Create a small, controlled tag vocabulary
Use a small set of tags that clearly state the operational purpose:
- Loyalty-Exclude-Staff
- Loyalty-Exclude-Wholesale
- Loyalty-Exclude-Reseller
- Loyalty-Exclude-Sponsored
- Loyalty-Review-Required
Shopify lets merchants add and remove customer tags and use them to create customer segments. Shopify Flow can also add or remove tags based on triggers and conditions.
Keep tag names professional. Customers may never see them in standard storefront experiences, but tags are administrative data that can be read or used by installed apps.
Build segments and review the matches
Tags are useful because they let you audit the affected population before you change program behavior. Shopify customer segments support customer_tags filters with CONTAINS and NOT CONTAINS operators.
Build one segment for each exclusion category and another for customers who should remain eligible. Review the actual names and order histories before a bulk change. Look for former employees, expired sponsorships, duplicate records, and customers tagged manually during a support interaction.
Mage’s automatic VIP tier tags are a separate example of structured status data written back to Shopify. Mage uses the format Mage VIP Tier: [Tier Name] and updates it when a customer moves tiers. That status tag helps segmentation, but it is not an exclusion tag.
Confirm the loyalty app can act on the tag
A tag identifies a customer. It does not automatically stop a loyalty app from allowing enrollment, earning, redemption, or messages.
Apply the Shopify tag, then verify how your loyalty platform handles it with test accounts. Use the testing checklist below before applying the workflow at scale.
“Cannot say enough good things about the team at Mage Loyalty, one of the absolute best organizations we have ever worked with, full stop! So glad we connected with them, completely redid our loyalty program, new concepts, use of loyalty, increasing user engagement, showing us where we were not valuing our best customers, just WOW, amazing team!”


Read the West Coast Goalkeeping case study →
Decide what happens to points, pending earnings, and rewards
| Program element | Preserve | Freeze | Remove or expire | Customer communication needed |
|---|---|---|---|---|
| Existing balance | Honor under normal rules | Keep visible but unavailable | Only after documented policy and notice | Yes |
| Pending earnings | Approve if eligible before effective date | Hold for review | Reverse if policy says order was ineligible | Yes, if material |
| Active reward | Allow use until expiry | Disable redemption | Cancel only under stated terms | Yes |
| Loyalty messages | Continue transition messages | Pause promotional sends | Stop all loyalty communications | Usually |
| Account access | Keep account active | Keep account active | Do not remove solely for exclusion | Explain any change |
Existing balances
Choose your balance policy before tagging anyone. The practical options are to preserve rewards, freeze them, remove them after notice, or convert them to a separate staff or partner benefit.
Silent deletion creates avoidable disputes. State the effective date and explain whether older rewards remain usable.
Pending points and return windows
Review pending earnings separately from approved balances. In Mage, purchase earnings are awarded when an order is paid unless an approval time holds them as pending. A refund reverses the earnings, including a proportional reversal on a partial refund.
Approval time can help when an order needs review or when you want earnings to clear after the return window. Before changing eligibility, check whether the account has pending points, refunds in progress, or active discount codes.
Redemption and communications
Decide whether an excluded customer can redeem a reward earned before the policy took effect. There is no universal right answer, but there should be one documented answer.
You may preserve a balance during a transition while stopping promotional loyalty messages immediately. Record the affected accounts and policy effective date before changing records.
Test the exclusion workflow before applying it at scale
Test one account in each exclusion category
Create or identify one account for staff, wholesale, reseller, sponsored partner, and an ordinary DTC customer. Test each account against the exact policy you intend to use.
Check four outcomes: can the customer earn, can they redeem, do they receive loyalty communications, and does their activity appear correctly in reporting? A customer must be signed in for Mage purchase earnings, so test both signed-in and guest checkout behavior. Guest checkouts do not earn purchase points in Mage.
Check online checkout and Shopify POS
Do not stop at storefront testing if you sell in person. Run the same checks through Shopify POS.
Mage’s POS tools let staff view a customer’s points balance, rewards, and points history. Staff can also make manual adjustments, which are recorded as POS actions and can include notes. Use that audit trail for genuine corrections, not as a substitute for a clear eligibility policy.
Use Test Mode only for controlled pre-launch testing
Mage Test Mode is useful for controlled QA. It blocks non-test customers from earning, redeeming, and triggering integration events while customers on the test list can interact normally.
It is not a live production mechanism for excluding only staff, wholesale, or reseller accounts. Turning it on affects everyone outside the test list. Use it to validate your program before launch or before a major configuration change, then test the actual production exclusion workflow separately.
Communicate exclusions without making legitimate customers feel punished
Put the rule in program terms
State eligibility by transaction type and account relationship. “Orders placed using employee pricing do not earn or redeem consumer loyalty rewards” is clearer than “we reserve the right to exclude anyone.”
Your loyalty program terms should match checkout FAQs, support macros, and internal instructions.
Use plain-language customer support replies
Keep explanations neutral and specific.
For staff: “Your staff benefit already applies to this purchase, so consumer loyalty rewards are not added to the same order.”
For wholesale or resale: “This order is placed under commercial terms, which are separate from our consumer loyalty program.”
For sponsors: “Your partner benefits are managed through your sponsorship agreement rather than the public rewards program.”
Review the policy every quarter
Review exclusion tags quarterly. Check former employees, expired sponsorships, customers whose wholesale status changed, and accounts tagged manually by mistake.
Also review whether the policy is producing false positives. Good policies leave room for documented exceptions without turning every exception into a negotiation.
Frequently asked questions
What does it mean to exclude a customer from a loyalty program?
A loyalty program customer exclusion is a rule that prevents a defined account or transaction type from earning, redeeming, enrolling, receiving loyalty communications, or some combination of those actions. Define the exact scope before changing the customer record.
Should employees earn loyalty points if they receive a staff discount?
Employees should usually not earn consumer loyalty points on purchases that use a staff discount, unless the merchant has deliberately approved that exception. Stacking both benefits can reduce margin twice and distort loyalty reporting.
How do I exclude customers by tag in Shopify?
Create controlled customer tags, build segments to audit who matches, and verify that your loyalty platform can apply the intended restriction. A Shopify tag identifies and groups a customer, but it does not automatically block loyalty earning, redemption, enrollment, or messages.
Can wholesale customers earn points in a loyalty program?
Wholesale customers can earn points when a merchant deliberately designs a separate B2B policy, but they should not automatically receive DTC rewards on top of wholesale pricing. Shopify B2B customers are associated with company locations and use customer accounts, which helps merchants separate commercial activity from consumer purchasing.
What happens to existing points when a customer is excluded?
Existing points can be preserved, frozen, removed after notice, or converted into a separate benefit, depending on the merchant’s written policy. Record the effective date and balance before changing eligibility so support teams can explain the outcome consistently.
How can loyalty exclusions prevent program abuse?
Loyalty exclusions prevent predictable abuse by separating staff-priced purchases, resale inventory orders, and sponsored accounts from consumer reward economics. Combine exclusions with approval delays, refund reversals, points-history reviews, documented manual adjustments, and regular tag audits.
Exclude accounts because their commercial relationship differs from the DTC program, not because they look unusual in a customer list. Tag the relationship, define the exact restrictions, test the workflow across checkout and POS, and document what happens to existing rewards before applying the policy in bulk.
Graeme is the co-founder at Mage Loyalty. He heads product development, from complex loyalty migrations and large-scale data handling to building the features shaping the future of loyalty on Shopify.


















