Map a supplier's file to your PIM once, in a visual editor. After that, every new file from that supplier publishes on its own. No developer ticket, no redoing it in a spreadsheet.
You do the thinking once, when you build the mapping. Every file that arrives afterward follows that same rule, so a file that ran clean last month runs clean this month too.
Drag the columns from the supplier's file onto your PIM's fields on one screen. The tool proposes matches on its own, and a completeness badge shows straight away how much of the required data is covered.
For a rule that needs a small decision, such as "if the size is EU46, use 46", describe it in plain language. The tool turns it into a fixed rule with a confidence score attached. Below 0.8 it flags the rule for a second look instead of letting it through.
Files arrive by upload, a link, or straight from email, and publish to your PIM on the schedule you set. No one needs to touch that supplier's mapping again until the file itself changes shape.
For your IT colleague: a run makes no model calls, it only replays the fixed rule from step 2, so behaviour is reproducible from one run to the next. The security section below has the rest.
A live badge for required-field coverage, per-field required and optional toggles, and a row-by-row before and after dry-run before anything is written.
A schedule per profile, in your workspace timezone. A worker publishes the profiles that are due and sets the next run, so no one has to remember to do it.
Export any selection of mappings as one portable file and import them into another workspace. It carries the mapping design only, never credentials and never data.
A source rail of detected columns, a live PIM attribute rail, and drag-to-connect edges between them, with auto-layout, ghost-edge suggestions and variant markers. In between sit the transform blocks: ValueMap, RegexReplace, Template, Expression, Concat and Split, and a decimal-tolerant Calc node.
Each workspace has its own learning environment. Approved mappings are remembered, so the next supplier file opens with better suggestions than the one before it.
Sign up online and a guided setup walks you from connecting your PIM to your first mapped profile. Every plan starts with a 14-day free trial, and you get your own workspace subdomain.
Connect Ergonode, Akeneo in both the open-source CE and the Serenity SaaS, or Pimcore 11 through its Datahub API (beta). One visual mapping experience; each connector handles its own write semantics.
Idempotent runs (create, update, upsert) with delta sync, so only changed products are re-pushed. Push to a staging PIM first, then production, with live progress and per-row results. Batched GraphQL for Ergonode, ND-JSON for Akeneo, Datahub mutations for Pimcore.
Text, select and multi-select with option creation, multi-currency prices, units and metric families, dates, relations, categories, and Akeneo channels and locales. Create brand-new PIM attributes right from the editor.
Suppliers rarely send the text your channels need. Two blocks in the flow editor write it for you, and you stay the editor of record.
Connect one field and fill every language your channel needs. A single English description populates Dutch, German, French and the rest in one pass.
Pick the fields the text should be built from, add your own instruction, and get a written product text per row. A webshop description from brand, material and size, for example.
Correct a text once and your correction wins over the model from then on. It applies everywhere that value appears in your workspace, and it survives switching AI provider or model.
Set one tone of voice for the whole workspace, and list the terms that are never translated, such as brand and product names.
Before a run you see how many AI calls are new, how many values come from memory, and the estimated cost. Bring your own key (Anthropic, OpenAI, Gemini, or your own endpoint), with usage and cost tracked per workspace. Or work without a key at all and use the built-in matching.
The AI is spent at design time. Every value is remembered per workspace, so a re-run of an unchanged file makes no calls and produces exactly the same result.
Stop chasing suppliers for files. Upload one yourself, point a profile at a share link, or give the supplier an email address. Every route lands in the same mapping, on whatever schedule you set.
Drop an Excel, CSV or XML file on the profile. You pick which row holds the column names, with an optional second row of friendly labels.
Paste a share link and the file is fetched right away, then again on every scheduled refresh. No addresses or sender rules to manage.
Every profile gets its own address. Inbound mail is signature verified, unknown senders confirm by double opt-in, and a changed file structure sends the profile back to review.
Google Drive 
DropboxGoogle Sheets, iCloud Drive and any direct file URL work the same way.
This section is written for whoever signs off on new tools touching your PIM. Send them this part first.
Every sensitive step is gated, every tenant is isolated at the database, and every action is on the record.
TOTP two-factor with recovery codes and a freshness window. Approvals, production runs, role changes, and secret access can each require fresh 2FA.
A tenant ID on every scoped table with Postgres row-level security, enforced fail-closed at the database, not just in the app.
PIM keys, TOTP secrets, and credentials are stored in libsodium sealed boxes. Bring your own AI provider key, with token and cost tracking.
A reviewed, admin-approved profile lifecycle and an append-only audit log with a filterable activity timeline. Per-tenant custom subdomains with automatic TLS.
Beyond Admin and User, define custom roles with per-feature rights: who can approve, run, or create attributes and options.
Profiles move through New, In progress, In review, Approved and Archived. Admins tailor which stage transitions exist per workspace, and can move or edit profiles at any stage.
Combined with a deterministic runtime and a mandatory dry-run before any production write, this is the part of the product built for your review, not for the catalog team's daily use.
The full product on every paid plan. You only choose how many suppliers you run. Per tenant, billed monthly upfront.* These are introduction prices, valid through 31 December 2026.
A supplier you set up today keeps publishing on its own, from every new file.
Your catalog team builds mappings in a visual editor. No engineering ticket.
Dry-run previews and deterministic replays keep your PIM clean.
2 supplier profiles
For a first one or two suppliers. Build your first mappings, see dry-run results before anything publishes, and get comfortable with the workflow.
5 supplier profiles
For a team whose supplier list grows most months. Everything in Start, plus room to keep adding suppliers without a new conversation about pricing each time.
50 profiles
For a data team handling supplier volume that no longer fits a fixed count. Everything in Grow, without a profile ceiling.
Unlimited + SSO
For organisations that need single sign-on, a custom domain and an SLA.
These are introduction prices, valid through 31 December 2026.
A mapping you build once keeps publishing on its own, file after file, without anyone rebuilding it from scratch. No setup fee. Bring your own AI key and there is no metered AI charge on top, or skip the key and use the built-in matching. Change plan or cancel any time.
*Billed monthly upfront by credit card. Prefer to pay on invoice? Billed per three months upfront, 30-day payment terms. All prices exclude VAT; VAT is added where applicable. The prices shown are introduction prices, valid through 31 December 2026.
Turn the supplier files you dread into clean products in your PIM, visually, without a developer ticket.
Questions about mapping your suppliers into Ergonode, Akeneo or Pimcore, or want a walkthrough? Send us a note and we'll get back to you.
