Your system told of sales, returns and stock moves
The customer asks: Our system hears about every sale, return and stock move
- Verdict: Ready, with limits (3)
- Door: Outside app · area: Integrations, payments and hardware › Events from the shop
- Recipe: Building a connected app
- Sample: none yet
- Checked: carried 2026-10-15 · not re-run
What you build
An outside app reads the event feed and reacts to each sale, return and stock move.
Limits
- The kit's samples read the shared feed, whose key is not limited to one app (a feed scoped to your app is an extension point, chapter 9).
- Webhooks try three times, then stop: use the feed for anything you must not miss.
- An offline sale's events appear when the till syncs, possibly hours later.
Tell the customer
Your system hears of each sale, return and stock move shortly after it is saved.
What next
- Tell the customer the 3 limits above, and write them into the proposal.
- Follow the recipe: Building a connected app.
- 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
- Filter the product list to the products on promotion — Ready, with limits (3)
- Open quotations cancelled every night; a report sent every morning — Ready, with limits (1)
- Orders from our own online shop come in; stock and prices go out — Ready, with limits (2)
- Our CRM sees our customers and their sales — Ready, with limits (2)
Start a project shortlist with this need · Put it in your blueprint · Every need