The iVendNext partner guide
What this is. The guide for everyone who builds for an iVendNext customer — outside partners, customers' own IT teams, and our own Custom Development team. Its outline is the build ladder. Every chapter is written; each says what the kit has proven and what it has not.
Read it before you quote a customer: chapters 1 and 3 first, then the chapter for each rung your project needs.
The guide's own rules. iVendNext names only; no customer named. Each chapter is a plain guide first: what it does and who it is for, a picture where a sample was walked, when to use it, the steps with their commands, what is refused, and what happens when the builder's service is down and when the till is offline. A Technical notes section at the end keeps every technical fact: the tests, what the kit has proven and what it has not, run ids, pins and design choices.
Chapters
| # | Chapter | Status | Recipe · sample |
|---|---|---|---|
| 1 | Welcome and the one path | ✅ written | — |
| 2 | Getting started — sandbox, keys, the first call | ✅ written · the hosted sandbox: recipes/hosted_sandbox.md (not open yet) · sign-in for partner apps: recipes/sign_in.md |
recipes/integration_user.md, recipes/connected_app.md · api/collection/, api/openapi.yaml |
| 3 | The ladder and the four rules | ✅ written | one recipe per rung (linked in the chapter) |
| 4 | Configure first | ✅ written | recipes/configure_no_code.md, recipes/receipt_format.md · samples/s5_config_pack/, samples/s4_receipt_pack/ |
| 5 | Outside apps and the event feed | ✅ written | recipes/connected_app.md, recipes/integration_user.md, recipes/event_feed.md + tools/feed_client/ · recipes/webhook_receiver.md (the nudge) · samples/s1_warranty/service/, samples/s2_bins/service/ |
| 6 | Till keys | ✅ written | recipes/point_handler.md (step 6, the remote key), recipes/ai_till_key.md · samples/s1_warranty/, samples/s2_bins/ · tools/standin_caller/ |
| 7 | Manifests | ✅ written | recipes/manifest.md, recipes/approvals.md · samples/s11_approvals/manifest.json (the permission example), samples/s2_bins/manifest.json · tools/manifest/ |
| 8 | Sandboxed functions | ✅ written · no published extension point offers one yet | tools/wasm_kit/README.md, tools/wasm_kit/CONTRACT.md |
| 9 | The extension points, and how to ask for a new one | ✅ written · six live, the rest specified or being specified; the library is published with the kit's first release | extension-point request form |
| 10 | Integrations | ✅ written | recipes/system_sync.md, recipes/estate_rollout.md, recipes/bi_feed.md · samples/s7_system_sync/, samples/s8_estate_rollout/, samples/s9_bi_feed/ |
| 11 | Payments, fiscal, hardware | ✅ written · the fiscal reader is the one open door; payments and the wallet are not covered yet | recipes/manifest.md (fiscal_readers) · tools/manifest/ |
| 12 | Handheld and the other apps | ✅ written · no Handheld document was booked in a kit test | tools/feed_client/ · samples/s7_system_sync/ |
| 13 | AI on iVendNext | ✅ written | recipes/ai_till_key.md, recipes/ai_manager.md · tools/mcp_server/ · samples/s6_ai_till_key/, samples/s10_ai_manager/ |
| 13a | Screens and user experience | ✅ written · Desk actions, pages and the standalone portal shipped | samples/s2_bins/manifest.json (native screens) · samples/s16_pick_route/ (Desk action) · samples/s17_partner_page/ (page in our frame) · samples/s13_portal/ (a standalone portal) |
| 14 | Testing and release | ✅ written | recipes/release_gate.md · samples/s12_release_gate/ · recipes/money_kit.md (the idea) · tools/manifest/ |
| 14a | Deploying to a chain of stores | ✅ written | recipes/estate_rollout.md · recipes/manifest.md · recipes/connected_app.md |
| 15 | Customer archetypes | ✅ written | samples named per example |
| 16 | Possible, not possible, limits | ✅ written | per row |
| 17 | Submitting, support, feedback | ✅ written · submission opens with the repository | feedback/, kit/blueprint.md |