Wallet category-scope register

A wallet percentage is difficult to interpret when sales include products that the customer’s total-spend estimate excludes. This wallet category-scope register documents the boundary before the calculation begins. The workbook holds inclusion decisions, the economic unit, reporting dates, scope version and recorded agreement. Formula-driven counts show which parts of that boundary still need to be resolved.

What to enter

Create one scope record per product or category whose treatment needs agreement. Included? says whether it belongs in the wallet definition. Economic unit distinguishes USD from a volume measure. Start and end dates define the same period for both parts of the later ratio. Scope version, owner and agreement date record which definition the reviewer accepted. Keep IDs stable when names change.

Use the workbook

1. List the product/category boundary for the book under review. Make exclusions explicit, including large one-time purchases when your stated scope excludes them.
2. Agree the unit and period with the people supplying sales and total-spend evidence. Resolve mixed units before accepting a common wallet number.
3. Record a version and agreement date. Transfer only Complete decisions to your mapping rules, keeping prior versions for historical comparisons.

Keep the amber inputs separate from the pale blue calculation columns. The worksheet has 20 prefilled detail rows, from 13 through 32. If you need more records, extend every affected formula and summary range together, then check a first, middle and final row. Save a dated working copy before replacing the sample.

The synthetic example

The sample includes MRO consumables, excludes capital equipment and leaves repair services awaiting agreement. Replacement parts has reversed dates and is Invalid period. There is one agreed included record, one agreed excluded record and two unresolved records. Supplying the repair-services agreement date completes that decision; changing an owner alone does not change its status.

How the results update

Scope status requires the category, unit, chronological reporting period, version, owner and agreement date. The included and excluded counts use only Complete records. The unresolved count is all identified records less complete records. These formulas measure whether the specification is usable, not whether the categories are economically correct. They update when an agreement or period changes.

Limits and a useful next step

The register is a record of the selected definition. It does not convert currencies, allocate invoice lines, remove tax or reconcile accounts. Those transformations need separate documented inputs. Changing the boundary can move wallet share even when customer behavior stays the same, so compare historical results on a common version. Link this artifact to the calculation and evidence records rather than using it as a second formula guide.

For the underlying method, read share of wallet by industry. product taxonomy for analytics covers the adjacent question. If you want to review the required fields and one reporting output, discuss your setup. Views depend on your records and agreed definitions.