The customer's own ERP kept in step both ways

The customer asks: Our ERP and iVendNext kept in step: items, prices, stock and purchase orders

Verdict: Ready, with limits (4)
Door: Outside app · area: Integrations, payments and hardware › ERP
Recipe: Keep a customer's own system in step with iVendNext
Sample: S7 — a system sync: a customer's own ERP, order system or warehouse system in step with iVendNext
Checked: carried 2026-10-16 · not re-run

What you build

Your outside app on the API and the event feed, keeping its own map of record ids, its own place in the feed, and a nightly reconciliation.

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).
Webhooks try three times, then stop: use the feed for anything you must not miss.
One ERP per company.

The ERP and iVendNext stay in step within minutes, and a nightly pass reconciles them.

Tell the customer the 4 limits above, and write them into the proposal.
Follow the recipe: Keep a customer's own system in step with iVendNext.
Copy the sample: S7 — a system sync: a customer's own ERP, order system or warehouse system in step with iVendNext, and change it.
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.