Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Store settings, branding, legal content and checkout controls

Test the public store enable and disable control

Verify enabled access and the deliberate 404 response when disabled. 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.

Audience: Administrators and authorised commerce managersPermission: Enterprise POS: Manage settingsModule v1.0.0 · code-inspected
Jump to steps
Where to goEnterprise POS → Settings

What you’ll accomplish

Verify enabled access and the deliberate 404 response when disabled. This section documents every live store option, its validation and its operational effect.

Follow these steps

  1. Go to Enterprise POS → Settings and open the workflow that matches “Test the public store enable and disable control”. Confirm the page or record context before making a change.
  2. Go to Enterprise POS → Settings.
  3. Check the current values before editing.
  4. Change only the intended fields and toggles.
  5. Save the settings form.
  6. Go to /shop and a test checkout to verify public behaviour.
  7. Recheck existing orders before changing financial configuration.

Fields and options to review

  • Guide focus: Verify enabled access and the deliberate 404 response when disabled.
  • Store title
  • Currency
  • Tagline
  • Default SEO description
  • Accent colour
  • Default online-stock location
  • Flat shipping charge
  • Internal new-order email
  • Bank-transfer instructions
  • Terms URL
  • Privacy URL

Rules the system enforces

  • Currency must be exactly three letters and is locked after the first order.
  • Money is stored in integer minor units.
  • Accent colour is normalised through the safe-colour helper.
  • Legal URLs must be valid URLs when supplied.
  • The default location must belong to the current tenant.
  • Unchecked toggles are saved as disabled.

How to confirm it worked

  • The specific outcome described by this guide is visible and remains tenant-scoped.
  • The public store reflects saved branding and checkout controls.
  • Checkout methods and stock handling follow the saved toggles.
  • Existing historical order currency and values remain internally consistent.

Safety checks and troubleshooting

  • Test changes in a non-production checkout first.
  • Do not change currency after trading begins; the controller prevents this.
  • Use HTTPS legal URLs and approved email addresses.
  • Do not put secrets or card details in bank instructions or public text.
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.

eCommerce & POS Module overviewUnderstand why currency becomes lockedTroubleshoot a rejected currency changeTest guest checkout settingsTest signed-in client invoice payment availabilityUnderstand the Enterprise POS menuCreate a POS locationBrowse the connected Store settings, branding, legal content and checkout controls topicBrowse all eCommerce & POS Module guidesOpen the related Help Centre category