// The portal layer for your PIM
PIMgate runs alongside your existing PIM and turns its data into branded, entitled portals for customers, suppliers, and sales — without touching the source.
// The problem
Your PIM is the source of truth for product information. But the people who need it most — customers waiting on assets, agencies building campaigns, suppliers submitting data, sales reps building quotes — don't live inside it. They wait on email threads, FTP folders, and shared drives. PIMgate ends that.
// Architecture
PIMgate consolidates product, customer, and operational data from your PIM, ERP, CRM, and any other system — then exposes it cleanly to every place it needs to go. Add a source without touching a channel. Add a channel without touching a source.
Per-channel entitlements. Per-tenant branding. Always under your domain.
// Connections
A clean, versioned REST API with rate-limited tokens — plus webhooks, push, pull, and scheduled delivery. Use whichever fits the consumer: a shop polls, a CMS subscribes, a mobile app pulls on demand.
GET /v1/products GET /v1/products/:id GET /v1/assets GET /v1/categories POST /v1/webhooks GET /v1/sync/diff # Per-tenant tokens. Per-token rate limits. # Filtered by entitlements server-side.
Consumers fetch on demand. Cacheable, idempotent, fast.
PIMgate posts to your endpoint. Useful for one-shot syncs.
Subscribe to events. Notified the moment data changes.
Cron-style polling and exports. Per-tenant cadence.
Mix and match per integration. The same product can feed your shop via webhook, your sales portal via scheduled export, and your mobile app via on-demand pull — without duplicating logic.
// Delta sync
PIMgate compares each new export against the previous one and computes the diff at the field level. Downstream consumers receive only what actually changed — by pull, push, or webhook — keeping payloads small and integrations cheap.
<product id="42">- <name>Sensor v1</name><ean>4001234</ean>- <stock>120</stock></product>
<product id="42">+ <name>Sensor v2</name><ean>4001234</ean>+ <stock>87</stock></product>
GET /v1/sync/diff?since=2026-04-24Returns only the records that changed since the given timestamp.
POST https://yourapp.com/syncPIMgate posts the changeset to your endpoint after each export.
event: product.updatedPer-record events with a delta payload — wire it to anything.
Typical reduction vs. full re-syncs on incremental updates.
Know exactly which attributes changed, not just which records.
Every export is preserved. Compare any two points in time.
// How it works
PIMgate ingests from your PIM — XML, API, or scheduled SFTP. Your PIM stays the source of truth.
Define who sees what. Per-tenant, per-role, per-market, per-category. Entitlements down to the asset.
Branded portals for every stakeholder. Customer access, supplier submissions, sales-rep workspaces — under your domain.
// Capabilities
Branded asset access for the people you sell to.
Bring partner data in without polluting the PIM.
Equip your reps with the data their accounts need.
Multi-tenant by design.
Built on PIM data, normalized and indexed.
A safe bridge while you switch PIMs.
// Built for enterprise
Tenant isolation at the schema level. One breach doesn't cascade.
Every route, every query, every asset checked against an explicit permission catalog.
Hetzner Falkenstein, Postgres, daily snapshots, off-host backups.
Every action — invite, share, download, role change — written to an append-only audit log.
Enterprise solution. Tell us about your PIM and we'll set up a call.