RevLayerIQ

Telecom architecture guide

Telecom pricing engine vs. rating engine.

Pricing, rating, charging, billing and mediation solve different problems. This guide explains where each system belongs and how the decisions connect.

Request a DemoExplore the Pricing Engine

The short answer

A telecom pricing engine determines the eligible customer-facing offer before purchase. A rating engine calculates the monetary value of measured usage events. A billing engine assembles recurring and one-time charges, balances and invoices after an offer has been selected.

These systems exchange information, but they should not be treated as interchangeable.

System-by-system comparison

System Primary responsibility Typical inputs Typical outputs
Pricing engine Determine the eligible customer-facing offer Address, market, customer, product, channel, active rules Price, promotion, term, disclosure, offer ID
Product catalog Define commercial and technical product structures Products, components, compatibility, lifecycle Approved product definitions
Mediation Collect, normalize and route usage events Network events, CDRs and usage records Validated records for rating or charging
Rating engine Calculate a monetary charge for usage Normalized usage, tariff and account context Rated usage events or charge amounts
Charging engine Authorize and apply real-time or near-real-time charges Usage request, balance and charging rules Authorization, reservation and balance update
Billing engine Maintain charges, balances and invoices Subscriptions, recurring fees, rated usage, adjustments Account balance, statement and invoice
Order management Orchestrate fulfillment of the selected offer Customer order, product and offer ID Validated order and fulfillment actions

Where the pricing engine sits

EcommerceAssisted sales
↓
Serviceability + product context
↓
Pricing engine: eligible customer-facing offer
↓
Order management → provisioning → billing
↓
Mediation → rating or charging → invoice

The architecture separates the commercial promise from the systems that fulfill and bill it. RevLayerIQ records the pricing decision and returns a unique offer ID. That identifier can travel with the selected order so downstream teams can trace what was presented without asking the billing system to recreate an earlier offer configuration.

Why the distinction matters for broadband operators

Faster commercial change

Pricing teams can update governed customer-facing treatments without embedding every decision in billing or channel code.

Clear ownership

Serviceability owns availability, pricing owns the eligible offer, ordering owns fulfillment and billing owns the account charge.

Better traceability

The offer ID connects the promise presented before purchase with order and billing workflows downstream.

Example: a new fiber acquisition offer

  1. Serviceability confirms which fiber products are available at the address.
  2. The channel sends product, market, customer and channel context to the pricing engine.
  3. The pricing engine applies rack rate, eligibility, segmentation and active promotion rules.
  4. The channel receives the complete offer and unique offer ID.
  5. After selection, order management orchestrates fulfillment and passes the treatment downstream.
  6. Billing establishes recurring and one-time charges. Rating becomes relevant only if a service includes usage-based charges.

This is why a broadband offer engine can complement an existing BSS and billing platform without replacing it.

Frequently asked questions

Is a pricing engine another name for a rating engine? No. Pricing engines decide the offer presented before purchase. Rating engines calculate charges for measured usage.

Can billing store the selected price? Yes. Billing can receive and apply the selected treatment. That does not make billing the best place to govern every pre-purchase eligibility and channel decision.

Where does mediation fit? Mediation collects, validates, transforms and routes network usage records before rating or charging. It is downstream from customer-facing offer selection.

Does RevLayerIQ replace BSS? No. RevLayerIQ is designed to fit above existing BSS, billing, CRM, ecommerce and serviceability systems as the governed telecom pricing engine.

How does this relate to omnichannel pricing? Connected customer channels can request offers from the same decision layer, creating governed omnichannel pricing without forcing each application to reproduce the rules.

Put the pricing decision in the right layer.

See how RevLayerIQ can connect customer channels to one governed broadband offer engine.

Request a Demo