Store design objects

Use this article to find the object behind a part of the storefront. It is an inventory rather than an explanation.

:::note For how these records work together, which one controls a given part of the page, and what to change to affect it, read how stores, themes, and design elements relate. That article covers the model; this one lists the objects and their API names. :::

Four chains to know

The domain is not one hierarchy. It is four short chains that all start at the Store.

Two things about that table are worth stating plainly, because they are what people get wrong:

• A content block is never on a page directly. The join record is what places it, and it carries the order. See junction objects.
• The store, not the theme, decides most configuration. The theme owns markup. Currency, checkout behavior, domain, and which menus to use are on the Store record.

Objects in this domain

Where it meets other domains

• Catalog. Content blocks attach to products and categories as well as pages, and menu items link to them. See catalog objects.
• Content. Articles and their categories are separate from pages and take content blocks the same way, through Content Block Article.
• Customers and accounts. A membership can gate a page or an article, through Membership Page and Membership Article. See customer and account objects.
• The storefront. Most of these objects have a Liquid counterpart, and the On the storefront section on each object reference names it. The Theme Template records are the template keys a theme resolves.

Almost every relationship in this domain runs through a join record, more so than anywhere else in the schema. Junction objects is worth reading before you query or import here.