What does CPU mean in Nory?
In Nory reporting, CPU fields apply to CPU locations and deliveries from CPU suppliers. These values are used to make sure stock received through CPU workflows is reflected correctly in reporting and cost calculations.
Where will I see CPU in Nory?
Once CPU is enabled for one of your chosen locations it will appear as a separate tab under “Production” in Nory.
How CPU affects calculations
CPU functionality matters because CPU deliveries feed directly into actual inventory and cost reporting.
In the Management Report
Nory defines COGS using this formula:
`(Opening Count Quantity × Previous Closing Count Price)
(Delivered Quantity × Average Delivered Price)
((Transfers Balance – CPU Delivered Quantity – Closing Count Quantity) × Current Item Price)`
Nory defines Cost of Sales (actual) using this formula:
`(Opening Count Quantity × Previous Closing Count Price)
(Delivered Quantity × Average Delivered Price)
((Transfers Balance – CPU Delivered Quantity – Closing Count Quantity) × Current Item Price)
(Wasted Quantity × Current Item Price)
((Batch created quantity - used as batch ingredient quantity) × Current Item Price)`
This means CPU-delivered stock is part of how Nory calculates actual inventory cost and gross profit performance.
In the Stock Reconciliation Report
For CPU locations, CPU Received Value helps represent the value of stock received through CPU suppliers. This ensures the report reflects the real source and value of stock movement during the reporting period.
Why CPU functionality matters
Accurate CPU tracking helps teams:
understand the true value of stock received through CPU workflows
improve accuracy in actual cost reporting
reduce confusion when reconciling stock movement across locations
investigate variances more effectively when counts, deliveries, or transfers do not line up
How to investigate issues with CPU-related figures
If CPU-related values do not look right, use the same investigation process Nory recommends for stock variances:
1. Validate core inputs
Start by confirming:
closing stock counts are accurate
deliveries are logged correctly
transfers are recorded correctly
waste is logged consistently
2. Check delivery and supplier data
Because CPU fields rely on deliveries from CPU suppliers, review whether the correct quantities, dates, and pricing were entered. The Stock Reconciliation Report notes that CPU Received Value reflects pricing at the time of ordering or delivery note adjustments.
3. Review recipe and POS setup
If report values still look off after counts and deliveries are validated, review recipe mapping, portion sizes, and POS integration. Nory’s variance troubleshooting guidance recommends checking recipe accuracy and POS mapping when investigating unexplained differences.
4. Review batch activity where relevant
If the item is also used in batch production, batch activity may affect actual usage and cost reporting. Nory’s batch guidance explains that produced quantities, usage in batches, and variance are all important when reconciling batch-driven stock movement.
Common questions
Why do I only see CPU fields for some locations?
Because CPU-specific fields only apply to CPU locations or stock received from CPU suppliers. If a location is not operating with CPU-related workflows, those fields may not appear or may not be relevant.
Does CPU affect variance?
CPU data can affect the actual side of your reporting because it feeds into cost and stock movement calculations. If CPU deliveries are missing or incorrect, this can contribute to mismatches during reconciliation and make variances harder to interpret.
Does the CPU interact with batches?
Potentially, yes. Batch-related calculations are handled separately, but if CPU-supplied stock is later used in batches, both CPU and batch activity can influence the final view of actual usage and cost.