Sale details some customers must give before paying
The customer asks: An account customer's purchase order number, an insured patient's policy number or a contractor's project required at Pay, and nothing asked of other customers
- Verdict: Ready, with limits (8)
- Door: Check before payment · area: Till controls and approvals › Payment
- Recipe: Required sale details: the details a customer group gives before paying
- Sample: S50 — Required sale details (pp_rsd): the details a customer group gives before paying
- Checked: run on our test bench 2026-10-24 · a rule per customer group refusing Pay while a needed sale detail is empty, a group taking the rule above it, a rule held only at its POS Profiles
What you build
A rule record per customer group naming the sale details it needs (Sale Attribute) and, optionally, the POS Profiles it holds on, and a service that answers the check before payment with refuse and the retailer's words while one of them is empty. A group with no rule takes the rule of the nearest group above it.
Limits
- Answered when the cashier presses Pay, not when the customer is chosen.
- The detail must be filled, not checked: its shape is the Sale Attribute's own pattern.
- The sale's details only, not a line's.
- Refunds are not judged. An exchange's new items are, as a sale, except an exchange rung without its sale when nothing is owed.
- A detail switched off, or hidden by a field rule, cannot be filled at the till.
- An exchange's screen and a sale made from a quote have no place to fill a sale detail: fill it on the quote first; refund and ring a new sale instead of an exchange.
- A group's own rule replaces the rule above it entirely.
- Offline sales are flagged when they reach iVendNext, never refused.
Tell the customer
At Pay the till asks for the details your rule needs for that customer's group, in your words; other customers are never asked.
What next
- Tell the customer the 8 limits above, and write them into the proposal.
- Follow the recipe: Required sale details: the details a customer group gives before paying.
- Copy the sample: S50 — Required sale details (pp_rsd): the details a customer group gives before paying, and change it.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Test it with your service stopped: the till applies the answer you declared for when it is down.
Related needs
- A coupon only a new customer may use, or only customers of one group — Ready, with limits (6)
- A coupon or a loyalty points balance pays no more than part of the sale — Ready, with limits (1)
- Delivery-platform customers paying only by the platform's method, no on-account for a cash customer, and methods that may not be combined — Ready, with limits (6)
- Insurance co-payment: the insurer pays part of a prescription and the customer the rest — Not yet
Start a project shortlist with this need · Put it in your blueprint · Every need