Important notice for Ship customers

Migration date: March 9, 2026

On March 9, 2026, Ship will perform an automatic migration for Danske Fragtmænd from EDI communication to API communication.

• ✅ Already using API?
  No changes will be made, and no action is required.
• 🔄 Using EDI?
  Your setup will be automatically migrated to API based communication.
   

Update: The migration script was released this morning 9th of March at 06:00 CET. Version 18.197.1.12 is now available for On-premises customers and also on Shipment Server and Ticket.

What’s changing?

As part of the migration, Ship will switch to Danske Fragtmænd’s API setup:

• Shipment booking will be handled via the API
• Shipping labels will be retrieved directly from Danske Fragtmænd’s API
• EDI files will be moved to a new archive location
• Shipping documents will be updated to the new document versions
   

What you need to do before March 9

Please follow the checklist that matches your Ship setup to ensure a smooth migration.

Ship in the Cloud / Shipment Server

• Transmit all shipments no later than Friday, March 6
• Do not create or transmit new shipments until the migration is completed
• The migration will run automatically on the morning of March 9
• No action is required after the migration
   

Ship On-premises

• Transmit all shipments before starting the manual update
• Do not create or transmit shipments during the update process
• Update Ship to the latest version to ensure compatibility
• Resume shipment creation once the update and migration are fully completed
   

FAQ

How do I know if my setup uses EDI or API?

If your Danske Fragtmænd (DK - 10) setup uses shipment booking, you are already receiving labels from the carrier’s API.

Will the API change affect shipment updates or deletions?

No — your workflow stays the same.
You can still update or delete shipments until they are transmitted.
Transmit time remains the point where Ship sends the final version to Danske Fragtmænd.