ssam//commerce

Open for select engagements — Q1 2027

Commerce systems,
engineered
end to end.

I'm Sam Junaid — a software engineer building the storefronts, backends, integrations, and automations that modern businesses run on. This is the working map of that practice.

samcommerce@prod — console
$ samctl status --all
web/samcommerce up healthy
edge/tls ok certs current
data/postgres-16 up migrations clean
ops/backups ok restore-tested
 
# this site, describing itself honestly.

FIG. 01 — THE STACK BEHIND THIS PAGE

// 01 — Ecosystem

One engineer, connected systems.

Professional work, engineering practice, experiments, tools, and writing — organized the way the work actually relates, not as a flat portfolio.

// 02 — Selected work

Systems in production.

Client engagements are anonymized where required — the architecture and engineering decisions are described faithfully. No invented metrics.

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 workProduction2025 — ongoingTrading Company Site & Operations BackendPublic site and supporting operations backend for a trading company: catalog-style product presentation, structured content management, and a PostgreSQL backend with a dedicated automated backup container.ReactNode.jsPostgreSQLDockerAutomated backupsN°03Client 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°04Client workProduction2024 — ongoingOperations Automation & Messaging InfrastructureEvent-driven automation for business operations: webhook and schedule triggers, queued delivery, reminder fan-out across email and SMS, and audit trails that make automated behavior explainable after the fact.Node.jsWebhooksCronEmail/SMS providersPostgreSQL
All projects & case studies

// 03 — Systems

How things actually ship.

Every system I operate follows the same shape: isolated container groups, one data spine, backups that get restored, and a proxy that terminates TLS so nothing else has to care.

EDGEISOLATED COMPOSE PROJECT — PER CLIENT / PER SYSTEMreverse proxynginx · tlscertbot renewalweb containerstorefront · portalnext.js / reactapi / jobs containerback office · cronnode.jspostgres 16primary datastoreschema migrationsbackupsnightly dumprestore-testedinternetONE SERVER · DOCKER NETWORK PER STACK · NO SHARED STATE BETWEEN CLIENTS

FIG. 02 — DEPLOYMENT TOPOLOGY, PER SYSTEM

The engineering practice

// 04 — Now

The honest snapshot.

What's on the bench right now — updated as things move.

› Building

  • //samcommerce.dev — this ecosystem
  • //Product-data linter (deterministic core)

› Operating

  • //Retail-credit & trading platforms (client, anonymized)
  • //Nightly backup rotation & restore drills

› Exploring

  • //Agentic catalog QA — prototype
  • //Webhook replay harness — prototype
  • //Runbooks as agent checklists — concept

// 05 — Writing

Notes from the work.

Implementation notes, architecture walkthroughs, and opinions — written from systems that actually run.

2026-10-12One server, many clients: isolating stacks with DockerThe compose-project pattern I use to host multiple client systems on a single server without letting them touch each other — and the discipline that makes upgrades boring.2026-09-28Anatomy of an installment platformLedger-first balances, idempotent reminders, and deliberately boring staff tooling — a walkthrough of a retail-credit operations architecture.2026-08-30Conversion is an engineering problemConversion work that matters isn't a theme tweak — it's latency budgets, catalog integrity, and failure states. An argument for treating conversion as infrastructure.
All writing

// Engage

Have a system to build, improve, or rescue?

Tell me what you're working on. I read everything myself and reply to serious inquiries.

Start a conversationhello@samcommerce.dev