Orange is launching Quality on Demand API with traffic prioritization in early access

Most digital services are still built on an implicit assumption: mobile connectivity is “best effort.” It works, until the exact moment where performance becomes the product: a live interaction, a mission-critical field workflow, or a latency-sensitive session where a few seconds of degradation translate into drop-offs, churn, or operational incidents. With Quality on Demand, Orange is turning network performance into an application-controlled capability, requested only when it matters and released when it doesn’t.

What is launching in Spain (and why it matters)

In July 2026, MasOrange will launch an early access implementation of Quality on Demand focused on a first, pragmatic capability: traffic prioritization. For product and engineering teams, the promise is concrete: when your user enters a critical step, your application can request a time-bounded QoS session to prioritize traffic between the user’s device and your application server, using two QoS profiles: High and Medium. This is not “always-on premium connectivity.” It’s a controlled uplift designed for moments where the business outcome is decided, finishing a transaction, completing a remote assistance session, or ensuring continuity in an operational workflow.

Use cases: where quality of service becomes a measurable business lever

The strongest use cases are the ones where performance variability creates direct, measurable loss and where you can clearly isolate the “critical minutes” worth prioritizing. In gaming and immersive experiences, a short latency spike can ruin a match and trigger churn; QoD lets platforms protect competitive sessions, tournaments, or paid premium moments. In live video and real-time collaboration (remote expert assistance, inspections, incident response), the uplink is often the weak point: a frozen frame or audio drop is not just poor UX, it’s a failed intervention QoS traffic prioritization can be activated for the duration of the call, then stopped automatically. In industrial and field operations, prioritizing connectivity during task execution (startup of a connected procedure, remote control, critical telemetry windows) reduces failed jobs, repeat dispatches, and support escalations. The common pattern is simple: activate QoS only for the step that drives revenue, safety, or SLA, and treat it as a product control (like fraud checks or payment authorization) rather than as a network hope.

What is Quality on Demand API enabling now

Festival payments using token systems

Prioritize the validation and payment confirmation flows at peak times (bars, top‑up points, entry gates). This keeps queues moving by reducing retries and transaction failures caused by congestion.

Industry 4.0

Trigger QoD when a human operator takes remote control of an autonomous vehicle (parking/platooning). Prioritizing control and telemetry flows improves responsiveness and stability during the takeover window.

Scooter/bike rentals

Use QoD for the few seconds around unlock and payment confirmation to improve reliability in dense city areas. Fewer failed starts means fewer support contacts and churn moments.

Conclusion

The Spain launch of Quality on Demand marks a practical shift: applications can stop treating network performance as an uncontrollable variable and start treating it as an on-demand capability, via QoS traffic prioritization (High/Medium) in July 2026 early access, then enhanced offers and availability on additional markets by the end of 2026.