IQ Connect set out seven OSS/BSS workflows to test before launching an MVNO, covering product eligibility, activation, porting, billing, payments, inventory and commissions.
The piece frames pre-launch testing as a controlled run through the subscriber lifecycle, with failures and retries included and named owners and auditable results recorded.
Seven workflow checks
The seven workflows are product eligibility and order capture; new activation and provisioning; number port-in and port-out; rating, charging and billing; payments and reversals; SIM and eSIM and device inventory; and dealer commissions and exceptions.
The pass conditions are operational, not abstract. Orders should be accepted with a complete record or rejected with a clear reason, provisioning should capture every request, response and retry, and billing should match an independently calculated expected result.
Porting and billing controls
The article says the FCC requires secure customer authentication around number porting and SIM changes, so the port-in and port-out workflow needs to enforce that control.
It also says IQ Connect’s billing security is PCI DSS v4.0.1 compliant and assessed through a full Report on Compliance by a qualified third party.
Dealer commissions and traceability
For dealer-driven launches, the workflow test extends to eligibility rules, reversals, tiers and adjustments.
IQ Connect’s partner portal is described as linking activation records, transaction records and commission calculations so a payout can be traced back to its source transaction.
Read for MVNO launch teams
For MVNO operators, the checklist is a reminder that launch readiness lives in the handoffs: order capture, provisioning, billing, payments and commissions all have to reconcile cleanly.
That also makes the workflow list a benchmark for teams comparing OSS/BSS platforms against the same operational test.