COS Wholesale Engine

The wholesale layer between fiber networks and the ISPs that sell on them.
Multi-ISP, multi-vendor, and M&A-ready.

COS Wholesale Engine is the layer between fiber networks and the ISPs that sell on them. One infrastructure operator runs several service providers on shared infrastructure, with full automation and subscriber visibility. As wholesale broadband software, it covers the full wholesale layer: service locations, multi-vendor provisioning, cross-operator ticketing, and per-ISP invoicing.

API-first wholesale layer

Built for wholesale. Ready for Open Access and M&A

Standards-oriented integration layer (REST APIs), enabling ISPs to plug in their own BSS/OSS and support/NOC systems.

This solution is also a strong fit for mergers and acquisitions (M&As), serving as the wholesale layer across disparate tech stacks, allowing operators to integrate acquired networks faster and more cost-effectively, and to keep acquired ISPs’ customer-facing tech stacks in place for migration over time.

The Typical Wholesale Engine Customer

  • Open access/wholesale operators with fiber or fixed wireless infrastructure
  • ISPs with an M&A strategy, consolidating ISPs, or operating multiple brands
  • Operators of multi-technology/vendor networks seeking unified operational processes

What COS Wholesale Engine does

A single wholesale layer for locations, services, provisioning, ticketing, and wholesale billing

Service locations and coverage

  • Service locations & build lifecycle

    Areas, address/service locations, and deliverability rules are provided as the single source of truth that ISP partners use to sell and operate.

  • Service qualification for partner ISPs

    Automated qualification against serviceable addresses and available products. Partner ISPs know what can be sold before an order is raised.

  • Geospatial intelligence at national scale

    Address and network data at national scale supports qualification, build planning and partner reporting, without a separate GIS query layer.

Provisioning and installation

  • Zero-touch provisioning & multi-vendor support

    EMS/NMS integrations allow multiple EMSs to be controlled in parallel—ideal for operators using several technology vendors or for avoiding rip-and-replace in M&A scenarios.

  • Appointment and installation scheduling

    Installation slots are coordinated across operator, contractor and ISP. Confirmations return to the ordering partner automatically.

Incidents and operations

  • Disruptions & ticketing for cross-organization collaboration

    Built for fast incident handling, escalation, and communication between the network operator and participating ISPs.

  • Structured audit & activity timeline

    A complete record of what changed, when it changed, and which system triggered it. Every order carries its own history.

Integration and settlement

  • Standardized integration layer (APIs)

    ISPs’ BSS/OSS tech stacks integrate via a standards-oriented integration layer (REST), with straightforward API extensions when needed.

  • Integration transparency & API diagnostics

    Every call, payload and failure between connected systems is visible. Faults are traced to the system that caused them.

  • Wholesale broadband billing with automatic accuracy

    Billing is generated from live order activations. Data is aggregated monthly per ISP

  • Enterprise reporting & data export

    Role-based reporting with structured export into finance, BI and partner systems. No manual extraction between organizations.

imageFiber network datacenter supporting multi-operator wholesale broadband infrastructure

M&A Readiness

ISP Consolidation Is Accelerating. The Bottleneck Is Usually the BSS/OSS Stack.

Private equity is rolling up regional ISPs. Municipalities are acquiring last-mile assets. Tier 1 operators are entering new markets through acquisition rather than greenfield build. Every deal creates the same operational problem: two networks, two subscriber bases, two billing systems, and one deadline to make it work.

The default answer is rip-and-replace. Published integration timelines run from 7 to 20 months. The plans are usually too optimistic. And the revenue risk is real: forced migrations trigger churn at exactly the moment synergies are supposed to emerge.

The same pattern is running in the UK. More than 100 altnets built competing full fibre networks; around 80 still operate. Ofcom’s 2026 Telecoms Access Review puts altnet take-up near 18 percent, against roughly 38 percent for Openreach. nexfibre agreed to acquire Netomnia for GBP 2 billion, and the CMA referred the deal to a Phase 2 inquiry with a statutory decision deadline of 15 December 2026. Overbuild pressure is forcing consolidation faster than the systems underneath can absorb it.

The smarter path is to separate where you take cost from where you protect revenue.

One wholesale layer. No forced migration.

COS Wholesale Engine sits above acquired networks as the wholesale layer. The acquired ISP keeps its brand and customer portal. Its billing stack keeps running. COS manages service locations, provisioning, wholesale billing, and cross-organization incident handling across every entity in the portfolio.

Multiple ISPs and brands operate on the same infrastructure simultaneously. Multiple EMS/NMS systems run in parallel via a standards-oriented REST API. System consolidation happens in controlled phases — on your timetable, not a migration vendor’s.

For ISP Executives

Acquired customers stay on a known experience. Churn risk during the transition window drops. Local brand equity — built over years — stays intact and keeps generating revenue.

For Operations and Build Teams

Multiple EMS/NMS systems run in parallel under one wholesale layer. Multi-vendor infrastructure is an operational asset, not a liability. No rip-and-replace required to unify NOC and field operations.

For Investors and Portfolio Operators

Profitability rises twice: first from revenue retention and cross-sell across all brands, then from phased system consolidation that methodically lowers unit costs. Wholesale billing is generated from live activations — auditable and accurate from day one.

ISP Consolidation Success — Whitepaper

How to capture cost synergies without destroying the brand equity and customer loyalty that drive revenue. Covers the architecture decisions, integration sequence, and the case for a revenue-first consolidation thesis.

Download the Whitepaper

Fiber optic cable infrastructure managed by COS Wholesale Engine BSS/OSS

Why choose Wholesale Engine?

Why Operators Choose Wholesale Engine

  • Separation of Infrastructure and Customer Operations

    Traditional telco stacks are vertically integrated. COS Wholesale Engine enables clean separation while keeping both sides fully synchronized.

  • Enables Cross-Selling

    Multiple ISPs can be active in any market with no risk of syncing errors or clashes. In M&A scenarios, all brands can remain active, maximizing take-rates across selected or all markets.

  • Reduced Time to Market

    By allowing most systems to remain intact during M&A consolidation, integration time is dramatically reduced. BSS systems can be consolidated gradually if desired.

  • Fewer wholesale billing disputes

    Clear, auditable wholesale invoicing aligned to activations removes the most common source of billing friction, and makes free riders visible.

Ready to run a multi-ISP network without the integration penalty?

COS Wholesale Engine is in production across open access networks, wholesale carriers, and post-M&A broadband operators in North America and Europe, including large-scale wholesale operators covering more than 4 million passings. COS Systems has been ISO 27001 certified since May 2026. It handles the wholesale layer — so you can add ISPs, absorb acquisitions, and scale take-rates without replacing what’s already working.

“COS Wholesale Engine gives us the operational foundation to support our wholesale model and accelerate market launches with major service providers.”

Rob Johnson, CTO, PRIME FiBER. A COS customer, PRIME FiBER runs COS Wholesale Engine in production for its Sun City, Arizona expansion. AT&T sells retail service on that network. Tier 1 retail, on a COS-powered network.

Book a demo to see how it maps to your network architecture and business model.

Frequently Asked Questions

What is COS Wholesale Engine?

COS Wholesale Engine is a BSS/OSS platform for infrastructure operators running open access networks, wholesale fiber, or multi-ISP environments. It manages service locations, zero-touch provisioning, cross-operator ticketing, and wholesale billing across multiple service providers on a single shared infrastructure — via a standards-oriented REST API that connects to each ISP’s existing tech stack.

How does COS Wholesale Engine support ISP mergers and acquisitions?

COS Wholesale Engine acts as the wholesale layer across disparate BSS/OSS stacks. In an M&A scenario, the acquired ISP keeps its customer portal and billing systems running. COS sits above them as the operational spine — handling provisioning, service locations, and wholesale billing across all entities. BSS consolidation happens in controlled phases, on the operator’s timeline, which eliminates the churn and revenue risk that comes with forced Day-1 migrations.

What is the difference between COS Wholesale Engine and COS Business Engine?

COS Business Engine is designed for retail ISPs managing their own subscriber base — it covers the full customer lifecycle from signup through billing and support. COS Wholesale Engine is designed for infrastructure operators who provide network access to multiple ISPs. It manages the wholesale layer: service locations, multi-provider provisioning, cross-operator ticketing, and wholesale invoicing. Operators typically run one or the other based on their business model, though some open access operators use both.

Does COS Wholesale Engine require replacing existing ISP billing systems?

No. COS Wholesale Engine connects to existing ISP BSS/OSS platforms via REST API. Each service provider on the network retains its own billing stack and customer-facing systems. COS manages the infrastructure and wholesale layer above them. This is specifically designed for M&A scenarios and multi-vendor environments where rip-and-replace is operationally and financially impractical.

How does wholesale billing work in COS Wholesale Engine?

Wholesale billing is generated directly from live order activations, not from manual data entry or reconciliation. This means invoices are accurate by default and aggregated monthly per ISP. There are no billing disputes caused by timing gaps between activation and billing records — the data source is the same for both.

What network technologies and vendors does COS Wholesale Engine support?

COS Wholesale Engine supports multi-vendor and multi-technology networks. Multiple EMS/NMS systems can be controlled in parallel through the platform, which is designed for operators running fiber, fixed wireless, or mixed-technology infrastructure across different vendors. This hardware-agnostic architecture removes vendor lock-in and is specifically suited to post-M&A environments where acquired networks run on different equipment.

Can an acquired ISP keep its own brand and customer portal?

Yes. COS Wholesale Engine sits above the acquired network as the wholesale layer. The acquired ISP keeps its brand, its customer portal and its billing stack. COS manages service locations, provisioning, wholesale billing and cross-organization incident handling. No subscriber is migrated at cutover.

How long does it take to integrate an acquired network?

Published integration timelines for UK altnet transactions run from 7 to 20 months, and the cost lands after the deal closes. COS Wholesale Engine shortens that by separating operational consolidation from subscriber migration. Systems consolidate in controlled phases while subscribers stay where they are.

What should wholesale broadband software include?

Wholesale broadband software should manage 4 functions on one data model: service locations and deliverability, provisioning across vendors, cross-operator ticketing, and activation-based wholesale billing. Splitting these across separate tools creates the sync errors and billing disputes that wholesale operators know well. COS Wholesale Engine integrates all 4 behind a standards-oriented REST API.