
All activities described in this case study were carried out individually over the course of 6 months. This case study is a personal learning project and has no direct relationship with the Square brand or company.
Square operates in the payments and business management systems sector. This project expands that ecosystem into self-checkout, using real products as a starting point rather than an abstract
concept.
SquareUp currently operates in the payments sector but is seeking expansion by introducing a new mobile product and
transforming Square Register, an existing product, into a self-checkout system that meets customers' needs when shopping in grocery stores.
The project focuses on the phase between product selection and leaving the store.
Before making any assumptions, I needed to understand what was actually happening in retail. I started by observing customers in stores and supermarket chains across São Paulo, just observing. Then I gathered opinions from online forums, conducted a survey, carried out interviews, and mapped the entire service journey, from the parking lot to the exit receipt.
The process was not linear. Each step raised new questions that led me to the next one.

Field study
Survey
Interviews
Service Blueprint
Desk research
Personas
JTBD
MoSCoW
Heuristic Evaluation
Card Sorting
Tree Testing
Crazy 8s
Low-Fidelity Wireframes
Paper prototype
High-Fidelity Wireframes
5 Testing Rounds
Mid-Fidelity Prototypes × 3
High-Fidelity Prototypes × 4
Maze + In-Person Testing
Other techniques applied but not presented: Tree Testing, Jobs Story analysis, WCAG AA accessibility benchmarking, and comparative analysis of existing interfaces.
To understand how people feel about self-checkout before speaking with anyone, I explored online forums and communities, gathering spontaneous opinions from both Brazil and international markets.
At the same time, I conducted desk research using articles, reports, and news about the retail sector, comparing the Brazilian context with international markets.

Even with the information I had gathered, some questions remained, which led me to conduct a survey. Although self-checkout is not yet widely adopted in Brazil, the data revealed the same three recurring problems regardless of market.

I conducted direct field immersion. I observed the behavior of shoppers across three retail chains: Carrefour, Extra, and Walmart, monitoring self-checkout kiosk usage and mapping friction points in real time.
To deepen my understanding, I conducted 18 interviews with customers who had used self-checkout at least once.

I analyzed leading players to understand which ideas were worth bringing into the project.
The item identification process at Zara and Amazon Go is automatic, eliminating the need to scan products one by one.
Product recommendations and offers are displayed based on the aisle where the user is currently located.
18+ verification is handled discreetly, without requiring a visibly present employee.
Customers can search for products and be guided to their actual location within the store.

Using the journey map and service blueprint, I identified and synthesized every touchpoint and pain point uncovered throughout the research, creating a clear view of where users faced the greatest challenges.

Summary of key user needs throughout the journey
Xênia had never completed a self-checkout purchase without asking for help. She became the approval benchmark for every design decision.

The Jobs to Be Done framework revealed that users want autonomy, speed, and the ability to complete their purchases without relying on anyone else.
Separating problems into what users can control and what they cannot control was essential for defining where design could realistically help. The numbers below are referenced throughout the proposed solutions.
Problems users cannot control
Problems users can control
What can reduce unwanted touchpoints and user pain points in the self-checkout experience?
Based on a moderated Card Sorting session with 12 participants and 40 cards using Maze, I organized the navigation structure. I then conducted two rounds of Tree Testing with 14 participants using Treejack to validate the hierarchy before creating any wireframes, achieving an 85.1% direct success rate in the final structure.
With that foundation in place, I ran a Crazy 8s session with two user profiles: one person who had never used self-checkout before and another who was already familiar with the process.

In order: User Sorting, Treejack, Crazy 8s.
Before investing time in the final design, I decided to learn from potential usability issues by conducting the first round of testing using paper wireframes printed at iPhone 15 Pro size.
I tested the main app and kiosk flows using the think-aloud protocol. As participants interacted, I manually swapped the paper screens without interfering in the process.

Based on the pain points identified earlier, I designed specific solutions for each challenge. Every solution indicates where the problem was discovered and which pain points it addresses.
"I want to scan everything with my phone and leave. No lines, no conversation."
— Survey
"I prefer using a scanner that I can carry around the store while shopping."
— Desk Research
The app keeps the camera continuously active while the cart remains visible below in a single bottom sheet. When an item is scanned, it is confirmed with a spring animation that does not interrupt the flow. The camera remains visible but dimmed in the background, so users always know they are still in scanning mode.
This solution addresses pain points: 1 • 3 • 9

"The produce lookup table is awful. I never know the correct code. I give up halfway through."
— Interview, Xênia, 54 years old
"At Extra, the scale asks for a code that isn't visible anywhere."
— Field Observation
A category selection screen was introduced before the product grid. Users first choose a category and then identify the product using a high-quality image (300px). Weight is captured through the integrated scale, and the price is calculated automatically in real time.
Without this screen, 40% of participants selected the wrong product. With it: zero errors.
This solution addresses pain points: 10 • 11

"Being able to verify my age for 18+ items instead of needing an employee."
— Survey
"At Extra, an employee checks the customer's ID in front of everyone."
— Field Observation
When the system detects an age-restricted item, it offers three options: enter CPF on the kiosk, verify through the app, or request assistance. If the CPF has already been provided, verification happens automatically.
A privacy notice appears before the CPF field. Participant P5 initially refused to enter their CPF before reading that the information would not be shared. The order was changed accordingly.
This solution addresses pain points: 6 • 12

"If this were a real store, I would have called an employee. I would have been stuck there."
— Paper Test
The "The sensor didn't open" button was redesigned from a subtle 14px text link into a 52px card with an icon and sufficient contrast. Users can declare that all items were scanned, and the declaration is logged with a timestamp and session data. The exit is then released without requiring employee intervention.
This solution addresses pain points: 12

"I first clicked on Lists expecting to create one, then add items. It felt like I needed to create the list first and only then add something to it."
— Usability Test
"The app doesn't really help me while I'm shopping. I still use paper."
— Interview, Manuela, 33 years old
The app includes a dedicated list hub where users can create, edit, and activate shopping lists before leaving home. During scanning, the interface maintains two tabs: SCANNED and ON THE LIST. When an item from the list is scanned, it is checked off automatically. A progress bar provides visibility into completion status.
This solution addresses pain point: 8



App and Kiosk Prototyping
The following features were deprioritized during this project but could add value to both the product and the business in future versions.
Features (v2)
Store aisle map + shopping route guidance: requires an internal map for each store.
Loyalty program: each retail chain has its own system and would require partnerships.
Monthly budget tracking: expands the product beyond self-checkout into personal finance management.
Scalability across multiple supermarket chains: requires a store selection flow.
Retention Opportunities (Open Questions)
Could gamification increase engagement? How would it fit within the grocery shopping experience?
Could a rewards club improve retention? What types of rewards would be meaningful?
Could app adoption be encouraged through discounts? How would those incentives be managed by retailers?
Could the system suggest items based on a user's recurring purchases?
Opportunities
Creating spaces for conversation within the supermarket.
One of the project's goals was to make shopping faster. While investigating the causes of delays, I discovered that some older customers felt less lonely when talking to other people in line or interacting with cashiers. This highlights the importance of deeply understanding the problem. If I had only considered low familiarity with technology, this pattern would never have surfaced.
Scalability Across Supermarkets
The system was initially designed for a specific supermarket. To scale across multiple retail chains, it would be necessary to introduce a flow that allows users to select their current store. This model could then be expanded to additional supermarkets, enabling more people to use the service.
ROLE
Product Designer
DATE
February 2026 - June 2026
TOOLS
Figma · Miro · Google Forms · Optimal Workshop · Treejack · Maze
INDUSTRY
Self-Checkout