The registration in the system

Import Routines

The importer in the PIM system uses the API function of the application. In this process, logics are integrated via JSON file that automatically retrieves a provided CSV or Excel file. Many of our customer applications use this functionality to automatically enrich data in the PIM system or to create new records. The functionality corresponds to the procedure of output via API. However, the import routine offers additional possibilities for data manipulation.

Mapping of Import Data

Data often comes from global systems within a company. There, they are stored in various databases, making it necessary to incorporate multiple importers.

Each import requires a primary characteristic to know which items the data should be enriched with.

The imports can be adjusted by our development team. For example, if specific fields in the import are allocated with acronyms that have a different meaning, this will be mapped with the import. Another use case can be the construction of a product title that is to be assembled from several fields.

Many other scenarios can be realized using this functionality.

Digital agency for many years

Through years of work for large corporations such as Procter & Gamble, Unilever, Merz, Duracell, De’Longhi, Coty, Wella, BASF, Knauf, L’Oréal, dm Drogerie, etc., we have learned a lot and recognized that the old patterns of separating data into the respective functional areas still occur and far too frequently.

In this context, the DAM system is seen as the media database of marketing. Product information is firmly in the hands of logistics or R&D, legal information is found in the database of the legal department, and marketing texts are lying dormant in various Word files. Just to name a few examples …

Structural change and rethinking

A key factor is, therefore, providing data on a central platform. We call this Single Point Of Information.

Sounds simple, but it is highly complex. Because technically, data often lies in various places and not always in the best quality. Ten or more sources are not uncommon.

Many specialist areas need to be addressed. We repeatedly notice a certain inertia here.

PIM and DAM systems are a crucial step in the digitization of the company. They lead to significant resource and efficiency advantages and are the foundation for quality, completeness and distribution of product data of all kinds.

Interfaces create performance

Our strategy, therefore, primarily concerns the central provision of data, which should be able to do one thing above all. Sell!

In the establishment, the following aspects must also be fundamentally considered:

1. Communication within the company, showcasing advantages and disadvantages, breaking down barriers

2. Making systems as simple as possible to use

3. Enabling content syndication, API, output containers, gradually implementing download formats

4. Providing product data and media data in an integrated manner, allowing no media breaks and avoiding duplicate data

5. Establishing workflows (Traffic Light Indicator, editing, importer, API, approvals, GDSN, etc.)

Here is a statement from our owner Oliver Dietz to conclude:

Experience counts, we notice this every hour and every day of our work.  The implementation of a PIM and DAM system is a big step and must be desired, lived, and supported by the management. Only then can barriers be broken down and employees be taken along. This is a communication task that has at least the same importance as the purely technical work. We cover both areas as dietz.digital, as we are a digital agency that has been driving communication for many years and lives digitalization and programming on a daily basis.

What field types are available in the PIM system?

• Single-line text

• Multi-line text

• Selection fields, dropdowns

• Radios

• Checkboxes

• Units of measurement

• etc.

They are available to import, edit, and provide data as structured as possible.

The filters and types also ensure that data can be selected and found.

Units of Measurement

The units of measurement field is a special type consisting of three field types.

• Precision (is equal to, approximately, less than, more than)

• the value (price, weight, content, quantity, etc.)

• and the format (€ , kg, g, cm, mm, etc.).

This can ideally represent ingredients, allergens, vitamins, prices, etc.

Validations, Validities

Fields can be validated based on criteria, such as the input of “text only” or “numbers only”.

The validity of fields is also adjustable. For example, prices or certain characteristics can be set according to a time period. The visibility in the system can also be controlled. This makes it possible to have fields in the system, but only display them in the backend.

Field Limitations

Field limitations are adjustable for multi-line and single-line text. Here, based on bytes or characters. The byte limit is a special case and is, for example, needed to limit the search terms for the Amazon A9 backend keywords to 249 bytes. If it were more, Amazon currently ignores all keywords.