The Shopify markdown campaign checklist: before, during, and after

Before launch

Scope and data

• List exact product and variant IDs.
• Confirm every variant is active and available in intended channels and markets.
• Capture current Price and Compare-at price values.
• Confirm currency and rounding behavior.
• Validate cost or internal floor data.
• Exclude new products without enough evidence.

Campaign logic

• State the business goal in measurable terms.
• Set a start date, review cadence, and hard end date.
• Calculate every step from the captured original price.
• Set an absolute effective-price floor.
• Set a maximum discount.
• Decide whether the final price holds or restores.
• Define what a manual merchant price change does.

Customer experience

• Test product and collection page sale presentation.
• Switch between participating and nonparticipating variants.
• Test cart and checkout with realistic quantities.
• Review active product, order, and shipping discount combinations.
• Verify relevant markets, currencies, devices, and sales channels.
• Make campaign terms understandable.

During the campaign

• Re-read the current database and Shopify price before each mutation.
• Check the campaign goal before escalating.
• Recalculate the proposed effective price.
• Refuse zero or negative prices.
• Enforce floor and cap in a fixed order.
• Pause on conflicting manual changes.
• Record the before value, after value, reason, and request identity.
• Make retries safe so the same job cannot double-apply a step.

At every review

Ask:

1. Did the campaign meet the unit or pace goal?
2. Was there enough relevant exposure to interpret the result?
3. Did another promotion or merchandising change affect the period?
4. Does the next price remain safe after rounding and combinations?
5. Has the product, cost, deadline, or merchant intent changed?

At campaign end

• Stop future scheduled jobs.
• Hold or restore the price according to the explicit end rule.
• Do not overwrite a newer manual price.
• Confirm storefront presentation after the final write.
• Record units sold, elapsed time, price history, and remaining quantity.
• Feed the result into buying and assortment review.

Language for reporting

Report “units sold while the product was priced at $X,” not “the discount generated X sales,” unless the measurement design supports a causal claim. A controlled operational history is valuable even when it is not an experiment.

Why this checklist is strict

A price mutation affects real merchant money. Safe automation requires locking, idempotency, guard checks against the effective price, an immutable record, and a reversible path. If a campaign cannot satisfy all five, it is not ready to automate.