Activate WooCommerce and Delta adds two things: template types for the storefront screens, and approximately seventy abilities for products, orders, coupons and store settings.
Storefront templates
Products and the shop do not use the blog templates. WooCommerce supplies its own types.
| Screen | Template |
|---|---|
| Shop, category and tag listings | One archive type, with display conditions |
| A single product | One product type, with display conditions |
| Cart, and the empty cart | Their own types |
| Checkout, payment and thank you | Their own types |
| The account screens | One type per screen |
The archive and product types accept display conditions. Build more than one and point conditions at them.
The remaining types match by type alone. Edit the template that ships. Display conditions on these types are rejected.
“Design the shop listing and the product page to match the site.”
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.
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.
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.
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.