Location-aware dual branding for a regional retailer

A regional retailer with physical store locations and a shared e-commerce platform needed one WordPress site to support two distinct regional brands without splitting into separate front-end codebases.

I helped build a location-aware branding system for a regional retailer operating two distinct brands on a single WordPress/WooCommerce site. The challenge was to keep the experience unified from a development standpoint while allowing customers to see the brand, navigation, and product discovery flow that made the most sense for their region.

Instead of maintaining two separate sites, I supported a shared architecture that could intelligently switch brand context based on geographic signals, explicit user choice, and page-level business rules. That let the business preserve operational efficiency while still presenting shoppers with a more localized experience.

The challenge

The business had two regional brands serving different geographic footprints, but both lived inside the same WordPress ecosystem. That created a messy balancing act: the site needed to default to the right brand by region, respect intentional user choices, allow editorial overrides where needed, keep the homepage aligned to the primary brand, and avoid showing the wrong products or messaging to the wrong audience.

There was also an experience problem. A visitor could land on a section associated with one brand while actually shopping in the other brand’s region. Without guardrails, that created confusion around locations, navigation, merchandising, and fulfillment.

What I built

I worked within the WordPress theme to support a decision system that determined the active brand in a clear order of priority: page-level ACF overrides, homepage behavior, brand-specific URL patterns, stored user preference via cookies, and geolocation fallback using WP Engine’s city data. This created a predictable and maintainable way to control branding across the site.

I also helped support persistence and cleanup rules around brand selection. Query-string brand switches could set a preference cookie and then redirect to a clean URL, while brand-specific paths reinforced the active experience. The homepage intentionally reset the experience to the primary brand, which kept the main entry point consistent.

Beyond logos and navigation, the active brand also influenced what shoppers could discover. Search and autosuggest behavior were filtered by brand so product visibility aligned with the current regional experience. Delivery logic also inherited brand context based on pickup city, helping keep fulfillment behavior consistent with the storefront the customer was using.

UX and business considerations

One of the more useful touches was a lightweight “brand mismatch” prompt. When the detected region didn’t match the brand being viewed, the site could surface a simple nudge to switch to the more relevant experience. That made the system feel less rigid and more customer-friendly, especially for users arriving through deep links or returning with an older cookie state.

From a business standpoint, this approach protected a single shared codebase while still supporting regional differentiation. That meant less duplication, easier maintenance, and more consistent editorial control than trying to run two fully separate sites. It also gave the business flexibility to tune the experience through content rules, merchandising exclusions, and geo-based defaults instead of brute-forcing everything with duplicated templates. This is the sort of problem WordPress can solve elegantly when it is treated like an application platform instead of just a CMS with a theme bolted on.

Outcome

The finished approach created a smarter regional experience inside one WordPress/WooCommerce installation. Visitors could see the brand most relevant to where they shopped, user intent was respected through cookies and URL handling, editors retained control where exceptions were needed, and product discovery stayed aligned with the active brand.

At the same time, the business avoided the overhead of maintaining separate front-end builds for each regional identity.