What UnoPim is and who it suits
UnoPim is a PIM with a built-in DAM, released under the MIT licence and installed on your own infrastructure (PHP with MySQL, MariaDB or PostgreSQL). Its data model is typical for this class of tool: attributes grouped into families, a category tree, simple and configurable products with variants, plus channels, locales and currencies. The product team gets a completeness score for product records, CSV and XLSX import and export, and a change history.
In practice it is picked by companies that have outgrown spreadsheets and description fields in the ERP, want full control over the installation and have PHP skills at hand. For a distributor or manufacturer with a technical catalog it is a way to put parameters and images in order before they reach the shop.
What flows from UnoPim to the shop
There is one direction: from the PIM into the Endora Commerce catalog. The shop writes nothing back to UnoPim.
- Product content: descriptions, attributes and categories land in the shop catalog.
- Images: product media sync together with the product record.
- Schedule: regular sync keeps the shop current without retyping by hand.
The integration is about content. Price lists, stock levels and customer trading terms are separate modules in Endora Commerce, usually fed from the ERP, for example through Comarch ERP Optima.
Import runs and what the admin sees
The UnoPim connector is a separate module package with its own section in the admin panel. Imports are recorded as runs, described with a vocabulary shared by all PIM connectors:
- mode: full or delta,
- trigger: manual or scheduled, among others,
- status: queued, running, completed, completed with issues, failed, skipped,
- counts: how many items were considered, created, updated, skipped, withdrawn and how many failed,
- issues at three severity levels: info, warning, error.
“Completed with issues” is a state of its own, distinct from “failed”: an import can finish, and the issue list shows what deserves a look on the data side.
Protecting fields from being overwritten
Not every value has to come from the PIM. A sales rep may write a better description in the shop, or order the gallery differently from the product team. That is why an admin with catalog write permission gets a protection toggle labelled UnoPim in the product editor: a protected field is not overwritten by the next import, and the run reports it in a separate count.
The protection grammar shared by PIM connectors covers the name and description (also per locale), individual attributes, SEO fields, gallery positions, attachments, category assignments and prices in a specific price list.
What to prepare on the UnoPim side
| Item | What to watch for |
|---|---|
| API credentials | The UnoPim REST API uses OAuth: you need a client ID and secret plus the username and password of an API user. |
| API user permissions | Since version 3.0 UnoPim enforces permissions on reads as well, so the account must be able to see products, categories, attributes and media. |
| Network reachability | The UnoPim instance must be reachable from the server running Endora Commerce. |
| UnoPim upgrades | Version 3.0 replaced the shared OAuth signing keys with per-installation keys, which invalidates tokens issued earlier. Check the connection after such an upgrade. |
The details are in the UnoPim API authentication documentation.
One active PIM and switching systems
Several PIM connectors can be installed on one installation, but only one is active at a time. Trying to enable a second one ends with a message naming the connector that is already active. A fresh install has none active: the admin picks one on the modules screen.
Switching does not destroy data. Products imported earlier stay in the catalog, and each connector’s connection settings, mappings, field protections and run history are preserved and come back when it is enabled again. That makes a migration to UnoPim from another system, or the other way round, easier.
UnoPim or another PIM
UnoPim is a sensible choice when the MIT licence, self-hosting and a PHP stack matter to you. If the company already works in Akeneo, Pimcore or Ergonode, there is no reason to change PIM for the sake of the shop: each of them has its own connector. The full list of connections is on the integrations page.
