After item data has been added to the GDSN pool and the hierarchies were created, it is possible to publish it for a specific customer (data recipient), market groups (IM only) or target markets (DSE only) by sending a GDSN publication message. By doing this the data recipient has the ability to view and synchronize the published item including all the child items below that item. An existing publication for a specific customer, market group or target market can be deleted.

Note: Only the root item of a hierarchy has to be published actively. The rest of the hierarchy will be published with it automatically.The root item of a hierarchy may be target market specific.

After an item has been published and subscribed to by a data recipient, some additional validations are triggered for the published GTINs and their hierarchies. If an item or a hierarchy fails due to incorrect or insufficient data, a corresponding response GDSN message will be generated by the GDSN pool. The Informatica B2B DX proceeds this file and creates a publication status entry for the affected item.

In order to make the publication process more traceable, you shouldn't publish individual items manually but use the approach described below.

Mark items for publication

After the item data and item hierarchies are maintained completely and have been sent to the GDSN pool they are ready for publication. Some items may have to be unpublished since they are deprecated, some may have to be republished to a certain data recipient.

You can add all that information to the affected items using an import, it is not possible at the moment to add those information in the Product 360 UI directly. The detailed description of the data to be imported is described in the pool specific chapters below.

Publish items automatically

Once you've added the publication status information to the items, the next run of the scheduled publication export job picks up all that data and creates corresponding GDSN messages. Of course, it's also possible to start a publication export manually.

Note: GDSN publication messages are only created for items that had been sent to the GDSN pool before. Even if an item is marked for publication, it won't be published if it hasn't been sent to the GDSN pool successfully.

There's a special algorithm which analyses the publication status entries created by the import of publication markings and by responses sent by the GDSN pool. The following rules apply:

In general, a publication message will only be created if the item has successfully been sent to the GDSN pool before.
If there's a publication status of message type "Item response" or "Publication response" created after the publication marking, no publication message will be created
Publication messages of type "republish" or "unpublish" will only be created if the item has been published successfully before