Cost of goods report
Audience: Inventory manager, finance manager, center admin
The cost of goods report analyzes how much you spent procuring retail and consumable products and identifies variances between projected and actual expenses. Zenoti provides two versions of this report: a legacy expenditure report under the classic reporting framework, and a V2 Cost of Goods report in the modern reporting framework with per-transaction detail.
When to use Legacy vs. V2:
- Legacy (Reports > Inventory > Expenditure) β cumulative variance summary with Projected vs. Actual rollups and the Retail Product Expense graph on the Inventory dashboard. Use it for period-over-period audit-driven analysis.
- V2 (Reports Dashboard > Cost of Goods) β transaction-level detail with multi-method costing (Perpetual Average Cost, Latest Procurement Price, Configured Purchase Price columns side-by-side) and AG Grid filtering, grouping, and export. Use it for per-transaction reconciliation and margin analysis.
Data refresh: Real-time on Refresh (Legacy) and on grid load (V2). Values reflect transactions captured at the moment of click.
On this page
- Before you begin
- Run the report
- V2 Cost of Goods report β filter reference
- V2 Cost of Goods report β column reference
- How projected and actual expenses are calculated
- Stock value
- Retail product expense graph
- Worked examples
- Troubleshooting
- Related articles
Before you begin
- Enable the legacy expenditure report for your organization under Configuration > Reports > List of reports.
- For V2: ensure the org has access to the modern reporting framework (permissions live under the Inventory group in the report permissions section).
Permission: Expenditure under View Inventory Reports in the Inventory Manager section of the security role β Required to access the legacy inventory expenditure report.
Permission: Cost of goods report (under the Inventory report permissions group) β Required to access the V2 Cost of Goods report.
Run the report
Legacy expenditure report
- Select the center for which you want to run the report.
- Navigate to Reports > Inventory.
- Select the Expenditure report.
- Select the filter criteria (date range, product type) and click Refresh.
To export the report, click the Excel or CSV icon.
V2 Cost of Goods report
Navigation: Reports > Inventory > Cost of Goods.
- Navigate to Reports Dashboard at the organization or center level.
- Search for and select Cost of Goods.
- Set the centers, date range, and additional filters from the Filter reference.
- The grid loads with per-transaction rows.
Use the AG Grid controls (column-header sort/filter, group, hide/show columns, export) for further analysis.
V2 Cost of Goods report β filter reference
| Filter | Description |
|---|---|
| Centers | Select one or more centers to include. |
| Date range | The time period for transactions. |
| Categories | Filter by product category. |
| Sub-categories | Filter by product sub-category. |
| Brands | Filter by product brand. |
| Business units | Filter by business unit. |
| Products | Search for specific products. |
| Product types | Retail, Consumable, or Both. |
| Costing method | Perpetual Average Cost or FIFO (the two values of the StockCostingMethods enum). |
| Consumption type | Filter by Sale, Service Consumption, or Checkout. |
| Search | Free-text search across product name and code. |
| Group column | Group results by a selected dimension (Vendor, Center, Category, Sub-Category, Brand, Product Type, Consumption Type). |
V2 Cost of Goods report β column reference
| Column | Description |
|---|---|
| Transaction Date | The date when the sale or consumption occurred. |
| Center Code | The short code of the center. |
| Center Name | The full name of the center. |
| Consumption Type | The type of event: Sale, Service Consumption, or Checkout. |
| Invoice# | The invoice number for the sale or service. |
| Guest Name | The guest who purchased or for whom the product was consumed. |
| Sold By | The employee who processed the sale or service. (BOM uses Therapist for the same provider attribution per R4-E.) |
| Service Code | The service code (blank for retail sales). |
| Service Name | The service name, if applicable. |
| Product Code | The unique product code. |
| Product Name | The display name of the product. |
| Product Type | Retail or Consumable. |
| Product Size | The size variant, if applicable. |
| Product Color | The color variant, if applicable. |
| Qty | The quantity sold or consumed. |
| Cost Of Goods | COGS calculated using Perpetual Average Cost (quantity Γ Perpetual Average Cost). The Cost-of-Goods column. |
| Effective Cost of Goods | COGS after FIFO correction for negative-to-positive stock transitions. When a PO delivery brings on-hand from negative to positive, the average cost resets to the incoming lot price. This column reflects the corrected value. |
| Offset | The cost-adjustment value for negative-to-positive transitions: Effective Cost of Goods β Cost of Goods for transition units. A non-zero value means the system applied a FIFO-based correction. |
| Purchase Price | The configured purchase price from the vendor. |
| Purchase Price Incl Discount | The purchase price after vendor discounts. |
| COGS Purchase Price | COGS calculated using the Configured Purchase Price (quantity Γ purchase price including discount). |
| Latest Procurement Price | The unit price from the most recent PO delivery. |
| COGS Latest Procurement Price | COGS calculated using the Latest Procurement Price. |
| Category | The product category. |
| Sub-Category | The product sub-category. |
| Brand | The product brand. |
| Business Unit | The business unit. |
Three Cost-of-Goods-Sold columns shown side-by-side, not three costing-method enum values. The Cost of Goods, COGS Purchase Price, and COGS Latest Procurement Price columns let you compare three different cost bases side-by-side for the same transaction. The
StockCostingMethodsenum itself has exactly two values: Perpetual Average Cost and FIFO.
FIFO disambiguation. FIFO appears in this report in two contexts: (1) FIFO is one of the two
StockCostingMethodsenum values (Perpetual Average Cost being the other) β orgs configured for FIFO will see Cost of Goods reflect a FIFO basis instead of Perpetual Average. (2) FIFO correction for negative-to-positive transitions β applied to the Effective Cost of Goods column regardless of the org's costing method, to prevent average-cost inflation when a PO delivery brings on-hand from negative to positive.
How projected and actual expenses are calculated
The Legacy expenditure report compares two expense metrics.
Projected expense
The cost Zenoti auto-calculates against the period's outflow and consumption activity, before reconciling against actual procurement.
Projected Expense = Cost of:
- Outflow Sold quantity
- β Inflow POS (Point of Sale) Return
- Outflow PO quantity
- Outflow PO Return quantity
- Outflow Consumed quantity
Actual expense
The cost actually incurred to maintain stock through the period, reconciled against procurement and audit closing.
Actual Expense = Cost of:
- Opening Quantity
- Inflow PO quantity
- Inflow Transfer quantity
- β Outflow PO Return
- Inflow PO Return
- Inflow Converted quantity
- β Outflow Converted quantity
- (Inflow Bundle quantity + Inflow Unbundled quantity)
- β (Outflow Bundle quantity + Outflow Unbundled quantity)
- β Outflow PO quantity
- β Outflow Transfer quantity
- β Outflow In Transit quantity (stock dispatched on a TO that has not yet been received at the destination center; the V2 column literal is
Outflow Qty-InTransit) - β Closing Quantity
Offset
The Offset column on the V2 grid captures the cost adjustment Zenoti applies to prevent average-cost inflation during negative-to-positive stock transitions (see column reference above).
Stock value
The Stock value displayed on the post-audit summary reflects the current center's inventory worth at the cost basis Zenoti uses to value stock.
Stock Value = Sum of Audited Quantity Γ Perpetual Average Cost for the center
This formula is consistent with the Stock Value column on the Current Stock report and uses cost β not sale price β as the multiplier.
Retail product expense graph
Note: The Retail Product Expense graph appears on the center dashboard, not as a standalone report. It visualizes the same data as this report in chart form. The full description of the graph and its dashboard placement is owned by Inventory reports; this report's role is to provide the underlying expense data.
The Retail Product Expense β Expected vs. Actual graph on the Inventory dashboard displays up to the five most recent audits performed in the last six months:
- Projected Expense (blue) β The expected procurement cost.
- Actual Expense (green) β The actual procurement cost.
- Stock Value (orange) β The audited stock value (per the formula above).
Click the color codes below the graph to show or hide each metric. The graph displays data for both retail and consumable product types using separate tabs.
If fewer than five audits exist in the six-month window, the graph shows whichever audits do exist. If more than five audits exist, the graph shows the five most recent only β for the full history, use the expenditure report directly.
Tip: If the projected expense consistently exceeds the actual expense, your reorder calculations may be overestimating demand. If actual exceeds projected, investigate potential waste or pricing changes.
Video: Cost of Goods Report (3:10) β Walk-through of the Cost of Goods report.
Worked examples
Example 1 β Constant cost period
A center has these transactions for a product at $10 Perpetual Average Cost:
| Transaction | Qty |
|---|---|
| Opening | 50 |
| PO received | 20 |
| Sold (outflow) | 30 |
| POS return (inflow) | 2 |
| Consumed (outflow) | 5 |
| Closing | 37 |
- Projected Expense = $10 Γ (30 β 2 + 0 + 0 + 5) = $10 Γ 33 = $330
- Actual Expense = $10 Γ (50 + 20 + 0 β 0 + 2 + 0 β 0 + 0 β 0 β 0 β 0 β 0 β 37) = $10 Γ 35 = $350
- The $20 variance indicates higher actual consumption than projected, which could signal waste or unrecorded transactions.
Example 2 β Average cost shift after a higher-priced PO
The same center then receives a second PO at a different price, illustrating how Perpetual Average Cost adjusts.
Starting state: 37 units at $10 average cost (= $370 stock value).
PO received: 20 units at $13/unit (= $260 procurement value).
New on-hand quantity: 37 + 20 = 57 units.
New Perpetual Average Cost = (37 Γ $10 + 20 Γ $13) / 57 = ($370 + $260) / 57 = $630 / 57 = $11.05 (rounded to two decimals).
After this PO, every subsequent sale or consumption is valued at the new $11.05/unit average until another procurement event shifts it. This is why the V2 Cost of Goods report's transaction rows may show different cost bases for the same product across the date range.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Projected vs. Actual variance is non-zero with no expected waste | Auto-checkout entries, transfer-in-transit lag, or unrecorded conversions affect Actual but not Projected. | Reconcile against the Stock ledger report for the same period; identify any Stock Out from Adjustment or In Transit rows that explain the gap. |
| Effective Cost of Goods differs from Cost of Goods unexpectedly | A PO delivery brought on-hand from negative to positive; FIFO correction was applied. | Inspect the Offset column for the same row to see the correction value. The non-zero Offset is by design. |
| Cost columns show zero | The product had no procurement events before the consumption row's transaction date, so Perpetual Average Cost is undefined. | Add an opening-stock value or a configured Purchase Price for the product, then re-run the report after the next procurement. |
| Non-zero Offset with no obvious cause | A negative-stock period existed earlier in the date range; the FIFO correction fired silently when a PO delivery cleared the negative balance. | Use the V2 grid's Group-by-Product-Code feature, scroll to the timeline-leading row for the product, and look for a Stock In from PO event coinciding with on-hand transitioning from negative to positive. |
| Missing audit data in the Retail Product Expense graph | The org has no audits in the last six months, OR the audit history was truncated. | Run an inventory audit for the center; the next graph render will surface it. |