Connect
Attach the PIMs you run today through their standard exports or APIs. No plugin inside the PIM, no change to its data model, no new licence on the source side.
FEATURE · CONNECT & CONSOLIDATELIVE
Connect every source. Touch none of them.
PIM Gate reads from the PIM, ERP and supplier files you already run — via XML, REST or scheduled SFTP — and consolidates them into one canonical product record. Your PIM stays the source of truth. Nothing is written back unless you configure it.
XML · REST PULL · SFTPSCHEDULE PER SOURCEREAD-ONLY BY DEFAULT
Add a source without touching a channel. Add a channel without touching a source.
01 · What it does
Three jobs, done before any channel sees a record.
Consolidate
Several sources, one record per SKU. Content from the PIM, commercial fields from the ERP, supplier values from files — mapped onto one canonical schema, with the origin of every attribute kept.
Keep in step
Every source runs on its own schedule. Each run is versioned, and changes are detected at field level, so downstream consumers receive only what actually changed.
02 · PIM connectors
The PIMs you already run, connected as they are.
PIM Gate ships with connectors for Viamedici EPIM, Akeneo, Pimcore, Stibo and Censhare. Each one reads the system's standard XML export, so your PIM team keeps its data model, its workflows and its release cycle. The PIM does not know PIM Gate exists — and it doesn't need to.
- Standard connectors for Viamedici EPIM, Akeneo, Pimcore, Stibo and Censhare (XML)LIVE
- No plugin, module or schema change inside the source system
- Several PIMs per tenant — e.g. one per brand or country company
- Read-only by default; write-back only where you configure it
CONNECTORS INCLUDED · S 2 · M 5 · L ∞ · XL ∞
PIM connectors
The PIMs you already run, connected as they are.
03 · Ingestion & scheduling
Three ways in. One schedule per source.
Different systems deliver differently. PIM Gate accepts XML exports, pulls from REST APIs, and collects files from scheduled SFTP drops. Each source gets its own schedule — nightly for the full PIM catalog, hourly for commercial fields, whenever a supplier delivers. Every run is stored as a version, so you can see exactly what arrived, when, and what changed compared with the previous run.
- XML import — full exports and partial filesLIVE
- REST pull from source APIs on a defined intervalLIVE
- Scheduled SFTP collection for systems that can only drop filesLIVE
- Independent schedule per sourceLIVE
- Field-level change detection on every run, feeding delta sync → Versioning & migration
Ingestion & scheduling
Three ways in. One schedule per source.
04 · Mapping
Every source field lands on one canonical attribute.
Source systems name, type and unit their fields in their own way. PIM Gate maps each field onto its canonical open schema — with data type, unit, locale and market flags — and records which source supplies which attribute group. Downstream, every portal and API sees one consistent record, regardless of how many systems fed it.
- Per-attribute mapping from source field to canonical attribute
- Units and data types normalized at the gate, not in each channel
- Source precedence per attribute group (e.g. content from PIM, delivery time from ERP)
- Mapping UI with safe cutover for self-service changes2026
Until the mapping UI is released, mappings are configured with our onboarding team as part of setup.
Mapping
Every source field lands on one canonical attribute.
05 · Operations
Credentials locked away. Connections watched.
Source credentials belong to your tenant and nobody else. They are stored encrypted and, once entered, can be replaced but not read back in the interface. Connection health — last successful run, record counts, failed records and alerts when a source stops delivering — is on the roadmap as a dedicated view.
- Encrypted credential storage per tenant, write-only in the UIROADMAP
- Connection health view with alerts on failed or missing runsROADMAP
- Every configuration change to a source recorded in the append-only audit log
Operations
Credentials locked away. Connections watched.
06 · Custom connectors
Not on the list? We build the connector.
Standard connectors for SAP, Microsoft Dynamics and Oracle, and for CRM and DAM systems such as Salesforce, HubSpot and Cloudinary, are on our roadmap. You don't have to wait for them. If a system can export a file or answer an API call, we build and maintain a custom connector for your tenant at a fixed price.
- Custom connector for any source with an export or API — available now
- Fixed price: €3,500 one-off, €1,200 per year for maintenance and updates
- Standard ERP connectors (SAP, Dynamics, Oracle)ROADMAP
- Standard CRM & DAM connectors (Salesforce, HubSpot, Cloudinary)ROADMAP
Custom connectors
Not on the list? We build the connector.
See all integrations →
07 · Specifications
Connect & consolidate at a glance.
| Spec | Value | Status |
|---|---|---|
| Standard PIM connectors | VIAMEDICI EPIM · AKENEO · PIMCORE · STIBO · CENSHARE (XML) | LIVE |
| Ingestion methods | XML · REST PULL · SFTP (SCHEDULED) | LIVE |
| Schedule | PER SOURCE | LIVE |
| Run history | EVERY RUN VERSIONED | LIVE |
| Change detection | FIELD LEVEL | LIVE |
| Target model | CANONICAL OPEN SCHEMA | LIVE |
| Mapping UI · safe cutover | PER ATTRIBUTE | 2026 |
| Write-back to source | OFF BY DEFAULT · CONFIGURABLE | — |
| Credential storage | ENCRYPTED · PER TENANT · WRITE-ONLY UI | ROADMAP |
| Connection health & alerts | — | ROADMAP |
| Connectors included | S 2 · M 5 · L UNLIMITED · XL UNLIMITED | — |
| Custom connector | €3,500 + €1,200/YR · AVAILABLE NOW | — |
| Standard ERP connectors | SAP · DYNAMICS · ORACLE | ROADMAP |
| Standard CRM & DAM connectors | SALESFORCE · HUBSPOT · CLOUDINARY | ROADMAP |
| Hosting | DE (HETZNER FALKENSTEIN) · CH ON REQUEST | — |
08 · Works with
Sources we connect today — and next.
Viamedici EPIMAkeneoPimcoreStiboCenshareXMLRESTSFTPSAP · CUSTOMMicrosoft Dynamics · CUSTOMOracle · CUSTOMSalesforce · ROADMAPHubSpot · ROADMAPCloudinary · ROADMAP