Skip to content

Reimagining a 25-year-old POS and retail management platform.

Role
Design Lead
Outcome
A 25-year-old retail platform needed to be retired. I led the design of the new platform, including the mobile POS, the end-to-end experience for orders, as well as security and permissions. I also designed a prototype to demonstrate the vision for the retail management platform.
Storefront design of the orders list beside one open order. In the list, finished orders have a plain Paid or Refunded label, one order has an orange Partially paid label, and an online order has Paid and a teal Waiting for pickup label. The open order shows its two items waiting for pickup and its total.

The problem

Our legacy platform, RQ, needed to be rebuilt. The data storage costs were going to balloon in 2027 and we found ourselves unable to innovate. Every new feature took months to deliver, and was risky due to the complexity of a system built over 25 years.

The research

Over the years, I had done extensive user research and captured many points of user friction, or business friction. The main issues I’ll discuss in this case study are:

Wireless retailers did not want their sales people to be tied behind a desk. They wanted to have more flexibility with the experiences in their stores, which meant sales staff could walk around and engage with their customers, and then complete the transaction from anywhere in the store. They also wanted choice in the hardware they could operate with. For example, Samsung would never use an iPad.

The legacy platform was built piece by piece. It started with sales, and then orders, quotes, and returns. Each of these was built as a separate workflow, which made it 4 times the work if we wanted to change the payment experience, or the experience for adding products. It also made the backend extremely complicated as everything was pieced together over the years. Add the carrier integrations into the mix, and you can see how it was brittle, and needed to be completely redesigned for the modern POS. This was one of the most significant pieces of research I completed. It required understanding all of the various order types (in-store, dropship, buy online, pick up in store, reserve online, pick up in store etc). It also needed to cleanly map to states like open, in progress, and complete, and within that the status of several fulfillment and payment statuses.

QuoteIts own workflowOrderAnother workflow, saved on its ownSaleHas to be finished once startedRefundA separate workflow againCustom workBuilt on top, customer by customerExtra clicks to become a sale
In the old POS, quotes, orders, sales, and refunds lived in separate silos. Turning an order into a sale took unnecessary steps, and custom patches were stacked on top for different clients over time.

The last piece of research referenced in this case study is the carrier activation flow. Activations were one of the most frustrating and time-consuming parts of the checkout process in RQ. Because of a legacy integration with carriers, reps had to navigate cluttered screens and manually re-key customer details that had already been collected. Knowing that this was a critical part of the wireless retailers’ workflows, we had to get it right in the new POS. I asked one of my senior designers to work through the end to end experience, and share user journeys and flows starting in the carrier activation platform, ending in our POS and retail platform.

Decisions and trade offs

  1. We decided to build Storefront, a new POS for wireless retailers. Our timelines were aggressive, so once the tech team decided that they wanted to build with Flutter, I decided that the component library we would use would be Google Material Design 3. I decided that we should build using the default component styles, and handle styling the app once we decided on the new brand. This allowed our small design team of 3 to move quickly, and follow the design system patterns that were defined by Google. The app had a very Google look and feel, but the trade off allowed us to hit our timeline to launch Storefront on stage to our clients at SummitX.

  2. I decided the order UX had to be scalable and flexible to support a single experience. Every transaction ultimately lands in one of three outcomes: open, complete, or cancelled. Whether an item was paid for, picked up, or partially refunded was just a state within one transaction. We needed one flexible core model that could handle those details as layers on top. I defined that order model, and our team built the entire user experience around it. The development team built the new platform's data model on it. Every part of the company's software, from the point of sale to retail management, runs on orders, so that model became the foundation of the entire redesign.

  3. While the UX work was completed by one of my senior designer team members, I was ultimately responsible for the user experience for the new activation UX. I approved his design, which resulted in a 60% reduction in steps, reducing the POS transaction time by minutes compared to the legacy platform.

RQ's Quick Sale screen with the Phone Activation Wizard open on its Plan Details step: fields for the device, ESN or IMEI, term, rate plan, SOC code, phone number and contract number, with Cancel, No Term, Start Over and Next. Across the top of the sale, separate buttons for a refund, trade-ins, add-ons and bill payments.
Before: RQ's phone activation wizard, a form of fields the rep filled in by hand.
Storefront design of the Import activation panel over a new order: four carriers to choose from, Rogers selected, an activation number entered, and an Import button.
After: in Storefront, the rep picks the carrier and enters one activation number.

The work

A POS for any device

We designed and built a POS that can be installed and used on any device on any platform. iOS, Android or Windows. Phones, tablets or computers. I decided on the UX patterns for the overall app experience, while my team handled the specific interactions like the carrier activation flow, adding products to a cart, or adding a customer etc.

One experience for every order

I designed the experience for orders, and how and when they move between the different states and statuses. This was a project that was highly collaborative with the tech team to ensure that we covered every edge case in our legacy software, ensuring that our one workflow could support in-store, buy or reserve online and pick up in-store, dropship, and of course full or partial returns and refunds.

Where it startsIn store, online, dropship or repairOne transactionOpen until it endsOn the same transactionPaid, fulfilled or refunded, or notHow it endsComplete or cancelledDetails, not separate workflows
A sale can begin anywhere: in store or online. It stays open while details like payment and fulfillment are completed, then closes as complete or cancelled.

Retail management vision prototype

In addition to the POS work, I also designed a prototype of the retail management platform, which included an AI first experience for inventory management, AI powered insights and guidance, as well as an experience for customers and partners to design and build their own apps within our ecosystem. This included an app store, and an admin area for billing, security, permissions, and app management within their ecosystem.

Hub design of the inventory dashboard, with charts of stock levels over time, low stock alerts by region and aging inventory value, then inventory turnover, in-transit inventory and inventory variance by store.
Visual inventory dashboard displaying stock levels over time, low stock alerts by region, and aging inventory.

Outcome

Our product and tech team reached our goal of completing the MVP on tight timelines to launch at SummitX, and allow our biggest clients to experience the app on their own in our “store of the future” interactive experience.

I completed the vision for the retail platform, and presented it to our clients on stage at SummitX. We successfully communicated the future direction of where we wanted to go, specifically around retail management AI experiences, data and insights, and AI chat experiences where the user can engage with the system using chat to articulate their questions and objectives. You can see this vision showing up on the marketing material the company is sharing, and the point of view they are expressing about the future of retail management and AI.

When I left, the company was actively working on new POS features while we began testing the new POS in real stores.

What I would do differently

Because timelines were so tight, we were unable to do usability testing in a real retail environment. We did test flows with internal users, and employees that had not seen the flows before, but we were unable to test poor internet connections, how the experience worked when a sales rep and customer were not behind a desk, or at a booth, or a technician selling services at a client’s house etc.