Planning often means reviewing the same kinds of small Min/Max changes day after day — a 1-unit bump on a fast mover, a monthly A-class refresh, a C-item that barely moved. Auto Min/Max lets you encode which items Recurrency can accept for you, then handles the export overnight.
A new rule category, Min/Max Automation, selects the item-locations that should auto-accept
Matching items in Needs Review are exported to your ERP on the nightly run
A nightly cap keeps each run bounded; leftover items roll to the next night
Settings → Export Jobs → Automated Exports shows what ran, what changed, and what failed
💡 Auto Min/Max only applies Recurrency’s recommended Min/Max. It does not invent new values.
How Auto Min/Max Works
Auto Min/Max has two parts: which items and the nightly export.
1. Item selection (Min/Max Automation rules)
You choose the set of item-locations Recurrency is allowed to auto-accept by putting one or more rules in the Min/Max Automation category.
Rules in this category work like other Recurrency rules: they run nightly and return a list of item-location pairs. Unlike Planning Filters or Daily Workflow, a Min/Max Automation rule does not just flag items for review — it authorizes Recurrency to accept the current recommended Min/Max for those pairs.
You can use more than one Min/Max Automation rule. If two rules select the same item, there is no conflict: both are accepting the same recommended Min/Max.
Common starting points:
Small changes. Auto-accept when Min and Max are moving by a small amount (for example ±10% or ±2 units). Many teams exclude anything going to or from zero so those still get a human look.
Trusted segments. Auto-accept low-cost or high-velocity items.
Anything you already bulk-approve today. If a Planning filter or Daily Workflow bucket is “select all → accept,” it is a good candidate to move into Min/Max Automation.
⚠️ Min/Max Automation is not the same as an Overrides rule. Overrides change Recurrency’s recommended Min/Max. Auto Min/Max accepts the recommendation that is already on the item and writes it to your ERP.
2. Nightly export
After the nightly rule run finishes — including any recommended Min/Max overrides — Recurrency:
Collects item-locations from all deployed Min/Max Automation rules
Keeps only pairs that are in Needs Review and actually need an export (Excluded, Flagged, and OK are skipped)
Sorts by largest change first (a jump from 0 → 20 is exported before 1 → 2)
Exports up to your nightly limit using async Min/Max export
Defers anything over the cap to the next night
Because Min/Max values typically do not change every day, each night tends to export a different set of items. After the first catch-up, volume usually drops to whatever newly entered Needs Review.
⚠️ The current nightly limit is 100 items. Any items left over will be processed the following night.
How to Get Started
Auto Min/Max is enabled with your Customer Success Manager. Today, Recurrency deploys the Min/Max Automation rules for you — the same way custom rules are set up.
Decide what Recurrency can auto-accept. Start narrow (small % changes, a single supplier, A-class only) and expand once you trust the run history.
Reach out to your CSM with the criteria. If you already have a “small changes / bulk approval” rule, we can recategorize it to Min/Max Automation.
Recurrency turns Auto Min/Max on for your instance, deploys the rule(s), and sets a nightly limit.
The first nights may catch up on a backlog. After that, only new Needs Review items in the rule are exported.
Check Settings → Export Jobs → Automated Exports the next morning to confirm what ran.
Want something custom? Share the criteria with your CSM (example: “Auto-accept Needs Review items where Min and Max both change by 10% or less, excluding anything going to or from 0”). We’ll evaluate it and set it up.
Reviewing What Ran Last Night
Go to Settings → Export Jobs, then open the Automated Exports tab.
You’ll see:
Recent runs — a bar chart of nightly runs. Green = success, red = at least one batch in the run failed.
Last run — item-locations exported, items not applied (deferred past the nightly cap), duration, and run status.
Largest changes — the biggest Min/Max moves from that run (current → new). Click through to view every change, searchable by item or location.
Run history table — Run ID, status, started time, duration, item-locations, batches exported, and batches failed.
Exports are chunked into batches so a failure is isolated to a batch, not the entire night. Failed batches show in red on the chart and in the table so you can retry or inspect.
You can also filter Planning by the Min/Max Automation rule to see which item-locations are in the auto-accept set.
What Auto Min/Max Does Not Do
It does not auto-accept Excluded, Flagged, or OK items.
It does not override a value you set by hand in Planning. It only accepts Recurrency’s current recommendation.
It does not replace Daily Workflow or Planning review. High-impact, volatile, or policy-sensitive items should stay in those workflows.
Best Practices
Start small. A tight small-change rule plus a low nightly cap is easier to trust than auto-accepting the whole catalog on night one.
Keep a human queue. Leave large deltas, new items, and anything going to or from zero in Needs Review / Daily Workflow.
Watch the first week. Use Automated Exports to confirm volumes, largest changes, and any failed batches before widening the rule.
One purpose per rule. Use Min/Max Automation for “Recurrency may accept these.” Use Daily Workflow for “a person should look at these.” Use Overrides only when you want to change the recommendation itself.
FAQs
Q: Can I turn Auto Min/Max on for a single item?
A: Not today. Selection is by rule — any item-location the rule returns (and that is in Needs Review) is eligible.
Q: What if two Min/Max Automation rules select the same item?
A: That’s fine. Both are accepting the same recommended Min/Max, so there is no override conflict.
Q: Why didn’t all of my rule’s items export last night?
A: Only Needs Review items that actually need an export are counted. The rest may be Excluded, Flagged, or already OK. Anything still pending may have been over the nightly cap and will go out on a later night (largest changes first).
Q: Can I undo last night’s run?
A: Auto Min/Max writes the same Min/Max export as a manual accept from Planning. Use Audit Logs and Automated Exports to see what changed. To revert, update those items in Planning (individually or via bulk/CSV) and export the values you want.
Q: Will this hammer the same items every night?
A: Only if recommended Min/Max keeps changing by enough to put the item back in Needs Review. After a successful export, the item typically moves to OK until the recommendation moves again past your review threshold.
Q: Who can create a Min/Max Automation rule?
A: Same as other custom rules today — your Recurrency CSM deploys them with you. Once deployed, anyone can filter Planning by the rule and anyone with access to Export Jobs can review Automated Exports.