BigCommerce handles catalog, cart, and checkout well, but complex configurators often outgrow theme constraints. Embedding a Next.js app in an iframe keeps the configurator team moving fast while the storefront stays on BC’s rails.
The fragile part is parent ↔ iframe communication. We standardize on small, versioned message types: selection changed, price updated, add-to-cart with payload IDs–never ad-hoc DOM scraping across the boundary.
Review and rating widgets from third parties were hurting LCP. Caching at build or edge with revalidation gave us fresh enough social proof without the user paying for a waterfall on every navigation.
The outcome is a store that still feels native to BigCommerce for ops and SEO, while the configurator gets the React ergonomics and testability we needed for a high-SKU LED catalog.
