ssam//commerce

// Commerce — 04

The catalog is the system.

Ecommerce engineering across Shopify and Shopify Plus: themes built to be operated, product data treated as the spine of the business, and conversion handled as an engineering discipline rather than a coat of paint.

Shopify / PlusLiquidProduct dataConversionIntegrations

// A — Principles

How commerce systems get built here.

  1. 01Theme architecture that survives redesigns

    Section-based, merchant-editable, versioned like code. A theme is an interface to the catalog — not a place to hide business logic.

  2. 02The product data spine comes first

    Fields, metaobjects, naming conventions, and feeds designed so storefront, search, and integrations read from one source of truth. Slow data breaks everything downstream.

  3. 03Conversion is infrastructure

    Performance budgets per template, checkout path integrity, and failure states designed with the same care as the happy path.

  4. 04Integrations are contracts

    Payments, shipping, ERP, inventory, CRM — each integration gets explicit ownership of its data, retries, and failure behavior.

  5. 05Operations close the loop

    Order flows, fulfillment, and CX tooling are part of the storefront's design — because the customer experiences the operation, not the org chart.

  6. 06Respect the platform

    Shopify does some things brilliantly and others badly. Knowing which is which is most of the value of an engineer who works on it daily.

// B — Architecture

The shape of the system.

DEMANDCATALOG SPINEOPERATIONSstorefronttheme architecturecheckout pathperformance budgetsproduct datacatalog modelmetaobjects / fieldsfeeds & QA rulespricing integrityoperationsorders · fulfillmentCX toolingintegrationspayments · shippingerp / inventorycrm · marketingSLOW CATALOG DATA BREAKS EVERYTHING DOWNSTREAM — THE SPINE IS ENGINEERED FIRST

FIG — THE COMMERCE SPINE. DEMAND ON ONE SIDE, OPERATIONS ON THE OTHER, DATA IN THE MIDDLE.

› Typical engagements

  • Theme builds & rebuilds — from design handoff to a merchant-operable, version-controlled theme.
  • Catalog remediation — modeling, cleanup, and QA rules for catalogs that outgrew their structure.
  • Conversion engineering — performance passes, checkout-path fixes, failure-state design.
  • Integration work — getting the store to speak honestly with payments, shipping, and back-office systems.
Read: conversion is an engineering problemRelated experiments

// C — In practice

Commerce work in production.

Client storefronts and commerce-adjacent systems. Store names stay private; the engineering is described plainly.

N°01Client workProduction2025 — ongoingInstallment & Retail-Credit Operations PlatformA production platform for a retail-credit business: customer portal, staff back office, installment scheduling, automated payment reminders, and role-based access — shipped as an isolated Docker stack with restore-tested backups.Next.jsTypeScriptPostgreSQLDockerNginxCertbotN°02Client workProductionOngoingShopify Theme & Conversion EngineeringEcommerce platform work across client storefronts: theme architecture that survives design changes, product data that feeds everything downstream, and conversion infrastructure — speed, checkout paths, and failure states.Shopify / PlusLiquidTheme architectureMetaobjectsAnalyticsN°03IndependentActive2026samcommerce.dev — This EcosystemThis site: a personal technology ecosystem rather than a portfolio — professional work, engineering practice, experiments, tools, and writing under one identity. Designed as a design system first, deployed as its own isolated container.Next.js 16TypeScriptTailwind CSS 4Framer MotionMDXDocker

// Engage

Store pushing against its platform?

Theme rebuilds, catalog remediation, conversion engineering — or an honest opinion on whether the problem is really the theme.

Start a conversationhello@samcommerce.dev