Tiered pricing for HQ vs branch vs government vs GSA buyer, how does Magento handle it?

Magento has three layers that combine to deliver per-buyer contract pricing:

• Customer groups, the coarsest segmentation (e.g. retail, wholesale, government, gsa, abilityone). Group-level catalog price rules apply a percentage discount or fixed adjustment to all SKUs.
• Tier prices per SKU + customer group, the price book. Each SKU has a tier-price row per customer group with the negotiated contract rate. Bulk import via CSV from your contract management system.
• Catalog price rules + cart price rules, the conditional layer. “If customer is in fedgov group AND product attribute gsa_eligible = yes, apply GSA Schedule price.” “If branch buyer ordering for a different ship-to than their HQ, require HQ approval.”

For the multi-location case where HQ negotiates the contract but branches order against it: Adobe Commerce B2B Companies ships a Company structure with shared pricing inheritance (HQ price book cascades to all branches) + per-branch budgets + multi-step approval workflows. On Open Source, Aheadworks B2B Suite or Amasty Company Accounts provides 80% of the same capability for ~$2k, $3.5k one-time.

Punchout-delivered pricing overrides everything: when the buyer punches out from Coupa with their customer ID + contract ID in the cXML header, Magento applies the contract-specific price book regardless of the buyer’s standard customer group. This is how you avoid “the price on the storefront doesn’t match what Coupa shows” disputes.