A feed of your own app's events
The customer asks: Our app gets its own queue of what changed, with business labels
- Verdict: Ready, with limits (1)
- Door: Event feed · area: Integrations, payments and hardware › Events from the shop
- Recipe: Reading iVendNext's events reliably
- Sample: none yet
- Checked: carried 2026-10-15 · not re-run
What you build
The event feed extension point: your app pulls its own queue (sales, customers, stock) and marks each item done.
Limits
- The kit's feed client and its samples have not been run against this extension point: not run.
Tell the customer
Your app reads its own queue of changes and nothing is lost while it is down.
What next
- Tell the customer the 1 limit above, and write it into the proposal.
- Follow the recipe: Reading iVendNext's events reliably.
- 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.
Stop your service for a while and start it again: it must catch up from the event feed, missing nothing.
Related needs
- Change the limits and who is told in one settings page, not in each rule — Ready, with limits (3)
- Check a limit (an item's maximum discount, say) against the ceiling only when someone sets or changes it, not on every edit of the record — Ready, with limits (3)
- Our system hears about every sale, return and stock move — Ready, with limits (3)
Start a project shortlist with this need · Put it in your blueprint · Every need