Purchases by Product Group
Purchases per product grouped by product group (category). For seeing which categories absorb most of the buying budget.
Questions It Answers
- Which category has the largest purchase value this month?
- How much was spent on category X versus last month?
- Which products within a category are bought most often?
Filters
| Filter | What it does |
|---|---|
| Transaction Date | Date range of the purchase invoices. Empty means the whole history - slow on years of data, so always fill it. |
| Division | Pre-filled from the user role's default division. A role locked to one division cannot change it. |
| Department | Limits to one department (warehouse/outlet) inside the division; pre-filled from the role default when set. |
| Product Code | One product only - handy for tracing the history of a single item. |
| Product Group | One group from the Product Group master. |
How To Read It
Nested result: Product Group > product rows with Quantity, Unit, Gross, Discount, Net, Tax, Extra Tax, Subtotal (= Net + taxes). No COGS or profit columns - these are purchases.
Why The Numbers May Differ
- Counts every Purchase invoice in the period, including those still awaiting approval when the workflow is on - unlike the "by Division" reports, which count approved documents only.
- A product whose group is changed in the master moves its whole history to the new group - the report reads today's group.
- Purchase returns are not deducted. For net purchases, subtract the Purchase Return report with the same grouping.
- Quantities are not converted between units: a product bought in boxes and in pieces shows as separate rows with their own quantities.
Purchase Price Permission
Columns derived from COGS or purchase prices - COGS, inventory value, purchase prices and totals, and profit - appear only for roles that have the Show Purchase Price History permission in User Roles. For other roles those columns are absent from the screen, prints, and exports, and the server does not send the figures at all - they are not merely hidden by the layout.
- A missing column does not mean the data is empty. If the user should see it, turn the permission on for their role and ask them to log in again so the report layout follows.
- Custom-built reports are not protected automatically; a copy made with Duplicate in Report Designer keeps the settings of the original.
Menu Location
- Procurement / Purchase Reports / Purchases by Product Group
/report/purchaseperproductgroup