StockSweep StockSweep | Help Center

Escalation Chains Explained

How staged, progressive discounting works — and the specific mistake this article exists to prevent on a chain's first run.

Last updated: September 22, 2026

Contents
Show all sections (10) ▼

An escalation chain is a specific automation rule type. Instead of one discount, it applies a ladder of stages as a product ages — for example 5% at 90 days, 7% at 180 days, 10% at 365 days. It shares the same safeguards as a standard rule — see Automation Rules & Safeguards. But the way it decides "what stage is this product at" is different, and that difference can cause a real mistake if you don't understand it first. This article exists to prevent that mistake.

Estimated time: 4 minutes

What you'll accomplish

  • Understand how a chain decides which stage a product is at
  • Know why a product never jumps backward, and rarely jumps two stages at once
  • Understand the one situation a chain treats differently on a product's first evaluation
  • Know the plan and configuration requirements before creating one

Requirements

  • Plan: Pro or Enterprise. Escalation chains are not available on Free or Growth.
  • Stages: a chain needs 2 to 5 stages. Consecutive stages must be at least 7 days apart, and their trigger-day thresholds must be strictly ascending (stage 2 cannot trigger sooner than stage 1).
  • Create one from Automation → Escalation Chains → Create escalation chain, or as the "Escalation Chain" rule type from Automation → Rules → Create rule.

How stage progression works

Every product a chain has ever acted on keeps a record of the highest stage it has reached. On each run, the chain recalculates which stage the product currently qualifies for, based on its measured days-without-sale. It only acts if that is higher than the stage already on record:

  • Advance-only. A chain never reverts a product to an earlier stage, and it never re-fires a stage it has already reached. This is what stops a nightly run from re-applying the same discount and drifting the price further each time.
  • Skip-jump, target-only. A product can cross two thresholds between runs — for example, it was never evaluated until it was already past both the 90-day and 180-day marks. When that happens, the chain applies only the stage it currently qualifies for, never the intermediate ones it jumped over.
  • Anti-compounding. Each stage's discount percentage is calculated from the product's original price, not from the price after the previous stage's discount. Stage 2's "7%" always means 7% off the original ticket price, not 7% on top of stage 1. Discounts never compound into something deeper than you configured.

The first-evaluation case

A product with no sale on record at all (never sold, not just slow) is a special case. Without a real last-sale date, there is no way to measure "how many days without a sale" honestly. Treating "no data" as "maximum age" is a mistake this exact mechanism has caused in production before. A never-sold item entering a chain for the first time landed on the deepest configured stage immediately, instead of walking up the ladder the merchant configured — the discount was reverted within hours once noticed.

To prevent that, a product with no sales on record that is evaluated by a chain for the first time is always started at stage 1. This holds regardless of how the age math would otherwise place it. Once it has a history row (it has been evaluated at least once), normal advance-only progression applies from there. This clamp only affects a product's very first evaluation.

FAQ

Can I edit a chain's stages after it's created and running?

Yes, but changing thresholds or adding/removing stages changes what "current stage" means for products already partway up the ladder — review the Escalation Chains list after an edit to confirm existing progress reads the way you expect.

Does a chain respect my margin floor and the 90% discount ceiling?

Yes — every stage's discount goes through the same margin-protection check and the same system-wide 90% absolute ceiling as a standard rule's discount action. See Automation Rules & Safeguards.

What's the minimum gap I can set between stages?

7 days, system-wide. This isn't a per-chain setting — it's a floor on how close together two stages can trigger, so a chain can never functionally collapse into "apply both discounts at once."

Why is my chain's product count so much lower than my Dead Stock count?

A chain only acts on products matching its own conditions and only advances a product when it actually reaches a new stage. A product sitting at stage 1 without yet reaching stage 2's threshold is correctly "not due" — it isn't skipped, it just hasn't aged into the next stage yet.