Headless CommerceNov 2025 - Jan 2026Technical Lead

Headless SFCC Storefront with React and Next.js

Led the frontend foundation for a headless SFCC storefront with Next.js, React, TypeScript, SLAS authentication, Shopper APIs, and reusable commerce UI patterns.

6 mapped

Frontend domains

Mapped product, auth, customer, cart, checkout, and merchandising concerns into clear frontend ownership boundaries.

4 key flows

Auth readiness

Implemented login, logout, profile navigation, and persisted session behavior with SLAS token handling.

~35% faster setup

Delivery speed

Reduced new feature setup time with reusable UI patterns, typed utilities, linting, folder conventions, and shared hooks.

Challenge

The team needed a modern headless frontend on top of SFCC without weakening core commerce behavior for discovery, pricing, promotions, cart, and checkout.

Authenticated shopper journeys required reliable login, logout, profile navigation, token handling, session persistence, and failure-state behavior.

Multiple developers needed to ship against SFCC data contracts without creating inconsistent components, duplicated API logic, or fragile route patterns.

Technical Approach

Built the storefront with React, Next.js, TypeScript, and Tailwind CSS, emphasizing typed commerce contracts, reusable components, and predictable route structure.

Integrated SFCC Shopper Login and API Access Service for authenticated user flows, token persistence, profile menus, and session boundaries.

Partnered with SFCC backend and OCAPI teams on catalog, pricing, promotion, inventory, customer, cart, and checkout contracts before scaling feature work.

Architecture Decisions

Implementation choices tied to business impact

Next.jsReactTypeScriptTailwind CSSSFCCSLASShopper APIsJest

Typed commerce architecture

Established reusable components, hooks, utilities, route conventions, and TypeScript models so SFCC data contracts stayed explicit across the UI.

Focused auth boundaries

Isolated authenticated UI and SLAS token handling so shopper session concerns did not leak into unrelated product, cart, or merchandising components.

Commerce API resilience

Designed for expired sessions, token refresh, partial API failures, empty states, and shopper edge cases before they became production defects.

Discuss a similar project