Configure cash on delivery or collection expectations
Explain the supported cash option operationally; there is no separate enable toggle in version 1.0.0. 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 goEnterprise POS → Settings
What you’ll accomplish
Explain the supported cash option operationally; there is no separate enable toggle in version 1.0.0. This section documents every live store option, its validation and its operational effect.
Follow these steps
- Go to Enterprise POS → Settings and open the workflow that matches “Configure cash on delivery or collection expectations”. Confirm the page or record context before making a change.
- Go to Enterprise POS → Settings.
- Check the current values before editing.
- Change only the intended fields and toggles.
- Save the settings form.
- Go to /shop and a test checkout to verify public behaviour.
- Recheck existing orders before changing financial configuration.
Fields and options to review
- Guide focus: Explain the supported cash option operationally; there is no separate enable toggle in version 1.0.0.
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.
