Ergonode PIM integration

Who this connection is for

Ergonode is a cloud PIM: the product team works in a browser and the vendor runs the system. Data is organised with attributes, product card templates, category trees and language versions, while images and files live in a built-in multimedia library. It tends to be chosen by companies that have outgrown spreadsheets but do not want to set up and maintain a PIM server of their own.

The integration makes sense when the product team in Ergonode owns descriptions and parameters and the B2B shop only has to display them. If content is written directly in the shop admin panel, a PIM connector is not needed.

What moves from Ergonode to the shop

There is one direction: from Ergonode into the Endora Commerce catalog. The shop sends nothing back to the PIM.

• Products and attributes: product data from Ergonode updates the shop catalog after each sync.
• Categories: the category tree travels with the products.
• Media: image files assigned to a product reach the shop together with it.

Customer-specific prices, stock levels and trading terms follow a different route: they usually come from the ERP, not from the PIM. Ergonode is responsible for how a product is described, not for what it costs a particular company. ERP connections are covered on the all integrations page.

When a sync runs

There are two ways of working and both can be used together:

1. Schedule: the import starts according to a set timetable, with nobody involved.
2. On demand: an administrator starts a sync manually from the admin panel, for example after a large round of description edits or before a campaign launch.

The shared contract for PIM connectors in Endora Commerce describes every import run with the same vocabulary. A run has a status (queued, running, completed, completed with issues, failed, skipped), a mode (delta or full) and item counts: considered, created, updated, skipped, withdrawn and failed. Import issues carry one of three severities: info, warning, error.

What to prepare on the Ergonode side

Ergonode exposes data to integrations through a GraphQL API. Before go-live it is worth checking a few things described in the vendor’s documentation:

• API key. Keys are created in Ergonode system settings, in the API keys tab. By default a key has read-only access. A key cannot be changed later; if needed, a new one is generated. Details are in the authentication guide.
• Segment. A key can be tied to a segment, in which case it only sees the products in that segment. This is a convenient way to send the B2B shop only the part of the range that is meant to be sold there, not the whole PIM catalog.
• Request limits. The API has a per-minute request limit that depends on the plan and a limit on concurrent requests, with a separate limit for fetching multimedia files. With a large catalog full of images this affects how long the first, full import takes. Current values are listed on the API limitations page.
• Product types and languages. Ergonode distinguishes simple products, products with variants and grouping products, and lets you maintain content in multiple languages. Before launch you need to decide which types and which language versions should reach the shop.

One active PIM and switching connectors

Several PIM connectors can be installed on one installation, but at most one is ever active. On a fresh install none is switched on: the operator picks one on the modules screen. An attempt to enable a second one is refused, naming the connector that is already running.

Switching connectors does not destroy data. Products imported earlier stay in the catalog, and the connection settings, mappings and run history of the connector you switched off are preserved and come back unchanged when it is enabled again. This matters when migrating between PIM systems: you can switch the source without rebuilding the shop catalog from scratch.

The shared PIM connector layer also defines a uniform way of pointing at fields an administrator wants to protect from being overwritten on import: the name, the description, a single attribute, SEO fields, a gallery position, an attachment, a price in a price list or a category assignment. The protection scope available for Ergonode is confirmed during implementation.

Ergonode or a different PIM

If Ergonode is already running in your company, the choice is simple: the shop connects to what you have. The field scope, the segment and the schedule are easiest to settle in a short conversation, so get in touch.