From Discounts to Intelligent Commerce
Running promotions as a governed process: a campaign register, interaction rules from your real tools, margin checks, and a measurement routine
A promotion operating system is a way of running promotions, not a product: a campaign register with owners, goals, and stop rules; interaction rules taken from the tools you use; a margin check before launch; and reviews against a baseline. Discount Prime is one component; POS, subscriptions, marketplaces, Shopify B2B companies, and minimum order quantities stay with other tools.
At a glance
- Challenge
- Promotions run as disconnected events with no owner for the whole picture: nobody knows which offers are live, how they interact, or whether they earned their cost.
- Approach
- A campaign register with goals and stop rules, written interaction rules, a pre-launch margin check, clear tool boundaries (POS, subscriptions, B2B companies), and weekly and monthly reviews.
- Discount Prime campaign types used
- Full campaign portfolioProfit analyticsConflict management
Scenario-based case study: the merchant is fictional and modeled on patterns across Discount Prime stores. Prices, costs and outcome figures are illustrative assumptions for teaching, not measured results from a real store.
Short Answer
A "promotion operating system" is not a product you install. It is a way of running promotions: one register of every live offer with an owner, a goal, and an end date; written rules for how offers interact in the tools you actually use; a margin check before launch; and a measurement routine that compares results with a baseline. A discount app is one component. Discount Prime covers many campaign types, its own overlap rules, and campaign-level profit reporting on Shopify. It does not cover point-of-sale pricing, subscriptions, marketplaces, Shopify B2B companies, or minimum order quantities, so those stay with native Shopify or other tools.
Merchant Scenario
Everlane Collective is a fictional retailer with several brands, multiple Shopify Markets, retail and wholesale customers, physical stores, marketplace listings, and a loyalty program. Each team sees a different symptom:
| Team | Symptom |
|---|---|
| Marketing | Wants more campaigns to hit targets |
| Finance | Sees discounts eating margin |
| Operations | Clearance does not move fast enough |
| Loyalty | Members want exclusive offers |
| Technology | Nobody can explain why a product sold at a given price |
The problem is not a missing discount type. Nobody owns the full picture of which offers are live, how they interact, and whether they earned their cost.
Stages of Promotion Maturity
| Stage | What it looks like | What to add next |
|---|---|---|
| 1. Store-wide discounting | One code or one sale | A margin check before every sale |
| 2. Category promotions | Different offers per collection | Exclusions written down; a campaign register |
| 3. Customer segmentation | VIP, wholesale, first-order offers | Clear rules for who is logged in and how segments are maintained |
| 4. Behavioral offers | Bundles, spend thresholds, free shipping, quantity tiers | Before/after-discount settings documented per campaign |
| 5. Promotion architecture | Many concurrent campaigns | Overlap rules from your tools, a launch order, pre-launch tests |
| 6. Operating model | Promotions governed like any other business process | Owners, a calendar, a review routine, and a stop rule for every campaign |
Many merchants do not need stage 6. A store with a few campaigns a year is well served by a register and a margin check. The model earns its overhead when many people launch offers across many products.
The Operating Model
1. A campaign register
One shared table, updated at every launch:
| Field | Example |
|---|---|
| Campaign and tool | "Winter clearance", Discount Prime Flat Product Discount |
| Goal and metric | Clear 1,200 units of last season's outerwear; units sold |
| Products and customers | Outerwear (last season), all customers |
| Settings that change price | 30% off; combines with free shipping |
| Owner | Merchandising lead |
| Dates and stop rule | Ends on its end date or when stock falls below a set level |
2. Interaction rules from your actual tools
Write down how overlaps resolve, from the tools, not from intent. For Discount Prime:
- there is no priority setting;
- each variant belongs to one price-changing campaign at a time, and the campaign already holding it keeps it until you move it in the conflict resolver;
- if several Tiered Spend (order) campaigns qualify, the smallest discount applies; for shipping, the largest applies;
- bundles, cross-sell, gifts, and upsells either take the better of their saving and the product discount, or add to it, depending on the campaign's setting;
- Discount Prime discounts are set to combine with Shopify's native discounts, so check native discounts too.
For native Shopify discounts, record each discount's combination settings. See Enterprise Promotion Architecture for a worked example of these rules across twelve requirements.
3. A margin check before launch
Cost-based floors exist in Discount Prime only for Wholesale / B2B Pricing, Dropshipping Pricing, and Product Bundles, and only where Shopify has a unit cost. For other types, check each product before launch: to keep a gross margin floor f after a discount d, the product's list-price gross margin must be at least d + f × (1 − d). With a 40% floor and 30% off, that is 30% + 40% × 70% = 58%. Products below that either get a smaller discount, are excluded, or are accepted knowingly.
4. Know where each requirement lives
| Requirement | Where it is handled |
|---|---|
| Product, quantity, spend, bundle, gift, cross-sell, upsell, shipping offers in the online store | Discount Prime or native Shopify discounts |
| Segment- or login-based pricing (VIP, wholesale via segments) | Discount Prime campaigns with customer eligibility |
| Company-specific contract prices (Shopify Plus B2B companies and catalogs) | Native Shopify B2B; Discount Prime does not read companies |
| In-store (POS) pricing | Shopify POS and its own discounts; Discount Prime has no POS-specific logic, so test in POS before assuming how its campaigns behave there |
| Subscription pricing | Your subscription app; Discount Prime has no selling-plan logic |
| Minimum order quantities | A dedicated tool; Discount Prime tiers set minimums for a discount, not for checkout |
| Marketplace prices | The marketplace channel's own tools |
| Market- or country-specific offers | Discount Prime shipping campaigns only; test other offers in each currency |
| Plan limits on campaign types and live variants | Check the pricing page |
5. A measurement routine
- Weekly: each campaign's Estimated Profit next to revenue in Discount Prime analytics (revenue after discounts minus Shopify product cost and shipping subsidy; refunds not subtracted), margin colors, and lines missing cost.
- Monthly: gross profit per order and units sold against a baseline period, adjusted for refunds; campaign-level results against each campaign's goal.
- Per campaign: a stop rule decided before launch, for example "end if gross margin on campaign orders stays below the floor for two weekly reviews after cost data is complete".
- For bigger decisions: a holdout (a period, region, or customer group without the offer) where you can run one, because before/after comparisons mix in season, traffic, and other campaigns.
What This Looks Like for Everlane
| Problem | Operating-model answer |
|---|---|
| Marketing wants more campaigns | Every new campaign enters the register with a goal, an owner, and a stop rule |
| Finance sees margin erosion | Margin check before launch; weekly review of campaign margin colors |
| Clearance is slow | A clearance campaign with a units-sold target and a planned depth change if it misses |
| Loyalty wants exclusives | VIP-only campaigns on a segment, with login required, listed in the register |
| Nobody can explain a price | Interaction rules written down; the order breakdown in Discount Prime analytics shows which campaign applied |
Everlane's stores, marketplace listings, and subscriptions keep their own pricing tools. The register lists them too, so the whole team sees every live offer in one place even though no single tool runs them all.
Pre-Launch Checklist for Any Campaign
| Check | Pass condition |
|---|---|
| Register entry complete | Goal, metric, owner, dates, stop rule filled in |
| Overlaps reviewed | No unexpected "Products excluded due to conflicts" |
| Margin check | Every product above the floor, or exceptions approved |
| Test carts | Below, at, and above each threshold behave as intended |
| Native discounts | Combination settings checked against the new campaign |
| Currencies | Thresholds tested in each market's currency where relevant |
Common Mistakes
- Expecting one app to govern prices across online store, POS, subscriptions, and marketplaces.
- Writing a priority list that none of the tools enforces.
- Launching without a stop rule, so campaigns outlive their purpose.
- Reading attributed results as incremental without a baseline or holdout.
- Assuming every campaign type enforces a margin floor.
Frequently asked questions
What is a promotion operating system?
A way of governing promotions: every live offer is listed with an owner, goal, metric, dates, and stop rule; how offers interact is written down from the actual tools; each campaign passes a margin check and test carts before launch; and results are reviewed against a baseline. It is a process supported by tools, not a single app.
Does my store need this level of process?
Not always. A store running a few campaigns a year is well served by a simple register and a margin check. The full model earns its overhead when many people launch offers across many products, customer groups, or markets and nobody can explain why a product sold at a given price.
Why do my Shopify discounts keep conflicting with each other?
Usually because nobody wrote down how the tools resolve overlaps. In Discount Prime there is no priority setting, each variant belongs to one price-changing campaign at a time, several qualifying order-level campaigns resolve to the smallest discount, and its discounts combine with native Shopify discounts. Record these rules and each native discount's combination settings before launching.
Which pricing needs does Discount Prime not cover?
It has no POS-specific logic, no subscription (selling plan) logic, no Shopify B2B company or catalog support, and no minimum order quantity enforcement, and it does not manage marketplace prices. Only its shipping campaigns target markets or countries. Keep those needs in native Shopify or dedicated tools and list them in the same campaign register.
What should I measure instead of discount usage?
Gross profit per order and units sold against each campaign's goal, compared with a baseline period or a holdout, and adjusted for refunds. Discount Prime's analytics give a weekly campaign view (Estimated Profit after discounts, product cost, and shipping subsidy), but they do not subtract refunds and show attributed, not incremental, results.
Go deeper
Features used
From the blog
Setup guides
Run this architecture in your store
Every campaign type in this case study is included in Discount Prime, with profit analytics to verify the margin impact.