Approval rules and approvals
Approval rules are your own checks for the steps where a mistake costs money: confirming an order, dispatching it, settling a payment, approving a purchase order, adjusting stock. (Earlier versions of ARC called them controls.) Each rule checks one step. When its conditions match, it either blocks the step with your message, holds the step until someone with the right permission approves it, or asks the person doing the step to confirm your message before it goes ahead.
Before you start
- To add, change or switch approval rules on and off you need the permission to manage approval rules. New organizations give it to the Owner and Admin roles.
- To decide an approval, a person needs the approval permission the rule names, for example "approve large orders" or "verify payments". Grant these in Settings > Users & Teams, in the role & permission editor, under the Approvals group. See Manage users, teams, and permissions.
- With no rule switched on, nothing changes: every step works exactly as it did before.
What an approval rule is
An approval rule is written as a sentence you can read back:
When an order is confirmed, if order total is more than 50 000 and highest line discount is more than 10%, then needs approval from people who can approve large orders.
- When. The step the rule checks. Twelve steps take any outcome: an order is confirmed, an order is changed after it is confirmed, a shipment is booked (any dispatch), an order is marked delivered, a shipment status changes, a payment is recorded, a payment is settled against invoices, a supplier payment is settled, a bill is created, a purchase order is approved, goods are received, a credit note is issued, and stock is adjusted. Eleven more take Block or Ask to confirm only, never Needs approval: an order is cancelled, a purchase order is cancelled, a purchase order is emailed, a sales invoice is created, an invoice is cancelled, an invoice is emailed, a payment is voided, a quote is emailed, a quote is converted to an order, a return is created, and a draft or cancelled document is deleted.
- If. One to ten conditions, joined by all or any. Each condition picks a fact from a fixed list (order total, highest line discount, customer overdue balance, payment method, who created the purchase order, and so on), an operator such as "is more than" or "is one of", and a value. There are no formulas or scripts. If you need a fact that is not on the list, ask your Growmax representative; new facts are added for every organization.
- Your fields. Your own yes/no, choice and number fields (Settings › Custom fields) on the document the step checks, or on its customer or vendor, are listed under Your Fields and work like any other fact. An empty field never matches. While a rule that is switched on tests a field, you cannot archive, delete or change the type of that field: open the rule or switch it off first. Changing a field a rule tests makes a waiting approval out of date, and cannot be done while that approval is waiting.
- Then. Block with a message you write, Needs approval from the people who hold one approval permission, or Ask to confirm with a message you write.
- Scope (optional). Leave some customers out, or apply the rule only to some warehouses.
Amounts are compared in your base currency, at the exchange rate stored on the document. Day counts use your organization's time zone.
Block, needs approval or ask to confirm
-
Block. The step is refused and the person sees your message. Nothing is saved. Use it for things that must never happen, such as dispatching from the wrong warehouse.
-
Needs approval. The step is held and an approval request is raised for the people who hold the permission. The person asking can never approve their own request, whatever their role. When an order created as confirmed needs approval, it is saved as a draft and the request is for confirming it.
-
Ask to confirm. The person doing the step sees your message in a dialog and chooses to go ahead or go back. You can make them tick a box (for example "I have counted the cash") and give a reason. If they go ahead, the step runs and the document's history shows who confirmed, the message they saw, their reason, and when. Choose who the rule asks: your staff, or buyers in the portal and the buyer app. A message for staff is never shown to a buyer.
A confirmation is a record, not a lock: anyone who can do the step can confirm it. When something must not happen, use Block; when someone else must agree, use Needs approval. A confirmation never overrides a block or skips an approval: it is only asked once nothing else would stop the step.
When nobody can be asked. Integrations calling the API, imports, payment gateways, carrier updates and scheduled jobs have no person at a screen, so the step goes ahead and the rule counts it as not asked. So does an older version of the sales or buyer app that cannot show the dialog. AI never confirms: when Minori or an outside AI agent tries a step that asks to confirm, it is stopped, and a person does the step in ARC.
A confirmation is valid once, for 15 minutes, for that person, that document as it stands, and that version of the rule. If the document or the rule changes, the person is asked again.
Off, Observe and Enforce
Every rule has a mode:
| Mode | What happens |
|---|---|
| Off | The rule is not checked. |
| Observe | The rule is checked and records what it would have refused, but refuses nothing. |
| Enforce | The rule blocks, holds, or asks to confirm real actions. |
- Go to Settings > Approval Rules.
- Choose New Rule. To build your own rule, choose Start From Scratch, pick when it should run (search, or browse by Sales, Shipping, Invoices and Payments, Purchase, or Stock and Other), then Continue to Conditions. To start from a common rule instead, choose Use a Ready-Made Rule and Add (Observe) one. A new rule is always added in Observe.
- Use Test on a Record in a rule's ⋯ menu to see what the rule would do on an existing order, payment or other document. A test changes and records nothing.
- Watch the Last 30 Days column (how many checks the rule flagged out of all it ran; point at it to see refused, would refuse, asked to confirm and passed) for a while, then choose Switch to Enforce in the rule's ⋯ menu. Switching to Enforce asks for a reason, which is kept in the settings history.
The Last Changed column shows who last changed each rule's mode and when; hover over it for the exact time and the reason given. Search the list by rule name, and sort it by any column.
Before a rule can be switched on, a setup check makes sure the rule is valid and that someone other than the person asking could approve it. If nobody else holds the permission, the rule cannot be switched on until you grant the permission to someone else.
If rules cause trouble, Switch All to Observe in the More Options menu stops every enforcing rule from refusing at once, with a reason that is kept in the settings history. Resume Enforcing turns them back on.
The settings that keep their own pages (Allow Negative Stock, Ship Only After Invoice, Approve New Customers and Credit Limits) are linked from the Built-in Settings button beside New Rule.
Decide approvals in the inbox
Open Approvals from the main menu. It has three tabs:
- To Decide: requests waiting for you, because you hold the permission or you are covering for someone who does.
- Raised by Me: requests you asked for.
- All: every request in your organization, for people who can manage approval rules.
Open a request to see the document, the rule, the values that were checked when it was asked, and its history. Then:
| Action | What it does |
|---|---|
| Approve and Apply | Approves and carries out the held step at once, as you. Every rule on that step is checked again. |
| Approve Only | Approves; the person who asked carries out the step themselves by trying again. |
| Reject | Refuses the request, with a reason. |
| Return for Changes | Sends it back to the person who asked, with a reason. |
| Recall | The person who asked withdraws a request that is still waiting. |
An approval never carries out the step by itself. Someone (you, with Approve and Apply, or the person who asked) runs the step again, and it goes through every check as normal.
While a request is waiting, the document shows a banner. Only the notes, the delivery date and the internal reference can change until it is decided. If the document changes in a way the rule checks (a higher total, a new line), the approval no longer counts: the banner says Changed Since Approval, and the next attempt asks again. A change in exchange rate alone never does this. A request expires seven days after it was asked if the step has not been carried out by then, even when it was already approved.
You receive an in-app notification when a request needs you and when your own request is decided.
The Approvals inbox. To Decide holds the requests waiting on you.
Several rules on one step
When more than one approval rule matches the same step, the approvals are asked one after another, not all at once:
- The first matching rule raises its request.
- When it is approved and the step is tried again, the next rule raises its request.
- The step goes through once every matching rule is approved.
If any rule blocks, the step is refused straight away and no approval is asked. Asking for several approvals in one request is not available yet.
Where each step is checked
- Dispatch rules act when the order ships or a shipment is booked, not when it is invoiced. If your organization invoices first and the invoice issues the stock, that stock issue is not checked by a "shipment is booked" rule. The courier booking that follows is.
- Changing an order after confirmation is checked as "an order is changed", whether the change comes from the console, the sales app, the buyer app or Minori.
- Raising a document after it was approved asks again. Raising the total of an approved purchase order, or raising a bill's total or a bill line's price after the bill was created, checks the purchase order or bill rules again. The person making the change is the one asking, and someone else approves.
- A cost change on the product page is a stock adjustment. It is checked by stock adjustment rules, the same as a cost change on the Stock Levels adjust screen.
- A stock count checks each line as its own adjustment, not the count as a whole.
- Minori and AI agents go through the same rules as people. A request Minori raises is shown as raised by Minori for the person it acts for. Minori never approves.
Rules on records
Besides the steps above, a rule can watch a record itself. Today that record is Product (under Catalog in the When list); more records follow. The rule reads the same way:
When a product is made active, if any variant where main image is empty and gallery is empty, then block: Every variant needs an image.
- Pick the moment. Choose Product, then what happens to it: it is created, it is saved (any change to something a rule can check, including a change to one of its variants), it is deleted, or its status changes to Active, Inactive or Discontinued. Creating a product counts as saving it, and as making it active when it is created Active.
- Check the variants. A product's variants are its own list. Press Add Condition and choose Variants to say "any", "all" or "none of the variants where…", or to compare the number of variants where… with a number. Press Add Check for each check on the variant, up to five (all of them must hold for a variant to count). An empty list is read the way it sounds: "any variant where…" is false for a product with no variants, and "all" and "none" are true; the rule's sentence says so.
- Image fields. A product has three places for images, and each is its own field so you choose which one you mean: the product's images, a variant's main image, and a variant's gallery. The rule only asks whether the field is empty or set; it never reads or shows the image itself.
- Block or ask to confirm. Both work at every product moment. Needs approval is not offered on records yet. When a save is blocked, the person sees your message and, for a variant rule, how many variants broke it ("1 of 3 variants meet the checks."). When it asks to confirm, the dialog shows your message once, even if one save touches several moments.
- Every way of saving is checked. The product page, the quick edits in the product list, bulk status changes, cloning, product and variant imports, the sales and buyer apps' product tools, apps that call ARC's service API, Minori and the Zoho item sync. A bulk status change, bulk delete or bulk create asks once for the whole set, and a block names up to 20 products and changes nothing.
- Imports and Zoho are held back, not lost. An import has no one to ask, so a product that breaks a block rule is skipped: all its rows are marked as errors ("CONTROL_BLOCKED" and your message) and the rest of the file is imported. A confirm rule never stops an import. A product from Zoho that breaks a block rule is held back and listed in Settings > Integrations > Zoho under Held Back by Approval Rules, with a Re-run button once it is fixed. While it is held back, ARC does not send that product to Zoho. A product that exists only in Zoho and breaks an "on activation" rule has to be fixed in Zoho first. A deletion Zoho made that a rule refuses is tried again each night.
- Start in Observe. As with every rule, a new product rule starts in Observe: products still save, and the rule counts how many it would have blocked. Look at the numbers for a week before you switch it to Enforce. The kill switch turns every rule, product rules included, back to Observe.
What is not covered yet: your own custom fields in product rules (you will see a clear message if you try), a rule for "a variant is made active" on its own, and changes that are side effects of other settings (reassigning products to another brand, removing a unit, renaming an attribute, changing the base currency, category membership). Undoing a change with Minori's undo is not checked either. On the product page, a rule is checked on a preview of your edit before anything is saved and again as it is saved; in the rare case the two disagree because someone else changed the product at the same moment, a variant change can already be saved when the rule stops the rest. A variant save can also show two confirm dialogs in a row, one for a stock adjustment rule and one for the product rule.
Ask Minori about your approval rules
If you can manage approval rules, Minori (and an AI agent you connect to ARC) can help with them. It can:
- List and explain your rules: what each one checks, its mode, and how often it stopped or held a step in the last 30 days. It never tells you who edited a rule or who switched all rules to observe.
- Tell you why a step was held, from the rule's own record of that decision: which rule, its message, and the permission an approval needs.
- Test a rule on one existing record and tell you what the rule would decide. It tests as a person in the console, so a condition on AI or on the app reads as the console. Nothing is saved.
- Draft a rule from your description, using only the facts on the list (including a product's variants: it can draft the "every variant needs an image" rule above). It asks when something is unclear (which step, what "new customer" means, who approves). It gives you a link that opens the rule builder filled in, marked Drafted Rule. Nothing is saved until you check it and press Save, and a new rule starts in Observe.
Minori never saves, switches on, switches to Enforce or archives a rule, never switches all rules to observe, and never approves, rejects, confirms or delegates anything. For those it points you to the rule's page or to Approvals. It also will not draft a looser version of a rule that has just held one of your own steps: change that rule yourself in Settings › Approval Rules, or ask someone else who manages approval rules. Minori's own approval settings (which chat cards it may apply without asking) are a separate thing from approval rules.
Payments, carriers and other automatic updates
Updates that no person makes (a payment gateway confirming a payment, a carrier reporting a delivery, a scheduled tracking check) are never lost because of an approval rule:
- A payment the gateway captured is always recorded, and counts as verified.
- A delivery or shipment update that a rule refuses is held on the shipment, and your staff are alerted to deal with it.
A payment counts as verified when a payment gateway captured it, or when someone other than the person who recorded it approved its settlement. A staff-recorded payment with no such approval, and a portal bank-transfer payment still pending, are not verified. The ready-made "payment before release" and "buy after funds clear" rules therefore need payment verification switched on (or a payment gateway) before offline payments can ever satisfy them.
Things to know
- The app a request came from is a label, not a lock. "Channel" conditions (console, sales app, buyer app, portal, Minori, API) are reported by the app itself. Use them to describe a rule, never to stop someone: what a person may do is decided by their role and permissions.
- "Proof before Delivered" needs a courier that returns proof of delivery. Staff cannot upload proof by hand, so orders sent with your own couriers stay held by that rule.
- Not checked yet: Zoho sync changes to orders, purchase orders, payments and stock (product items from Zoho are checked by product rules, see Rules on records); return pickups and return shipments; cancelling a shipment or fixing an orphaned one; credit notes created automatically when an invoice is cancelled or a payment is voided; opening stock entered when a product is created; transfers between your own warehouses; stock put back by a return.
- Delegation. Covering for an absent approver is available through the API only; there is no screen for it yet.
- Notifications are in-app only for now; approval emails are not sent.
Tips
- Start every new rule in Observe for a week. The would-refuse count tells you whether the threshold is right before it affects anyone.
- Grant each approval permission to at least two people, so one person's leave does not hold everything up.
- Write block messages that tell the person what to do next, for example "Book this order from its own warehouse".
- Use Ask to confirm for a reminder people should read before a step, not for a rule that must hold: anyone can click Confirm.