Should Loyalty Points Apply Before or After Shipping and Taxes?

Apply loyalty points to the merchandise subtotal, not shipping or taxes
The cleanest rule is to apply loyalty points to product subtotal only, not shipping or taxes. That means customers earn points based on the value of the items they buy, and redeemed points reduce the merchandise portion of the order instead of covering tax or freight charges.
That setup is usually the best fit for small-to-midsize merchants because it matches how most store owners think about real revenue. Shipping often passes straight through to a carrier. Taxes pass through to the government. Neither amount works like product revenue in your business.
It also keeps the program easier to explain. A customer can understand “earn points on what you buy” much faster than “earn points on some parts of the order, redeem them on other parts, except under certain checkout conditions.”
If you are reviewing your rewards rules, keep the logic simple enough that a customer can understand it at a glance.
What does it mean for loyalty points to apply before or after shipping and taxes?
This decision is really about which part of the order your points program touches. The order total at checkout usually has four pieces: merchandise subtotal, discounts, shipping, and taxes.
Here is the simple version:
- Merchandise subtotal: the total price of the products in the cart before shipping and taxes.
- Shipping: the delivery charge the customer pays.
- Taxes: sales tax, VAT, or similar charges collected at checkout.
- Final total: the amount the customer actually pays after discounts, shipping, and taxes are all included.
If points apply before shipping and taxes, the points calculation happens on the merchandise subtotal. If a customer buys $80 of products, pays $9 shipping, and owes $6 in tax, the earning base is $80, not $95.
If points apply after shipping and taxes, the program uses more of the final total. In that same order, points might be earned or redeemed against the full $95. That sounds generous. It also changes the economics fast.
This is where store owners get tripped up. “Before or after” sounds like a tiny settings question. It is not. It changes what you reward, what you discount, and what the customer sees at checkout.
Why does this rule matter for your loyalty program?
This rule matters because it affects margin, customer clarity, repeat purchase behavior, and how much cleanup you create for yourself later. Small settings create very real outcomes.
Start with margin. If you reward points on shipping and taxes, you are giving value on money that is not really yours to keep. A maker brand on OpoShop might sell a $42 candle, charge $8 shipping, and collect $4 in tax. If points are earned on the full $54, the program is rewarding $12 that does not reflect product revenue.
Then there is redemption behavior. If customers can redeem points against the full order total, some orders become more expensive for you than they look at first glance. A boutique owner offering a $10 birthday reward may think that reward is reducing product margin. If the reward also offsets shipping, the economics are different.
Customer clarity matters just as much. Checkout is where confusion shows up. A shopper who sees points advertised on the whole order but then notices tax still due, or shipping excluded without warning, is more likely to feel the math is off. The rule itself is not the problem. Surprise is the problem.
And then there is admin. A DTC brand using Perkly to watch points outstanding as a liability needs rules that stay consistent month after month. Subtotal-only logic is easier to explain in terms, easier to test in checkout, and easier to review in the dashboard when redemptions start rising.
How should you set your points rules for earning and redemption?
Set your earning and redemption rules around the same base: merchandise subtotal only. That gives you one clean logic for orders, signup rewards, birthday rewards, and checkout redemptions.
A simple method works best here. Decide what counts, write it down plainly, test what customers see, and then watch the numbers after launch.
1. Decide the earning base first
The earning base should usually be product subtotal before tax and shipping. If a customer spends $60 on products, they earn points on $60. If shipping adds $7 and tax adds $5, those amounts do not count toward earned points.
That setup is especially useful for a maker brand that wants a no-developer setup. The brand can tell customers, “You earn points on every order,” and still avoid rewarding tax amounts the business never keeps.
2. Match redemption rules to the same logic
Redemption rules should usually follow the same subtotal-only structure. If customers can redeem 500 points for $5 off, that $5 should reduce merchandise subtotal, not act like a catch-all credit against every line item at checkout.
A lot of confusion disappears when earning and redemption use the same base. Customers learn the rule once. Your team learns the rule once. The store stops making exceptions.
3. Document the rule where customers actually see it
The rule needs to show up in the places that matter: the rewards panel, checkout messaging, and your program terms. Hiding exclusions in fine print is where support tickets begin.
A weak explanation leaves room for doubt:
Weak: "Points apply to eligible purchases." Stronger: "Earn points on product subtotal. Points do not apply to shipping or taxes. Rewards redeem against merchandise subtotal at checkout."
That second version is not fancy. It is clear. Clear wins.
4. Check what the dashboard tells you
After launch, watch how the rule affects your program inside Perkly. Look at top members, redemption activity, and points outstanding as a liability. If redemptions jump after a birthday campaign, you want to know whether those rewards are reducing product revenue only or also eating into shipping recovery.
A points program works best when the rules are easy to explain, easy to track, and tied to repeat purchase goals.
Before vs after shipping and taxes: which approach is best?
Subtotal-only is usually the best approach because it is the fairest balance between customer value and store economics. The other options can work, but they create more tradeoffs than most merchants need.
Here is the side-by-side view:
| Rule type | Subtotal only | Subtotal plus shipping | Full order total |
|---|---|---|---|
| What points apply to | Products only | Products and shipping | Products, shipping, and taxes |
| Margin impact | Lowest risk | Moderate risk | Highest risk |
| Customer clarity | Easiest to explain | Can be confusing | Often looks generous but creates messy checkout math |
Subtotal-only is the best fit for most DTC brands, boutiques, and makers because it rewards what the customer bought without discounting pass-through charges. A $90 apparel order with $8 shipping and $7 tax still feels rewarding when points apply to the $90.
Subtotal plus shipping can make sense if free shipping is a major part of your brand promise and your margins can absorb it. Even then, it is usually better to make that a separate reward instead of your default rule.
Full order total is the loosest option. Customers like it at first because it feels broad. Store owners like it less once they see the redemptions stack against product discounts, shipping recovery, and taxes all at once.
If you want a middle ground, separate shipping rewards are cleaner than making shipping part of every points rule. You could let customers redeem a special shipping reward at 1,000 points while keeping normal earning and redemption tied to subtotal. That keeps the main program simple.
Common mistakes merchants make with shipping and tax point rules
The most common mistakes are rewarding tax, creating checkout math that feels inconsistent, and writing rules that only make sense to the merchant. All three are avoidable.
The first mistake is earning points on tax amounts. Tax is collected, not earned. If a customer places a $120 order with $10 shipping and $11 tax, rewarding points on $141 tells the program to treat tax like sales revenue. That is usually the wrong signal.
The second mistake is letting redemptions hit every part of the order without thinking through the cost. A $15 reward applied to a $50 cart can feel fine. A $15 reward that also offsets shipping on low-margin items can change the order economics more than expected.
The third mistake is inconsistent logic across reward types. We see merchants give signup points one way, birthday rewards another way, and order-earned points a third way. A small merchant on OpoShop is better off rewriting the rules so signup points, birthday points, and order-earned points all follow the same subtotal-only logic.
Another mistake is poor checkout language. Customers do not need legal writing. Customers need plain writing. “Rewards exclude non-merchandise charges” is technically true, but “Points do not apply to shipping or taxes” is much easier to understand.
And yes, applying points after tax can confuse customers at checkout. A store owner comparing both setups in an OpoShop store will usually notice that merchandise-subtotal messaging is easier to follow than final-total math that changes after shipping and tax are calculated.
If you are tightening your rules to protect margin, do it in a way customers can actually follow.
What we recommend for most Perkly-style loyalty programs
We recommend using merchandise subtotal as the default rule for both earning and redemption. For most stores, that is the cleanest, fairest, and easiest setup to maintain.
That means customers earn points on product value only. It also means redeemed points reduce the product subtotal, not shipping and not taxes. If you want to reward shipping from time to time, make it a separate reward rather than the default behavior across the whole program.
This recommendation fits the real-world cases most often. A boutique merchant deciding whether a birthday reward should cover shipping will usually get a better result by keeping the birthday reward on merchandise only. A DTC brand watching points outstanding in Perkly will usually prefer tighter rules that protect margin. A maker brand that wants no developer work will usually prefer one rule that stays consistent everywhere.
We would also keep the language visible in three places:
- Rewards panel: tell customers what purchases earn points.
- Checkout area: tell customers what rewards can reduce.
- Program terms: spell out shipping and tax exclusions in plain English.
For merchants on OpoShop, simple rules tend to age better. They are easier to explain to staff, easier to support, and easier to trust when you review redemptions later.
Best answer: For most Perkly-style programs, use merchandise subtotal as the earning and redemption base, and exclude shipping and taxes by default. That rule protects margin, keeps accounting cleaner, and gives customers a checkout experience that makes sense the first time they see it. If you want extra generosity, add a separate shipping perk instead of making every order harder to price.
If you sell on OpoShop and want your rewards setup to stay simple as the store grows, start with rules you can explain in one sentence.
FAQs
Do most loyalty programs exclude shipping and taxes from points?
Yes. Most loyalty programs work off merchandise subtotal rather than the full order total. Excluding shipping and taxes keeps the points logic tied to product revenue instead of pass-through charges.
Should customers earn points on the order subtotal only?
Yes, that is usually the best default. Customers earn points on what they actually bought, and the store avoids giving rewards on shipping fees or tax amounts it does not keep.
Can loyalty points be redeemed against shipping costs?
Yes, but it is usually better as a separate reward instead of the default rule for every redemption. A shipping-specific reward keeps your main points logic cleaner and easier to manage.
How should I explain shipping and tax exclusions in my rewards rules?
Use plain language and put it where customers will see it. “Earn points on product subtotal. Rewards apply to merchandise only, not shipping or taxes” is much clearer than vague legal wording.
What setup is easiest for a small OpoShop merchant to manage?
A subtotal-only setup is the easiest for a small OpoShop merchant to manage. One rule for earning and one matching rule for redemption keeps checkout, support, and reporting much simpler.
Should loyalty points work the same way as store credit or discounts?
Not always. Loyalty points can act like a discount at checkout, but the rules do not need to mirror store credit exactly. For most merchants on OpoShop, points work best when they follow a tighter rule set than general store credit.
Want a simpler way to turn one-time buyers into repeat customers? See how Perkly fits into your OpoShop store.