Redesigning a shared purchase flow so customers could buy multiple wireless lines in a single session, removing the biggest friction point for new customers at one of Canada's largest telcos.
Buying more than one wireless line meant repeating the entire checkout for each one, with pricing that stayed unclear until late in the flow.
Mapped the dependencies of a purchase flow shared across teams, then redesigned the cart and pricing around multi-line orders, within back-end limits.
For the first time, customers could complete a full multi-line order in one session, with trade-in and eSIM flows left undisrupted.
01 — Context
Rogers Wireless is the entry point for millions of new customers, known internally as New Activation Customers (NACs), who are buying phone plans and lines. But the purchase flow had a structural gap: there was no way to buy more than one line in a single session. Each line needed its own full checkout, start to finish.
For families, small businesses, and any customer adding multiple lines, this meant completing the same multi-step flow repeatedly. The drop-off rate was significant, and pricing confusion throughout the flow was making it worse.
02 — Problem
The lack of multi-line support was eroding trust at the most sensitive moment in the purchase journey, and unclear pricing was making it worse. Two constraints shaped what a fix could look like.
Customers buying plans for a family or team had to complete the full purchase journey separately for every line. Each repetition added friction and made it more likely they'd give up before finishing.
Pricing on the site was frequently misinterpreted. Users couldn't tell what they'd actually be charged until late in the flow, which eroded trust right when it mattered most.
The purchase flow was shared infrastructure, so any change affected multiple teams and ongoing projects at once. Designing in isolation wasn't an option.
There was no existing multi-line functionality in the back-end architecture. The solution had to be grounded in what was actually buildable.
03 — Research & discovery
Because the purchase flow touched so many teams, I started by mapping stakeholder KPIs and the constraints of the existing flow structure before proposing anything. This kept us away from unnecessary design effort and toward practical, approvable solutions.
I also audited the purchase flows of Telus, Bell, Verizon, and AT&T. The finding was consistent: these platforms were bloated with marketing content at the exact moments users needed utility. Dynamic pricing was hidden until the cart stage, and cart summaries were minimal.
Shared weakness across all competitors
Every competitor prioritised promotional content at the moments users needed clarity, obscuring pricing and burying the cart under upsells.
The opportunity
Show the right information at the right moment: pricing upfront, and a cart summary that updates in real time.
After research, four changes rose above the others as the highest-impact given the constraints: multi-line entry points in the cart, a cart rebuilt to manage multiple lines, a real-time pricing summary, and transparent pricing surfaced earlier in the flow, in that priority order. Several secondary adjustments were flagged within the checkout and configuration steps, but these four were the structural fixes the experience needed most.
04 — Systemic work
Beyond individual screens, the single and multi-line flows were shared infrastructure, so a change to one had direct ripple effects on the other. I mapped these dependencies before any design decisions were locked. That meant making sure new components could handle asynchronous API failures, that existing single-line flows stayed intact, and that adjacent features (device trade-ins, eSIM activation) weren't disrupted.
I also authored documentation, usage guidelines, and contribution models so teams could autonomously adopt and build upon the system. A UI kit alone isn't enough. Teams need the context to use it correctly without depending on the original designer.
05 — Solutions
Final designs adjusted per NDA. Contact fionaqylai@gmail.com for the full case study.
The most direct fix to the repetitive checkout problem: entry points within the shopping cart letting users add additional lines without leaving the purchase flow. Customers could now build their full order in one continuous session. This single structural change eliminated the core source of friction.
The cart was rebuilt from scratch to support multiple lines. Shortcuts to duplicate, delete, and edit let customers manage a multi-line order easily. A clear entry point to add another line sits directly in the cart, so customers can keep going without leaving it.
A real-time pricing panel updating as users made selections. Users had a clear, running view of total cost at all times, removing pricing uncertainty as a reason to abandon mid-session. Seeing an accurate total in real time addressed the trust erosion that unclear pricing had been causing.
I moved pricing upstream, showing it directly on the merchandising page instead of hiding it until the cart. Users could see what each plan cost, and what they'd save by adding multiple lines, before committing to any selection. This reduced misinterpretation and gave customers a reason to add more lines.
06 — Outcomes
The redesign removed the structural gap that had been driving high-intent drop-off, and the systemic work meant teams could build on top of it without depending on the original designer.
"Adding an 'Add another line' entry point to the cart sounds simple, and structurally it was. But getting there meant mapping every stakeholder KPI and every back-end constraint first. The simplest solution took the most groundwork."
07 — Reflection
Working on shared infrastructure made it impossible to design in a vacuum. Every decision had ripple effects across teams and projects I had to account for before proposing anything. That constraint helped. It forced clearer thinking about scope, sequencing, and what "done" meant for each change.
The back-end constraint helped too. Because multi-line functionality didn't exist in the back end, we couldn't just wireframe an ideal state. We had to work directly with engineers to stress-test assumptions early and avoid late-stage blockers. That collaboration produced a better-scoped solution than UX-led exploration alone would have.