Adobe Commerce Price Rules and Your Inventory System

A discount looks like the simplest lever in retail. A percentage comes off a price, a banner goes up, and sales rise. Anyone who has run a promotion on a growing online store knows the reality is less tidy. The same discount that fills the cart can empty a shelf, collide with another offer, or leave a customer staring at a product the warehouse can no longer deliver.

Pricing rules sit at the point where marketing ambition meets operational reality. In Adobe Commerce (the platform formerly known as Magento) they let a merchant describe a promotion once, attach conditions to it, and let the store apply it automatically or through a coupon. Done well, they attract new customers and encourage existing ones to add a second or third product to the basket. Done carelessly, they stack in ways nobody intended and promise stock that does not exist.

This article walks through the two families of price rules, the conditions that make them precise, the priority logic that keeps them from fighting each other, and the often neglected link between promotions and your inventory system. Along the way it uses the practical examples our team has built for clients, expressed in Costa Rican colones where the original scenario called for it.

Why price rules deserve executive attention

It is tempting to leave promotions to whoever happens to own the campaign calendar. That works until the first Black Friday, when a store with a dozen overlapping offers discovers that its margin on a best-selling product has quietly disappeared. A price rule is a commercial commitment executed by software, and software applies commitments literally. If two rules both qualify, the system needs to know which one wins. If a rule says every product is eligible, it means every product, including the ones you were hoping to protect.

Three questions help frame the conversation before anyone opens the admin panel. What behavior are we trying to change, for example a first purchase, a larger basket, or the clearance of aging stock? Which customers should see the offer, everyone or a defined group? And can the business actually fulfill the demand the offer will create? The first two are marketing questions. The third is where inventory enters, and we return to it later in the article because it is the question that most often gets skipped.

Adobe Commerce handles promotions in two places, both found under Marketing > Promotions in the admin. Catalog price rules change what a product costs before anyone adds it to a cart. Cart price rules act on the shopping cart itself, once the customer has chosen what to buy. Understanding which of the two fits a given objective is the foundation for everything else.

Catalog rules change the price before the cart

A catalog price rule modifies the price a shopper sees on the category page and the product page. Because it is applied before the product reaches the cart, the discounted figure simply becomes the new price of the product in the storefront. There is no coupon to enter and no extra step for the customer, which makes catalog rules the natural tool for visible, always-on offers, seasonal sales, and loyalty pricing for known groups.

According to Adobe's documentation on creating catalog price rules, a rule can reduce the price as a percentage of the original, as a fixed amount, or by adjusting the final price to a specific percentage or value. That flexibility covers most of the scenarios a merchant needs. Typical examples include a 10 percent discount across the entire store, a 10 percent discount limited to certain categories, a 20 percent discount on a list of specific SKUs, a 29 percent discount reserved for the customer group called Employees, and a Black Friday offer that takes 2,000 colones off every product in the shop.

The first of those examples shows how simple the mechanics can be. In the walkthrough below, a single rule applies a 10 percent discount to everything in the store.

Narrowing the same discount to a single category requires only a condition. The second walkthrough shows a 10 percent discount that applies to products in category A and leaves the rest of the catalog untouched.

Fixed-amount rules behave differently, and they are the right choice when the offer is easier to communicate in currency than in percentages. The third walkthrough covers the Black Friday case, where every product receives the same fixed reduction.

A fixed discount deserves a note of caution. A reduction of 2,000 colones is generous on a 10,000 colones product and ruinous on a 2,500 colones accessory. Before launching a store-wide fixed amount, check the lowest-priced items in the catalog and decide whether they should be excluded by a condition.

Conditions decide who and what a rule touches

A rule without conditions is a rule about everything. Adobe is explicit on this point: when the conditions section is left blank, the rule applies to all products. That is convenient for a store-wide sale and dangerous for anything more selective, so the first discipline of promotion design is to add a condition deliberately, not to remove one by accident.

For catalog rules, conditions can be built on categories, product attributes, attribute sets and SKUs, and they can be combined so that a product qualifies only when all of them, or any of them, are met. This is what makes it possible to run a 20 percent offer on a handpicked list of SKUs while the rest of the shop stays at full price. It also allows more strategic scenarios, such as discounting a particular brand or a specific product line during its launch window.

Who sees the price matters as much as what it applies to. Rules can be limited to customer groups and to specific websites, which is how a store gives employees, wholesale buyers or loyalty members their own pricing without exposing it to anonymous visitors. Dates complete the picture. A start and end date let a campaign switch itself on and off, which protects the business from the classic failure of a Monday morning discovery that last weekend's sale is still running.

Cart rules shape the basket

If catalog rules are about price, cart rules are about behavior. They apply after products have been added to the cart and can take the entire basket into account, including the subtotal after other discounts. Adobe's guide to cart price rules describes three ways to deliver them: with no coupon, so the discount applies automatically when the conditions are met; with a specific coupon code; or with auto-generated coupons, which are useful for personalized campaigns. Usage limits can restrict how often a coupon is redeemed overall and by each customer.

The actions available are broader than most merchants expect. A rule can take a percentage off the product price, subtract a fixed amount from selected items, subtract a fixed amount from the whole cart, or apply a buy X get Y logic that gives free units once a threshold is reached. Adobe Commerce, as opposed to the open source edition, also supports a free gift action.

The scenarios our team builds most often fall into a few patterns. A 10 percent welcome discount for customers who create an account turns a visit into a registered contact. A 10 percent discount for products in a given category, applied without a coupon, rewards customers for browsing a section the merchant wants to promote. A 5 percent offer on selected products, unlocked by a 5 percent coupon code, suits email campaigns where the code identifies the audience. A 10 percent benefit for the VIP customer group recognizes the best customers without a visible banner for everyone else.

The more inventive patterns deal with the basket as a whole. A 5,000 colones discount on the entire cart, triggered when a specific product is included, works as a bundle incentive: the anchor product pulls other purchases with it. A 2,000 colones discount on a product limited to two units, with the third unit sold at the regular price, controls exposure on a lead item. And the classic buy 10, get 1 free rewards volume purchases, which makes it particularly relevant to B2B buyers who order in quantity.

Conditions for cart rules go well beyond products. A cart rule can evaluate the subtotal, the quantity of items, the total weight of the order, the payment method, the shipping method and the shipping address. It can also look at the customer's history, such as the number of orders placed, the average order amount, the total amount spent, and the status of those orders. Customer attributes open further possibilities: the date the customer account was created or updated, first and last name, email, and the date of birth, which supports birthday campaigns that trigger on the day, within the month, or within one or two weeks of the occasion.

These conditions turn a promotion from a blunt instrument into a targeted one. A free shipping offer for orders above a threshold can be limited to a particular carrier. A discount on cash on delivery orders can be removed when the merchant wants to steer customers toward card payments. A welcome offer can be restricted to customers with zero previous orders, so that it truly serves acquisition and not just a reshuffling of existing buyers. For a deeper look at one popular pattern, see our guide to applying cart rules to give free shipping to your customers, and our introduction to Adobe Commerce coupons.

Priority and discarding subsequent rules

With several active rules, the store needs a way to decide which one applies first, and whether the others may still apply afterward. Left unmanaged, a product can qualify for two or three discounts at once, and the customer receives a price the merchant never intended to offer. Adobe Commerce solves this with two settings on every rule: a priority and an option to discard subsequent rules.

Priority is a number, and the lowest number carries the highest priority. A rule set to 0 is evaluated before a rule set to 1, which is evaluated before a rule set to 2, and so on. Adobe also notes that rules sharing the same priority do not combine, so assigning distinct priorities is the safest habit. When a rule has its discard subsequent rules option set to Yes, no lower-priority rule is applied to a product that has already matched it. That is the mechanism for preventing stacking.

A concrete example makes the logic clear. Suppose a merchant wants every product in the catalog discounted by 20 percent, while a chosen set of products receives a deeper 50 percent discount. The two rules are configured as follows.

• Rule one is the 50 percent promotion. It has priority 0, a condition that identifies the selected products, an action that applies a 50 percent discount, and discard subsequent rules set to Yes.
• Rule two is the 20 percent promotion. It has priority 1, no conditions so that it covers the whole catalog, and an action that applies a 20 percent discount.

When a product belongs to the selected set, rule one is evaluated first because it has the higher priority. It applies the 50 percent discount and, because it discards subsequent rules, the 20 percent promotion never touches that product. Every other product misses the condition of rule one and falls through to rule two, so it receives the standard 20 percent. The result is exactly what the merchant planned, with no accidental combination into a 60 percent price.

The opposite design is just as legitimate. If a merchant wants discounts to accumulate, leaving discard subsequent rules at No allows rules to stack. The point is not that stacking is wrong, but that it should be a decision. Many stores adopt a simple convention, with exclusive rules for customer-specific pricing at the top, then seasonal campaigns, then the general store-wide offer at the bottom.

Where promotions meet your inventory system

Everything above describes how a price is calculated. None of it says whether the product can be shipped. That is the gap where promotions most often hurt a business, and it is the reason this topic belongs in any conversation about integrating a store with an inventory system.

Consider what a successful promotion does. It concentrates demand on a small number of products in a short window. A store that runs a 50 percent offer on a selected list of SKUs is, in effect, forecasting that those items will move quickly. If the inventory system does not share the same view of availability, the store can sell units that are already committed elsewhere, cancel orders after payment, and spend the following week apologizing. The discount that was supposed to build loyalty ends up eroding it.

Adobe Commerce addresses availability through Multi-Source Inventory, described in the Adobe inventory management introduction. In this model, stock is held in sources, which can be warehouses, stores or a drop-ship supplier, and sources are assigned to stocks that serve specific sales channels. The figure the shopper cares about is the salable quantity, which reflects what can actually be promised after pending orders are taken into account. For a merchant, the practical consequence is straightforward. A promotion should be planned against salable quantity, not against the raw count of units on a shelf.

When the store is connected to an external system, such as an ERP or a warehouse management platform, the integration becomes the guardian of that number. The questions to settle are operational. How often does stock synchronize, in real time, every few minutes, or nightly? Which system owns the truth when the two disagree? What happens to a promotion when the integration fails and the data goes stale? A nightly sync that is perfectly acceptable for a slow-moving catalog becomes a liability on the day a flash offer drives a week of sales in an hour.

The same logic applies to the promotional calendar. Stock that is reserved for a campaign should be visible to both systems, so that a sales team taking phone orders does not consume the units the website has already advertised. Our article on the key integrations in your ecommerce covers how inventory, payments and logistics connect, and our piece on saving money in inventory management looks at the cost side of carrying the right stock.

There is also a pricing question hiding in the data. If the inventory system knows that a product is overstocked, that is a signal to promote it. If it shows scarcity, the same signal says to protect the price. Connecting the two turns promotions from calendar-driven events into decisions informed by stock position. That is the territory of dynamic pricing, which we cover in dynamic pricing in ecommerce, and of our pricing and revenue consulting practice.

A working routine for safe promotions

The merchants who run promotions with the fewest surprises tend to share a routine, and it is neither elaborate nor expensive. It starts with a written definition of the objective and the expected volume, so that the operations team knows what to prepare. It continues with a review of the rule configuration by someone who did not build it, checking the conditions, the priority and the discard setting against the intended outcome. A test on the staging environment follows, using real customer groups and a sample of the products involved, with a close look at the final price in the cart and at checkout.

Before the launch, the team compares expected demand with salable quantity and decides what happens when stock runs out. Some merchants let the offer end with the stock, others pause the rule, and others redirect shoppers to a similar product. During the campaign, someone watches orders, stock and margin together, because any one of them can drift. Afterward, a short review records what the promotion actually delivered in revenue, margin and returning customers, and feeds the next plan.

It also helps to keep the rule inventory tidy. Rules created for campaigns that ended two years ago do not disappear, and an expired condition can interact with a new one in surprising ways. A quarterly cleanup of inactive and overlapping rules is among the cheapest forms of risk management in a store. Our guide to creating a catalog price rule in Adobe Commerce provides the step-by-step view for teams who want to practice before going live.

Promotions as part of a wider commercial design

Promotions are most effective when they sit inside a coherent commercial model. A store that discounts constantly trains its customers to wait for the next offer. A store that uses targeted rules, such as a welcome benefit, a loyalty tier, a volume incentive for business buyers, and occasional store-wide events, builds a pricing architecture customers can understand. Each rule has a purpose, an audience and an end date, and each can be measured.

That architecture also makes the customer experience better. Shoppers notice when prices behave consistently, when a coupon works as promised, and when an advertised product arrives on the date they were given. Those small moments of reliability build the kind of trust that no discount can buy. This is why we encourage teams to treat price rules, stock availability and fulfillment as one system rather than three separate projects. Our ecommerce work for B2C companies and our Adobe Commerce practice start from precisely that view.

The tools to do this are already in the platform. Catalog rules for visible prices, cart rules for basket behavior, conditions for precision, priorities for order, and an inventory model that tells the truth about what can be sold. What remains is the discipline to use them together, and the willingness to design a promotion as an operation and not just as a message.

If you are planning a campaign or reviewing how your promotions connect to your stock, our digital transformation toolkit offers frameworks to structure the work. When you want an experienced second opinion on your rules and integrations, request a diagnostic with an ICX consultant and we will review them with you.