Xcoden — E-commerce engineering

Commerce systems built from scratch.

We design and build custom e-commerce platforms for businesses whose operations don't fit a template. Five systems shipped, each architected end to end — from data model to checkout to fulfillment.

What we build

Most agencies configure a platform and stop where it stops. We start with the part your business actually depends on, then decide what belongs on a platform and what has to be written.

01

Custom commerce platforms

Full builds in Laravel for businesses whose logic outgrew what a hosted platform allows — pricing engines, quote flows, inventory rules, operational tooling.

02

Platform engineering

Shopify, Magento, and WordPress work past themes and apps: custom checkout, catalog logic, ERP and payment integrations, performance.

03

Systems architecture

Data models, service boundaries, and integration design settled before the first migration runs — because retrofitting the foundation is the expensive way to do it.

04

Long-term development

Continued work on systems we know, with the person who built them. No handoff to a team that has to learn your codebase first.

Selected work

Five systems, all built from scratch, all still running.

GadgetSalvation

gadgetsalvation.com

A consumer electronics buyback platform. Customers describe a device, get a priced offer, ship it in, and get paid — which means the catalog, the condition grading, the offer engine, and the payout pipeline all have to agree with each other. Built end to end on Laravel.

Scope
Full build
Stack
Laravel, MySQL, Redis
Sector
Resale & buyback
Status
Live, ongoing

Shopuvs

shopuvs.com

Two sales channels running off one physical shelf — a card-payment storefront and an eBay store. The whole system turns on separating stock from the things that sell it: a sellable is assembled from stock units, so availability is computed from its components rather than stored, and a matching set and the single piece built from the same unit draw each other down automatically. Both channels call one stock service, which debits the shelf and re-pushes availability to every affected eBay listing. Built end to end on Laravel with a Filament back office.

  • Stock engine. An append-only movement ledger where every entry carries an idempotency key built from the order and line, so a re-synced eBay order or a retried payment webhook cannot double-count. Editing a count by hand moves through the same path as a sale and reaches eBay like any other change.
  • eBay Sell API integration. OAuth, inventory publishing, multi-variation listing groups, availability and sold-count read-back, importing listings created outside the app, plus category taxonomy and business policies. A refusal from eBay is treated as an ordinary outcome that lands on the item for a human; only transport failures retry.
  • Pre-publish validation. A chain that checks the listing against eBay's own category rules before publishing — required item specifics, allowed values, length limits, cross-aspect constraints, numeric aspects — so the seller reads the problem in the app instead of a refusal a minute later.
  • Variation editing. A combinations grid generated from the attributes a listing varies by, matching already-filled rows on an order-independent signature so regenerating adds what is missing instead of discarding SKUs, stock and photos that live eBay offers depend on. Reorderable, because option order is the order a buyer picks from.
  • Storefront and checkout. Blade and Tailwind shop with a session basket that re-resolves price and availability on every read, so a basket left open overnight cannot charge yesterday's price. Card details never reach the application; the signed webhook is the only thing that marks an order paid, and it debits stock once per line.
  • Back office. Filament panel over inventory, the shelf, eBay and web orders, shipping and tracking, refunds with stock reversal, reusable listing prefills and storefront pricing.
  • Background work. Queued publishes and availability pushes that collapse a burst into a single call and read live counts when they run, scheduled listing and order syncs, a buyer-data retention scrub, and a reconciler that asks the processor what became of any pending order the webhook never reported.
  • Deployment and tests. Provisioning and deploy scripts that never touch the live database, photos or environment, and a suite of 223 tests with eBay and payments faked at their seams so no HTTP leaves the test run.
Scope
Full build, both channels
Stack
Laravel, Filament, Tailwind, Stripe, eBay Sell API
Sector
Resale & apparel
Status
Live, ongoing

NDS The Label

ndsthelabel.com

A direct-to-consumer fashion storefront built from the ground up — catalog, product presentation, and checkout designed around the brand rather than fitted to a theme.

Scope
Full build
Stack
—
Sector
Fashion, DTC
Status
Live

Universal Taxi Dispatch

universaltaxidispatch.com

A booking and dispatch platform — the kind of operational system no storefront product ships with, and the reason it was written rather than assembled.

Scope
Full build
Stack
—
Sector
Transport & logistics
Status
Live

Circular & Sustainable

circularandsustainable.com

An editorial publication on the circular economy — e-waste, textiles, recycled content, right-to-repair law. A static site on edge infrastructure with no database, no CMS and no admin login: an article is a Markdown file, and a push publishes it. It ships zero bytes of JavaScript to the browser, which is a constraint the whole design is held to rather than a result that happened.

  • Content architecture. Separate collections for editorial articles, guides and corrections, each with a typed frontmatter schema enforced at build time — a malformed article fails the build instead of reaching production. The filename is the permanent URL, and drafts render locally but are stripped from the published build.
  • Editorial integrity. A named byline, a public corrections log, and last-verified dates that flag themselves as possibly out of date after six months rather than presenting an old check as a current one.
  • Images. A responsive srcset sized to the prose column so phones are not sent full-width originals, eager-loaded lead images, social cards whose card type follows the image's shape, and generated cover art for articles that have no photograph.
  • Interaction without JavaScript. Topic filtering and a featured-post home page built in CSS alone, keeping the no-JS constraint intact.
  • Search and syndication. Sitemap, RSS feed, article structured data, and meta descriptions driven off the same frontmatter the page renders, so they cannot drift apart.
  • Edge layer. A Worker in front of the static assets that redirects www to the apex preserving path and query, scoped so content-hashed assets are still served directly and a page with images does not bill ten invocations instead of one.
  • Build gates. Schema validation and type-checking, plus a check that fails the build on the run-together text the framework's whitespace handling produces silently — invisible in the source, and shipped five times before the check existed.
  • Design and delivery. The entire design in one stylesheet with working light and dark schemes, security headers site-wide, immutable caching on fingerprinted assets, a real 404 status on unmatched routes, and automatic deploys on push.
Scope
Full build
Stack
Astro, Cloudflare Workers
Sector
Publishing
Status
Live, ongoing
Laravel Shopify Magento WordPress MySQL Redis Filament Stripe Astro Cloudflare Workers

How we work

Three commitments that decide most of what follows.

Architecture before code

The data model and the service boundaries get settled first. Every expensive rebuild we've seen started as a schema decision nobody wanted to make early.

Own the critical path

The workflow your revenue depends on shouldn't be a plugin you can't read. We build that part, and you keep it.

Built to be maintained

Readable code, documented decisions, and a system the next developer can pick up — whether or not that developer is us.

Tell us what you're building.

Send a short description of the project and where it's stuck. You'll get a real reply from the person who'd do the work — not a scheduling link.

Based in
Chicago, Illinois
Engagements
Full builds, platform work, retainers
Response
Within one business day