Built to connect: why Perfion for manufacturers and distributors
03.11.2026
For manufacturers and distributors, product information involves more than describing individual items. It also needs to explain how products fit together: which spare part belongs to which machine, which accessories work with a particular model, and which documents apply to each variant.
These connections help customers choose suitable products and give internal teams the information needed to support them. Perfion lets businesses manage those relationships alongside descriptions, specifications, images and documents, creating a product model that can adapt as the assortment changes.
What our Danish roots taught us about good design
Boyum IT Solutions was founded in Denmark in 1997. Danish design has long emphasized function, simplicity and adaptability, principles that also inform how Boyum IT approaches software.
Think of a set of interlocking building blocks. The same pieces can form a simple structure or a detailed model, and individual sections can be changed without rebuilding everything from the ground up. Their usefulness comes from both the pieces themselves and the way they connect.
Product information works in a similar way. Specifications, images, documents and compatibility details each serve a purpose, but their relationships give them context. In Perfion, teams can organize these elements around their products, reuse shared information and adapt the model as their assortment grows.
Why product relationships matter
A product record can hold a name, description, dimensions and images. Manufacturers and distributors also need to manage the information that connects one item to another.
A machine may have several configurations, each with specific components, replacement parts and technical documents. An accessory may work with multiple product families. A certificate may apply to a group of products sold in a particular market.
When those relationships are maintained separately in spreadsheets or shared folders, teams have more information to reconcile whenever something changes.
In Perfion, businesses can define fields, relationships, variants and structures that reflect their assortment. Product teams can connect parts to the equipment they support, associate documents with relevant products, and organize shared information across product families.
This helps reduce duplicate maintenance and makes it easier to identify which products are affected by a change.
A practical example: “Will this battery fit my drill?”
Consider a business selling drills, batteries, chargers and drill bits online. Customers need to know whether a battery works with a drill they already own and which charger to use with it.
A compatibility list maintained separately from product information creates another source for teams to check and update. Bringing those relationships into the product model gives teams a structured way to maintain them.
In Perfion, a battery can be linked to the drill models it fits and to its compatible chargers. Through configured integrations and publishing processes, that information can be made available in the webshop and other connected channels.
When a new drill is introduced, the product team can add its compatibility relationships and publish the updated information. Clearer guidance can help customers make informed choices and reduce compatibility-related returns and support inquiries.
Preparing product information before launch
Descriptions, images, technical documents and translations often need to be prepared before a product is ready for sale. That work may involve several teams contributing at different stages.
By managing product information alongside the ERP system, teams can gather and enrich content while a product is still in development. Marketing content can progress alongside operational product setup, helping teams coordinate the information needed for launch.
Teams can also identify missing content earlier and prepare it for the intended markets and sales channels.
Adapting the model as the business changes
A structure made from interlocking blocks can be extended or rearranged as the design develops. Product teams need similar flexibility when new categories, markets and sales channels introduce different information requirements.
A business may need additional technical attributes, new relationships between products, or content in another language. Perfion allows teams to adjust fields, relationships and structures through configuration. The technical support required depends on the complexity of the change and the systems involved.
The Actions module also supports data processing, integrations and automation. Some requirements can be addressed through configuration, while more complex scenarios may require technical expertise or development.
This gives businesses options for extending their product information processes as their needs evolve.
Connecting product information with ERP and sales channels
ERP and PIM systems serve complementary purposes. The ERP system manages operational information such as orders, inventory, pricing and financials, while Perfion manages and enriches product content for sales and communication channels.
For businesses using SAP Business One or Microsoft Dynamics 365 Business Central, connecting the systems can allow product teams to build on relevant ERP data rather than maintain it separately. The information exchanged and the update process depend on the connector, configuration and implementation.
Enriched information can then be distributed to connected e-commerce platforms, catalogs and other outputs. Images and documents can be managed alongside the products they describe, helping teams prepare content for different uses.
Clear responsibilities for where information is maintained and how it reaches each channel help keep these processes coordinated.
Exploring a connected product model with Perfion
For manufacturers and distributors evaluating PIM, a useful starting point is a representative product family with variants, accessories, spare parts and technical documentation.
Mapping that example reveals which relationships need to be managed, which information comes from the ERP system, and what each sales channel needs to receive.
Request a free Perfion demonstration to explore how its product model, configuration and integrations could support those requirements.