Password required
Voyix Checkout Kit
A blueprint for cross-product coherence and improved collaboration across Voyix point-of-sale teams
2025
Design Systems
Touchscreen Kiosk

Voyix Checkout Kit
A blueprint for cross-product coherence and improved collaboration across Voyix point-of-sale teams
2025
Design Systems
Touchscreen Kiosk

Voyix Checkout Kit
A blueprint for cross-product coherence and improved collaboration across Voyix point-of-sale teams
2025
Design Systems
Touchscreen Kiosk

Overview—
I authored a proposal for greater alignment across NCR Voyix’s numerous point-of-sale products, outlining shared benefits for all teams and a strategy for incremental adoption. The proposal served as a lever for foundation-level consolidation of retail POS systems and teams in 2026.
Overview—
I authored a proposal for greater alignment across NCR Voyix’s numerous point-of-sale products, outlining shared benefits for all teams and a strategy for incremental adoption. The proposal served as a lever for foundation-level consolidation of retail POS systems and teams in 2026.
Overview—
I authored a proposal for greater alignment across NCR Voyix’s numerous point-of-sale products, outlining shared benefits for all teams and a strategy for incremental adoption. The proposal served as a lever for foundation-level consolidation of retail POS systems and teams in 2026.
The challenge—
From many, one?
Following the 2023 spin-off of the software-focused NCR Voyix, leadership signaled that product unification and standardization would be top priorities. Decades of POS UI efforts across numerous industry verticals had produced an array of insular systems, unpredictable cross-product experiences and significant barriers to collaboration between internal teams. The challenge: how might we reset baseline UI standards for design and dev teams in a way that would ensure unified, maintainable and coherent experiences for our customers?
From many, one?
Following the 2023 spin-off of the software-focused NCR Voyix, leadership signaled that product unification and standardization would be top priorities. Decades of POS UI efforts across numerous industry verticals had produced an array of insular systems, unpredictable cross-product experiences and significant barriers to collaboration between internal teams. The challenge: how might we reset baseline UI standards for design and dev teams in a way that would ensure unified, maintainable and coherent experiences for our customers?
The challenge—
From many, one?
Following the 2023 spin-off of the software-focused NCR Voyix, leadership signaled that product unification and standardization would be top priorities. Decades of POS UI efforts across numerous industry verticals had produced an array of insular systems, unpredictable cross-product experiences and significant barriers to collaboration between internal teams. The challenge: how might we reset baseline UI standards for design and dev teams in a way that would ensure unified, maintainable and coherent experiences for our customers?




POS variants across grocery, fuel and restaurant verticals had been developed by separate teams with unique customer requirements in mind. The experience layer was valid, but no two POS UIs shared the same design system.
The core recipe
By mid-2025, NCR Voyix had been operating without a formal design systems team for almost two years, further hampering POS unification goals. Though fully occupied with another project, I put some evenings and weekends towards a Q3 2025 presentation and set of demos to socialize and advocate for a strategy of incremental unification. The core elements: shared design tokens, shared core components and adaptable, shared patterns.
The core recipe
By mid-2025, NCR Voyix had been operating without a formal design systems team for almost two years, further hampering POS unification goals. Though fully occupied with another project, I put some evenings and weekends towards a Q3 2025 presentation and set of demos to socialize and advocate for a strategy of incremental unification. The core elements: shared design tokens, shared core components and adaptable, shared patterns.
The core recipe
By mid-2025, NCR Voyix had been operating without a formal design systems team for almost two years, further hampering POS unification goals. Though fully occupied with another project, I put some evenings and weekends towards a Q3 2025 presentation and set of demos to socialize and advocate for a strategy of incremental unification. The core elements: shared design tokens, shared core components and adaptable, shared patterns.
1. Shared tokens
A detailed directory of foundational design decisions
2. Shared components
Core components shared by all POS applications
3. Shared patterns
Trusted and tested interaction patterns
Universal design tokens
Some POS products hadn’t yet adopted design tokens as a source of truth, while others had already made the leap. No two products referenced the same token set. All existing token libraries were limited to overwrites and additions to Material UI core tokens. A foundational element of my proposal was a library of universal design tokens, intended to set a baseline any product using any front-end framework.
Universal design tokens
Some POS products hadn’t yet adopted design tokens as a source of truth, while others had already made the leap. No two products referenced the same token set. All existing token libraries were limited to overwrites and additions to Material UI core tokens. A foundational element of my proposal was a library of universal design tokens, intended to set a baseline any product using any front-end framework.
Universal design tokens
Some POS products hadn’t yet adopted design tokens as a source of truth, while others had already made the leap. No two products referenced the same token set. All existing token libraries were limited to overwrites and additions to Material UI core tokens. A foundational element of my proposal was a library of universal design tokens, intended to set a baseline any product using any front-end framework.

Semantic, framework-agnostic design tokens supported a core collaboration goal: both design and dev should be able to intuit a token’s role without prior framework experience or documentation.

Semantic, framework-agnostic design tokens supported a core collaboration goal: both design and dev should be able to intuit a token’s role without prior framework experience or documentation.

Semantic, framework-agnostic design tokens supported a core collaboration goal: both design and dev should be able to intuit a token’s role without prior framework experience or documentation.
Design tokens can power any component variations required by each product—no divergent component libraries required.
Design tokens can power any component variations required by each product—no divergent component libraries required.
Design tokens can power any component variations required by each product—no divergent component libraries required.
Shared components and patterns
To demonstrate the unifying potential of shared components and patterns, I created a range of POS prototypes covering different real world retail and restaurant scenarios. Each was built with the same set of core components.
Shared components and patterns
To demonstrate the unifying potential of shared components and patterns, I created a range of POS prototypes covering different real world retail and restaurant scenarios. Each was built with the same set of core components.
Shared components and patterns
To demonstrate the unifying potential of shared components and patterns, I created a range of POS prototypes covering different real world retail and restaurant scenarios. Each was built with the same set of core components.
Employee-facing retail checkout: Lookup and add an item to the sale.
Employee-facing retail checkout: Lookup and add an item to the sale.
Employee-facing retail checkout: Lookup and add an item to the sale.
Employee-facing restaurant checkout: Compose and add a combo to the sale.
Employee-facing restaurant checkout: Compose and add a combo to the sale.
Employee-facing restaurant checkout: Compose and add a combo to the sale.
Customer-facing retail checkout kiosk: Lookup and add an item to the sale.
Uniformity x Flexibility
Shared components and patterns, paired with a robust, themeable token library, offer the best of both worlds: a unified, maintainable, user-friendly experience for collaborating teams, while preserving flexibility for unique customer and industry requirements.
Uniformity x Flexibility
Shared components and patterns, paired with a robust, themeable token library, offer the best of both worlds: a unified, maintainable, user-friendly experience for collaborating teams, while preserving flexibility for unique customer and industry requirements.
Uniformity x Flexibility
Shared components and patterns, paired with a robust, themeable token library, offer the best of both worlds: a unified, maintainable, user-friendly experience for collaborating teams, while preserving flexibility for unique customer and industry requirements.
I built a theme builder prototype to demonstrate the role of design tokens in calibrating the unique look and feel of each POS template.
I built a theme builder prototype to demonstrate the role of design tokens in calibrating the unique look and feel of each POS template.
I built a theme builder prototype to demonstrate the role of design tokens in calibrating the unique look and feel of each POS template.
Less is more
By mid-2026, retail self-checkout and cashier point-of-sale products teams formally agreed to merge component libraries, adopting many of the recommendations I’d proposed. Early estimates point to a reduction of total maintained components by 75–80%.
Less is more
By mid-2026, retail self-checkout and cashier point-of-sale products teams formally agreed to merge component libraries, adopting many of the recommendations I’d proposed. Early estimates point to a reduction of total maintained components by 75–80%.
Less is more
By mid-2026, retail self-checkout and cashier point-of-sale products teams formally agreed to merge component libraries, adopting many of the recommendations I’d proposed. Early estimates point to a reduction of total maintained components by 75–80%.