Operations Settings

Configure request categories, payment categories, fraud detection thresholds, and auto-approval limits for your store operations.

Operations Settings control how store operations work for your store. From here you can create request categories, configure payment classifications, set up fraud detection rules, and define auto-approval limits. Getting these settings right from the start helps your team create consistent requests and ensures the right controls are in place.

Request categories

Request categories organize store requests into logical groups. Each category can have its own default priority and receipt requirements, which speeds up request creation and ensures consistency across your team.

Examples of request categories include “Kitchen Supplies,” “Cleaning Materials,” “Equipment Maintenance,” and “Packaging.” You can create as many categories as you need.

For each category you can configure:

  • Category name — A descriptive label for the category.
  • Default priority — The priority level (Urgent, Normal, or Low) that is automatically selected when a team member creates a request in this category. It can be overridden.
  • Receipt required — Whether a receipt or proof of purchase must be attached when the request is fulfilled.
  • Active status — Whether the category is available for new requests. Deactivating a category hides it from the creation form without deleting historical data.

Payment categories

Payment categories classify operational payments for cost tracking and reporting. They map to your organization’s cost classification structure so that expenses flow correctly into financial reports.

For each payment category you can configure:

  • Category name — A label such as “Market Purchases,” “Transport,” or “Facility Repairs.”
  • Cost classification — The accounting classification this category maps to, used for financial reporting and expense tracking.
  • Auto-approval limit — A maximum amount below which requests in this category are automatically approved without manager review. Set to zero to require approval for all amounts.
  • Receipt required — Whether receipts must be submitted during reconciliation for payments in this category.

Fraud rules

Fraud detection rules help protect your store from unauthorized or suspicious payments. Each rule can be individually enabled or disabled, and thresholds can be configured per store to match your operational patterns.

Navigate to Operations & Projects → Settings → Fraud Rules to see the full list of available rules. For each rule you can:

  • Enable or disable — Turn individual rules on or off depending on your store’s needs.
  • Set thresholds — Configure the numeric limits that trigger the rule, such as maximum transaction amount or daily cumulative limit.
  • Set severity — Choose whether a triggered rule results in a Warn, Escalate, or Block action.

Changes to fraud rules take effect immediately for all new requests. Existing requests that have already been scored are not re-evaluated.

Setting up categories

Follow these steps to create your first request categories:

  1. 1

    Navigate to Operations Settings

    From the sidebar, go to Operations & Projects → Settings. Select the Request Categories tab.

  2. 2

    Create a category

    Click Add Category. Enter a name that clearly describes the type of requests it will contain, such as “Cleaning Supplies” or “Equipment Repair.”

  3. 3

    Configure defaults

    Set the default priority for requests in this category. Enable receipt requirements if proof of purchase should be collected upon fulfillment.

  4. 4

    Save and repeat

    Click Save to create the category. Repeat for each category your store needs. You can always add, edit, or deactivate categories later.

The Operations Settings page lets you manage request categories, payment categories, and fraud detection rules.
Start with default categories

If you are not sure which categories to create, start with a small set of broad categories like “Supplies,” “Maintenance,” and “Restocks.” You can always break them into more specific categories later as your team’s needs become clearer. Over-categorizing from the start can slow down request creation.