> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lanternhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set auto-approval rules

> Understand which changes auto-approve, set your personal buyer rules, or configure company defaults and targeted policies as a Lantern admin.

After you have reviewed a supplier or product group, you should not need to
repeat the entire review for every small change. Auto-approval lets qualifying
target changes pass within limits your team chooses, leaving changes outside
those limits for a buyer to inspect.

Use a default policy for routine changes and targeted rules for business areas
that need different tolerances or manual review. Your first manual approval
establishes the reference used by ordinary tolerance checks; unchanged accepted
targets remain approved.

For example, you can use tighter limits for one supplier at one location,
or require manual approval for that combination while other items keep using
the default policy.

* **Buyers:** [review your approvals and set personal rules](#for-buyers-review-approvals-and-set-my-rules)
  where **My rules** is available. Ask your Lantern admin for company-wide changes.
* **Admins:** [set company defaults and targeted rules](#for-admins-set-the-company-policy)
  for the team.

## Choose what your team should review

* **Start with a group you have reviewed.** Manually approve targets you are
  comfortable using before relying on tolerance rules for later changes.
* **Choose limits that reflect the buying decision.** Consider both the
  percentage change and its dollar value. Use the example below to decide
  whether meeting either limit is enough or both should be required.
* **Keep exceptions deliberate.** Use targeted rules for groups needing tighter
  limits or manual review. After the next recommendation update, check a few
  matching items to confirm the policy behaves as intended.

## Understand auto-approval

### What are the thresholds compared against?

Auto-approval compares the effective **New Max** or **Line Point** with the
maximum saved at the **last manual approval**:

* **Percentage-Based:** the change from that approved maximum as a percentage
  of the approved maximum.
* **Value-Based:** the absolute quantity change from that approved maximum,
  multiplied by supplier cost.

Both criteria include a change exactly at the configured limit. Percentage
evaluation needs a positive approved maximum; value evaluation needs supplier
cost. Without a saved manual-approval baseline, an ordinary item still needs
manual approval.

> [!NOTE]
>
> The table's **Max Variance (%)** compares New Max with the current ERP target.
> Auto-approval uses the last manually approved target instead. That displayed
> variance alone may therefore not predict whether the item qualifies.

For an illustrative policy of **±20% AND $100**, a change from an approved
maximum of **100 units** to **120 units**, at **$5 per unit**, is 20% and \$100.
It satisfies both limits. With **AND**, exceeding either limit needs review;
with **OR**, satisfying either enabled criterion is enough.

Percentage and dollar limits answer different concerns. An illustrative change
from one unit to two is 100%, but at $5 per unit it is only a $5 change in the
maximum's value. At the other extreme, a small percentage on an expensive item
can represent a substantial commitment. Choose **OR** or **AND** according to
which of those changes your team wants to review.

### Personal and company rules

Admins manage **Company defaults**, including company custom rules. Buyers use
**My rules**, when available, for the items they manage. In **Buyer rules**,
admins can review buyers' saved policies; each buyer edits their own rules.

Eligible personal rules take priority over company custom rules, which take
priority over company defaults. Within each layer, the
[rule-matching priorities](#what-if-more-than-one-rule-matches) still apply.

## For buyers: review approvals and set My rules

Your team's approval policy determines which target changes need your review.
Approve targets you have checked, then use **Last Manual Approved** to understand
the baseline for later changes. You can follow the company policy without
changing any settings.

### Set your personal rules

1. On **Min/Max** or **Order/Line Points**, select the toolbar **Approve**,
   then **Approval Settings** and **My rules**.
2. If an **ERP buyers** selector is shown, confirm the buyers for all your rules.
3. Select **+ Add rule** and fill in the conditions for your group. If the card
   shows **All products for the selected ERP buyers**, select **+ Add condition**
   to narrow it to the locations, suppliers, or product lines you want.
4. Set **Percentage-Based**, **Value-Based**, or both, and choose **OR** or
   **AND** when both are enabled. Turn off both criteria to require manual review
   for the matching group.
5. Resolve any empty selections or overlap messages, then select **Save my rules**.
6. Check the saved rules. The displayed approval statuses update with the next
   recommendation update. Saved personal rules are used for export checks immediately.

If **My rules** or **Approval Settings** is not shown, ask your Lantern admin
to review the policy you need. Include the affected supplier, location, or
product group and the changes you want to keep reviewing.

For example: “Please keep this supplier at our main branch on manual review,
while other items continue using the company tolerances.”

## For admins: set the company policy

Use company settings to choose the default tolerances and any groups that need
different rules. Your current table filters do not define a rule's membership;
choose its locations, suppliers, buyers, or product lines in the rule itself.

### Set the default policy

**1. Open Approval Settings**

On **Min/Max** or **Order/Line Points**, select the toolbar **Approve**,
then **Approval Settings**. Open **Company defaults** when that tab is shown.

**2. Choose the permitted change**

Enable **Percentage-Based**, **Value-Based**, or both of the criteria
available to you. Enter the percentage as the positive amount beside **±**;
the limit applies in both directions.

**3. Choose how two criteria combine**

When both are enabled, choose **OR** to accept either passing criterion,
or **AND** to require both to pass. Use the explanation shown in the dialog
to confirm the intended policy.

**4. Apply the settings**

Select **Apply Settings** and check the success message. The new policy
takes effect with the next scheduled recommendation update.

### Add a targeted exception

1. Under **Custom approval rules**, select **+ Add rule**.
2. The new rule starts with a **Location** condition. Keep it or change the
   condition dropdown to **ERP buyer**, **Supplier**, or **Product line** when
   those options are offered.
3. Select one or more values for the condition.
4. Select **+ Add condition** to narrow the same rule with another dimension.
   For a supplier-specific rule at one branch, combine **Supplier** and
   **Location**.
5. Set the rule's complete **Percentage-Based** and/or **Value-Based** policy,
   including **OR** or **AND** when both are active. Its thresholds replace
   the default for matching items; omitted thresholds do not inherit.
6. Resolve empty selections or overlap errors, then select **Apply Settings**.
7. After the next recommendation update, reload the page. Inspect items
   that should match the rule and items that should keep using the default.

### Require manual review for a particular group

Keep the targeted rule **enabled**, but turn off both threshold criteria.
The rule shows **Requires manual approval**.

For example, a supplier undergoing a disruption may need manual review at one
location. Add that supplier/location rule and leave both criteria off. Matching
items use this manual-review policy instead of the default tolerance policy.

If personal rules are available, check whether a higher-priority personal rule
applies before relying on a company rule to require manual review.

**Pausing the rule is different.** A paused rule is ignored; another matching
rule or the default can then auto-approve the items. Pausing retains its settings
for later use. Removing a rule also allows the next matching policy to apply.

These settings control automatic tolerance approval. They do not erase existing
human approvals or saved overrides.

## FAQs

### How granular can auto-approval get?

You can combine the conditions offered in **Approval Settings** to give a
particular supplier, location, buyer, or product line its own policy.

| Condition | What it matches |
| - | - |
| **Location** | One or more locations selected in the rule. |
| **ERP buyer** | One or more ERP buyer IDs assigned to items, where offered. |
| **Supplier** | One or more primary suppliers for the item/location, where offered. |
| **Product line** | One or more product-line codes for the item/location, where offered. |

For example, selecting two suppliers and two locations means **either supplier
AND either location**, covering four combinations. Leaving out a condition
leaves that dimension unrestricted. An ERP buyer condition uses the buyer ID
assigned to the item, rather than the Lantern user who is signed in.

Large selections can exceed the editor's combination limit. Selections multiply
within a rule and add across rules, including paused rules: ten locations and
ten suppliers use 100 combinations. Keep selections focused on the groups that
need a different policy.

Missing buyer, supplier, or product-line assignments do not match a condition
requiring that value. Another matching rule or the default then applies.

### What is the auto-approval percentage based on?

The effective new maximum compared with the **last manually approved maximum**.
The table's **Max Variance (%)** uses the current ERP target instead. See
[threshold baselines and examples](#what-are-the-thresholds-compared-against)
when choosing your limits.

### I approved this item before. Why is it back?

An item can need another review when its new target moves beyond the tolerance
allowed since your last manual approval. Compare **New Max** with **Last Manual
Approved** and check which rule applies.

**Start Stocking** and **Discontinue** can also need a separate stocking
decision even when the quantity change fits a tolerance.

### Can I keep one supplier or location on manual approval?

Yes. Use an enabled targeted rule with both threshold criteria turned off.
Admins manage company rules; buyers can use **My rules** where available.
Follow [require manual review for a group](#require-manual-review-for-a-particular-group)
for the setup and the difference between disabling thresholds and pausing a rule.

### What if more than one rule matches?

Lantern chooses the rule with **more condition types**. For example,
Location + ERP buyer takes priority over Supplier alone.

If the number of condition types ties, priority is determined by the presence
of **Supplier**, then **Product line**, then **ERP buyer**, then **Location**.
Selecting fewer values within one condition does not increase its priority.
The displayed order of rule cards is not the priority order.

Enabled rules with the same condition types cannot overlap on the same value
combination; the editor asks you to resolve that overlap. If no enabled custom
rule matches, the default policy applies.

### Does auto-approval also export the targets?

No. **Auto-Export** is a separate setting where your integration supports it.
It sends approved recommendations after a successful recommendation update.
Configuring approval tolerances does not itself enable automatic export.

For a manual handoff, see
[apply reviewed targets](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.