Service · Web development

Custom PIM portal development for wholesalers, manufacturers and retailers.

A central hub where all your product information lives (variants, attributes, photos, datasheets, translations, certificates and marketplace mappings) and from which everything flows at the push of a button to your webshop, Bol, Amazon, dealers and print. Custom-built around your catalogue, connected to your ERP and DAM, and structured in your own taxonomy.

Central product dataVariants & attributesDAM & mediaMultichannel publishingAI enrichment

A PIM portal is the foundation of your product data.

A PIM portal (Product Information Management) is the single source of truth for everything you know about your products and want to tell the world. Specifications, variants, colours, sizes, materials, weights, translations, marketing copy, certificates, photos, videos, technical datasheets, marketplace attribute mappings: it all comes together in one place and flows from there, in a structured way, to every channel you serve. For wholesalers, manufacturers and retailers with hundreds to hundreds of thousands of items, that is the difference between a team that sees data maintenance as a daily backlog and a team that can confidently set up new product launches, language markets and marketplaces.

Without a PIM, product information is scattered across Excel files, an ERP field that was never meant for marketing copy, a ZIP of photos on a network drive and a handful of fields filled in directly in Magento or Shopware. Every new product launch then takes a disproportionate amount of work, and every new language market or marketplace means going back to purchasing for data you already had before. A PIM portal tackles this by recording, per product record, which attributes are mandatory for which channel, which translation is missing where and which asset is not yet available, all visible in a dashboard your product managers and content team use every day.

We have been building product and data platforms for wholesalers, manufacturers and retailers since 2015. This type of platform often overlaps with a B2B e-commerce portal and a dealer portal; the PIM sits beneath both as the data layer. For compliance around the Digital Product Passport and sustainability data, see also DPP software, and for the broader integration architecture, integrations.

Three flavours of PIM portal.

Which type of platform fits depends on the size of your range, the number of channels, languages and marketplaces you serve, and how deeply the portal needs to be embedded in your existing ERP, DAM and webshop. In the first conversation, we advise which option makes sense for your situation: a custom portal, an implementation of Akeneo or Pimcore with additional custom modules, or a combination.

Compact project · fixed sprint budget

PIM light for SME wholesalers

A structured portal for a few thousand SKUs, with variants, core attributes, product photos and multichannel output to one or two channels, typically your own webshop plus one marketplace. Suited to wholesalers and manufacturers who currently work in Excel and are looking for a successor that scales without an immediate enterprise budget.

SKU catalogueVariantsPhoto uploadCSV export
Mid-sized project · fixed sprint budget

PIM portal with multilingual support, workflow and marketplaces

For retail and e-commerce with multiple language markets and marketplaces: workflow with approval steps, translation management, channel-specific attribute mappings to Bol, Amazon, Otto, Kaufland and Zalando, plus an integrated DAM for product photos, lifestyle shots and videos. Includes integrations with your order management system and webshop.

MultilingualWorkflow + approvalChannel mappingDAM
Larger project · fixed sprint budget

Enterprise PIM with GS1, ETIM and AI enrichment

A mission-critical PIM with deep integrations into your ERP and MES, industry standards (GS1, ETIM, 2BA, ECLASS), Digital Product Passport fields, multi-tenant theming for different brands and business units, and AI attribute completion to automatically fill gaps in product data based on datasheets and existing descriptions.

GS1 / ETIM / 2BADPP fieldsAI enrichmentMulti-tenant

What you get at the end.

A production-ready PIM portal plus everything around it to manage it yourself, add new channels and scale as your product range and language markets grow.

  • The platform itself, in productionProduction and staging environments, running in your own cloud (GCP, AWS, Azure) or hosted by us. Includes a CDN for your DAM files so product images load quickly worldwide, including for your marketplaces and partner feeds.
  • Full codebase and documentationSource code, build instructions, architecture overview, data model schema and API documentation. You are not locked in to a vendor; another team can take it over.
  • ERP, webshop, DAM and marketplace integrationsWorking integrations with your existing systems via integrations or a message bus. Real-time product data and attribute mappings from the PIM to your webshop, marketplaces and partner feeds.
  • Data quality reporting and channel completenessA built-in dashboard that shows, per channel, which attributes, translations and assets are still missing from your products, so you can close gaps proactively before a product launch needs to start.
  • Admin and end-user manualShort manuals for your product managers, content team, purchasing and marketing, plus a data steward manual for the people who safeguard quality across your catalogue.
  • Onboarding and train-the-trainer sessionsSessions for your product and content teams, plus train-the-trainer for lead product managers, so they can bring their own people up to speed in your own way of working.
  • Maintenance and further developmentOptional maintenance contract: monitoring, backups, security patches, keeping channel integrations up to date when marketplace APIs change, and ongoing extensions with new modules. Fixed monthly price per tier.

When a PIM portal is the right choice.

Four patterns where a Product Information Management portal takes noticeable work off your hands, for your product managers, your content team and your channel managers. If you recognise one of them, a conversation is usually worthwhile.

Excel legacy

Product data lives in Excel

Your product managers keep specifications, colours, sizes, marketing copy and marketplace attributes in spreadsheets that are uploaded to the webshop every quarter or sent to marketplaces via FTP. Versions get lost, errors creep in, changing an attribute for one channel unintentionally affects another, and nobody has an overview of who last changed what.

Channels demand more

New marketplace, old data

You want to sell on a new marketplace, such as Amazon, Bol, Otto, Kaufland, Zalando or MediaMarkt, but their mandatory attribute list goes beyond what you currently record. Category-specific size charts, material composition, energy labels, harmonised codes: the buyer has to go back to the supplier manually to retrieve data you once knew for certain but never recorded properly.

Translations

Languages and regions multiply the work

For each language market you need marketing copy, product names, keywords and compliance text in a different language. Translations currently live in separate documents that are merged per release, and you have no overview of which products are still missing in which language. Or worse: all translations go through a single external party you have to call for every small change.

Images & assets

Photos and datasheets scattered everywhere

Product photos live on a network drive, lifestyle shots in a Dropbox, datasheets as loose PDFs. Your webshop often links to an older version, marketplaces have their own more recent version, and the print catalogue pulls from yet another source. That leaves you exposed to compliance problems around label claims.

How a PIM project runs.

1

Introduction

A conversation to understand which channels the portal needs to serve — your own webshop, marketplaces, dealers, print, partner feeds — which ERP and DAM systems sit around it, and what your product categories, variants and attributes look like today. By the end, you'll have a first sketch of the scope and an idea of where we start.

2

Discovery with your product and content team

A workshop with your product managers, content team, purchasing and marketing, plus short interviews with a cross-section of end users — a product manager launching new lines, a data steward safeguarding quality, a marketer filling marketplaces. What do they do now, where do they run into problems, what do they expect from the portal? By the end: data model, screen flow and a plan per module.

3

Building in sprints

A working build every two weeks. Your team tests along, and a pilot category from your catalogue runs through it. We start with the data model and the first channel output — usually your own webshop — and expand in later sprints with variants, translations, marketplaces, DAM and AI enrichment. That way you see value early and can adjust the scope every sprint.

4

Phased rollout and maintenance

We roll out in phases to your full range, run onboarding sessions, and provide ongoing maintenance for security, marketplace API changes, ERP integrations and further development of new modules. As you add channels, languages and marketplaces, the portal keeps evolving with you.

Modules we build almost every time.

A PIM portal is built from a set of recognisable building blocks. Which ones you need depends on your range, channel mix and industry, but the following modules come up in almost every project — sometimes as the core, sometimes as an extension in a second phase once the foundation is running.

Data model

Product catalogue with variants and families

A flexible data model with product families, master products, variants at axis level (colour, size, material), bundles and kits. Each category has its own attribute set, so a TV needs different fields from a sofa, and a screw different ones again. Versioning per record and an audit trail per change mean you can always see who changed what and when.

Attributes

Attribute library with validations

A reusable library of attributes — number, text, enumeration, measurement with unit, date, asset reference — with rules for mandatory fields per channel. A product-page attribute that is required for Bol may be optional for your own webshop, and a weight field may be in kilograms but required in pounds for Amazon. Validations stop bad data from polluting the portal.

Multilingual

Translation management and language variants

Configurable per attribute whether it is language-dependent. Product names, descriptions, marketing copy, material descriptions, warranty text — all with separate language variants and a built-in overview of what is still missing per language. Integrations with DeepL, Google Translate or a translation agency for first-pass translations, with human approval steps before publication.

DAM

Digital asset management for product media

An integrated DAM for product photos, lifestyle shots, videos, datasheets, user manuals and certificates. Each asset has metadata, a validity period, a rights overview and automatic image derivatives for different channels — a 4K shot for your own page, a compressed version for marketplaces, a square crop for social. Version control means old photos can be replaced without breaking links.

Workflow

Workflow with approval steps

A workflow configurable per channel and per product category: a product manager writes, a data steward checks, marketing approves commercial copy, compliance approves label claims. Only when every step is green does the portal publish to the relevant channel. Statuses are visible on a dashboard so everyone can see what is waiting on whom.

Channel mapping

Channel mapping and publishing

For each output channel — your own webshop, Bol, Amazon, Otto, Kaufland, Mediamarkt, partner feeds, print catalogue — we build a dedicated mapping from your internal attributes to that channel's attribute structure. This includes category mapping (your category to the marketplace category), price overrides and region-specific compliance text. Publication is push or pull, with retry logic for API outages.

Compliance

GS1, ETIM, 2BA and Digital Product Passport

For industries where classification standards apply — installation technology, construction, electronics, food, automotive — we link your product data to GS1-GDSN, ETIM, 2BA, ECLASS or a custom taxonomy. For the European Digital Product Passport requirement (expected under the ESPR from 2027), we already capture the DPP fields: origin, materials, recyclability, repairability and compliance documents. See also our page on DPP software.

AI enrichment

AI attribute completion and category suggestions

For catalogues with thousands of items where attributes are incomplete, we deploy an AI layer that suggests missing attributes — size, material, weight, category, keywords — based on datasheets, existing descriptions and competitor pages, with a confidence score and human approval before publication. See also our page on AI development for our approach.

Reporting

Catalogue health dashboards

Insight into attribute completeness per channel, translation coverage per language market, asset freshness, workflow lead time and publication status per marketplace. Dashboards for your product managers and data stewards, plus self-service reports for the marketing team who steer on completeness per channel. Exportable to Power BI, Tableau or Looker.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Industries we build PIM portals for.

The terminology differs per industry — some wholesalers call it a "product database", manufacturers say "specs management", retailers "content hub" or "product DAM" — but the underlying patterns are similar. In installation technology and construction, it often comes down to deep ETIM and 2BA integrations, many categorical attributes per product line and certificates that must be passed on to quote modules. In fashion and electronics, seasonal collections, variant explosion (colour × size × style) and marketplace attribute mappings play a bigger role. For manufacturers and private-label producers, it is often about brand asset management, multi-tenant theming per customer brand and a separate approval flow per brand.

In installation technology and construction, we work with wholesalers who supply to distributors using ETIM classifications and to the Dutch installation market using 2BA. In fashion and sport, there are also deep variant flows (colour × size × fit) and seasonal collections that rotate every quarter. In food and consumer goods, allergen and nutritional data come into play, plus GS1-GDSN for supplier synchronisation. In electronics, energy labels and RoHS data are mandatory. In automotive parts, OEM cross-references, vehicle fitment and TecDoc are key.

We choose the right architecture case by case. For one client, an implementation of Akeneo or Pimcore with additional custom modules fits; for another, a fully custom PIM makes more sense because the standard package isn't flexible enough for their explosion of categories. We always advise based on what your team already runs and what your maintenance partner supports, not on a preferred stack. For our broader approach to integration, see our page on integrations.

Tech stack and integrations.

We build PIM portals as modern web applications on a stack that works in virtually any enterprise environment and remains maintainable. Front end in React, Vue or Next.js with TypeScript; back end in Node.js, Python (Django or FastAPI) or .NET — depending on what your own IT team knows. For the data layer, we typically combine PostgreSQL with MongoDB for flexible attribute sets, plus a vector database (pgvector, Weaviate, Qdrant) for semantic search or AI enrichment. For asynchronous publication to marketplaces, we use a message queue (RabbitMQ, Azure Service Bus, Kafka) so that a slow-responding marketplace API doesn't hold up your own product managers.

On the ERP side, we integrate with SAP S/4HANA, SAP Business One, Microsoft Dynamics 365 Business Central, Exact Online, Exact Globe, AFAS Profit, Unit4 or an in-house ERP. For digital assets, we work with Bynder, Brandfolder, Cloudinary or a custom DAM. For webshops, we cover Shopify, Shopware, Magento (Adobe Commerce), BigCommerce, Sana Commerce or a headless front end on Next.js or Nuxt. For marketplaces, we use the native APIs of Bol, Amazon SP-API, Otto, Kaufland, Mediamarkt and Zalando, or go through an aggregator such as ChannelEngine or EffectConnect. For industry standards, we support GS1-GDSN, ETIM, 2BA, ECLASS and TecDoc.

Compliance is no side issue for PIM platforms. The European ESPR regulation requires a Digital Product Passport for a growing number of product categories, starting with batteries and extending to textiles, electronics and furniture. For industry-specific compliance (energy labels, RoHS, REACH, CLP for chemicals, allergens for food), we build validation into the data model, so publishing to a channel fails automatically if mandatory compliance fields are missing. For the wider context, see our page on AI development for the attribute enrichment side.

If your PIM feeds a webshop on CloudSuite, you decide up front which system is in charge of which field. How we build that integration is covered on Building a CloudSuite integration.

Frequently asked questions.

What clients usually want to know before we start.

What is the difference between a PIM and an ERP?
An ERP is your transaction system: stock, purchasing, sales, finance, delivery. A PIM is your marketing and publishing system for product information: everything you want to tell customers, dealers and marketplaces about your products, including descriptions, photos, attributes, translations and certificates. The two work together: your ERP maintains SKUs, stock and prices, while the PIM enriches each SKU with marketing content and publishes it to your channels. In practice, ERP and PIM always work side by side, and a good integration between the two is one of the most important architectural choices.
What is the difference between a PIM and a DAM?
A DAM (Digital Asset Management) is about media: photos, videos, datasheets, design files. A PIM is about structured product data: attributes, translations, variants, prices, compliance fields. In modern implementations the two are tightly linked or even combined: your PIM references the assets in the DAM for each product, and the DAM knows which products use which assets. We often build an integrated PIM + DAM, or integrate with an existing DAM such as Bynder, Brandfolder or Cloudinary.
Do you build custom, or do you set up Akeneo or Pimcore?
Both are possible. Akeneo and Pimcore are mature open-source PIMs that work well for many wholesalers and retailers. We implement them, configure your data model, build your channel mappings and extend them with custom work where your situation differs. For industries with highly unusual attribute structures, a fully custom PIM is often a better fit. In the first conversation we determine which route suits you. Our loyalty lies with your situation, not with a vendor.
Can the portal integrate with SAP, Dynamics, Exact or AFAS?
Yes. We build integrations with SAP S/4HANA, SAP Business One, Microsoft Dynamics 365, Exact Online, Exact Globe, AFAS Profit, Unit4, NetSuite, Odoo and proprietary ERPs via REST, SOAP or a message bus (RabbitMQ, Azure Service Bus). Bidirectional where needed: SKU creation and master data from the ERP, marketing enrichment and publication from the PIM. Our approach is described on integrations.
How do we handle marketplaces and their mandatory attributes?
For each marketplace, we build an attribute mapping from your internal data model to their category-specific attributes. Bol, Amazon SP-API, Otto, Kaufland and Zalando each have their own taxonomy. For each product, the portal shows a completeness report per channel: "Ready to publish on your own webshop, still missing three mandatory attributes for Amazon FR." This prevents launches from stalling on data that was just not quite in order. For marketplaces without a direct API, we integrate via an aggregator such as ChannelEngine or EffectConnect.
How does AI attribute completion work?
For catalogues with thousands of items where attributes are incomplete (typically after an acquisition, or for a wholesaler migrating from older systems), we deploy an AI layer. The model analyses available datasheets, product photos, existing descriptions and, if needed, references on competitor pages, and suggests values for missing attributes, each with a confidence score. Suggestions go into an approval queue for a data steward, and are only published after human approval. For some low-risk attributes (keywords, short SEO descriptions), we can enable automatic publishing above a threshold value. See also our page on AI development.
How do we handle workflow and approval for each product launch?
A workflow that is configurable per category and per channel: writer, reviewer, marketing approval, compliance approval, publication. Statuses are visible per record and in a dashboard. For seasonal launches, we can build in bulk workflow actions. For high-risk categories (food, children's products, electronics requiring certification), automatic compliance checks block the workflow if mandatory certificate assets are missing.
What about multilingual content and regional variants?
You can configure per attribute whether it is language-dependent: product name and marketing copy usually are, weight and EAN code are not. The portal shows a coverage report per language: the percentage of your catalogue that is complete in each language. First-pass translations run via the DeepL or Google Translate API, with human approval before publication. For regional overrides (a separate energy label text for DE, or a different description block for BE-NL), we support language variants plus regional overrides. If you work with external translation agencies, we integrate via XLIFF export and re-import.
What about the Digital Product Passport (DPP) and ESPR?
The European ESPR regulation requires a Digital Product Passport for a growing number of product categories: a structured set of data on origin, materials, recyclability, repairability and compliance, accessible via a QR code or NFC chip on the product. For batteries this starts earlier than for other categories, and it will expand to textiles, electronics, furniture and construction materials. We build the DPP fields into your PIM data model now, so you are ready before the obligation applies to your category. For the issuing side (QR codes, hosted product pages, NFC payload), see our separate page on DPP software.
How long does it usually take to go live?
That depends heavily on the scope. We deliver a compact PIM-light for a wholesaler with a few thousand SKUs and a single output channel over a handful of sprints. A mid-sized PIM with multilingual support, workflow and two to three marketplaces runs over several sprints. An enterprise PIM with GS1, ETIM, DPP, AI enrichment and multi-tenant theming is a programme of many consecutive sprints, sometimes delivered in phases per brand, language market or product line. We always work with a fixed sprint budget, so you can adjust the scope every sprint.
Do you build custom, or do you also integrate with an existing PIM package?
Custom, pragmatic, and often combined with an existing package. For the data model, attribute library, workflow engine, DAM integration and channel mapping, we use proven libraries and services where possible rather than rebuilding them. We do build the interface, the company-specific validations, the marketplace aggregator integrations and your industry classifications to order, because that is where every organisation differs. For clients with an existing Akeneo, Pimcore, Salsify, Plytix or Inriver, we implement custom modules on top, or a custom front end that drives the package. That way you stay in control of what is strategic, and you don't pay for custom work where standard building blocks do the job.

Fabian van Dijk

Business developer · fabian.vandijk@appfront.nl

Talk to us about your PIM portal.

A no-obligation introductory call of half an hour. We listen to your catalogue structure, your channel mix and the pain points that currently cost you the most time, ask sharp questions, and give you direction you can actually use, even if we turn out not to be the right partner. For more context on our approach, you can also take a look at our software development page or the overview of integrations.

Share LinkedIn Email

Edit content