POS-data: Setting corresponding EAN-number to magazine editions

Production date

03.09.2025

Background

In some situations, different editions of the same magazine (registered as a product in DI) may be sold simultaneously in retail stores. Until now, the POS-data solution has not supported assigning sales to the correct edition in such cases. Prior to this release, all POS-registered sales of a DI product were automatically linked to the most recent edition of that product.

Example

• Product 1 has different editions published both August 1st (edition 1) and August 15th (edition 2) in DI.

• Edition 1 will be sold in retail stores from August 1st to August 25th, while edition 2 will be sold from August 15th to September 5th.

So what happens when an edition 1 product is sold at a retail store at August 20th?

1. Until this release, the sale of edition 1 on August 20th would be registered to edition 2, since August 15th was the latest edition of the product.

2. With this new release, you can now connect the correct EAN-number to its corresponding edition. So the sale done on August 20th can now be connected to edition 1.

How is the connection between EAN-number and edition done?

When setting up a single edition in the publication calendar in DI Publisher, you now have the option to link that edition to an EAN number already registered to the product (see screenshot below).

This step is optional, and only necessary if your product uses POS data and has overlapping editions—a common scenario for magazines.

The option will only appear for retail store sales magazines that have multiple EANs connected to them, as it’s not needed for other types of products.