← Back to Genius Hub

Handi-Ramp Product × B2 Methodology

Product categorization answers what was sold. B2 buyer segmentation answers who was invoiced. They are independently established at their proper grain, then joined for reporting.

Need the exact B2 rule order? Open the B2 classification decision sequence →

Posted Genius invoice lines Signed credit notes B2 v5: 2025-01-01 → 2026-09-16 Unknown remains visible
Independent product categorization and B2 buyer segmentation join at invoice-line reporting grain A left product branch maps posted Genius invoice lines into approved product buckets or visible exceptions. A right branch assigns buyer type using three levels of evidence. The approved product and buyer results join into product by buyer reporting. Product categorization — what was sold B2 buyer segmentation — who was invoiced Posted Genius invoice line HR/HPI route · invoice date · signed credit Approved mapping hierarchy 1. Month-specific Item Matrix 2. Exact Route + SKU · 3. Defined variant 4. Documented SKU-family addition Approved product result Handi-Ramp Aluminum / Steel bucket Biggies + PetStep split from Steel → Other Visible exception — not forced Freight · tax · CCFEES · AP/AR · unmapped Level 1 · direct entity Reviewed buyer · official government identity Level 2 · transaction / product CVR / Yard Ramp / MH / hose-pipe-cable reviewed CVR quote · >$1k non-slip aluminum Approved business-purchase evidence → B2B Level 3 · exact Woo checkout Exact linked order — never generic WOO-AR .gov · company / work domain · personal/no company Invoice-level B2 assignment B2G overrides B2B · hard B2B protects from B2C B2B · B2C · B2G · Unknown Join at invoice-line reporting grain Product category × buyer segment → Handi-Ramp Product × B2 summary No product result is inferred from B2; no B2 result is inferred from product category. Boundary: B2 v5 covers through 2026-09-16. Later posted invoices are OUTSIDE_B2_COVERAGE — not Unknown. This is buyer segmentation, not lead attribution.

Product categorization — what was sold

Posted Genius invoice lineHR/HPI route · invoice date · signed credit
↓
Approved mapping hierarchyMonth-specific Item Matrix → exact Route + SKU → defined variant → documented SKU-family addition.
↓
Approved product resultHandi-Ramp Aluminum / Steel bucket; Biggies + PetStep split from Steel → Other.
↘
Visible exception — not forcedFreight · tax · CCFEES · AP/AR · unmapped items remain auditable.

B2 buyer segmentation — who was invoiced

Level 1 · direct entityReviewed buyer or official government identity.
↓
Level 2 · transaction / productApproved business-purchase product or order evidence → B2B.
↓
Level 3 · exact Woo checkoutExact linked order: .gov, company/work domain, or personal/no company.
↓
Invoice-level B2 assignmentB2G takes precedence; hard B2B protects from B2C; Unknown remains visible.
Join at invoice-line reporting grainProduct category × buyer segment → Handi-Ramp Product × B2 summary. B2 v5 ends 2026-09-16; later sales are outside B2 coverage, not Unknown.

Read left-to-right within each lane, then downward into the reporting join. The three B2 levels are evidence-development layers; final assignment still follows the stated precedence rules.

Why product and B2 stay separate

Products identify the item sold. B2 identifies the invoiced buyer. Combining them before either is resolved would smuggle assumptions into both dimensions.

What never decides B2 by itself

Sales channel, personal name, tax status, salesperson, ship-to address, or an unapproved product cue. Those signals can prompt review, not automatic attribution.

How this becomes lead attribution later

Buyer segmentation is a revenue outcome dimension. Lead/source attribution would be a separate, later join using a deterministic order, contact, or campaign key.

Audit rule: preserve the B2 run/version, rule, and evidence source with every refresh. A later inference should never overwrite the historical basis of an invoiced result.