Alteration and made-to-measure tickets
The customer asks: A garment's alteration or made-to-measure order taken at the counter, with its fitting, due date and hand-over
- Verdict: Ready, with limits (3)
- Door: Manifest · area: Documents and print › Your own records, fields and buttons
- Recipe: Alterations and made-to-measure tickets
- Sample: S53 — Alterations and made-to-measure tickets (pp_alt)
- Checked: 2026-10-29 · bench
What you build
A ticket as your manifest's own record type: the garments and what to do to each, the measurements, the next fitting, the date it is ready, the tailor, and the till sale or order it was paid on. A workflow Taken → With the tailor ⇄ Fitting → Ready to collect → Handed over sets a tick, Ready to collect, that the retailer's own Notification reads to tell the customer; a print format gives the customer's slip and the garment's tag; a report lists the tickets due. The charge and any deposit stay at the till (a service item or a line surcharge; the till's order or a layaway).
Limits
- The ticket is written in iVendNext Desk; staff name the sale or the order on it. A till key that writes it from the basket is a version of your own.
- Who may edit a record in a workflow state is checked in the browser only: follow the four safeguards in chapter 13a.
- A manifest's notification goes only to the retailer's own users: the message to the customer is the retailer's own Notification (an SMS one names the phone in its condition, or each ticket of a customer with no phone logs a failed send).
Tell the customer
Each alteration and made-to-measure piece has a ticket from the counter to the hand-over, with a slip, a garment tag, its fittings and a message when it is ready.
What next
- Tell the customer the 3 limits above, and write them into the proposal.
- Follow the recipe: Alterations and made-to-measure tickets.
- Copy the sample: S53 — Alterations and made-to-measure tickets (pp_alt), 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.
Install it on your sandbox the way the shop's administrator will; the checker refuses a manifest that declares code.
Related needs
- A button on a record that rechecks stock in our ERP or assigns a pick route — Ready, with limits (1)
- Extra fields on a purchase order and its lines, a goods receipt, a stock transfer, an expense or the till close — Ready, with limits (1)
- Keep each customer's prescriptions in iVendNext — Ready, with limits (2)
- Keep our own records, such as a warranty register, in iVendNext with their own screens and print formats — Ready, with limits (2)
Start a project shortlist with this need · Put it in your blueprint · Every need