Visual layout over a catalog you never copy

Partner

Builder.io is a visual editor that renders components you registered from your own codebase, so a marketer rearranges a page without a deploy and without inventing markup the design system has never seen. Its commerce plugins are what separate it from a general purpose page builder.

We run it on our own store. The M8 shop pairs Builder.io with Shopify Hydrogen, and Builder's Shopify plugin syncs product data between the two, so layouts and product displays change visually while Shopify stays the only system holding products, prices, and orders. Monogram is a Builder.io partner.

Monogram logo

Editing

Where Builder.io fits, and what it holds

  1. The catalog never gets a second copy

    Builder's Shopify plugin makes product data available inside the editor without importing it. On the M8 shop, layouts and product displays get rearranged visually, with no developer time and no deploy, while every product, price, and order still lives only in Shopify. Presentation moves; commerce facts do not.

  2. A page is a component tree, not a document

    Builder stores a layout as JSON that its SDK renders against components you registered. You can fetch that JSON at any time, which sounds portable, and it only means something to a renderer that knows your component names. Worth understanding before it holds several hundred pages rather than after.

  3. Experiments ship outside your pull requests

    A/B tests and targeting are built into the editor, so a variant goes live without a code review. The speed is the point. The cost is that experiment logic sits outside the repository, where your test coverage, your analytics conventions, and anyone reading the codebase will not find it.