Technical case study

DHB63

A Laravel and Next.js rebuild of an established WooCommerce storefront, including structured migration of historical commerce data.

Visit website
DHB63: deployed public website

Real public interface. Captured October 2026.

Project overview

A Laravel and Next.js rebuild of an established WooCommerce storefront, including structured migration of historical commerce data.

My role

Full-Stack Developer

The problem

Modernize the storefront and application while retaining historical records and the relationships that make commerce data useful.

What I delivered

  • Implemented the Laravel backend, database architecture, REST APIs, Filament administration, and redesigned customer storefront.
  • Built catalog, variants, categories, stock, cart, checkout, payment, orders, authentication, and customer accounts.
  • Mapped and migrated customers, products, variants, orders, media, content, and related legacy records.
  • Developed batch imports, checkpoints, validation, reconciliation, and migration audit tooling to preserve historical business information.

How the system fits together

Technical architecture Conceptual flow
  1. Legacy WooCommerce data
  2. Import mapping
  3. Batch validation & checkpoints
  4. Laravel database
  5. Reconciliation & audits

Engineering challenges

  • Mapping legacy variants and related records into the new schema without losing historical context.

Technical decisions

  • Use checkpointed imports and reconciliation tooling to make the migration inspectable and repeatable.

Implementation context

This WordPress/WooCommerce rebuild is separate from the nopCommerce migration on the Production Engineering page. No record totals from that migration are attributed to DHB63.