--- title: "Usage Per 1000" slug: "usage-per-1000" description: "Usage Per 1000 normalizes item consumption per 1000 guest covers, enabling cross-location comparisons to identify waste or portion variance." updated: 2025-08-26T19:47:50Z published: 2025-08-26T19:47:50Z canonical: "docs.restaurant365.com/usage-per-1000" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.restaurant365.com/llms.txt > Use this file to discover all available pages before exploring further. # Usage Per 1000 The R365 inventory system uses a usage per $1000 calculation to calculate theoretical on hand quantities and values. Both usage per $1000 and theo on hand are visible in areas of R365 to serve as guidance for managing items, particularly when it comes to inventory counts and purchase orders. R365’s usage per $1000 calculation is an approximation of an item’s usage over about 90 days. The calculation uses R365 inventory transactions and POS sales to average historical inventory consumption and predict future inventory item usage. An item’s usage per $1000 is then used to calculate a reasonable assumption of the quantity of an item that a location has on hand. This is R365’s **theoretical on hand** amount. Theoretical on Hand—or Theo on Hand—values represent the quantity of an item that a location should ideally have on hand. This calculated value is based on an item’s transactions since the item’s **last inventory count** and its system-calculated usage per $1000. Usage per $1000 and theo on hand are updated each night and an item’s most updated values can be found on the purchased item record. These values are used to suggest quantities on orders, generate inventory quantities, and shown on some Reports to make comparisons. --- ## Usage Per $1000 In R365, usage per $1000 refers to the quantity of an item used per $1000 in sales in about a 90 day time frame. It is calculated using the base unit of measure of the item, which is the lowest U of M for any Measure Type (Each, OZ-wt, OZ-fl). The system uses the following calculation: ![The equation usage per $1000 equals (StartCountQty + CountToCountTotalInvQty - EndCountQty) divided by (CountToCountSales / 1000)](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-WS0ECLD1.png) In this calculation, to calculate the item usage, the system takes the beginning count quantity of the item, adds and subtracts the quantities based on the item’s activity, then subtracts the ending count quantity of the item. The result represents the total usage for the item during for the 90-day time-frame. This item usage is then divided by the quotient of total sales by 1000. The variables of the equation can be described as follows: | | | | --- | --- | | **EndCountQty** | The item quantity as of the *most recent* inventory count. This is the ‘ending count.’ | | **StartCountQty** | The item quantity from the count approximately 90 days before the date of the count used for the EndCount Quantity. This is the ‘beginning count’. > [!NOTE] > If there was no count taken, exactly 90 days from the most recent count, then the system will use the *closest* count regardless of whether it is before or after the 90 day mark. > > > > **Example**: if there was a count 89 days prior and a count 100 days prior, the system will use the count from 89 days before because it is closest to 90. | | **CountToCountTotalInvQty** | This is the item quantity when all the inventory transactions between counts have been totaled. This considers all the **approved** inventory transactions for the item that occur between the day *after* the StartCountQty date **up to and including** the day of the EndCountQty. The system assumes that the starting and ending inventory counts occur at the end of the day. Because of this, the item activity from the start date is excluded while the item activity from the end date is included. > [!NOTE] > Only transactions that have been approved are used to calculate the usage per $1000. The following inventory transactions are used: \| Increase Inventory \| Decrease Inventory \| \| --- \| --- \| \| AP Invoices (Purchased Items) \| AP Credit Memo (Refunded Items) \| \| Transfers In \| Transfers Out \| \| AR Credit Memo \| Waste Log \| \| Commissary Receiving \| Commissary Sales \| \| \| AR Invoices \| \| \| Donations \| \| \| Catering Sales \| > [!WARNING] > CountToCountTotalInvQty includes transactions **between** inventory counts and does not consider the inventory counts themselves. | | Increase Inventory | Decrease Inventory | | AP Invoices (Purchased Items) | AP Credit Memo (Refunded Items) | | Transfers In | Transfers Out | | AR Credit Memo | Waste Log | | Commissary Receiving | Commissary Sales | | | AR Invoices | | | Donations | | | Catering Sales | | **CountToCountSales** | Refers to the total sales made from the date *after* the beginning count to—and including—the date of the ending count. These sales totals are pulled from all the **approved** Daily Sales Summaries that occur during the time frame. This CountToCountSales total is then divided by $1000. | The system then takes the item usage and divides it by the sales to find the item’s actual usage per $1000 in sales. Usage per $1000 is updated only once at the end of every day. Overnight, R365 will update the usage per $1000 that is shown on the Item Cost tab of the purchased item record. --- ## Theoretical on Hand R365’s theoretical on hand quantity reflects how much of an item that a location **should** currently have in stock. The system uses the following equation: ![Theo On Hand = EndCountQty - (UsagePer1000 * (EndCountToAsOfSales / 1000)) + EndCountToAsOfTotalInvQty](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-IS9M6P7Q.png) The theo on hand equation approximates what a location has on hand by totaling quantities from the last inventory count, the item's most updated usage per 1000, and latest inventory transactions since that last count. The variables of the equation can be described as follows: | | | | --- | --- | | **EndCountQty** | The item quantity as of the last, or *most recent* inventory count. | | **UsagePer1000** | The system calculated value for the item’s usage per $1000 in sales across an approximately 90-day time frame. | | **EndCountToAsOfSales** | The total amount of sales since the last inventory count. This total sales is divided by $1000 to utilize the per $1000 structure. > [!NOTE] > This considers all sales from the day **after** the date of the inventory count that the EndCountQty is pulled from. Only sales from **approved** daily sales summaries are used. This differs for the Theo on Hand calculated on a [purchase order](/doc/docs/purchase-orders-create-and-enter-a-purchase-order) form. Read more in the note below. > [!WARNING] > Purchase Order Theo on Hand Values > > The Theo on Hand value on the purchase order form depends on the PO’s **order date.** > > - **If the Order Date is Today:** The calculation uses sales data from both **approved and unapproved** daily sales summaries beginning the day after the inventory count date that the EndCountQty is based on. > - **If the Order Date is in the Future (e.g. Tomorrow or Later)**: The calculation uses any existing approved and unapproved daily sales summaries as well as **forecasted sales** for **each relevant future date**. | | **EndCountToAsOfTotalInvQty** | All the item’s activity or **approved** inventory transactions that have occurred since the last inventory count. > [!NOTE] > Only transactions that have been **approved** are used to calculate the theo on hand. The following item transactions are used: \| Increase Inventory \| Decrease Inventory \| \| --- \| --- \| \| AP Invoices (Purchased Items) \| AP Credit Memo (Refunded Items) \| \| Transfers In \| Transfers Out \| \| AR Credit Memo \| Waste Log \| \| Commissary Receiving \| Commissary Sales \| \| \| AR Invoices \| \| \| Donations \| \| \| Catering Sales \| \| \| AP Credit Memo (Refunded Items) \| \| \| \| | | Increase Inventory | Decrease Inventory | | AP Invoices (Purchased Items) | AP Credit Memo (Refunded Items) | | Transfers In | Transfers Out | | AR Credit Memo | Waste Log | | Commissary Receiving | Commissary Sales | | | AR Invoices | | | Donations | | | Catering Sales | | | AP Credit Memo (Refunded Items) | | | | An item’s Theoretical on Hand value is updated only once at the end of every day. Overnight, R365 will update the Theo On Hand quantity that is shown on the Item Cost tab of the purchased item record. --- ## Purchased Item Record An item’s most updated Usage Per $1000 and Theoretical On Hand values will be shown on the item’s purchased item record. Both values are shown on the Cost Summary card of the Item Cost tab. > [!NOTE] > These values are updated **once each night, overnight**. This means that an item’s most updated usage per $1000 or theo on hand will be based on approved item transactions and approved daily sales up to the end of the day prior to present day. > [!WARNING] > Usage per $1000 and Theo on Hand are location specific. Every location will have its own values for these for an item. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-4YISQU9D.png) Areas in which Theo On Hand and Usage Per $1000 (also Actual Usage) are surfaced will use the values that appear here. --- ## Using Theo On Hand Calculations that use Usage Per $1000 or Theo on Hand will utilize the values shown on the purchased item record to determine suggested quantities. This includes the **Suggest Qty** button on a purchase order and the **Generate Qty** button on an inventory count. ### Purchase Orders - Suggest Qty Users with create/edit/submit purchase order permissions have the ability to use the Suggest Qty button when filling out an order. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-6OR9YKEF.png) This button generates a suggested quantity to order on a PO. When the **Suggest Qty** button is clicked, users are prompted to select when the product is going to be used (consumption and buffer days). In this case, the system will use forecasted sales, the item’s usage per $1000, and the theo on hand to determine a quantity suggestion. If there is a day that is forecast to be $0, users will be notified before continuing. Learn more about [entering a purchase order](/doc/docs/purchase-orders-create-and-enter-a-purchase-order). ### Inventory - Generate Qty In an open inventory count, users with the **Generate Using Theo On Hand** permission have the ability to generate an inventory count using the theo on hand values generated by R365. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-27QM9VKQ.png) When clicked, all quantity values will be overridden and filled with the item’s theo on hand value. The storage location progress indicators will change to 100% and users can continue to review. Learn more about [generating an inventory count using theo on hand](/doc/docs/generate-an-inventory-count-using-theo-on-hand). --- ## Theoretical on Hand Report The [Theoretical on Hand](/doc/docs/theoretical-on-hand) report report shows users how much product is on hand as of the selected date. This report shows the theoretical on hand count as well as the quantities for other transactions that make up the theo on hand. It allows users to select a date parameter to run the report by. The 90 day window starts from the date selected in the As Of parameter. > [!WARNING] > The theo on hand value on this report **may** differ from the value shown on the purchased item record. This is because when Today is selected as the As Of date, the report calculates a value that considers approved transactions/counts that have occurred ‘today’ or the day the report is being run. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-LUH1X3F3.png) Restaurant365 POS (Point of Sale) A system used by businesses to process sales transactions and manage customer payments. Connected to R365 through a [POS integration](/doc/docs/pos-integration-overview). Structured documents that provide insights and summaries of various operational metrics and financial data. Access rights granted to users or user roles that dictate what actions they can perform within the system.