Useful integration starts with responsibility: which source is authoritative, who can change it and how do we recover when an exchange fails?
An order in the portal. An account in the ERP. A follow-up in another tool. At each handoff, someone checks, re-enters or asks whether the information is still correct.
Connecting systems can simplify that journey. But moving data from point A to point B is not enough: the whole process must remain understandable to the people using it.
For the customer account, price or order, which information is authoritative? The answer can vary by data type. The ERP may hold commercial terms, while a field application holds the record of a customer visit.
The goal is to define these roles before adding an interface. A screen can display information without owning it. This distinction helps prevent rules maintained in two places and contradictory corrections.
In an illustrative scenario, a portal prepares a request and submits it after approval. We need to identify required fields, the identifier linking records, permissions and exchange timing.
We also need to distinguish a received request from a processed request. A vague success message can lead a team to believe an order exists when it is still awaiting a check. Status should reflect what the system actually knows.
A service can be unavailable. A reference can be missing. A user can click twice. These situations should not leave the team guessing whether an action took place.
We define what can be retried, what must wait for a correction and what needs a human decision. Tracking identifiers and duplicate prevention belong in the scope to validate. A useful alert explains the blocker and how to continue.
Recovery deserves as much attention as the normal workflow.
A first engagement does not need to connect the entire business. A piece of information re-entered each day, a representative order or a handoff between two teams can provide a precise starting point.
At Progymédia, our approach is to understand this work, define the architecture and build exchanges around existing systems. Possibilities depend on the interfaces, access and constraints in your environment. Assessing them is part of the work from the start.
A price or document comes from the ERP. That does not mean every click needs to ask it for a fresh response. Here is how we organize these exchanges.
Processing an invoice takes more than reading its total. The right documents need to be found, their information compared and discrepancies given a clear next step.
