Understand combo and recipe products in version 1.0.0
This guide explains that that classifications exist, but component explosion/recipe stock logic is not exposed. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Know that classifications exist, but component explosion/recipe stock logic is not exposed. This section documents every product/category field, visibility control and validation used by the staff and public catalogue.
Follow these steps
- Go to Enterprise POS → Products / Categories and open the workflow that matches “Understand combo and recipe products in version 1.0.0”. Confirm the page or record context before making a change.
- Create categories before products where useful.
- Go to Products and create or edit a product.
- Enter identity, type, price, cost, tax, descriptions, image and SEO fields.
- Select stock, backorder, featured, public, active and noindex controls.
- Save and verify the product in staff search and, when eligible, /shop.
Fields and options to review
- Guide focus: Know that classifications exist, but component explosion/recipe stock logic is not exposed.
- Name, SKU, barcode, category and type
- Price, cost, tax rate and weight
- Short and full descriptions
- External image URL
- Meta title, slug and meta description
- Track stock, allow backorder, featured, public, active and SEO noindex
Rules the system enforces
- SKU is required and unique per tenant.
- Barcode is optional but unique per tenant when supplied.
- Product slug is tenant-unique and generated from the name when blank.
- Price/cost use minor-unit conversion; tax is validated.
- Weight is 0 to 100,000,000 grams.
- Only active and public products appear in the public store.
- Track-stock and backorder settings control availability checks.
How to confirm it worked
- The specific outcome described by this guide is visible and remains tenant-scoped.
- The product is available in authorised staff searches.
- Eligible products have canonical public product pages.
- Search, barcode and stock handling use saved values.
Safety checks and troubleshooting
- Use controlled external HTTPS image URLs.
- Do not reuse SKU/barcode values.
- Do not select specialised product types expecting workflows not implemented by version 1.0.0.
Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it.