ERP integration services connect business systems so people do not have to carry every record between them. Obdurate Systems builds the workflow layer around your ERP, CRM and internal applications, with agreed rules for what moves, what gets checked and what needs a person.
An illustrative workflow
- 01
Receive
An order, customer update or shipment event arrives from an authorised source.
- 02
Map
Translate fields and identifiers into the format the receiving system expects.
- 03
Validate
Check required values, business rules and whether the record already exists.
- 04
Act
Create a draft, update a record or request approval through a supported interface.
- 05
Resolve
Record the outcome and route failed or ambiguous cases to an owner.
An order is entered twice. A customer changes address in the CRM, but the ERP keeps the old version. Someone copies delivery updates into a spreadsheet because the customer team cannot see the warehouse system. Each application works; the handoff still depends on someone remembering it.
Start with one repeated transfer and the team responsible for it. Connect records, approvals and operational status while keeping the systems that already do their job.
Moving data is only part of the job. A custom API integration needs a source for each field, a way to match records across systems and a decision about which application owns each value. An update should not silently overwrite information owned elsewhere.
The implementation can include API calls, event handling or approved file imports and exports, depending on what your systems support. Legacy system integration starts with those constraints: available interfaces, permissions, rate limits, timing and the ability to test without changing live records.
These illustrate workflows we can assess for your systems; they are not claims of completed ERP projects.
- CRM to ERP
- Match a customer to an existing record, validate required billing fields and pass approved changes to the ERP. Flag conflicting values for review.
- Incoming order to ERP draft
- Turn a structured order into a draft after checking customer and product references. Keep missing information visible before someone approves the next step.
- Shipment event to status view
- Associate an event with the right shipment and update an operational view. Send unmatched references to the team responsible for resolving them.
A receiving system can be unavailable, a message can arrive twice and a request can time out after creating a record. We propose the handling for these cases before release: duplicate checks, safe retries, reconciliation and a named owner for unresolved records.
Delivery starts by mapping one flow and inspecting access constraints. We agree field ownership, build and test against representative cases, then review exceptions with your team. Release planning includes restricted access, traceable outcomes and monitoring so a failed transfer has somewhere to go.
Your ERP's native functions or an integration platform may already cover the requirement. We assess those options against the actual mapping, approval rules, failure handling and ongoing ownership. Custom development makes sense when there is a specific gap worth maintaining, including when a small extension to an existing connector is enough.
Related work: Logistics Control Tower
Our contribution to this collaborative engagement connected shipment events, EDI/API flows and internal systems into an operational layer for monitoring and exception handling. The case study describes the work contributed, with client names withheld.
Read the contributionDo we have to replace our ERP?
The starting point is to keep it and connect the surrounding workflow. We assess supported interfaces and discuss any constraints before development.
What happens when an integration fails or receives duplicate events?
The design should distinguish retryable failures from records that need review. Duplicate prevention and reconciliation depend on the interfaces involved; we agree that behaviour and the person responsible for exceptions before release.
Can you work with a system that has limited APIs?
We can assess supported file exchange, scheduled exports and other approved interfaces. Access is not always possible, and a reliable integration cannot be promised until those constraints are understood.
How do we choose between a connector and custom development?
Compare them against one real workflow, including exceptions, permissions and maintenance. If an existing connector covers the requirement, configuring it may be the right answer.
Which ERP products can you integrate with?
Share the product, version and required workflow. Feasibility depends on its supported interfaces, available access and business rules, which we assess before committing to a scope.
Name the applications, the record being copied, the exceptions and the outcome you need. Start with a short description, without credentials or sensitive operational records.
For the wider system landscape, explore our API and systems integration services.