Magento inriver: Bring Product Data From the PIM Reliably Into the Shop

inriver keeps product data centrally: articles with their attributes, relationships, media and language versions. The PIM is the source for everything a customer reads and sees about a product, while prices and stock usually come from an ERP. A shop is one of several channels fed from the PIM.

For Magento inriver that means: product data goes from inriver into the shop, usually only in this direction. Articles released in the PIM with descriptions, attributes, images and translations are created or updated in Magento as products. The advantage is obvious: your editorial team maintains data once, and every channel receives the same state.

The data model of inriver can be designed freely. Two businesses with inriver therefore often look very different: other entities, other fields, other relationships. Magento inriver therefore always begins with the question how your model is built and which parts of it are needed in the shop.

Prices, stock and orders usually do not belong in the PIM. We clarify in the inventory which data comes from which system so that the shop does not have contradicting sources.

Another point is the release process. In inriver articles usually pass through states such as draft, review and release. Magento inriver takes over only released articles so that unfinished texts never appear in the shop. What these states are called and what they mean we clarify with your editorial team, because it determines when an article becomes visible in the shop.

Which data flows in Magento inriver you define with us in the inventory. Typically there are five areas.

Not every Magento inriver project needs all five areas. Often it begins with orders and stock and later grows by article maintenance and documents. This way you see results quickly and can use the budget in stages.

The table shows a typical pattern. In your business it may differ, and that is exactly what we clarify in the inventory.

With Magento inriver a clear rule on data ownership prevents most disputes. Whatever can be changed in both systems leads to contradictions sooner or later. That is why we define exactly one leading system per type of data and describe the rule for the conflict case. Especially with variants, units and tax rates an assignment table that the department and the developers review together is worthwhile.

For Magento inriver, inriver offers according to the information we found a REST interface. The login runs through an API key that is generated in the administration area and sent along as a header. According to the vendor the documentation of the interface is available as an interactive description, and through it the model, entity types and entities can be queried. The vendor has developed the interface further in recent years.

According to agencies there is also an official adapter for Adobe Commerce that takes product data from the PIM into the shop. This information comes from posts by third-party vendors, we did not find an official description of the adapter. Whether and how far it covers your model we check before the quote and tell you openly if it is enough.

For Magento inriver the same holds as for every integration: the interface is only half of the work. The other half is the mapping: which field becomes which attribute, which entity becomes which product type, which language becomes which store view. We keep this mapping in the admin as settings so that it can be changed without development.

For the connection of inriver and Magento there is an adapter that agencies describe as official, as well as solutions from third-party vendors. Whether one of them fits your model we check honestly before a decision. If an existing adapter covers your requirements, it is often the more economical choice, and we will tell you so.

An individual development for Magento inriver pays off if your data model deviates from the usual: own entities, complex relationships, special rules for variants or several shops with different ranges. It is more expensive at the start but fits exactly. Include the care as well: a ready-made product saves development time but causes license and update costs, and an individual development needs someone who looks after it.

A middleware pays off if more than two systems are connected, for example PIM, ERP, shop and marketplaces. The decision aid is in the guide to ERP integration.

On the Magento side we build the integration as its own module according to the standards of the system, without interventions in the core. The module uses the interfaces and queues of Magento so that transfers run in the background and the shop does not become slower for visitors. Orders are placed in a queue on arrival and processed there until the ERP has confirmed them.

Prices by customer group, tier prices and several warehouses are mapped by Magento with its own functions that the integration fills. Where possible we use these standard functions instead of inventing our own tables. That keeps the shop update-capable and lets other developers join in later.

In the admin you see what was transferred: a log shows date, record and result, with a filter for errors. For the peculiarities of inriver we add settings in the admin, for example assignments of payment methods, shipping methods and tax classes, so that changes need no development.

With inriver the data model is the focus: entities, fields and relationships are freely defined in the PIM. Magento inriver therefore begins with mapping this model to the product types, attribute sets and categories of Magento.

We see these points again and again in projects. They can be planned if they are known early.

• Free data model

  The model in the PIM does not fit the product types and attribute sets of Magento and needs a clean assignment.

• Variants

  The variants in the PIM are formed differently than in Magento and lead to duplicate or missing products.

• Media

  Large images and many documents prolong the import and overload the transfer.

• Unclear data ownership

  Texts are changed in the PIM and in the shop and overwrite each other.

• Missing monitoring

  A failed import is noticed only after days because nobody looks at the log.

• Languages

  Missing translations lead to empty fields in individual store views.

An integration connects two systems with business data, so clear rules apply. The exchange runs encrypted, credentials do not lie in the source code but in the protected configuration, and the integration receives only the rights it needs. Access belongs to a separate service account, never to a private account of a person.

When testing we work with test data or anonymized data as far as possible. As soon as developers get access to personal data, for example customer accounts or orders from inriver, an agreement on commissioned data processing is needed. We clarify that before the start so that you are legally well set up.

The log of the integration contains what is necessary for operation but no credentials and no unnecessary personal data. Retention periods are defined with you. These notes are not legal advice, the concrete arrangement depends on your company.

We keep the start deliberately short so that you quickly know whether and how the integration is feasible.

The following constellations are examples from the practice of Magento inriver projects, not statements about particular customers. The first is a manufacturer with thousands of articles that are maintained in several languages and for several channels. The PIM is the only source for product texts, and the shop must not overwrite them.

The second constellation is a merchant with many variants and own relationships in the PIM. The challenge lies in mapping variants and accessories cleanly in Magento and keeping the order of the images. We define early what stays in the PIM and what arises in the shop.

The third constellation is a business that switches from another shop system to Magento and keeps inriver. Here the existing connection is the benchmark: what it achieves today the new shop should at least achieve. How the switch itself runs is described on our page on migration.

In all three constellations a delta comparison proves itself with Magento inriver: only articles that changed since the last run are transferred. That shortens the run time, spares the shop and makes errors easier to find. A first full run with a small part of the range serves as a test before all articles follow.

An interface is not a one-off project but ongoing operation. After the start a log monitors every transfer: what was transferred when, what failed, what is repeated? Errors that cannot be fixed automatically are reported visibly so that nobody learns of them only through a customer complaint.

Updates change the situation. A Magento update, a new state at inriver or a change of the vendor interface can affect the integration. Therefore the planning includes an agreement on how updates are tested and who approves them. Ongoing care can be regulated through a maintenance contract that covers monitoring, updates and error fixing.

Documentation is part of the delivery. You receive a description of the data flows, the assignments and the rules for special cases so that your team or another provider understands the integration and can continue it. Source code and access stay with you.

A flat figure for Magento inriver would be unreliable because the effort depends on your constellation. It is determined by the number of data flows, the quality of the data in inriver, the number of special cases with attributes, variants, media and languages and the required timeliness. A data flow in one direction is built much faster than a synchronization in both directions with conflict rules.

We work with an open hourly rate of 30 euros net, without emergency surcharge. After the inventory you receive a written estimate that lists the data flows individually so that you can control scope and order yourself. For clearly defined packages a fixed price is also possible. All prices are on the page pricing.

Besides the development, include the running items: hosting, maintenance and, where applicable, licenses or fees for inriver and for additional services. We show these items separately in the estimate so that you can compare quotes over several years.

An honest offer includes naming the limits. We do not sell a ready-made connector off the shelf but develop Magento inriver project by project according to your processes. That means: we implement exactly what you need, but not in a day and not for a flat price that cannot be calculated beforehand.

We are a web agency in which fixed freelancers work together, all from home offices. We are not a large agency with a hundred employees and cannot take on every project at every time. We tell you early whether and when we have capacity. We name customers only with their consent, and in the first conversation we gladly talk about comparable constellations.

We give no legal advice. Questions about commissioned data processing, data protection and the license terms of inriver you clarify with your legal adviser and the vendor. What is technically possible depends on version, operation and license of your system and is checked in the inventory.