Step-by-step guide to add a coupon to your store in Adobe Commerce

To add a coupon in Adobe Commerce, an administrator opens Marketing, Promotions, Cart Price Rules, creates a new rule, gives it a name, activates it, chooses the websites and customer groups, selects a specific coupon code, sets usage limits and dates, and defines the discount in the Actions section. The process takes minutes, and what takes longer, and matters more, is deciding who the coupon is for, what it costs the business and how its results will be judged.

Picture the commercial committee of a mid-sized online retailer on the Monday after a promotion. The marketing director presents a record week of orders. The finance director asks about margin and the answer is uncomfortable: the discount code, shared on a coupon website, was used many times by people who had never bought before and would not buy again, and nobody remembers whether the code was meant to expire. The operations manager points out that the code also worked on the second language store, where the checkout message appeared in the wrong language. A coupon is easy to create and easy to get wrong, and the cost of the error appears in the margin, not in the admin panel.

If you own an online store, you already know how important it is to attract and keep loyal customers. Coupons are a powerful tool for achieving both goals, as they give your customers incentives to shop at your store and make them feel valued for their loyalty. This guide explains the steps in the Adobe Commerce administration, one by one, and adds the business judgment that turns the steps into a promotion that earns its cost. It is written for executives who approve promotions and for the teams who configure them.

How do you create a coupon in Adobe Commerce, step by step?

The first step is to open the administrative panel and go to Marketing, Promotions, Cart Price Rules. Adobe's documentation on creating a cart price rule uses the same path and then asks for Add New Rule. A coupon in Adobe Commerce is not a separate object. It is a cart price rule that is configured to require a code, which is why everything below happens inside the rule form.

In the second step, enter the rule name, which is the name used to identify the coupon internally. In the example, the rule is called 15% discount, because the store will activate a 15% discount. Choose a name that tells a colleague, six months later, what the rule was for, who it was for and when it ran. Adobe describes the rule name as an internal reference, so it will not be shown to customers.

The third step is the description. The author adds a short description explaining why the coupon exists or how long it will be active, in the example the month of love and friendship, and states that it is shown to the customer at checkout. Adobe's documentation says that the description should state the rule's purpose and how it is used, while the text that appears in the order totals comes from the label fields at the bottom of the form, where a default label for all store views and store view specific labels can be set. In practice, use the description for the internal record and the labels for what the customer reads. The guide on creating and using CMS blocks in Adobe Commerce shows how to place promotional messages in the storefront itself.

The fourth step is to activate the rule. If the Active option is not set to yes, the coupon will not have any effect, and Adobe notes that leaving it as no is a way to prepare a rule without letting it take effect immediately. The fifth step is to choose the website. Select the specific website where the coupon should apply, or the main website if it should apply to all stores. The author adds a warning that is worth keeping: if the coupon applies to all stores, its description does not translate by itself, so for multilingual stores it is better to create two identical coupons with descriptions in the language of each website, each applied to its own store. Our article on the value and implementation of sites, stores and views in Adobe Commerce explains how that structure works.

The sixth step is the customer group. The coupon can go only to a specific group of customers or be general for all of them. Adobe adds a detail that matters for acquisition campaigns: leaving out the not logged in group limits the rule to registered customers. The seventh step is the coupon option. Select specific coupon if the discount should work with a defined code, and a new field called Coupon Code will appear, where the code that customers must type is entered. Adobe's documentation also lists an auto-generation option for creating many unique codes, which is the better choice when each recipient should receive a different code.

The eighth step is the usage limit per coupon, which refers to how many times the coupon can be used in the whole store. The author suggests entering a very large number when there is no limit. Adobe's documentation says that a blank field means no limit, so both approaches work, but a blank field is cleaner and clearer for the colleague who reviews the rule later. The ninth step is uses per customer. If the code is meant to be used only once by each customer, enter 1. Adobe clarifies that this limit applies to registered customers in the selected groups and does not apply to guests or shoppers who do not log in, which is a relevant fact for any store that allows guest checkout.

The tenth step is the date range. The From and To fields let the coupon have its own start and expiration, so nobody has to remember to deactivate it. Adobe notes that Magento Open Source works with dates only, so a coupon that should end at a specific hour cannot rely on this field alone. The eleventh step is the conditions section, which is optional. If no condition is added, the rule applies to all products. Conditions allow the coupon to apply only when the purchase is above a certain amount, or for a region, country, state or province, among others. Adobe lists cart attributes such as the subtotal, quantity, weight, payment method, shipping method and shipping destination, and product attributes when they have been enabled for promotion rules. The author did not add conditions in the example, and many first promotions are better off that way.

The twelfth step is the actions section. Select the option that applies a percentage discount on the price of the item and, in the discount amount field, enter the value, which in the example is 15 for 15%. Adobe describes other action types, such as a fixed amount per item, a fixed amount for the whole cart and buy X get Y free, together with options to apply the discount to shipping, to offer free shipping and to stop other rules from applying. Those options deserve attention, because they decide whether the coupon can be combined with other promotions.

The last step is to save the coupon and clear the cache from System, Cache Manager, Empty Cache, as the author recommends. Adobe's page on cart price rules does not document a cache step, and it adds that price rules are processed together with other system rules each night, so a new rule may take time to take effect and should be tested after saving. The prudent practice is to save, clear the cache if the store's procedures call for it, and then place a test order with the code on the real storefront before announcing anything. For the official reference on codes, Adobe's page on coupon codes goes deeper than this guide.

What does a coupon cost, and how should it be judged?

A coupon is a decision to give up margin in exchange for behavior. The behaviors a business wants are usually one of four: a first purchase, a larger basket, a faster decision or a return visit. Each one needs a different design. A first purchase code belongs to registered customers who have no orders. A larger basket code is tied to a minimum subtotal in the conditions. A faster decision code has an expiration date and a visible message. A return visit code goes to existing customers and is sent when their habits suggest they are drifting away.

The question for the executive is not whether the discount is attractive but what the business obtains per unit of discount. That requires three numbers agreed before the campaign starts: the maximum number of uses the company is willing to fund, the margin that remains after the discount on the products customers are likely to buy, and the metric that defines success, for example the share of coupon orders that come from customers who purchase again within a stated period. A promotion without those numbers is a bet that cannot be evaluated, which is a poor way to spend margin.

It also matters to know why shoppers leave without buying. Baymard Institute, a research firm on ecommerce usability, reports in its article on how to reduce cart abandonment that additional fees such as delivery charges and taxes are the leading cause, cited by 39% of shoppers in its survey, followed by slow delivery and forced account creation. The implication is that a discount is only one of several ways to recover a sale. If the cost shown at the end of checkout surprises people, a percentage code may be treating the symptom of a problem that free shipping thresholds or clearer pricing would solve for less.

How can a business keep coupons from eroding margin?

The first control is scope. A code limited by customer group, website, date and number of uses is far less likely to leak onto coupon websites than a general code with no expiry. The second control is stacking. Adobe's documentation explains that the Discard Subsequent Rules option prevents lower priority rules from applying to the same products, and that priority and this option work correctly only when each rule has a unique priority. A team that creates promotions without a priority convention will, sooner or later, see two discounts combine in a way nobody intended.

The third control is testing. Place orders as a guest, as a registered customer in each group and on each store view, with and without other promotions active. The fourth is a record: who requested the coupon, who approved it, what it was meant to achieve and when it should end. The fifth is review, after the campaign closes, of the actual redemptions against the plan. These controls take little time and are the difference between a promotion and a leak. The article on creating products in Magento 2 and Adobe Commerce is a useful companion, since the discount works on the products and attributes the catalog contains.

What are the trade-offs and risks?

The main risk is training customers to wait for discounts. A store that is always on promotion teaches its customers that the list price is not the real price, and its margin and brand suffer. The second risk is cannibalization: a coupon sent to all customers is used by many people who would have bought anyway. The third is operational, since errors in dates, websites or priorities create experiences that customer service must fix one order at a time. The fourth is compliance. Rules on promotions, price indications and consent for marketing messages vary by country, and the legal team should review campaigns that run across borders.

There is also a technical caution. The behavior of conditions, labels and processing times depends on the Adobe Commerce version and deployment, so the steps described here should be checked against the version your store runs and tested in a staging environment when the promotion is important.

What does this mean for the C-level?

For the chief commercial officer and the chief marketing officer, the coupon is a tool to be assigned to an objective, a segment and a budget, not a reflex. The questions to ask are who the code is for, what behavior it should create and how the result will be measured. For the chief financial officer, the relevant point is the cap: the maximum cost of the promotion should be known before launch and visible in the configuration through usage limits and dates.

For the chief customer officer, coupons are a way to recognize loyalty, as long as they are not the only one. A customer who feels valued for the service, the delivery and the relationship will not need a discount to return. For technology leaders, the discipline is governance: a naming convention, a priority convention, a test routine and an owner for each rule. Our practice in pricing and revenue works with leadership teams to connect these decisions with margin and growth targets.

How should a director start next week?

Ask the team to list all the cart price rules that are active today, with their dates, usage limits, customer groups and websites. In most stores this list produces surprises: rules that never expired, codes without limits and duplicates created for tests. Close what has no purpose and document what remains.

Then choose one coupon for the next campaign and define its objective, segment, cap and success metric on a single page before anyone opens the admin panel. Configure it following the steps above, test it as a guest and as a registered customer, and launch it to a part of the base. After the campaign, compare the results with the plan and keep the lessons. Repeat the cycle, and the promotion calendar becomes a source of knowledge about what your customers value.

How ICX helps

ICX Consulting helps commercial and technology teams design promotions that support growth without eroding margin. Our digital ecommerce for B2C practice covers the journey, the offer and the platform configuration in Adobe Commerce, and our team supports the design of rules, the testing routines and the measurement of results.

To define why customers choose you and which offers reinforce that reason, use the Value Proposition Toolkit. Are your promotions bringing customers who stay, or only customers who take the discount? Request a diagnostic with an ICX consultant.

Frequently asked questions

Where do you create a coupon in Adobe Commerce?

In the administrative panel, under Marketing, Promotions, Cart Price Rules, using Add New Rule. A coupon is a cart price rule that is set to require a specific code or to use auto generation of many codes.

Can a coupon be limited to one use per customer?

Yes. Enter 1 in the uses per customer field. Adobe's documentation notes that this limit applies to registered customers in the selected groups, so guest checkout needs a different control, such as a limit per coupon or a restriction to registered customers.

How do you make a coupon expire automatically?

Use the From and To dates in the rule. Magento Open Source works with dates only, so the coupon is valid for whole days. Test the end date on the storefront before relying on it.

Should the cache be cleared after saving a coupon?

The author recommends it, and many teams follow that practice. Adobe's page on cart price rules does not document a cache step and notes that rules are processed with the system's nightly routines, so always test the code on the live storefront after saving.

The best promotions are the ones the finance team approves in advance and the customer remembers with appreciation. If you want help turning your coupons into a growth tool, we would be glad to work with you.