A feature list tells you what a platform claims to contain. An end-to-end workflow test shows whether your MVNO can actually take an order, activate service, collect revenue and resolve exceptions.
The best pre-launch test is a controlled run through the subscriber lifecycle, including failures and retries — with named owners and auditable results. These are the same seven workflows IQ Connect’s OSS/BSS Platform is built to handle, so they double as a useful checklist regardless of which platform you’re evaluating.
The Seven Workflows at a Glance
| Workflow | Pass Condition |
|---|---|
| 1. Product eligibility & order capture | Order accepted with a complete record, or rejected with a clear reason |
| 2. New activation & provisioning | Every request, response and retry captured end-to-end |
| 3. Number port-in / port-out | Secure authentication enforced on every porting and SIM change |
| 4. Rating, charging & billing | Charges match an independently calculated expected result |
| 5. Payments & reversals | A failed payment triggers the correct grace period automatically |
| 6. SIM/eSIM & device inventory | Every item has a controlled, auditable lifecycle |
| 7. Dealer commissions & exceptions | A payout can be traced back to its source transaction |
1. Product Eligibility and Order Capture
Confirm the same product, price, taxes and promotions appear across every sales channel. Test invalid addresses, incompatible devices and expired promotions. Pass condition: the order is accepted with a complete record or rejected with a clear reason.
2. New Activation and Service Provisioning
Test the full path from approved order to usable service, including SIM/eSIM assignment and network profile confirmation. Capture every external request, response and retry.
3. Number Port-In and Port-Out Protection
Test correct and incorrect account information, pending requests and escalation. The FCC requires secure customer authentication around number porting and SIM changes — confirm your platform enforces this.
4. Rating, Charging and Billing
Validate recurring charges, usage rating, proration and refunds against an independently calculated expected result. If a platform is described as “real-time,” ask for the specific triggering event and measured latency rather than accepting the term at face value. Ask, too, whether the billing engine’s security posture has been independently verified — IQ Connect’s, for example, is PCI DSS v4.0.1 compliant, assessed through a full Report on Compliance by a qualified third party, not just a self-declared claim.
5. Payments, Reversals and Service Consequences
Test successful and declined payments, refunds and auto-pay expiration, and confirm the downstream service state updates correctly — a failed payment should trigger the right grace period and notification automatically.
6. SIM/eSIM and Device Inventory
Each SIM, eSIM allocation and device should have a controlled lifecycle. Test transfers, damaged stock and duplicate scans.
7. Dealer Commissions and Exception Handling
If selling through a dealer channel, test eligibility rules, reversals, tiers and adjustments. The activation record, transaction record and commission calculation should be linked so a payout can be traced back to its source — a platform with a built-in partner portal, like IQ Connect’s, is designed to link these records automatically rather than requiring a manual reconciliation step.
How to Run the Test
- Create a test matrix covering normal, boundary and failure cases.
- Assign a business owner and technical owner to every workflow.
- Reconcile platform records against payment and finance records.
- Repeat critical tests after every material integration or configuration change.
The Takeaway
A launch-ready MVNO platform isn’t defined by a feature list — it’s defined by these seven workflows holding up under real conditions, including the failure cases most demos skip. IQ Connect’s OSS/BSS Platform is built around exactly this standard, from independently verified billing security to a partner portal that keeps commission records traceable by design rather than by manual reconciliation.
Frequently Asked Questions
Which OSS/BSS workflow causes the most launch delays?
Activation and port-in handoffs, because they depend on external carrier systems and require careful exception handling.
What does “real-time” actually mean in an MVNO platform?
It should specify the triggering event, expected latency, and behavior during an upstream delay — ask any vendor to document this.
How often should these workflows be retested?
After every material integration, configuration or carrier change — not only before initial launch.
Contact IQ Connect
Email: [email protected]
Hours: 8:00 AM – 5:00 PM EST
Phone (Main): (888) 795-4808
Phone (Local): (786) 292-8488