Skip to main content

Integration with DAO/Bladkompagniet

Updated today

Iteras can automatically send distribution files to dao AS/Bladkompagniet (hereafter “Bladkompagniet”) whenever a magazine is issued (if you publish a newspaper, the setup is different—contact your Iteras consultant!). This article describes the integration.

Please note that communication regarding delivery delays primarily applies to daily newspapers and not magazines, as delays are costlier with Bladkompagniet and less critical for magazines than for newspapers.

Prerequisites

To set up this integration, the magazine must have a distribution agreement with Bladkompagniet, and each issue must be created under the print product in Iteras. The integration does not currently support time‑based releases, but you can run time‑based subscriptions and still create issues—then the integration will function correctly.

Integration setup in Iteras

Navigate to Account (top right corner) > Integrations > Distribution integration

Here are the configuration options:

  • Integration active: Toggle integration on or off. Must be on for it to work.

  • Publisher name: Name of the magazine’s publisher. If there is only one magazine, you may use its name for simplicity.

  • Distribution in countries: You can limit which subscribers are sent based on country. Typically select Denmark.

  • SFTP server: files.bladkompagniet.dk

  • SFTP port: 22

  • SFTP username: Provided by Bladkompagniet

  • SFTP password: Provided by Bladkompagniet

  • Folder with data to Iteras: Provided by Bladkompagniet

  • Folder with data from Iteras: Provided by Bladkompagniet

  • Enable KISS integration: Do not fill in for magazines (used for loose sales billing files)

  • Enable SALTII integration: Fill in (this is the protocol used between distributors in Denmark)

  • Allow complaints: Fill in (potential consequences—credit, re-delivery, extension—are configured via business policy)

  • Number of days complaints allowed: Set to the shortest interval between two issues of the year

  • Complaint codes: See further down

  • Default complaint code: We recommend 21

  • Products: Select the product(s) to be distributed via Bladkompagniet

  • Product ID in the distribution system: Provided by Bladkompagniet. Product ID relates to the title, not individual issues.

  • Limit to subscriptions with following conditions: Additional rules to determine which subscribers are included in distribution

  • Delivery type: Confirm with Bladkompagniet if not obvious

If complaints are allowed, Iteras can submit them to Bladkompagniet via the integration. In that case, complaint codes must be set up as per industry standard:

  • 20: Free text

  • 21: Product missing

  • 22: Product missing again despite earlier complaint

  • 23: No delay notice—product delivered late

  • 36: Wet product

  • 37: Damaged product

  • 41: Delivered through the letter slot (SBK, TF, SP)

  • 42: Must be delivered inside house, not in mailbox (SBK, TF, SP)

  • 43: Deliver to the floor, not the mailbox unit (SBK, TF, SP)

  • 44: Must go all the way through the letter slot (SBK, TF, SP)

  • 46: Must go fully into the mailbox (SBK, TF, SP)

  • 51: Wrong product received—needs new one

  • 53: Delivered to wrong address

You can also add code “99” for internal use.

Abbreviations after codes refer to setup options:

  • SBK: Send to Bladkompagniet

  • EM: Enable redelivery

  • TF: Allow free text

  • SP: Send notice

Once the integration is set up, you will be able to create complaints under subscriptions, and the distribution menu item will appear.

Integration Setup at Bladkompagniet

After configuring integration in Iteras, a test file with addresses is sent. Bladkompagniet must confirm receipt.

The file is sent from Iteras by assigning or reassigning an issue. If assignment is not possible, Iteras can still send the file manually.

Bladkompagniet must also enable the retrieval of complaints from Iteras. A test complaint is also sent to verify that it’s received.

Products with inserts for specific postal codes

It is possible to distribute inserts not sent to all subscribers—typically geographic targeting by postal code.


In that case, you have two products: the standard version without inserts, and the version with inserts. This is handled by overwriting the product ID for subscribers who should receive the insert version. You create a custom field for distribution days (functions: overwrite product ID in distribution; type: distributor product ID; link it to the relevant print product). Under Distribution > Calendar, click on the issue date when the insert should be included and add the agreed insert product ID from Bladkompagniet, along with the associated conditions. Conditions are required for this scenario—else all subscribers would get the same product ID.

You may have as many product IDs per issue as there are insert versions.

Addresses

When you set up a Bladkompagniet integration, your Iteras consultant must upload distribution addresses to your account. This allows you, when entering an address for a subscriber, to see if Bladkompagniet covers it—*only if the address matches exactly their system* (often matching DAWA address standards, which Iteras also verifies). Some addresses cannot be verified, e.g., ranges of house numbers (like “Ågade 43–45”), resulting in a rejection from Bladkompagniet. In such cases, you can contact the subscriber to get the correct address.

Typically, Bladkompagniet uses PostNord for coverage gaps, usually at a higher cost—more significant for newspapers than magazines due to higher frequency.

Daily use

Once integration is in place, Iteras automatically sends a distribution file via SFTP to Bladkompagniet as soon as an issue is processed. The file is typically processed the same day, and a return file is received, including a delivery date.

It’s essential that publication dates in Iteras match those booked with Bladkompagniet. Otherwise the return file cannot be matched.

Complaints in everyday use

When a subscriber has not received their magazine and it is past the delivery date, a complaint (if set up) can be created under the subscription. If complaint codes are configured as above (and they should be), you can select the appropriate code and optionally add free‑text details.

You can only choose an issue date to indicate which edition the complaint refers to.

If the complaint is rejected by Bladkompagniet, Iteras notifies you—but unfortunately you do not receive acknowledgment if it’s accepted. Thus the status in the complaint overview on the subscription remains “Sent.”

Get notified if something goes wrong

Did this answer your question?