Workflow under pressure · Toko Mama

Improving Hold Cart in a High-Traffic POS

When a cashier puts a transaction on hold, it shouldn't disappear into the system. It should stay easy to find, easy to resume, and never interrupt the checkout flow.

Client
Toko Mama
Role
Sr. Product Designer
Platform
Tablet POS
Constraint
No formal training
Toko Mama POS · Cashier Interface

A high-traffic store with
no room for confusion.

Toko Mama is a convenience store franchise in Indonesia where checkout speed directly affects customer experience. During busy hours, interruptions are part of the workflow. Customers forget items, change their payment method, or step away before completing a purchase. Cashiers need to pause one transaction, serve the next customer, then return without losing progress. A reliable Hold Cart feature wasn't just a convenience. It was essential to keeping the checkout line moving.

Toko Mama · a high-traffic checkout
User Profile
These cashiers aren't navigating software for fun. They're talking to customers, handling cash, and scanning items all at once. The tool had to work with them, not slow them down or make them think twice.
The Business Need
The business needed a way for cashiers to temporarily set aside a transaction without disrupting the queue. Resuming a cart had to feel immediate, predictable, and reliable, even during the busiest hours.
Design Constraint
Training was informal, usually just a manager showing the ropes on day one. There was no onboarding document, no structured walkthrough. Whatever we built had to make sense immediately, without explanation.

Saved, but lost.

The Hold Cart feature worked, technically. But the moment a cart was saved, it vanished from the screen. The interface reset to an empty state with no visible indication that the transaction still existed. The action succeeded, but from the cashier's perspective, the cart simply disappeared.

A temporary confirmation appeared, but once it disappeared, there was no visible sign that the saved cart still existed.

The cart disappears from the screen.
The interface resets to an empty state.
There is no visible indicator of where the cart is stored.

Why the Recall button didn't work: There was already a "Recall Draft" button, but it depended too heavily on memory. The label wasn't immediately clear, it provided no indication that a saved cart was waiting, and it only helped if the cashier remembered to look for it. Instead of supporting the workflow, the interface expected the cashier to remember something it should have made visible.

Direction: make it visible.

The Hold Cart feature itself wasn't failing. The problem started after the action was complete. Once a saved cart disappeared from view, cashiers had to rely on memory instead of the interface, and that became increasingly unreliable during busy checkout hours.

Rather than redesigning the workflow, I focused on changing the visibility of the interaction. If saved carts remained visible within the checkout experience, cashiers could immediately understand what was waiting without having to remember where it went.

Making saved carts visible.

When a cart is placed on hold, it remains visible as a tab at the top of the checkout screen instead of disappearing. This keeps every active transaction within sight, allowing cashiers to switch between carts without searching or relying on memory. Rather than introducing a new workflow, the design builds on the existing checkout experience by making saved carts continuously visible.

Saved carts remain visible throughout checkout, making it easy to switch between transactions without losing context.
No need to remember saved carts
No searching through hidden menus
Clear overview during peak traffic

What I owned, and why.

My Role
Reviewed the initial Hold Cart proposal and identified opportunities to improve the checkout workflow.
Identified usability risks that relied too heavily on cashier memory during busy transactions.
Proposed a visibility first interaction that kept held carts accessible throughout checkout.
Refined interaction states and edge cases before engineering handoff.
Design Considerations
Balanced business constraints by supporting up to three active Hold Cart sessions without overwhelming the interface.
Used a familiar tab based interaction to make switching between carts feel immediate and intuitive.
Prioritized operational clarity in fast paced checkout environments where interruptions were routine.

Clarity over complexity.

By keeping held carts visible throughout checkout, the interface no longer relied on cashier memory. In a fast paced retail environment where interruptions are constant, that meant cashiers could recover and continue transactions with greater confidence. As a result, they could:

See all active sessions at a glance
Switch between carts instantly
Continue transactions without searching

Held carts remain visible, making it easy to resume transactions and continue checkout without losing context.

The workflow becomes easier to recover from, even during busy checkout periods.

Reflection
Small visibility changes can have a large impact in high-pressure environments. Design decisions should reduce thinking, not add it.
Keep exploring

More work

Let's talk

Like what you see?