How Manufacturing Should Deliver Data for CPQ + M3
Simple intake guide by product family
What this is NOT
This is not a request for CPQ rule code.
What this IS
A request for the business inputs needed to build CPQ + M3 manufacturing rules.
The Goal
Give Manufacturing a clear picture of what data to provide, how it will be used, and how review, iteration, and adjustment should work.

This is a clarity tool, not the desired long-term manual process.
Simple Delivery and Review Flow
Manufacturing and the CPQ/M3 team each own distinct parts of the process. This left-to-right flow shows how business rules move from the factory floor into working system logic.
1
1. Manufacturing Defines Valid Business Rules
Valid materials, valid operations, quantity drivers, time drivers, exceptions
2
2. CPQ Captures Customer Choices
Only ask the customer what is truly needed
3
3. CPQ/M3 Team Derives Manufacturing Values
Derive hidden values where possible
4
4. M3 Product Structure Is Built
Translate rules into materials, operations, quantities, and timing
5
5. BOM + Routing Result Is Reviewed
Check expected BOM and expected routing
6
6. Adjust and Approve
Refine until results are correct, then scale

Manufacturing owns the business rules. CPQ/M3 rule writers own the system translation.
What Manufacturing Should Provide for Each Product Family
For each product family, Manufacturing should deliver information across six categories. Use these as your checklist when preparing inputs.
1. Scope
  • Product family name
  • Sample styles/SKUs in scope
  • Bucket: Standard / Configurable / MTO
2. Customer Choices That Matter
  • Which selections actually change material or process?
  • Examples: finish, size, stone, backing, packaging
3. Material Rules
  • What material/component is used?
  • When is it used?
  • How much is used?
  • Any substitutes or alternates?
4. Routing Rules
  • What steps are required?
  • In what sequence?
  • What is optional vs. always required?
  • What drives time?
5. Exceptions
  • Invalid combinations
  • Defaults
  • Special cases
6. Expected Result
  • What BOM should come out?
  • What routing should come out?
  • What test examples should be used for review?
Simple Fill-In Template
Complete one product family at a time — one material row at a time, one routing row at a time. Sections A and B set the context; C, D, and E capture the detail.
Section A — Family Scope
  • Product family:
  • Styles/SKUs in scope:
  • Bucket: Standard / Configurable / MTO
  • Base/template item in M3 if known:
Section B — Drivers
  • Customer-visible choices:
  • Hidden/derived manufacturing values:
Section E — Exceptions and Tests
  • Invalid combinations:
  • Defaults:
  • 3 test examples to validate BOM and routing:
Section C — Material Rules
Section D — Routing Rules

This can be completed one product family at a time, one material row at a time, and one routing row at a time.
Concept Example Only
Example Concept Only — "Pin Family"
Replace with actual Herff Jones values. The rows below are illustrative only — they show how the template is meant to be filled in, not the real business logic for this product family.
Section A — Family Scope
  • Product family: Pins
  • Styles/SKUs in scope: Example styles only
  • Bucket: Configurable
  • Base/template item in M3: Family template item
Section B — Drivers
  • Customer-visible choices: Finish, stone color, backing
  • Hidden/derived manufacturing values: Plating code, stone count, assembly flag
Section E — Exceptions and Tests
  • Invalid combination: Example only — use actual business rules
  • Defaults: Default finish / backing if applicable
  • Test 1: Gold + red stone + clutch
  • Test 2: Silver + no stone + safety backing
  • Test 3: Gold + blue stone + clutch
Section C — Material Rules
Section D — Routing Rules