Headless CommerceNov 2025 - Jan 2026Technical Lead

Headless SFCC Storefront with React and Next.js

Led frontend delivery for a headless ecommerce storefront on Salesforce Commerce Cloud, combining Next.js, React, Tailwind CSS, SLAS authentication, Shopper APIs, and reusable UI architecture.

Headless

Architecture

Delivered a React and Next.js storefront architecture on SFCC with reusable UI foundations and commerce API integration.

SLAS-ready

Auth flows

Implemented secure authenticated shopper experiences with token handling, session persistence, and profile navigation.

Standards set

Team quality

Defined linting, TypeScript, folder, hook, and utility conventions to improve code quality and onboarding speed.

Problem

The storefront needed a modern headless frontend on top of SFCC while preserving core commerce behavior for product discovery, pricing, promotions, cart, and checkout.

Authenticated shopper flows required secure login, logout, profile navigation, token handling, session persistence, and strong edge-case behavior.

The team needed maintainable engineering standards so multiple developers could ship against SFCC data contracts without creating inconsistent frontend patterns.

Approach

Built the frontend with React, Next.js, TypeScript, and Tailwind CSS, emphasizing reusable components, typed patterns, and predictable route structure.

Integrated SFCC Shopper Login and API Access Service for authenticated user flows, token persistence, and profile menu interactions.

Aligned with SFCC backend and OCAPI teams on catalog, pricing, promotion, inventory, customer, cart, and checkout data contracts.

Technical Decisions

Why the implementation choices mattered

Next.jsReactTypeScriptTailwind CSSSFCCSLASShopper APIsJest

Typed component architecture

Established reusable components, hooks, utilities, folder conventions, and TypeScript patterns to keep the storefront scalable and easier to onboard.

Focused auth boundaries

Isolated authenticated UI and SLAS token handling so shopper session concerns did not leak across unrelated storefront components.

Commerce API resilience

Handled expired sessions, token refresh, partial API failures, empty states, and shopper edge cases to protect the buying journey.