ERPNext / Frappe scope
Identify which Frappe apps and ERPNext records your team uses before defining a connection. Separate operational job updates from accounting entries and agree how custom fields map to Ever.
What we scope together
Review the installed edition and supported API, map customer and product identifiers, define tax and UoM handling, then agree invoice/payment references and recovery from sync failures. Availability depends on the scoped connector and acceptance tests.
Match the actual Frappe application and document model
Confirm the ERPNext/Frappe versions, installed apps, custom fields and document lifecycle used by the business. Map customer/item identifiers and approved transactions before granting write access. Custom DocTypes and workflow approvals can change the connection scope; an integration discovery should test the real configuration rather than assume every Frappe deployment is identical.
- 1Daily operations
- 2Ever Platform
- 3Ever Connect
- 4ERP / accounting system
- 5Review & reconcile
Connection scope and availability follow the published status.
What to bring to discovery
Provide the system/version, hosting model, relevant modules, record types, data owner and desired direction of flow. Describe one successful handoff and one exception, such as a duplicate or rejected record. We can then scope mapping, authorization, retries, reconciliation and acceptance. Share synthetic examples first; credentials and private exports belong in an agreed secure implementation process.
Your questions, answered
Does this page mean the connector is live?
No. Use the displayed status. Coming Soon, Planned and On Request entries require further implementation or scoping; they are not represented as accepted production connectors.
Can we request a custom connection now?
Yes. Request an integration with your workflow and system details. Ever Digital can define a bounded custom scope and acceptance plan; delivery depends on the agreed interface, access and implementation.