Complete Store Preview

Use this page as the big-picture map after you have read the individual view guides. A complete Woo storefront usually needs four customer-facing surfaces:

Surface	What it owns
Product archive	Product loop, product cards, add-to-cart forms, cart count, cart notices.
Single product	Current product data, variation selectors, quantity, add-to-cart, buy-now.
Cart page	Editable cart rows, coupons, shipping, totals, empty state.
Checkout page	Checkout form, address fields, shipping, payment, terms, notices, order summary, place order.

How The Views Connect

Product archive or single product
  AddToCartForm / AddToCartButton
  CartCount and CartNotices update

Cart page
  reads the same Store API cart
  updates rows, coupons, shipping, and totals

Checkout page
  reads the same cart
  collects checkout fields
  submits the order through Woo Store API

The product views add items into cart state. The cart page mutates that same cart. The checkout page consumes the cart and submits the order.

Route Ownership Checklist

Route	Required owner
Shop archive	archive-product template.
Product page	single-product template.
Cart	Page assigned to woocommerce_cart_page_id.
Checkout	Page assigned to woocommerce_checkout_page_id.
Order received	Woo-aware order confirmation route or block.
Product categories/tags	Product-aware taxonomy templates when the starter exposes those routes.

Read Woo Template Integration Contract before publishing a starter that owns those routes.

Shared Data Rules

• Product archives use {item.*} and {item.omewoo.*} inside the product loop.
• Single product templates use {this.*} and {this.omewoo.*}.
• Cart rows use cart item atoms inside CartItems.
• Checkout fields and selectors live inside CheckoutProvider / CheckoutForm.
• Order summary can reuse cart item and totals atoms in a read-only checkout context.

Shared Feedback Rules

Use cart-level feedback outside repeated product cards:

• CartCount shows current item quantity.
• CartNotices shows cart action messages.
• CheckoutNotices shows checkout validation and submit messages.
• Woo custom events are the integration hook for drawers, analytics, and checkout instrumentation.

Build Order

1. Build the Product Archive.
2. Build the Single Product template.
3. Build the Cart Page.
4. Build the Checkout Page.
5. Wire route ownership with Woo Template Integration Contract.
6. Add focused Recipes and Woo Custom Events integrations as needed.

That order keeps the first usable storefront visible while the deeper checkout and route details are added.