The customer's own order or warehouse system
The customer asks: Our order-management or warehouse system linked to the stores
- Verdict: Ready, with limits (2)
- Door: Outside app · area: Integrations, payments and hardware › Online shops and order systems
- Recipe: Building a connected app
- Sample: none yet
- Checked: carried 2026-10-15 · not re-run
What you build
Your outside app over the API and the event feed; the customer's systems stay its own, and you connect to them.
Limits
- The feed reports a change after it is saved, so your app corrects after the fact.
- 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).
Tell the customer
The order and warehouse systems exchange records with iVendNext through our app.
What next
- Tell the customer the 2 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