Inventory Budget β Bulk Raise Preview
Audience: Center admin, inventory manager
On this page
Before Zenoti commits a bulk raise, it evaluates every selected external purchase order (PO) against each center's monthly inventory budget and returns a preview of which center-month combinations would fall below zero β along with which purchase orders at those centers are causing the shortfall. This article explains how to read and act on that preview.
Before you begin
Your organization must have the inventory budget feature enabled. If Inventory budget does not appear in Configuration > Inventory, contact your Zenoti representative.
A bulk raise session must already be in progress. Navigate to Inventory > Orders, select the purchase orders you want to raise in bulk, and initiate the bulk raise action before the preview runs.
Only external purchase orders are evaluated against the budget. Internal inter-center transfer orders in the same batch are automatically skipped by the preview.
You need the following permissions under the Inventory section of your security role:
Permission: Add or Edit on the Inventory security object β Required to raise purchase orders and trigger the bulk raise preview. Admin path: Configuration > Security > Security Roles > [your role] > Inventory
Steps
Run the bulk raise budget preview
The preview runs automatically when you initiate a bulk raise session that includes purchase orders at centers where monthly budgets have been configured. You do not trigger it separately.
- Navigate to Inventory > Orders.
- Select the external purchase orders you want to raise.
- Select the bulk raise action (the Raise or Raise & email option from the action bar).
- Zenoti runs the budget preview before committing any raise. If no center-month combination would fall below zero, the bulk raise proceeds without interruption.
- If one or more center-month combinations would fall below zero, the preview results appear before the raise is committed. Review the results as described in the next section.
Note: Internal inter-center purchase orders in the batch are skipped entirely during the preview. Only external purchase orders β those raised against an outside vendor β are evaluated against the monthly budget.
Interpret the preview results
The preview returns a list of affected center-month combinations. For each combination, you can see:
- Center name β The center whose monthly budget would be exceeded.
- Month β The calendar month in which the shortfall would occur.
- Enforcement mode β Whether the center is set to Warn or Block for budget overruns. Zenoti determines this by first checking for a center-level enforcement override; if none exists, the organization-level enforcement setting applies. A Warn result means the raise can proceed with acknowledgement. A Block result means the raise cannot proceed for that center until the shortfall is resolved.
- Purchase orders causing the shortfall β The specific external purchase orders at that center that would push the monthly budget below zero.
Important: The enforcement mode shown in the preview results is read-only. It reflects the setting configured in Configuration > Inventory > Essentials > Budget enforcement and cannot be changed from within the preview.
Worked example
Your organization has three centers. Center A has a monthly budget of $5,000 with a Block enforcement mode. You have selected four external purchase orders for bulk raise: two at Center A totaling $5,200, one at Center B totaling $1,000, and one at Center C totaling $800.
The preview returns one affected center-month combination: Center A for the current month, with a shortfall, listing both Center A purchase orders as the cause. Center B and Center C do not appear because their budgets are not exceeded. Because Center A is set to Block, the bulk raise cannot proceed for those two purchase orders without first resolving the shortfall.
Decide how to proceed
After reviewing the preview results, you have the following options:
If enforcement mode is Warn for all affected centers: The preview surfaces the shortfall as a warning. You can acknowledge it and continue the bulk raise. The purchase orders at over-budget centers are raised along with all others in the batch.
If enforcement mode is Block for one or more affected centers: The bulk raise cannot be committed for the blocked purchase orders. To proceed, you must do one of the following before re-attempting the bulk raise:
- Remove the purchase orders at blocked centers from the current batch.
- Ask an authorized user to adjust the monthly budget for the affected center in Configuration > Inventory > Monthly budget so the batch no longer causes a shortfall.
- Split the batch β raise the unaffected purchase orders now and handle the blocked ones separately after the budget situation is resolved.
Important: Adjusting a center's monthly budget requires access to Configuration > Inventory. This is typically an admin-level task. Do not adjust budgets solely to bypass a legitimate budget control without authorization from your finance or operations team.
Tips
- Filter the orders listing by center before selecting for bulk raise. If you know a particular center is near its budget limit, reviewing that center's purchase orders individually before including them in a bulk raise session reduces the chance of a preview-blocked result.
- Check the enforcement mode for each center before initiating large bulk raises. Centers set to Block will halt the raise for their purchase orders; centers set to Warn will not. Knowing the mode in advance helps you plan the batch.
- The preview only evaluates the current month. If a purchase order spans multiple delivery windows, only the month in which it would be delivered and counted against the budget is evaluated. Plan your bulk raise timing accordingly.
- Internal transfer orders never affect the budget preview. If you see inter-center transfer orders in your batch, they are silently skipped β their presence does not trigger a budget warning or block, and they are raised normally.
- Use the preview results list to audit budget health across centers. The list of affected centers and purchase orders gives you a snapshot of which centers are most exposed before any commitment is made.
Troubleshooting
The preview does not appear, and the bulk raise commits immediately.
The budget preview only runs when at least one center in the batch has a monthly budget configured and the inventory budget feature is enabled. If neither condition is met, the raise proceeds without a preview. Verify that the inventory budget feature is enabled under Configuration > Inventory and that monthly budgets have been set for the relevant centers in Configuration > Inventory > Monthly budget.
A purchase order I expect to see in the preview results is not listed.
Only external purchase orders are evaluated. If the order is an internal inter-center transfer order, it is intentionally excluded. Also confirm that the purchase order's total would actually cause a shortfall β orders that keep the center-month balance at or above zero do not appear in the results.
The enforcement mode shown is Warn, but I expected Block (or vice versa).
Enforcement mode is resolved in a specific order: center-level override first, then organization-level default. If a center has its own enforcement setting configured, that takes precedence over the organization default. Check both levels under Configuration > Inventory > Essentials > Budget enforcement to confirm which setting is controlling the mode for the affected center.