Understand public-store product eligibility
Require active/public product and supported stock/backorder state. 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.
Where to go/shop
What you’ll accomplish
Require active/public product and supported stock/backorder state. This section documents public catalogue eligibility, category/product pages, cart handling and route behaviour.
Follow these steps
- Go to /shop and open the workflow that matches “Understand public-store product eligibility”. Confirm the page or record context before making a change.
- Go to /shop while the store is enabled.
- Browse categories or search products.
- Go to a canonical product page.
- Add a valid quantity to the session cart.
- Update or remove items.
- Check recalculated stock, promotions, tax, shipping and totals before checkout.
Fields and options to review
- Guide focus: Require active/public product and supported stock/backorder state.
- Public category and product slugs
- Search query and page number
- Session cart product IDs and quantities
- Coupon code
- Default stock location
- Availability and backorder status
- Canonical, meta and structured data
Rules the system enforces
- Disabled stores return 404.
- Public product lists use 24 items per page.
- Search-result pages use noindex,follow.
- The cart accepts at most 100 distinct product IDs.
- Each quantity is positive and no more than 100,000.
- Non-weighed quantities must be integers.
- Cart totals are recalculated server-side.
How to confirm it worked
- The specific outcome described by this guide is visible and remains tenant-scoped.
- Only eligible products/categories are displayed.
- Cart changes persist in the visitor session.
- Canonical URLs and metadata match the requested public item.
Safety checks and troubleshooting
- Do not rely on client-side totals or product data.
- Do not expose internal stock/audit details.
- Use HTTPS and privacy/terms links for production.
Stay within the supported module flow
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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.
