Activate WooCommerce and Delta adds two things: template types for the storefront screens, and about seventy abilities for products, orders, coupons and store settings. Your agent can also run WooCommerce’s own abilities through Delta.
Storefront templates
Products and the shop do not use the blog templates. WooCommerce screens have their own template types.
Delta ships no store templates. Until you build them, store pages show the plain layout. Ask the agent to build them in your design system:
“Build the shop templates to match the site.”
The basic set is the product archive, the single product, the cart, the empty cart, checkout, the account login and the account dashboard, plus a product card for listings. The other store screens keep the plain layout until you ask for them.
| Screens | Template types | Display conditions |
|---|---|---|
| Shop, category, tag and brand listings | Product Archive | Yes |
| A single product | Single Product | Yes |
| Cart | Cart, Empty Cart | No, matches by type |
| Checkout and orders | Checkout, Pay for Order, Order Received, Order Receipt | No, matches by type |
| Signing in | Account Login, Lost Password, Lost Password Confirmation, Reset Password | No, matches by type |
| The account area | Account Dashboard, Account Orders, View Order, Account Downloads, Account Addresses, Edit Address, Edit Account, Payment Methods, Add Payment Method | No, matches by type |
| Account pages that an extension adds, such as subscriptions or wishlists | Account Endpoint (extensions) | No, matches by type. Without one, the Account Dashboard template serves these pages |
Product Archive and Single Product accept display conditions. Build more than one and point conditions at them, for example a different layout for one product category.
The other types take no conditions. Build one template of the type and it renders that screen.
Layout and behaviour
You compose the layout: the product grid, the gallery, the attributes, the cart line items, the order history.
WooCommerce supplies the working regions: the add-to-cart form, the quantity fields, the payment step, and the login and address forms. A template calls each region by name.
Delta does not modify checkout, payment, cart or account handling. Gateways and extensions continue to work while the template calls these regions.
A template can also use WooCommerce’s own blocks: {{cart_block}}, {{checkout_block}}, {{order_confirmation_block}}, and {{mini_cart}}, which works anywhere, also in the header. Each one shows the block as it is set up on the store’s page, or WooCommerce’s default.
Cart and order rows have placeholders for each line: {{item_name}}, {{item_price}}, {{item_subtotal}}, {{item_data}} and {{remove_link}} in the cart, {{item_meta}} and {{quantity_html}} in an order, and {{order_actions}} in the account order list. Store loops, such as the cart items or a product’s gallery, also work in the header and footer.
Do not rebuild a payment, login or address form as your own markup. A copy renders correctly and fails at submission: card fields do not process, and addresses do not save. Call the region, then style around it.
Store colours
While WooCommerce is active, Delta loads a small base stylesheet after WooCommerce’s own CSS. It removes WooCommerce’s colours from prices, sale badges, star ratings and store buttons, so your design system styles the store. To change a store element, ask the agent to style it in site.css.
Required regions
Each storefront type has regions it must contain. A checkout without its payment region has no place-order control. A cart without its quantity region cannot update.
Delta checks for the required regions when a store template is saved and reports the ones that are absent. It also reports a region that is present but hidden with CSS.
The save proceeds. The report identifies what to restore.
A thank-you template that adds a heading of its own beside the order confirmation gets a warning too, because the confirmation already carries one.
Products, orders and coupons
Products are not posts. Each of these objects has its own abilities, because each has rules an ordinary entry does not.
Request a product, and the agent uses the product abilities.
Delta’s store abilities go through the WooCommerce REST API, so WooCommerce’s own checks and permissions apply to every change.
WooCommerce now publishes seven abilities of its own, named woocommerce/…, for finding, creating, changing and deleting products, finding orders, changing an order’s status and adding an order note. Delta’s eight abilities for the same jobs (delta/list-products, get-product, create-product, update-product, delete-product, list-orders, get-order and create-order-note) stay. The agent uses WooCommerce’s for plain cases and Delta’s for images, categories, tags, attributes, variable products, meta data, batches of ids and list filters, and on WooCommerce before 11. If you switch one off on the Abilities screen, its WooCommerce twin goes off too.