Connect your ERP without replacing it: data, permissions and tests

When should you connect the ERP rather than replace it?

When the ERP handles part of the operation well and the problem is at a boundary: sales captures orders elsewhere, customers cannot check their status or another department enters the same data again. Replacement adds migration and changes in working habits; keeping the system also requires checking whether it can exchange the missing information.

Follow an order from capture to closure. Mark each copy, approval and difference. If the problem is inside the ERP rules, review configuration first. If it crosses systems, define the connection. If the system no longer supports the process or a viable extension, assess replacement with scope and consequences in writing. The ERP-versus-custom comparison helps choose that level; this guide tests the connection.

Existing connector, API or files: which route fits?

Access does not follow from a product name. For example, Odoo 19’s external API documentation limits that access to its Custom plans and applies user permissions. Confirm your edition, hosting and contract: this reference does not mean every installation or plan allows the same connector. For another ERP, review its documentation and account terms.

If an existing connector passes your tests, another custom connector is unnecessary. If files are the only option, agree how much delay the process tolerates and how to detect changes since export. A claim of connecting to everything does not replace identifying a permitted operation and demonstrating it.

Which system controls each field?

Write a matrix before linking two screens. These are example decisions rather than assignments required for every business:

Bidirectional must not mean either system changes everything. If both edit a field, define conflict resolution and approval. For location quantities, complement the matrix with inventory between warehouses; for a spreadsheet catalog, prepare inventory migration from Excel first.

What access does the connection need?

Use an identifiable integration user with read/write access limited to the flow rather than the personal account that administers everything. Define what it may read, create, change or cancel and how access is revoked. Keep credentials outside shared spreadsheets and record actions and errors without exposing sensitive data.

Odoo 19’s API uses user permissions, record rules and field access; an API key does not remove those restrictions. In your tests, changing a customer identifier must not reveal another customer or allow out-of-scope changes. These are requirements the integration must pass, rather than guarantees created by a technology choice.

Worked example: one order, two attempts and an uncertain response

Download the ERP integration test CSV and pack instructions. A newly authorized order change is not the same event merely because it shares ORD-100: distinguish it from retrying op-100. Identity belongs to the operation rather than only the document.

An error can mean the destination received nothing, or that it saved the record but the response was lost. Creating again without checking can duplicate the order. If the interface cannot verify the result, agree on manual reconciliation or change the flow; repetition alone does not solve the uncertainty.

What if notifications arrive twice, late or out of order?

Automatic notifications help but do not replace confirmed state. Shopify documents that webhook delivery order is not guaranteed and explains delivery verification and duplicate handling. For your connection, decide what identifies a delivery, what identifies the business action and how to query current state before applying a delayed change.

Ask for a reviewable list of pending, rejected and confirmed operations. Reconciliation compares references, lines, quantities and states between origin and destination rather than simply counting successful send responses. Agree its frequency and owner according to the flow’s risk; a partially received order must stay in that review.

Which tests and recovery plan need to be written down?

Define who may pause the connection, where the team continues recording and how new references are preserved. On recovery, resume from the last confirmed result and reconcile pending operations. Returning to an older copy does not undo receipts, sales or physical movements that happened meanwhile; preserve those facts and correct the records with evidence.

What should you bring to the first integration stage?

A representative document, its fields, the current workflow, ERP edition, access conditions and exception examples. Choose one flow with a clear acceptance criterion. Separate configuration, development, provider access and maintenance in scope rather than assuming a license includes the full integration.

The CelMex Unlockers case shows orders and connections to digital-service providers. It supports integration work at that scope, not a delivered connector for every ERP or physical logistics. If customers need to consult or request orders, review the customer portal.

Use the scope worksheet with the data matrix and E01–E04 to agree on the test. See our approach to ERP development and extensions and process automation. Evaluate the option that fits your operation first; a connection does not require replacing what works.

Primary sources reviewed October 5, 2026. Availability, permissions and terms must be confirmed for the specific product and account; the proposed test does not guarantee provider access or an already implemented result.