Self-use worksheets
B2B catalog workbook
Specify who may see, buy, quote and approve, then test price precedence at the exact company and location.
Illustrative data, separate blank downloads.
Examples are fictional. They are not client results, live tests, quotations or product claims. Use the blank CSV files for your own records.
How to use this pack
- Define buyer role, company and location before defining product visibility or price. Use synthetic identifiers, never real customer records.
- Write expected access for both allowed and denied users. Check direct product links, search, cart and account paths where applicable.
- List every candidate price source and the intended precedence. Obtain current platform and app evidence for your plan, market and exact rule.
- Trace a quote through buyer approval, order creation and later edits. Record who can act, when repricing occurs and what happens to expired approvals.
Import CSV as UTF-8 with comma delimiters. The blank files contain headers and five empty editable rows. Add rows as needed. Preserve stable IDs. Keep secrets, passwords, payment details and personal customer data out of these sheets.
CSV files contain values only and no executable formulas or macros. Calculated example values are static. After changing inputs, recompute the calculated columns using the recipes shown below. Blank means unknown, while zero means a confirmed zero. Formula-like text and negative numbers are prefixed with an apostrophe for safer spreadsheet imports; remove the apostrophe only from verified numeric inputs when you calculate. Your own later edits are outside the generated-file safety checks.
Company access and product visibility
Define allowed and denied paths for each buyer context.
- Create at least one allowed and one denied case for each protected catalog.
- Include logged-out, wrong location and revoked access cases. A hidden navigation link is not access enforcement.
Blank editable CSV: Company access and product visibility (229 bytes)Illustrative completed CSV: Company access and product visibility (646 bytes)
Field guide
- Access case ID
- Stable acceptance case.
- Synthetic buyer role
- Role only, no personal data.
- Company and location
- Synthetic context and location.
- Catalog and products
- Protected population.
- Entry path
- Search, direct URL, cart or account.
- Expected access
- Allowed or denied and visible information.
- Revocation or boundary case
- What changes when access is removed.
- Observed result and evidence
- Not run until inspected.
- Access owner
- Authority to approve access.
Illustrative data
Fictional teaching example only. Replace it with your own verified records in the separate blank sheet.
| Access case ID | Synthetic buyer role | Company and location | Catalog and products | Entry path | Expected access | Revocation or boundary case | Observed result and evidence | Access owner |
|---|---|---|---|---|---|---|---|---|
| ACC-01 | Authorized buyer | DEMO-CO-A / location 1 | DEMO-TRADE / DEMO-SKU-A | Direct product URL | Allowed with approved location price | Revoked buyer must lose access | Fictional case; not run | B2B operations |
| ACC-02 | Unassigned buyer | DEMO-CO-B / location 2 | DEMO-TRADE / DEMO-SKU-A | Search and direct URL | Denied under proposed policy | No cached restricted price after context change | Fictional case; not run | B2B operations |
Price precedence and subtotal
Make competing price sources and the chosen rule visible.
- Name the source that should win under each context and verify it against platform/app behavior.
- Line subtotal equals quantity times effective unit price. Extend the model separately for shipping, tax, currency and discounts rather than assuming them.
Blank editable CSV: Price precedence and subtotal (272 bytes)Illustrative completed CSV: Price precedence and subtotal (402 bytes)
Field guide
- Pricing case ID
- Link to company/location context.
- Company, location and SKU
- Synthetic context.
- Base unit price USD
- Informational competing source.
- Catalog unit price USD
- Candidate catalog source.
- Contract unit price USD
- Candidate negotiated source.
- Expected precedence rule
- Explicit business rule to verify.
- Effective unit price USD
- Expected winning price, not automatic platform logic.
- Quantity units
- Order quantity for arithmetic.
- Line subtotal USD
- Calculated quantity times effective unit price.
- Verification state
- Quote, cart and order evidence needed.
Calculation recipes
- Line subtotal USD = effective unit price USD × quantity units. Precedence is a human-verified input, not inferred by this CSV.
Illustrative data
Fictional teaching example only. Replace it with your own verified records in the separate blank sheet.
| Pricing case ID | Company, location and SKU | Base unit price USD | Catalog unit price USD | Contract unit price USD | Expected precedence rule | Effective unit price USD | Quantity units | Line subtotal USD | Verification state |
|---|---|---|---|---|---|---|---|---|---|
| PRICE-01 | DEMO-CO-A / location 1 / DEMO-SKU-A | 30 | 24 | 20 | Assume verified contract overrides catalog | 20 | 12 | 240 | Fictional intended rule; not tested |
Quote to order state transitions
Preserve commercial intent through quote approval and order creation.
- Record each transition separately and specify who may trigger it.
- Define quote expiry, stock changes and repricing before claiming the quote can become an order.
Blank editable CSV: Quote to order state transitions (209 bytes)Illustrative completed CSV: Quote to order state transitions (626 bytes)
Field guide
- Synthetic quote ID
- No customer identifiers.
- From state
- Draft, submitted, approved or expired.
- Action and actor
- Who may trigger the next step.
- Required commercial inputs
- Price, currency, location, stock and terms.
- Expected next state
- Observable transition.
- Changed-price or stock behavior
- Hold, reapprove or agreed fallback.
- Evidence to retain
- Reference to authorization and resulting order.
- Decision owner
- Who resolves exceptions.
Illustrative data
Fictional teaching example only. Replace it with your own verified records in the separate blank sheet.
| Synthetic quote ID | From state | Action and actor | Required commercial inputs | Expected next state | Changed-price or stock behavior | Evidence to retain | Decision owner |
|---|---|---|---|---|---|---|---|
| DEMO-Q-01 | Submitted | Authorized approver accepts | USD quote revision 2, location 1, expiry recorded | Approved revision 2 only | Reapproval if quantity or price changes | Fictional approval and order link references | Sales operations |
| DEMO-Q-01 | Expired | Buyer requests order conversion | Expired revision 2 | Blocked pending renewed quote | Recheck price and stock | Fictional blocked transition case | Sales operations |
Buyer approvals and exception scenarios
Keep buying power separate from sign-in.
- Set a policy scope, currency and threshold before testing. Use synthetic transactions only in an authorized environment.
- Test below threshold, above threshold, self-approval, changed amount and unavailable approver.
Blank editable CSV: Buyer approvals and exception scenarios (206 bytes)Illustrative completed CSV: Buyer approvals and exception scenarios (704 bytes)
Field guide
- Approval case ID
- Stable test case.
- Buyer and approver roles
- Roles and separation of duties.
- Policy scope
- Company/location and currency.
- Approval trigger
- Amount, product class or other policy.
- Scenario
- Proposed action and boundary.
- Expected decision
- Allow, block or reapprove.
- Approver unavailable behavior
- Delegation must itself be authorized.
- Observed evidence and state
- Do not infer passed from setup.
Illustrative data
Fictional teaching example only. Replace it with your own verified records in the separate blank sheet.
| Approval case ID | Buyer and approver roles | Policy scope | Approval trigger | Scenario | Expected decision | Approver unavailable behavior | Observed evidence and state |
|---|---|---|---|---|---|---|---|
| APP-01 | Buyer / purchasing manager | DEMO-CO-A location 1, USD | Illustrative orders over USD 500 | Buyer submits USD 600 and tries self-approval | Hold until distinct authorized approver accepts | Hold; no unapproved bypass | Fictional policy, not run |
| APP-02 | Buyer / purchasing manager | DEMO-CO-A location 1, USD | Same illustrative policy | Approved USD 480 changes to USD 620 | Invalidate prior approval; request new decision | Hold until policy-approved alternative | Fictional policy, not run |
Assumptions
- All companies, roles, products, prices and observed results are fictional. No B2B setup was tested.
- The price arithmetic assumes 12 units at an approved effective unit price of USD 20, excluding tax, shipping, discounts and currency conversion.
Known limits
- The sheets specify intended behavior. They do not establish that a platform, plan or app supports that behavior.
- Do not treat company membership, product visibility, checkout authority and approval permission as interchangeable.
Source and method notes
- Approved growth program DESIGN: pack 3.
- Original decision worksheets. Examples are fictional and not platform capability, real test or performance claims.