Samples

Each sample is a small working example of one way in, with its tests. Pick the nearest one to your project, run it against your sandbox, and change it. Each card opens the sample's own page: what it does, how to run it and what its tests prove.

• S1 — warranty check (pp_wrc), connected leg

  you want to do something with every booked sale (register it, notify someone, audit it) and show the result to staff on the sale itself.

• S2 — bin locations (pp_bln): where stock sits inside a store

  your product keeps its own data beside the shop's (here, bins) and staff should see it in Desk and at the till.

• S3 — price-deviation audit: every line sold below list by more than a threshold

  you want an after-the-sale check on prices, discounts or anything else a booked sale carries.

• S4 — the receipt pack: a UAE tax invoice on the till sale

  the shop's receipt must carry what your market's tax rules ask for, and you want to ship that layout as a package the shop installs and removes cleanly.

• S5 — the configuration pack: reasons, IMEI, a line detail, member pricing

  what the shop needs is already in iVendNext and only has to be switched on and filled in.

• S6 — the AI till key: a short hint from the customer's own AI model

  the cashier needs an answer, during the sale, that only your service can give.

• S7 — a system sync: a customer's own ERP, order system or warehouse system in step with iVendNext

  another system is the master for items, prices or stock, and it must also learn of every sale.

• S8 — an estate roll-out as code: fifty stores and three regions from one file

  you open or change stores in numbers, and need to see what will change before it does and prove afterwards that the shop matches the file.

• S9 — a BI feed: sales, lines, payments and returns into a warehouse file, picking up where it stopped

  reports or dashboards outside the shop need the shop's sales, kept up to date and checked against the till's own end-of-day figures.

• S10 — the manager's AI assistant

  a manager wants to ask "what sold in the Durban store yesterday?" or say "put the 10% off AirPods promotion on" in plain words.

• S11 — price-change approvals with a nightly export

  a change must be requested, approved by someone else, and only then applied, with a record of who did what.

• S12 — the customer's release gate

  before every release, in your pipeline, against a staging shop.

• S13 — a standalone portal with "Sign in with iVendNext"

  a screen of your own, outside the shop, for people who already have shop accounts. If the screen can live inside the shop, use the native screens first (guide chapter 13a).

• S14 — price-change approvals across stores

  an approval whose approver depends on the store, and on how big the change is. For one shop with one approver, S11 is enough.

• S16 — Assign pick route (pp_pck): a Desk action

  you want a button on a Desk record that sends the record to your service and shows the answer.

• S17 — an order board (pp_pge): a partner page

  your service needs its own screen in the till or in Desk, and may hand one answer back to the sale.

• S18 — Members-only rule guard (a check before payment)

  When the cashier presses Pay, the shop's server prices the basket and asks this service. It refuses a sale that holds a members-only item for a customer who is not a member, in its own words, and asks the cashier for ID when the sale is at or above the shop's limit. Everything else is allowed. A refused sale books nothing.

• S19 — Unit codes at the scan (a scan source)

  The shop's own unit codes, read by the till's scan: one record per unit (its unique code, its item, its batch, Available or Sold) and a scan source over that table. A scanned unit lands as its item with its batch; a sold unit is refused. Data only: no service, nothing leaves the shop.

• S20 — Warranty capture and a member code (capture)

  Two capture services, each at its own address. On scan of an item in the named item groups, before its line goes on the sale, the service answers with a warranty reference for the line (a value of a line attribute the shop keeps). On customer add, before the customer is created, it refuses a customer without a mobile number or with a barred one, and otherwise sends a one-time code: the customer is created only after the right code. No answer writes a customer field or moves money.

• S21 — Field rules for one till theme

  The shop's own words and fields on one till theme, with no code: the sale's line reads Product, the customer's card says Stars, the new-customer sheet has no email field, and a new customer needs a phone. Data only.