Cyber Week30% off Lifetime with code CYBER — it will never be this cheap againUntil 28 Nov, 10:00 CET

Content & media

Shops

A WooCommerce, SureCart or FluentCart store behind your site: products as a source, product grids and pages, the buy box, the cart, and the shop’s own pages in your design.

A shop is a data source whose rows are a store’s products. You build what a visitor browses on the canvas, product lists, product pages and a cart, and the site ships as static Astro. The checkout, the payment, the order confirmation and the customer’s account stay where the store already has them, on WordPress. sitereal takes no payment and holds no payment key, and nothing a visitor does on the built site calls the shop: a product is bought with a plain form that works with every script removed. Three shops are supported, in beta: WooCommerce, SureCart and FluentCart.

Connecting a store

In Content, press + beside Sources and choose WooCommerce, SureCart or FluentCart, or press Connect a store on the Shop addon’s screen. Enter the address of the WordPress site the store runs on. No key is asked for: the shop’s public catalog is read for its published products.

  • A store belongs to its WordPress site. Posts and products of one site share its connection and its companion plugin, and the first store you connect switches the Shop addon on.
  • A limit and a query narrow what arrives: category=shirts, featured=true, anything the shop’s own product list takes.
  • Products are read while the site is built. A new price, a new product or one that sold out is on the site after the next build. The companion plugin can start one from WordPress.
  • The Shop screen, under Addons, lists every store with what it says about itself: its version, whether its checkout is in test mode, where its checkout is, and what a visitor would stumble over, such as a product that is sold out.

What a product is

Every product arrives in one shape, whichever shop it came from, so a card, a filter or a sort never cares which. Inside a shop’s Loop and on its product page, the Fields menu offers these keys.

KeyWhat it holds
name, slugThe product’s name and its slug.
excerpt, summary, contentThe short description as text and as the shop formats it, and the long one.
image, galleryThe main picture, and every picture.
price, price_textThe price as a number, for sorting and filters, and as the store writes it (19,90 €).
compare_at_text, on_saleThe price before a sale, while there is one.
recurring_text, tax_noteA subscription’s terms, and what the store prints after a price.
sold_out, stock_textWhether it can be bought now.
variantsEach choice with its own price, picture and stock.
categories, brandsNames, with their slugs beside them for filters.
url, linkThe product’s page on your site once product pages are on, and its address in the store.

Product grids and product pages

+ has one Product grid: a Loop over a shop with a product card in it, holding the picture, the name, the price and a button. Its Shop control points it at another store. It is an ordinary Loop, so you sort it, limit it, split it into pages and filter it like any other (Loops & conditions, Search & filters).

Switch on Entry pages on the store and design one page for every product, as for any source. It starts with the shop’s parts already bound: the pictures, the name, the price, the buy box and the description. Product pages are built where WordPress had them, /product/… for WooCommerce, so links that already exist keep working.

Wherever a product is in reach, Fields places a Price, a Buy box and a Product card already bound. A product the store hides from its catalog gets no card.

The buy box

The buy box is a form that posts to the store’s own checkout: the product, the chosen variant and the quantity. It needs no script, so it works on every host and with JavaScript off. A product with several variants gets a select, and one that is sold out says so and cannot be sent. A product a form cannot sell, one whose options only the store’s own page offers or one a visitor names the price of, gets a Choose options link to its page in the store instead.

The cart

Two parts from the Shop group in +: a Cart button for the header, with a count, and the Cart, a drawer that lists what was added. Put both in the header, in its template or its component.

  • With the cart on the page, a buy box adds to it instead of leaving for the checkout. The cart is kept in the visitor’s browser, and its checkout button hands every line to the store as one address.
  • A cart holds one shop’s products. On a site with two stores, Cart for on the Cart names the one it collects for, and a product of the other is bought at once at its own checkout.
  • The total is an estimate and says so: taxes and shipping are worked out at the checkout, by the store.
  • It is a script that only adds manners (public/scripts/cart.js, written where a cart part is and nowhere else). Without it every buy box still buys its product.

The shop’s pages in your design

The checkout, the cart, the account and the thank-you page are WordPress’s pages. With the companion plugin they wear your site’s header, footer and design: sitereal builds one page with a hole in it, the Shop pages, and the plugin puts the shop’s page into the hole.

  • Make the shop pages on the Shop screen, on a store’s settings, or under Shop on the Templates screen in Assets. It opens on the canvas like any page: its template is the header and footer around it, and Shop content marks where the shop’s page goes.
  • One kind can have a page of its own. A checkout often wants a quieter frame than the rest of the site: press Make its own for the checkout, the cart, the account or the thank-you page, and give it another template, or press New checkout template for a slim one with just the brand. Remove this page takes it away again.
  • Design chooses between This site’s design and WordPress theme, for a shop that should stay as its theme draws it.
  • The shop’s forms pick up your design system’s colors, type and buttons. Their fields and what they do stay the shop’s.
  • Each language of your site gets its own frame, and the plugin uses the one for the language WordPress shows.

This needs sitereal for WordPress 0.3 or newer; Headless WordPress & EmDash has the download. Without the plugin the shop’s pages keep the WordPress theme, and everything else on this page works the same.

What stays on WordPress

  • Orders, customers, payments, tax, shipping and coupons, with every payment method and extension the shop has.
  • The checkout, the cart page, the order confirmation and the customer’s account.
  • In headless mode the plugin keeps those addresses on WordPress while everything else goes to your site.

With an agent

Claude Code reads a shop through the MCP like any source: the guide’s shop topic says how a buy box and the cart are built, and sitereal_source_rows shows the products as a page receives them.