Troubleshoot an invalid promotion value
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Correct type-specific percent/fixed values.
Where to goEnterprise POS → Promotions
What this guide helps you do
Correct type-specific percent/fixed values. This section explains deterministic money calculations and the live promotion form/selection rules.
Follow these steps
- Go to Enterprise POS → Promotions and open the workflow that matches “Troubleshoot an invalid promotion value”. Confirm the page or record context before making a change.
- Go to Promotions.
- Create a named automatic or coupon promotion.
- Select percentage or fixed amount.
- Set optional minimum line value, category/product scope, dates and usage limit.
- Save and test against a qualifying basket.
- Disable the promotion when it should no longer apply.
Fields and options
- Guide focus: Correct type-specific percent/fixed values.
- Promotion name and optional coupon code
- Percent or fixed type
- Percent/fixed value
- Minimum line value
- Category and product scope
- Start/end date and usage limit
- Active status
- Product price, tax and shipping minor-unit values
Rules and limits
- Money is calculated in integer minor units.
- One best eligible promotion is selected per line.
- Promotions do not stack in the supplied calculation flow.
- Minimum value is evaluated per line, not as a whole-order threshold.
- Public checkout applies public promotion rules.
- Usage increments once per applied promotion per committed order.
Check it worked
- The specific outcome described by this guide is visible and remains tenant-scoped.
- Qualifying lines show deterministic discount/tax totals.
- Expired, inactive, over-limit or out-of-scope promotions do not apply.
- Order snapshots preserve calculated values.
Safety checks and troubleshooting
- Test boundary values and dates.
- Do not assume a stored stacking flag means stacking is active.
- Do not manually alter committed order totals.
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.
Related guides
Was this guide useful?Your response is stored only in this browser.
