Pimcore 11 has no REST webservice, so mappio writes through the Datahub GraphQL API: objects found by key, created under the folder you choose, updated one language at a time. The connector is in beta and this page says exactly what it does and does not do.
ConnectionSupplier files are built for humans. Pimcore is built for a schema. Most of the work is the distance between the two, and it comes back with every new file.
Pimcore 11 dropped it. Everything runs through a Datahub configuration you create yourself, which decides which classes are readable and writable and holds the API key.
A Pimcore object is not addressed by an identifier attribute but by a key inside a folder tree. A supplier row has to resolve to a key before anything can be written.
Localized fields are updated per language, which means a wide multi-language catalog is many small mutations rather than one document.
You draw the mapping on a canvas. Tricky rules are described in plain language and compiled once into a fixed rule, so runs stay reproducible. Below is what the Pimcore side of that actually does.
You create a Datahub configuration in Pimcore, expose the classes you want to fill, set an API key on the security definition and activate it. mappio connects to that endpoint with the key. Nothing is installed inside Pimcore.
Pick the class and the attribute rail scopes to its fields, the same way a family or a template does on the other two PIMs.
Before writing, mappio looks up the keys it is about to touch and decides per row whether that is a create or an update. The sweep finds unpublished objects too, so an object you created in an earlier run is updated instead of duplicated.
New objects are created under a folder path set per profile. When the Datahub configuration exposes object folders, you pick it from a searchable tree read live from Pimcore; when it does not, you type the path.
One create, then one update mutation per language, paced so a large catalog does not flood the endpoint. An update with nothing in it is skipped rather than sent.
Upload, share link or email intake, the visual flow editor, AI-compiled transforms, the Translate and Compose blocks, the row-by-row dry-run, the approval workflow, create, update and upsert modes, and delta sync are identical to the Ergonode and Akeneo paths. Only the write differs.
Values are written through Datahub update mutations per language. Select values map to the codes your class expects; mappio does not create new values or fields in the class definition.
We would rather you read this before you sign up than find it in week two. Every item below is a real boundary of the Pimcore connector today.
It writes to a real Pimcore instance today: it finds objects by key, creates them under a target folder and updates values per language. It has fewer features than the Ergonode and Akeneo connectors, and they are all listed here.
An object created by mappio is not published. Publishing stays a Pimcore decision. The key sweep does find unpublished objects, so the next run updates that object rather than creating a second one.
No variant parents and axes, no creating select values or options, no option enrichment and no workflow status transitions. Those are Ergonode and Akeneo features.
You cannot create a new class field from the editor. The class definition is managed in Pimcore.
The key sweep matches across all folders. If the same key exists twice you get a duplicate-key warning and the write targets the first match.
A wide multi-language catalog paces slower than the batched Ergonode and Akeneo write paths, where many products travel in one request.
Reading object folders is off by default in a Datahub configuration. Enable it to get the folder tree, or type the target path instead.
Pimcore 11 through the Datahub GraphQL API. Pimcore 11 has no REST webservice, so Datahub is the integration surface. You create a Datahub configuration, expose the classes you want to fill, set an API key on its security definition and activate it.
It writes to a real Pimcore instance today: it finds objects by key, creates them under a target folder and updates values per language. It is younger than the Ergonode and Akeneo connectors and has fewer features, which are listed on this page. We call it beta so you can judge that for yourself.
No. Objects created by mappio land unpublished, and publishing stays a decision in Pimcore. The existence sweep does find unpublished objects, so a later run updates the object you created rather than making another one.
By object key. Before writing, mappio sweeps the keys it is about to touch and decides per row whether that is a create or an update. The sweep matches keys across all folders, so if the same key exists twice you get a duplicate-key warning and the write targets the first match.
Yes. Everything before the write is the same as for Ergonode and Akeneo: the flow canvas, transforms, AI-compiled rules, the Translate and Compose blocks, the row-by-row dry-run, the approval workflow and delta sync.
The editor, the transforms and the workflow are shared. Only the write path differs per PIM, so each connector has its own page.
Start a workspace, connect your Pimcore instance and map your first supplier file. Fourteen days free, no card charged during the trial.
