Comparison
A discount code is a key the shopper has to bring. An automatic discount applies itself when the cart qualifies. The saving can be identical, so the real difference is attribution and friction: codes tell you which campaign earned the order and add a field to fill in, while automatic discounts remove the step and take the credit anonymously. Most stores need both, used for different jobs.
By CartKernel · Last reviewed 2026-09-07
Option A
A code the shopper enters at cart or checkout, tied to a campaign, partner or individual, with usage limits and reporting that shows exactly how it was redeemed.
Best for
Option B
A rule applied by the store when the cart meets the conditions, with no code to enter, shown in the cart and carried into checkout as part of the flow.
Best for
Side by side
| Criterion | Discount codes | Automatic discounts |
|---|---|---|
| How it applies | Shopper enters a code | Applies when the cart qualifies |
| Attribution | Redemption tied to the code and campaign | No campaign identifier of its own |
| Friction | One more field, and a reason to go looking | Nothing for the shopper to do |
| Exclusivity | Can be limited per customer or per use | Available to everyone who qualifies |
| Partner offers | Well suited, one code per partner | Not distinguishable by partner |
| Sitewide sales | Works, but leaks to code sites | Cleaner, since there is nothing to share |
| Combining offers | Governed by combination settings | Governed by combination settings |
| Reporting | Clear redemption counts and revenue | Read from order and sales reporting |
The main reason to use codes is that each one is identifiable. When a partner, a creator or a segment gets its own code, redemption tells you what that relationship produced without relying on cookies, click attribution or a platform's modelling. For affiliate arrangements and gifted product, it is the most reliable record you will have.
Codes also let you control who receives an offer. Limits per customer, single-use codes generated per recipient, minimum order requirements and end dates all constrain the giveaway, which matters when the offer is meant for one audience rather than the whole internet.
The trade-off is that codes travel. Once a code exists it can be posted anywhere, and coupon aggregation sites collect them. Unique per-recipient codes and sensible usage limits contain that, at the cost of more setup than a single shared code.
The visible discount field is a small conversion tax. A shopper who sees an empty code box often leaves to look for a code, and some of them do not return. When an offer is meant for everyone anyway, there is no reason to make them earn it by searching.
Automatic discounts apply the rule in the cart, so the price the shopper sees is the price they pay and the message can be stated on the product page and in the cart rather than hidden behind a field. For volume offers and bundles in particular, showing the saving as the quantity changes does more work than any code ever would.
What you give up is per-campaign attribution. An automatic discount does not tell you who it was for, so if you need to know which channel produced the order, either keep a code for that audience or make sure your analytics and order tagging can answer the question another way.
Decide upfront how offers may combine. Both types are governed by combination settings that determine whether an order, product or shipping discount can stack with another, and these need to be set deliberately rather than discovered when a cart ends up cheaper than intended. Check the current behaviour in your platform before a big promotion, since these settings change over time.
Put floors on everything. Minimum order values, exclusions for already reduced lines, caps on shipping offers and end dates on every code. Codes without expiry dates become permanent price cuts once they escape.
Then measure the whole promotion, not the redemption. Compare revenue, units and contribution margin after the discount against a normal period, and look at how many redeeming customers were already going to buy. A promotion that raises order counts while margin per order falls further is not a win, it is a busier way to earn less.
The honest bottom line
Use automatic discounts for offers everyone should get: sitewide sales, volume tiers, bundles and cart-level promotions where the code field only adds friction and invites shoppers to go hunting. Use codes when you need to know who earned the order or to limit who can claim it, which covers partner and creator campaigns, targeted email and SMS offers, and one-off gestures from support. Set combination rules, minimums and expiry dates before the campaign rather than during it, and judge every promotion on contribution margin against a comparable period rather than on how many times the offer was claimed.
We will tell you which fits, with your numbers.
Yes, and whether they stack on a single order depends on your platform's combination settings for order, product and shipping discounts. Configure those intentionally and test a few realistic carts before launching, so nobody discovers the interaction after the promotion is live.
It can, because an empty field prompts some shoppers to leave and search for a code. Options include applying offers automatically, collapsing the field behind a small link, or pre-applying a code from the campaign link so the saving is already in the cart when they arrive.
Give each partner their own code with an end date and sensible usage limits, and pair it with a link that pre-applies the discount so the shopper never has to type anything. The code handles attribution and the link removes the friction, which is the best of both.
Look at the period, not the coupon. Compare revenue, units, average order value and contribution margin after discount against a similar non-promotional period, and separate new customers from returning ones. Redemption counts show participation, not whether the promotion made money.
Services involved
A free Growth Analysis ranks what your store should fix first, by revenue at stake.