The four rules, and when the product has no door
Part 3 of 4 · 16. What is possible, what is not, and the limits
Back: Possible today with an extension point or a manifestNext: How it behaves before you quote, and technical notes
The four rules
- Money enters the sale visibly, before payment, and is never changed after the cashier has seen it; on a back-office document, before it is submitted.
- Don't override or patch iVendNext.
- Your code runs on your server; inside the customer's site you ship data.
- Your screens come through our doors — on the till your page as a sheet over the sale, the till's own sheets when an item is scanned, a customer is picked or a quantity changes, and extra fields; in Desk buttons, your pages and native screens. You can't put your JavaScript inside our screens.
The reasons and the alternatives are in chapter 3.
When the product has no door for it
The catalogue's cards whose verdict is Not yet (a new extension point, or product work on our side: ask us) or Not possible (it breaks one of the four rules), each with what to do instead.
| The customer asks | Verdict | Instead, today, and what to ask for |
|---|---|---|
| Add our own step or screen to Handheld | Not yet | Today: react to what Handheld books, from your own service reading the new records on the site. Ask us: the step you need in Handheld. |
| Build our connector inside iVendNext's integration framework | Not yet | Today: build an outside app instead. Ask us: to build the connector. |
| Change the order of the till's steps, or what every cashier sees | Not yet | Ask us: the change to the till's steps, with the reason; it is product work, not an extension point. |
| Customers pay with a buy-now-pay-later provider | Not yet | Ask us: a buy-now-pay-later tender in our payment connectors. |
| The final receipt printed while the till is offline | Not yet | Today: a provisional slip offline; the final receipt once the till reconnects. Ask us: a final receipt offline. |
| The next sale starts with the sales person of the last completed sale, splits included | Not yet | Ask us: a Retail Setting that carries the last completed sale's sales person (and splits) into the next sale. Today the sale starts with the cashier, then the profile's default seller, and the cashier changes it. Try on a sandbox (not run): add the cashier as the sales person by default, or have the seller scan a badge at tender. |
| Our country's tax and e-invoicing rules | Not yet | Today an outside fiscal service can record its result through a fiscal reader (the card outside-fiscal-result). Ask us: the country, through a fiscal app of ours. |
| A server in each store | Not yet | Ask us: a store server. |
| Several companies, countries or currencies in one site, with connectors | Not yet | One company is one country and one currency. Today: one site per company, so several countries mean several sites. Ask us: several companies in one site. |
| A surcharge added to the sale because of the payment method or a condition | Not possible | Instead: put the fee on the sale as an item the cashier adds before payment; a check before payment can refuse the sale, with your sentence, until that line is there (not run; not yet in the guide). |
Back: Possible today with an extension point or a manifestNext: How it behaves before you quote, and technical notes