Set pricing policies & guardrails
Tell MarginTide what "acceptable" looks like for your business once, and every recommendation arrives already checked against it.
What you get
- A margin floor and MAP rule every suggestion has to respect
- Control over how fast prices are allowed to move, and how they round
- Per-tag alert thresholds, so a volatile category can speak up sooner than the rest of your catalog
Pricing policies
Under Settings → Policies you define the rules MarginTide must respect when it suggests a price change: a minimum margin percentage, a margin-squeeze rise threshold, whether MAP is enforced, a price floor, how much a price may move in a day, the rounding rule, and your repricing strategy (including the undercut amount and offer-selection policy). Suggestions that would break a policy don't get silently applied — you stay in control of the boundaries while MarginTide does the watching.
Alert thresholds
Not every price movement deserves your attention. Threshold settings on the same page control how big a change has to be before it becomes an alert, and you can override the workspace default for specific product tags — so a volatile category can alert on smaller moves than the rest of your catalog.
How they work together
Policies shape what MarginTide may suggest; thresholds tune when you hear about a change. Together they turn a stream of raw price movements into a short list of decisions worth your time in the Action Center. Set policies before you connect a write-back integration — the guardrails apply whether a recommendation is applied by hand or pushed automatically, so getting them right up front means every suggestion, in every channel, already respects your rules.
Go further
- See what needs attention — where policy-respecting suggestions land.
- Get alerts when prices move — how alerts reach you once thresholds are set.
- Run a check & read a recommendation — where a policy first gets applied.
- Push accepted prices to your store — guardrails still apply when write-back is on.