INRIVER PIM INTEGRATION PROCESS

Integrating PIM with external systems with various types of data sources is a process that requires planning. We aim for a future-proof, plug & playable solution following the MACH standards. We identify inputs and outputs and define the interfaces between the systems involved. After the interfaces are clearly defined, each team can work on their side and contribute to the big solution.

Modularity of the arhitecture

We can integrate many different modules into your solution depending on your business needs. The integration can be a one-time data load or a continuous synced data exchange. Each module should be easily maintainable and replacable. While disconnecting the module from the system, the rest of the solution needs to keep working as no change is happening. The modularity of architecture enables multiple integration dev teams to work in parallel to reduce the overall time to market.

mach example

The usual flow of the integration process

The flow can be modified to support your specific business case

  • DEFINING THE INPUTS

     phase 1
    We list the existing data sources and plan the data flows. Each field that enriches the product needs to be listed and its owner defined, whether it is an ERP system, a CMS system, an arbitrary file or the PIM system will asume the ownership of a field.
  • DEFINING THE OUTPUTS phase 2
    We define where data needs to be sydicated out of the PIM system, and we define the interfaces. We use the existing connectors if they fit our needs or create new ones from scratch.
  • DEFINING THE FLOWS phase 3
    How data travels to and out of the PIM system should be a simple and straightforward process. The modern MACH approach utilizes the asynchronous patters that are easily monitored and retried if needed. The "transfer everything" action should be implemented and used for unexpected cases to recover from possible errors.
  • DRAW A PICTURE phase 4
    A picture is worth more than a thousand words. The entire tech landscape that integrates with the PIM system is presented in a clear diagram.
  • DEVELOP THE INTEGRATION MODULES phase 5
    Integrate system by system as a repetable process consisted of development work and testing. Data needs to be synced in both directions. If PIM updates data, external systems need to be notifed. If an external system updates the data, the PIM should know about it. We utilize the concept of webhooks to keep the modularity of the solution intact.
  • SIMULATE EDGE CASES phase 6
    Simulate transport errors and test the failover process. In the real world power outages exist, connectivity issues occur, peak loads happen. We are prepared for that.

Initial Data Load

We can help you import existing data to your PIM system or do the import for you. Data needs to be verified and checked before the actual import. You can read more details about the data load in the initial data load section.