For enterprise

Keep your PIM.
Check what goes into it.

openProd prepares supplier data before it reaches your PIM. Roles decide who can save and who can sync, and every change is on record.

Book a demo See integrations

Your week

Many suppliers, one PIM to protect.

When a catalogue is shared by many teams and fed by many suppliers, the questions are about control. Here is how openProd answers them.

  • Supplier files should not go straight into our PIM.

    openProd works in front of it. Files are read, mapped and checked there, and only the products you choose go on to your PIM.

    Synchronized

  • Not everyone should be able to publish.

    Roles decide who can create imports, who can apply them to the catalogue and who can run a Pimcore sync.

    Run Pimcore sync

  • Who changed this, and from where?

    The audit log records who changed what and when, with the source: the interface, an import, the API or the MCP server.

    Source Β· Import

  • AI costs have to stay predictable.

    Every analysis starts with a credit estimate someone accepts. The top bar shows this month's credits, with an organisation total where your role allows it.

    5–9 credits

01Integrations

In front of the PIM you run.

openProd reads your Pimcore model and prepares the matching structure. Supplier data is checked against it before the products you choose go back.

One job reads the model Classes and fields from Pimcore become families, attributes, units and dictionaries in openProd.

  • Pimcore connector

    Choose products to synchronize and see the state of each, verified in Pimcore.

  • Akeneo and Ergonode

    Supplier data is prepared and reviewed before it reaches your catalogue.

  • Your own systems

    Connect them through the openProd REST API.

See all integrations

02Security and governance

Who, what, when, and from where.

Users are invited by email and work within their roles. The audit log shows every change with its actor and its source.

Every change on the record Writes through the MCP server appear in the audit log with MCP as source and actor.

  • Users and roles

    Administrators manage users and roles. The interface hides actions a role cannot perform.

  • Audit log

    Products, attributes, assets, categories, settings, users and sign-ins, with retention settings.

  • Version history

    Every product save is a version you can compare and restore.

Security and governance

03MCP server and API

Open to your tools, within your rules.

AI assistants and agents read the catalogue through the MCP server and write only with scoped access. Your own systems use the REST API.

Read from the catalogue itself The client answers with the values DEMO-SEN-009 has in openProd, not with a guess.

  • MCP server

    Look up products, families, attributes, units and dictionaries, and update them with write access.

  • REST API

    Documented endpoints for your own systems. Reading the API documentation is a role permission.

  • One record

    Changes made through the API or MCP appear in the audit log with their source.

Explore the MCP server

Scenario

A pilot with one supplier.

How a first run can look with the openProd demo data and a Pimcore instance.

  1. Connect

    Read the model

    A connector job reads your Pimcore definitions and prepares families, attributes, units and dictionaries in openProd.

    Sync data model from Pimcore

  2. Configure

    Set the roles

    The supplier data team can create imports. Applying them to the catalogue and syncing stay with the catalogue owner.

    Apply imports to the catalog

  3. Pilot

    Run one supplier file

    Demo Supplier A's data sheet and weight update go through one import. The team decides what is uncertain.

    19 of 40 values

  4. Go live

    Sync what was checked

    The two new NPN sensors go to Pimcore and count as synchronized only once the result is verified there.

    Synchronized

Demo data. Demo Supplier A and its products are synthetic.

Questions

Before you roll it out.

Do we have to replace our PIM?

No. Use openProd in front of your PIM: supplier files are read, mapped and checked in openProd, and your PIM stays the system your channels use. Teams without a PIM can keep their catalogue in openProd.

Which PIMs does openProd work with?

openProd prepares supplier data for Pimcore, Akeneo and Ergonode. For Pimcore there is a connector that reads your data model and synchronizes the products you choose. How openProd connects to your setup depends on your edition and components; we agree it with your team and test it in a pilot.

Who can save data to the catalogue?

Only users whose role includes Apply imports to the catalog. Save to catalog asks for a confirmation, and the preview shows every change before it is written.

What does the audit log record?

Who changed what and when across units, attributes, families, products, assets, categories, settings, users, roles and sign-in events, with the source of each change. Retention is configurable.

Can AI tools change our catalogue?

Only through the openProd MCP server, with a token and scoped write access. Every write appears in the audit log with MCP as source and actor.

Where can our security team find more?

The Trust center describes how openProd handles security, privacy and data. Bring your questions to the demo and we answer them for your setup.

Pilot with one supplier file. Your PIM, your roles.

In the demo, we walk through your PIM, your roles and one of your supplier files.

Book a demo Visit the Trust center