Category Management Report: What to Include

A category management report explains what changed in a purchasing category, why it changed, and what the category owner should do next. Start with comparable invoice spend, separate price and quantity effects, and show supplier dependence. Close the review with an action, an owner, and evidence that will confirm whether it worked.

Set the category scope and reconcile the export

GSA describes category management as organizing purchases of common goods and services across an enterprise, using category spend information to manage suppliers, demand, and total ownership cost. A company report can follow that practical structure without adopting federal procurement rules.

Choose a category definition and keep it unchanged across the comparison periods. Export one row per invoice line with a unique invoice-and-line key. Standardize supplier identifiers, item codes, units, and currency before grouping anything. Use net amounts with credits signed; state how freight and tax are treated.

Reconcile the export to the accounts payable invoice register for the same posting period and scope. Keep excluded categories and unmatched rows in a separate reconciliation rather than deleting them silently. An unresolved category mapping is an exception to explain, not zero spend.

Build the period comparison in Excel

An illustrative Ohio manufacturer reviews maintenance consumables for September 2026 against August. These are all the category's invoice lines. Prices are net USD per unit; there are no credits, tax, freight, or currency adjustments in this example.

On a sheet named Spend, put these headers in A1:G1 and the rows below in rows 2:5. Store the dates as date values.

For these simplified rows, G2 is =E2*F2, filled down. In a real export, retain the actual net invoice amount and reconcile any difference from quantity times price.

On a report sheet, enter August 1, 2026 in B1, September 1, 2026 in C1, and Maintenance in A4. Enter this in B4 and copy it to C4:

=SUMIFS(Spend!$G$2:$G$5,Spend!$B$2:$B$5,$A4,Spend!$A$2:$A$5,">="&B$1,Spend!$A$2:$A$5,"<"&EDATE(B$1,1))

Microsoft documents SUMIFS for adding values that meet multiple criteria. Here the criteria select the category and month; extend the ranges together for your export. Covirage is not affiliated with Microsoft.

D4 = C4-B4
E4 = IF(B4=0,"No prior base",D4/B4)

Format E4 as a percentage. A missing prior base needs explanation, not an infinite growth percentage.

The proof is direct: 5,000 + 2,000 = $7,000; 6,600 + 2,500 = $9,100; and 2,100 / 7,000 = 30.00%. Percentages are rounded to two decimal places; dollar amounts here are exact.

Explain the change before suggesting savings

A 30.00% increase does not mean suppliers raised prices by that amount. Keep item definitions constant and build a bridge using prior prices for the quantity effect and current quantities for the price effect.

On a separate bridge sheet, use columns A:H as shown:

F2 = (C2-B2)*D2
G2 = C2*(E2-D2)
H2 = F2+G2

Fill down for both items. The bridge checks: 7,000 + 1,500 + 600 = 9,100 USD. Bearings account for the entire price effect. The remaining change reflects additional quantities at unchanged baseline prices.

This ordering assigns the price-and-quantity interaction to price. State that convention and keep it consistent. New items without a comparable prior price need a separate scope line, rather than an invented baseline. Use the cost savings dashboard to track a later initiative against an agreed baseline; this variance is not automatically savings available to capture.

Show supplier dependence and assign the next action

September supplier shares come from the same rows:

For example, Lake's share is 6,600 / 9,100 = 72.53%. Do not add unrelated categories to the denominator. This is spend dependence, not proof that another supplier can make the same bearings.

The category owner should validate the bearing price change against the contract and check why units increased. Record the finding, proposed action, owner, and due date. If quality issues explain replacement demand, connect the evidence to a quality management report. If approvals delayed orders, use the purchase order cycle time KPI for that separate investigation.

Place the accepted explanation in the management reporting package: category spend rose because both demand and bearing prices increased. A sourcing opportunity becomes credible only after specification, service, and alternative capacity checks.

Where it goes wrong

• Changing category mappings. Restate the comparison or show a scope adjustment when items move categories.
• Adding quantities with different units. Cases and individual pieces require a documented conversion before any price comparison.
• Calling every increase a price problem. Separate demand, price, and unmatched scope before assigning a sourcing action.
• Treating dependence as a savings estimate. Concentration identifies a question; it does not establish a lower achievable price.

Review your own category file in Covirage

Bring a purchasing file with category, supplier, item, quantity, and net amount columns; Covirage maps the columns, and its tools compute and check the comparisons. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring a sample of your own data.

See Covirage for procurement teams for the purchasing context.