AX-10 · Extend
Integrations
Payment, commerce, attendance, messaging, and other systems connected to ERPNext with a written contract for each flow.
Typical length: Scoped per integration
Outcome
A flow that fails visibly, retries safely, and has an owner when the other system changes.
Who it is for
- Stores selling on a web shop as well as by sales order
- Plants with biometric attendance
- Finance teams that want collections to land as payment entries
What is included
- Flow contract
- Source, target document, keys, what updates, what never updates, and how a human fixes a rejected row.
- Common connections
- Payment gateways, online stores, email, shipping, banks where a file or API exists, and attendance devices.
- Build
- Frappe REST, webhooks, or a scheduled job. Secrets stay in site config, not in a script body.
- Operate
- A log, an alert, and a short runbook. An integration without an error queue becomes a silent stock problem.
How the work runs
- 01Name the business eventPaid order, delivered shipment, or clock-in — not “connect the API”.
- 02Prove one directionThe happy path and one failure, on staging credentials.
- 03Hand over the runbookWho looks at the error log on a Monday morning.
Deliverables
- Interface note per flow
- Staging proof
- Error handling runbook
- Credential handover list