Updated
Evaluate system integration services through record ownership, idempotency, retries, reconciliation and a worked CRM-to-ERP order workflow.
A system integration services company should demonstrate how records stay correct when messages are duplicated, delayed, rejected or missed. A successful API call proves connectivity. A reliable integration also needs ownership rules, traceable business outcomes and a way to reconcile systems after failure.
Consider a fictional distributor whose CRM sends approved orders to an ERP. The ERP allocates stock, a payment provider reports payment state, and the CRM shows progress to the sales team. This is a useful procurement exercise because a superficially successful demo can still create duplicate orders or display an incorrect payment status.
Assign ownership at field level
Write down which system owns each business fact. The CRM may own the opportunity and sales contact, while the ERP owns stock allocation and the payment provider owns payment events. Do not allow both systems to overwrite the same field without a conflict policy.
Distinguish business identifiers from local database keys. A customer can have one stable integration identifier and separate CRM and ERP record identifiers. Preserve their mapping rather than assuming that matching names or email addresses establish identity. Document merges and corrections as well as new records.
Define what users see during disagreement. If the ERP rejects an order because inventory changed, the CRM should expose the rejection and a next action. Reporting “synced” merely because a request was sent hides the business failure from the person responsible for resolving it.
Turn the workflow into an explicit contract
An integration contract should identify required fields, allowed state changes and the meaning of success. In our example, “approved by sales” and “accepted by the ERP” are different states. An order should not advance to fulfillment based only on an optimistic CRM update.
Specify stable order and customer identifiers.
Define currency, units, rounding and time-zone representation.
Distinguish missing fields from deliberate empty values.
Identify the authority for prices, discounts and delivery addresses.
State which changes are allowed after an order is accepted.
Document validation errors that require a person's decision.
Set a versioning rule for changes that affect consumers.
Keep a sample of both accepted and rejected payloads.
Ask the supplier to explain these choices in business language before selecting middleware. If the underlying rule is ambiguous, adding an integration platform only distributes that ambiguity more efficiently. The REST and GraphQL comparison can inform an interface decision after the workflow is clear.
Design duplicate handling around the business action
Networks fail between a request being accepted and the caller receiving its response. A retry can therefore repeat an operation that already succeeded. Use stable idempotency identifiers where supported, and make repeated processing safe at the receiving boundary.
Stripe's idempotent request documentation is one concrete example of a provider's retry contract. Read the actual contract for each connected service; do not assume every API keeps keys for the same duration or treats mismatched parameters identically.
For the distributor, a repeated “create ERP order” operation should resolve to the existing mapped order, not create another shipment. A message identifier helps deduplicate deliveries, but the business identifier is also necessary when separate messages represent the same action. Handle concurrent deliveries with an appropriate database constraint or transaction rather than a check that can race.
Expect delayed and out-of-order events
The Stripe webhook documentation describes duplicate events, ordering considerations and signature verification. These are useful test cases even when your own integration uses a different provider. Verify incoming messages before acting on them, using the provider's required request representation.
An older event must not reverse a newer confirmed state accidentally. Decide whether to use a monotonic version, an authoritative resource lookup or an explicitly allowed state transition. The correct choice depends on the source system; comparing timestamps alone may fail when clocks differ or events describe different facts.
Acknowledge receipt only after the message has reached a durable point appropriate to the design. If slow work is placed on a queue, ensure that the queue handoff succeeded before reporting that the event was accepted. Then record processing state independently from receipt state.
Reconcile business outcomes, not just queue depth
Queues and logs can look healthy while one order never reached the ERP. Schedule reconciliation around business records: approved CRM orders without ERP mappings, paid orders still pending, or fulfilled orders whose CRM status is stale.
Give each mismatch an owner and a safe repair path. Replaying a message should be controlled, observable and idempotent. Store enough context to explain the repair without retaining unnecessary personal information indefinitely. A downloadable failure list with no ownership does not provide an operating process.
Keep a bounded retry policy for transient failures. Invalid credentials, unsupported currency and malformed addresses may require different treatment from a brief provider outage. Repeating a permanent validation error thousands of times increases noise and delays the action that would actually fix it.
Make failure scenarios part of acceptance
Ask the proposed supplier to demonstrate the following with a test account before production access:
Deliver the same order event twice and verify one business outcome.
Stop the destination service, restore it and inspect recovery behavior.
Reject one malformed record while allowing unrelated valid work to proceed.
Deliver a stale event after a newer state and check the result.
Revoke an integration credential and verify visible failure and containment.
Introduce a missing record and show reconciliation finding it.
Replay a repaired record and verify the complete audit trail.
Keep test credentials separate from production credentials. For access-control concerns, use the API security testing guide to define authorization cases beyond transport encryption.
Contain the vendor dependency
Check that the external API exposes the operation your business needs; a feature in the vendor's interface may not be available through its public API. Review authentication, scopes, pagination, rate limits, version policy, support arrangements and test-environment limitations before committing to a delivery plan.
Keep provider-specific payloads behind a clear integration boundary. Map them to your own business concepts and retain external identifiers separately. This makes a vendor change easier to assess without pretending that an adapter removes every migration cost. Define a continuity process for a critical dependency that becomes unavailable.
Store credentials securely, restrict their authority and plan rotation. Confirm permitted data use, processing location, retention and deletion handling against the applicable contract. Caching an external response also needs an explicit freshness and permission policy; it should not preserve access to information a user can no longer read.
Compare proposals by operating responsibility
Separate connector implementation from data cleanup, account setup, historical migration and ongoing incident response. A low connector quote can omit the work required to reconcile years of inconsistent customer records. Request explicit assumptions about record volumes, supported systems and support hours.
Build the estimate from discovery, authentication, field mapping, workflow logic, failure testing, monitoring and handover. Include recurring provider charges and maintenance for version changes, credential rotation, incidents and data repair. Endpoint count alone does not capture these costs: one payment action may require more controls than many read-only queries.
To reduce scope, choose one useful workflow, limit fields and avoid unnecessary bidirectional writes. Validate the vendor capability with representative records first. This produces a defensible estimate without inventing a universal integration price or delivery time.
Is real-time synchronization always necessary?
No. Stock allocation may need prompt confirmation, while a daily reporting extract may tolerate a scheduled batch. Select timing from the business consequence of stale data.
What should the handover contain?
Field ownership, state transitions, mappings, monitoring, credential rotation, reconciliation procedures and replay instructions. Include evidence from failure tests and identify who maintains each connector when an API changes.
How do we start with an unclear integration scope?
Choose one order journey and enumerate the states and exceptions with its business owner. Contact Voquarn with the connected applications and representative records, so discovery can expose the data and recovery requirements before implementation is estimated.
Written by
Moueen Togarvi
Founder & CEO at Voquarn Code, focused on product engineering, search growth, and practical AI systems.
