Data model, mapping and interface for your product information system
Whoever maintains product data, media and translations in inriver and runs a Magento shop does not want to enter them a second time by hand. This guide explains how you connect inriver to Magento, which data flows and what determines the effort.
Table of contents
- 1. What it means to connect inriver to Magento
- 2. Which data flows between shop and inriver
- 3. Die Wege, um connect inriver to Magento
- 4. Typical pitfalls when you connect inriver to Magento
- 5. Ready-made product or individual development: how you decide
- 6. The process when you connect inriver to Magento
- 7. Effort and costs when you connect inriver to Magento
- 8. How we support you with the integration
- 9. Summary
- 10. FAQ
1. What it means to connect inriver to Magento
inriver is a product information system (PIM) in which articles with attributes, relationships, media and language versions are maintained centrally. When you connect inriver to Magento, the PIM becomes the source of product content in the shop: released articles are created or updated in Magento as products, usually only in this direction.
The benefit shows in daily work. Your editorial team maintains data once, every channel receives the same state, and only released content appears in the shop. Prices and stock usually come from an ERP, the PIM delivers descriptions, attributes, images and translations.
This guide is aimed at manufacturers, merchants and managing directors who use inriver. The page on PIM integration and the guide to ERP integration give an overview, the guide merchandise management, ERP and PIM classifies the system types, and we describe the service on our page Magento inriver.
2. Which data flows between shop and inriver
| Data | Leading system | Direction | Typical rhythm |
|---|---|---|---|
| Products and attributes | inriver | inriver to shop | regularly or on release |
| Categories | inriver | inriver to shop | on change |
| Media | inriver | inriver to shop | on change |
| Translations | inriver | inriver to shop | on release |
| Prices and stock | ERP | ERP to shop | depending on need |
| Feedback on the import | Shop | Shop to inriver | optional, depending on concept |
Before planning technically, you define which system leads for which data. Whatever can be changed in both systems leads to contradictions sooner or later. Therefore define exactly one leading system per type of data and record the rule for the conflict case in writing. As a rule product texts stay in the PIM, and the shop does not overwrite them.
The data model of inriver can be designed freely, so every project needs an assignment table: which field becomes which attribute, which entity which product type, which language which store view. The department and the developers review it together, because the same terms do not always mean the same.
3. Die Wege, um connect inriver to Magento
There are essentially four ways for the connection. The first is the direct connection through the REST interface of inriver. According to the information we found, the login runs through an API key that is generated in the administration area and sent along as a header, and the documentation is available as an interactive description. Through it the model, entity types and entities can be queried.
The second way is a file exchange, which is simple and robust but not in real time. The third way is a ready-made adapter: agencies describe an official adapter for Adobe Commerce, we did not find an official description, so you should check scope and maintenance state before a decision. The fourth way is an individual development. Which way fits depends on data model, data volume and your processes.
4. Typical pitfalls when you connect inriver to Magento
Five points we always address
- ✓Data model: the model in the PIM does not fit the product types and attribute sets of Magento.
- ✓Variants: they are formed differently in the PIM 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.
- ✓Languages: missing translations lead to empty fields in individual store views.
Most of these points can be avoided with planning and a log that makes errors visible. Whoever wants to connect inriver to Magento should also demand a delta comparison: only articles that changed since the last run are transferred. An integration is ongoing operation, so care belongs from the start, best within a maintenance contract.
5. Ready-made product or individual development: how you decide
Whoever wants to connect inriver to Magento should first check whether an existing adapter covers your data model. If it covers your requirements, it is often the more economical choice. Before the decision check how it is maintained, how far the mapping can be adapted and what happens on updates of Magento or inriver.
An individual development pays off if your 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, and it needs someone who looks after it later. Have the costs over several years calculated before you decide.
6. The process when you connect inriver to Magento
Anyone who wants to connect inriver to Magento is best advised to proceed in four steps. First the inventory: which version of inriver do you use, how is it operated, which access exists, which data flows are desired and which special cases are there? From this a short concept arises that also records which system leads for which data. Then the work is done on a test system, never first against live data.
In the third step you check with real examples whether everything is correct: articles, orders, special cases. In the fourth step the start is made step by step, first the simple data flows, then the others. In the first weeks you look at the log together, which shows every transfer and every error. After that the integration runs in operation, and an agreement on updates prevents it from failing at the next update.
7. Effort and costs when you connect inriver to Magento
The effort depends on the complexity of the data model, the number of articles, languages and media, the special cases with variants and relationships and the desired timeliness. A data flow in one direction is built faster than a comparison in both directions. Besides the development, include the running items: hosting, maintenance and, where applicable, licenses.
A flat figure would be unreliable. We estimate in writing after the inventory, the hourly rate is 30 euros net, see pricing. General hints on costs are in the guide Magento costs.
8. How we support you with the integration
We are a web agency in which fixed freelancers work together, all from home offices. We develop the integration project by project, according to your processes and with documented rules, and we do not sell a ready-made connector off the shelf. Source code and access stay with you. More about our approach is on the page Magento inriver integration.
This guide gives general orientation. For a first conversation a short message through our contact page is enough. Please name your system, the version and the desired data flows, then we can assess the feasibility specifically.
9. Summary
Whoever wants to connect inriver to Magento makes the PIM the source of product content in the shop. Decisive are a clean mapping of the data model, clear data ownership and planning for ongoing operation.
Connect inriver to Magento at a glance
Clarify first
Data model, release process, access and desired data
Mapping
Assign fields, entities and languages to attributes, product types and store views
Ways
REST interface, file exchange, adapter or individual development
Operation
Plan log, delta comparison and care
Note: This article offers general orientation. The concrete feasibility depends on version, operation and configuration of your system.