Every price change carries an operational cost: it needs approval, your point-of-sale systems need updating, and price tags may need reprinting. A €0.15 change on a €45 product is rarely worth that effort. The minimum price change threshold is a Dynamic Pricing setting that filters out these tiny, not-worth-it changes before they reach you.
How it works
You set a threshold as a percentage, for example 2%. When the system calculates a suggested price, it compares the size of the change against your threshold:
If the suggested change is between 0% and 2% of the current price, it's discarded, and the product keeps its current price.
A change of exactly 0% (no change) is kept.
A change above the threshold is kept.
In other words, only changes big enough to matter make it through to your review.
How it differs from safeguards
It's easy to confuse this with safeguards, but they do different jobs. A safeguard caps a price at a certain boundary, a floor or a ceiling. The minimum price change threshold doesn't cap anything; it looks at the size of the change relative to the current price and decides whether the change is even worth suggesting. A change that passes the threshold is still subject to your safeguards afterwards.
When to use it
This setting is most valuable for merchants with large catalogues, where approving hundreds of trivial changes each run would be overwhelming. A 1–2% threshold is a good starting point: it clears out the noise while still surfacing every change substantial enough to be worth acting on.
If you ever notice that a product didn't change even though your actions should have moved it, a minimum change threshold is one of the first things to check: the change may simply have fallen below your threshold and been reverted to the current price. See also Dynamic Pricing: Common Customer Questions.