Retries, imports and manual entry can produce two records for one business object. A unique database key is helpful but cannot settle every semantic duplicate. A supplier can be created twice when two onboarding paths use different names or identifiers. Merging later may break orders, payments and audit trails. Decide which identifiers are authoritative and how possible matches are reviewed before a new record is accepted.
What good engineering looks like
What stable business identity identifies the same object across systems? Answer this for a named workflow and an accountable team. Identify the information needed at the moment of decision, the system that can settle a dispute, and the route for correcting dependent copies. The technical design should make those business rules visible to the people who operate and support the handoff.
-
Keep source identifiers and a trace of each transfer.
-
Detect exact and likely duplicates before mutation where possible.
-
Give an owner a merge or rejection route with an audit trail.
-
A named owner for a rejected, delayed or repeated item.
-
Evidence that the receiving system applied the intended business state.
A practical starting point
-
Choose one real case and write down its trigger, expected outcome and responsible team.
-
Submit two realistic records for the same party with minor spelling differences.
-
Check whether the system flags a possible duplicate, who decides whether to merge or retain both, and how linked transactions are protected. Keep evidence of the resolution so the next import does not recreate the problem.
-
Record what the test exposed, who will resolve each open question and how the fix will be checked.
Keep the first design small enough to review with the people who run the process. Test an exception alongside the normal case. A successful transport test shows that data moved; it does not by itself prove that the receiving team can make the right decision or recover from a partial failure.
The decision to make
Do not auto-merge uncertain matches where an incorrect merge would harm customers or operations. Decide what level of timing, traceability and recovery this workflow actually needs. Document assumptions that remain untested and revisit the choice when a partner, process or business rule changes. The point is a dependable operating decision, not simply a working interface.
Explore Algoza's related services: https://algoza.co.za/services/integration