What it does
One rule per customer group, held at every Pay: while a sale detail the group needs is empty, the till refuses the sale in your words.
What it does
- A rule per customer group: the sale details it needs, and the POS Profiles it holds on (none: every till).
- A group with no rule takes the nearest rule above it; its own rule replaces that one, so a rule with no details lets a group off.
- At Pay the cashier reads which details are missing, fills them under the sale's details and presses Pay again.
- Refunds are not judged; the walk-in customer's group counts too. An exchange or a quote's sale has no place to fill a detail.
How to set it up
- Make the app's user: tick Is Desk User, give it only the role IVENDNEXT RSD Integration (the install makes it), no User Permissions; generate its API key.
- In Role Permissions Manager, give that role Read on Customer Group.
- Customize Form for Customer: Customer Group's Perm Level 1, level 1 Write for managers only, no cashier (check Sales Master Manager). New customers take the default group.
- In Sale Attribute, make each detail your rules name (Active on, Required off). Whoever keeps the rules needs Select on Customer Group, Sale Attribute, POS Profile.
- In IVENDNEXT RSD Rule, add one rule per customer group that needs details.
- On IVENDNEXT RSD Rules feed choose that user as Application User. In Retail Extension Subscription open Required sale details: read what it sends, tick the consent, choose its POS Profiles, switch it on. Last, in the App library open Details and press Connect again.
Good to know
- At every Pay and refund the sale goes to required-sale-details.ivendnext.app (CitiXsys, US), with the cashier, the customer and the sale's details as typed. It reads your rules and groups, writes nothing, keeps no sale.
- No answer in 3 s, offline, or a key not yet sent by Connect again: the sale goes on, flagged for review. Must never sell without them? Set the down answer to Refuse after Connect again.
- It checks a detail is filled; the Sale Attribute's own pattern checks its value.
- A POS Profile takes at most three checks, 10 s together. Not checked: a park, a layaway deposit, an account collection, the Desk's POS screen.
- Adds
- 1 new list · 1 event feed · 1 till extension
- Used by
- Retail manager, Store manager, Cashier
- Licence
- Apache-2.0
Version and changes
Version 1.0.0 · 24 Oct 2026
1.0.0 (24 Oct 2026): First listed version, hosted by CitiXsys.
Need it your way?
An iVendNext partner can tailor this app to how your stores work: your own fields, rules and screens, delivered to your site alone. Ask your partner, or ask us through Help to introduce one in your region.
For builders: this app's code is open in the Partner Kit (Apache 2.0) · The code · How to make it your own
Related apps
Counter hardware
Connects the counter's cash drawer, receipt printer and customer pole display to the till. Set up each counter once in Desk; the counter's computer runs QZ Tray.
Age-restricted sale check
For alcohol, tobacco, vapes and other restricted goods: the till shows the date of birth to check at the scan, records the ID check on the sale, and refuses Pay without it.
Click and collect
A Desk board for the web orders a store must pick and hand over: the web orders still to pick, and on each delivery note who collected it. Nothing leaves your shop.
Call-centre orders by district
Phone orders sent to the store that serves the customer's district: set a store on each Territory, and Send to store on a draft order ships it and its lines from that store.