SyncManager offers a native integration with the GDSN data pool b-synced. Data model, validations, message choreography and the technical connection are immediately available. A user-friendly interface and preconfigured processes make GDSN easy to use.
In addition, the SyncManager can be expanded to an individual, full-fledged PIM system. A major strength is the high flexibility of the data model, validation and business logic, which can be adapted to the requirements of the project by configuration. As future requirements from retail, regulation or other sources can also be easily mapped, the system is future-proof.
Especially for suppliers, a wide range of options for distributing data to different recipients are important. Besides the GDSN, other goals and target markets play an important role for the supplier. The SyncManager makes it possible to distribute product information to different destinations easily, automatically and in many formats. This includes standard formats as well as Excel templates, which the supplier has to feed for the retailers. A flexible task system with workflow support and the definition of roles and rights to support clean processes complete the functional scope of the SyncManager.
Start with GDSN
Selection of the GDSN data model
As a pure SaaS solution, the SyncManager is immediately available and can be used directly. No installation is necessary and no personnel or know-how is required for operation and maintenance. Therefore very short implementation times are guaranteed and all components are always up to date. Furthermore the customer can focus on the essential – the data.
Maintenance of nutritional information
The start is even easier, as the complete GDSN data model can be loaded preconfigured by only one click. All attributes and value lists, all GDSN validations and the complete GPC are part of the data model. Appropriate UI elements with high usability are available for easy data maintenance. The packaging hierarchies are also preconfigured. However, the data model is not rigid, but can be modified or reduced as required. Further classifications can also be integrated (e.g. eCl@ss).
Allocation of media to products
The GDSN only allows the transmission of URLs for images and other media. These must be accessible by the recipient. The media management of the SyncManager supports this perfectly. Images and documents can be easily uploaded and stored in the SyncManager. The SyncManager then only passes on the externally accessible URL via the GDSN. Changes to the images are also detected and communicated.
Data Quality Board
In addition to the validation sets for GDSN, complex validations for other target markets or regulatory requirements can easily be added. Of course, target channel specific validations are also possible. The data is validated directly during maintenance and the user is notified of any errors or missing data.
But data quality must also be evaluated. The SyncManager provides a Data Quality Board for this purpose. This gives the user an optimal and always up-to-date overview of the data quality and the status of the data. The various widgets provide information about weaknesses in data quality as well as self-defined KPIs. The widgets allow a drill-down, directly to the list of products that are affected.
Setting the target markets for publication
A ready configured communication channel connects the SyncManager directly to the b-synced GDSN data pool. To publish a set of products simply the targets (GLNs or target market) have to be defined and the publication has to be started. The whole further choreography is done by the SyncManager.
The re-publication of changes can be automated or controlled by a workflow. The overview of different assortments is easy to keep track of, as it is possible to evaluate at any time when products were published and where they were published.
Product overview with feedback from the retailer
The feedback from the GDSN is displayed by the SyncManager directly on the product and can also be processed flexibly through a workflow. This allows an automated distribution of the required corrections through tasks to the responsible users. In order to avoid new confirmations, we recommend in these cases to think about creating a separate validation rule in the SyncManager.