Seven commerce engagements across three platform families. Most of this is client work — screenshots and specifics stay behind NDAs, so these read as engineering case studies: the situation, the constraints, and what got built.
DripDrop sells hydration products directly to consumers at real scale, which makes the storefront a production system, not a brochure. It's a side engagement alongside the XCentium day job — with primary-developer ownership of everything a modern DTC operation touches: product page UX, merchandising, analytics, consent, fulfillment, ERP, and new sales channels.
what I built
Shopify storefront development in Liquid — product page UX, flavor and pack-size selectors, merchandising logic driven by metafields
SEO and crawlability: metadata, rich snippets, structured data
Google Tag Manager instrumentation and Osano consent management
Fulfillment and inventory workflow support across the stack
technical texture
Agent-assisted development is part of the daily workflow here — planning, implementation, and review with coding agents against a live production storefront.
Variant selection UX is the heart of the product page: flavor × pack-size matrices, availability, and pricing logic all resolve client-side from structured metafield data.
ShopifyLiquidJavaScriptHTML5CSS3Google Tag ManagerOsanoShipFusionNetSuite / CeligoTikTok ShopREST APIsPlatform integrationsClaude CodeGit
A casino property needs its site to do two very different jobs: editorial marketing pages that content teams can compose themselves, and an authenticated player portal handling account-level data. Both demand accessibility and both sit on Optimizely CMS 12.
what I built
Frontend architecture for CMS-driven components — built so editors compose pages without developer involvement
Player Portal Dashboard Phase 2 — authenticated player-facing UI
Accessible UI work across the implementation
Backend and CMS integration points connecting portal UI to platform services
B2B distribution commerce is a different discipline from DTC: enormous catalogs, customer-specific pricing, account hierarchies, and buyers who order by part number. Configured Commerce with the Spire frontend is built for exactly this, and customizing it well requires knowing both halves — the React frontend and the .NET platform underneath.
what I built
Spire (React/TypeScript) frontend development against Configured Commerce
Platform configuration and customization on the .NET side
Industrial suppliers need commerce that handles technical products with deep specification data. This engagement covered both sides of the platform: Spire frontend work and the C#/.NET extension points behind it.
what I built
Configured Commerce frontend implementation
Backend platform work — extensions, configuration, and support
Ongoing implementation support across releases
Optimizely Configured CommerceSpire CMSReactTypeScriptC#.NETSQL / SQL Server
Not every valuable engagement is a greenfield build. This one was surgical: portal functionality, form work, platform configuration, and precise fixes inside an existing Configured Commerce implementation — the kind of work where reading the platform's behavior correctly matters more than writing lots of code.
Beauty supply distribution runs on catalog breadth. The work here centered on how products and categories surface, browse, and merchandise — plus UI enhancements and custom functionality layered onto the platform.
what I built
Product and category functionality
UI enhancements across the storefront
Custom platform functionality
Optimizely Configured CommerceSpire CMSReactTypeScriptC#SQL / SQL Server
A third commerce platform, same discipline: component-level frontend work inside Salesforce Commerce for a parts catalog measured in the hundreds of thousands of SKUs.
what I built
Salesforce Commerce frontend component development