Prescriptions kept as records
The customer asks: Keep each customer's prescriptions in iVendNext
- Verdict: Ready
- Door: Manifest · area: Documents and print › Your own records, fields and buttons
- Recipe: Shipping your own data in a manifest
- Sample: none yet
- Checked: carried 2026-10-15 · not re-run
What you build
Prescriptions as your manifest's own record type.
Limits
None known.
Tell the customer
Prescriptions are kept in iVendNext, with their own screen.
What next
- Follow the recipe: Shipping your own data in a manifest.
- 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.
Install it on your sandbox the way the shop's administrator will; the checker refuses a manifest that declares code.
Related needs
- A coded reason when a cashier voids, returns or discounts — Ready, with limits (3)
- Insurance co-payment: the insurer pays part of a prescription and the customer the rest — Not yet
- Keep the controlled-drug register the law asks for — Not yet
- A prescription number is required before a prescription item is paid for — Ready, with limits (1)
Start a project shortlist with this need · Put it in your blueprint · Every need