Installation

Requirements, the two packages you install, and the first connection.

Configuration

The connection, what it syncs and how often, and the plugin settings that apply to every ERP.

Connectors

The supported ERPs, why the add-ons are free, and how to write one for an ERP that is not on the list.

Field mapping

Rules, the transform vocabulary, and the overlay that lets a mapping correct the connector itself.

Syncing

Runs, delta watermarks, dry runs, dead letters and replay — and the console commands to put on cron.

Orders and B2B

Pushing completed orders, contract pricing at cart time, credit limits, and the Twig helpers.

Troubleshooting

Where to look first, and the failures that turn out to have ordinary causes.

FAQ

Licensing, the add-on model, what happens to your data, and the questions that come up before a purchase.

Erpy for Acumatica

Acumatica Cloud ERP through the contract-based REST endpoint, with one shared session per run so the integration does not spend your licence on logins.

Erpy for AFAS

AFAS Profit through GetConnectors and UpdateConnectors, with every connector and field name configurable because your implementation partner chose them.

Erpy for Business Central

Microsoft Dynamics 365 Business Central through the standard API v2.0 and an Entra ID app registration, with optional published pages for the prices and shipments Microsoft never exposed.

Erpy for Exact Online

Exact Online through its REST API, with the OAuth consent step, the rotating refresh token, the daily rate limit and division scoping handled for you.

Erpy for MYOB

Two connectors in one add-on, MYOB Acumatica (formerly MYOB Advanced) through the contract-based REST API and MYOB Exo through the Exo API gateway.

Erpy for NetSuite

Oracle NetSuite through SuiteTalk REST and Token-Based Authentication, with every bulk read done in SuiteQL so a large catalogue does not take all night.

Erpy for Odoo

Odoo Community or Enterprise through the external JSON-RPC API, with an API key, delta syncing on write_date, and errors read from the body because Odoo answers everything with HTTP 200.

Erpy for Priority

Priority ERP through its OData REST interface, addressing the same forms your consultant works in, with every form name configurable because no two Priority installations are alike.

Erpy for Sage

Four connectors in one add-on, for Sage Intacct, Sage 200, Sage X3 and Sage Business Cloud Accounting, four unrelated products that happen to share a name.

Erpy for SAP Business One

SAP Business One through the Service Layer, with one shared session so the licence is not spent on logins, and the tYES/tNO booleans and day-granular deltas handled for you.

Erpy for Unit4

Unit4 ERPx and Business World, with every resource path configurable and both authentication schemes offered, because no two Unit4 estates expose the same API.

Erpy for Visma

Visma.net ERP (Financials) through the integration API, authenticated with Visma Connect and scoped to one company, with delta syncing that actually filters.

Erpy Documentation