Skip to main content
BSS/OSS Academy
🏗️
Section 1.6

B2C vs B2B: One Platform, Two Models

Last updated 14 Oct 2026

B2C and B2B are two different commercial models that often run on the same BSS technology. A consumer buys one plan for themselves; an enterprise negotiates a contract that governs hundreds of services across legal entities, sites, and cost centres. The platforms — CRM, CPQ, Product Catalog, Service Catalog, COM, SOM, Inventory, Billing — can be shared, but the operating model, data model, catalog structure, order flows, contract logic, and billing complexity differ significantly.

Rule of thumb
Share the technology platform, separate the business models. Reuse the same engines, but keep product models, customer models, contract models, pricing, order flows, billing rules, SLA models, and approval workflows distinct for B2C and B2B.

B2C BSS assumes a single person, single account, single bill. B2B breaks every one of those assumptions. Enterprise customers are complex organisations with hierarchies, contracts, negotiated pricing, approval workflows, and multi-site deployments. Treating B2B like B2C — or retrofitting a consumer stack — is one of the costliest mistakes in telco transformation.

B2C — Simple & FlatB2B — Hierarchical & Contract-DrivenCustomerIndividual PersonAccountSingle, FlatBillSingle MonthlyOrdering: Cart-FirstBrowse → Add to Cart → CheckoutPublished catalog prices, instantApprovals: NoneSingle user, instant transactionProvisioning: Minutes → HoursFully automated activationEnterpriseTop-Level OrgLegal Entity AContracting BodyLegal Entity BContracting BodyBilling Acct 1Invoice RecipientBilling Acct 2Cost CentreBilling Acct 3Site-LevelOrdering: Contract-FirstNegotiate → Sign Agreement → Order Against ItNegotiated pricing, SLAs, volume commitmentsApprovals: Multi-LevelQuote → Order → Contract → Spend thresholdProvisioning: Days → WeeksFeasibility, site survey, phased rollout

B2C vs B2B — The structural differences that make enterprise BSS fundamentally different

B2C: flat and instant. B2B: hierarchical, contract-governed, and multi-step.

B2C vs B2B: Side-by-Side

B2C vs B2B BSS — Key Dimensions

DimensionB2CB2B
CustomerIndividual customerCompany with account hierarchy
Sales cycleShort, self-serviceLonger, sales-assisted
ProductsStandardised offersConfigurable solutions
PricingSimple, publishedNegotiated, contract-specific
ContractsBasic click-wrap termsComplex contract management (CLM)
Order flowSimple, single orderCommercial order decomposition
BillingSingle-account billingParent-child / multi-account billing
InventorySIM / device / subscriptionMulti-site / multi-vessel / multi-service
ApprovalsMinimal workflowMulti-level approval workflows
SLAStandard SLA modelCustomer-specific SLA commitments

The Two Flows

The clearest way to see the difference is to follow an order end to end. B2C collapses to a handful of automated steps. B2B inserts CPQ, CLM, and a commercial-then-service order decomposition, then tracks the result in the customer install base before billing.

B2C Flow — Simple & StandardisedB2B Flow — Configurable & Contract-DrivenCustomerIndividualCRMAccount & ContactProduct SelectionStandard offerOrder CaptureSingle orderProvisioningAutomatedBillingSingle billCompany / AccountHierarchyCRMOrg & rolesCPQConfigure & priceCLMContract lifecycleCommercial Order (COM)DecompositionService Order (SOM)FulfilmentService InventoryInstall baseProvisioningPhased rolloutBillingParent-child

B2C order-to-cash is short and standardised. B2B adds CPQ, CLM, commercial and service order decomposition, and install-base inventory.

B2C: Customer → CRM → Product Selection → Order Capture → Provisioning → Billing. B2B: Company → CRM → CPQ → CLM → COM → SOM → Provisioning → Service Inventory → Product Inventory/SLM → Billing.

Enterprise Account Hierarchies

B2C has a flat customer model. B2B requires a deep hierarchy representing the enterprise structure: Enterprise (top-level org) → Legal Entity (contracting body) → Billing Account (invoice recipient) → Sub-Account (department, cost centre, or site). Getting this wrong means billing disputes, misrouted orders, and broken SLA reporting. APIs: TMF666 (Account Management) for hierarchy, TMF632 (Party Management) for organisation and contact roles.

Ordering follows the hierarchy too. B2C is cart-first: browse catalog, add to cart, checkout at published prices. B2B is contract-first: negotiate terms, sign a framework agreement, then place orders against it over months or years. The contract — not the cart — defines pricing, SLAs, volume commitments, and special conditions, and every order must conform to those terms.

Why CPQ Is More Critical in B2B

B2C products are usually standardised — pricing is published and a checkout is enough. B2B products often require configuration, pricing rules, discounts, customer-specific approvals, sites, services, SLAs, and contract alignment. CPQ exists to answer one question precisely: "What are we selling, to whom, and at what price?" — and to do it under commercial governance.

Go deeper
Solution-level quoting, feasibility checks, multi-model pricing, and approval chains are covered in detail in Module 5 — CPQ, Pricing & CLM.

Top 5 Differences

  • Account model — B2B has account hierarchies; B2C has individual customers.
  • Commercial tooling — B2B requires stronger CPQ and CLM; B2C rarely needs either.
  • Order management — B2B order management is more complex (decomposition, multi-site, approvals).
  • Inventory / SLM — B2B install-base inventory is critical for support, billing, and renewals.
  • Billing — B2B billing is contract-driven and customer-specific; B2C is single-account.