Adobe Commerce / Magento 2

Brickworks multi-brand Adobe Commerce platform.

A shared Adobe Commerce catalog platform supporting multiple Brickworks brands, regional product availability, design services, store lookup, and sample requests beyond a conventional checkout model.

  • single commerce instance
  • multiple storefronts
  • catalog-first UX
  • theme inheritance
  • Akeneo integration
Austral Bricks storefront preview

Public summary

Many brand experiences, one catalog backbone.

Brickworks runs a network of product-led sites across Austral Bricks, Bowral Bricks, Daniel Robertson, Bristile Roofing, Austral Masonry, UrbanStone, Nubrik, GB Masonry, and Brickworks NZ. The platform behaves less like a standard retail checkout and more like a regional building-products catalog: users browse product ranges, filter by application and availability, request samples, find locations, and move into consultation or enquiry flows.

What made the architecture distinctive

Platform shape

One Adobe Commerce instance serving many regional storefronts.

The codebase maps many brand and state storefronts into one Magento application, with separate routes, store codes, and theme layers for Australian and New Zealand product experiences.

Commerce model

Catalog, samples, and enquiry journeys instead of checkout.

The experience is focused on product selection, regional range visibility, product education, store lookup, iVisualise, brick matching, colour consultation, and sample ordering.

Frontend

Multiple brand themes under shared Brickworks foundations.

The implementation uses a shared Brickworks theme foundation with brand-specific child themes for New Zealand, masonry, and export experiences.

Catalog operations

Platform controls for regional catalog visibility and search quality.

Local modules and patches support catalog visibility, OpenSearch filtering, product fallback behavior, SEO markup, and Akeneo-driven product data workflows.

Work themes

Engineering focus
  • Keep brand-specific presentation separate from shared catalog behavior.
  • Support regional product availability and state-specific catalog paths.
  • Preserve catalog performance while filtering hidden or unavailable products.
  • Work inside Adobe Commerce Cloud conventions and existing Magento module boundaries.
User experience focus
  • Help users select products by state, application, finish, size, and range.
  • Make brand switching feel connected while preserving distinct brand identities.
  • Support sample ordering and consultation flows without forcing a checkout pattern.
  • Expose technical product information, brochures, design notes, and store locations.

Need senior ownership across Adobe Commerce architecture and operations?

I work across platform architecture, catalog behavior, integrations, and operational delivery when the details need to hold together as one system.

Discuss a role or project