Skip to content

Rhenus Shipping Connector

The merchantCENTRAL Shipment Rhenus connector integrates Rhenus Freight Logistics into Microsoft Dynamics 365 Business Central. Unlike parcel carriers, Rhenus does not use a REST API but the position-based BORD512 flat file (an EDI standard for LTL freight). The connector generates this file directly in Business Central and transfers it by SFTP through an Azure Function — including multi-package (Colli), fixed-date delivery, an end-of-day manifest, and its own label generation.

What can the Rhenus connector do?

Feature Description
BORD512 EDI Position-based flat file with fixed field lengths, generated directly in BC
SFTP via Azure Function Transfer to Rhenus through a customer-hosted Azure Function bridge (BC SaaS cannot do SFTP directly)
Multi-package (Colli) Multiple packages per shipment; one label with its own number per package
:material-pallet: Package types Euro pallet, mesh box, carton, collo, container, and more — mapped to the BORD512 package type
Fixed date & Avise Fixed-date delivery (mandatory for FIX services) and recipient advance notification
PDF & ZPL Shipping label as PDF (laser printer) or ZPL pallet label (thermal printer)
End-of-day manifest Consolidated BORD512 manifest file per day
Sandbox mode Test BORD512 generation locally, without any SFTP upload

Quick start in 5 steps

If you are using the Rhenus connector for the first time, follow these steps:

Step 1: Have your Rhenus data and infrastructure ready

You need:

  • A Customer Code and Partner Code for the BORD512 transmission header (e.g. RKDBSP / RDEDUI)
  • Credentials for the Rhenus SFTP server (host, username, password)
  • An Azure Function acting as an SFTP bridge in your own Azure subscription (see Azure Function & SFTP)

Why an Azure Function?

Business Central SaaS cannot open SFTP connections. The BORD512 file is therefore sent by HTTPS to an Azure Function, which forwards it to Rhenus via SFTP. The function runs in your Azure subscription; the setup card includes a guided deployment guide (Azure Cloud Shell).

Step 2: Run the setup wizard

  1. Open Assisted Setup and start merchantCENTRAL: Set up Rhenus
  2. Enter the Azure Function / SFTP credentials, Customer/Partner Code, and the shipper address
  3. Run the connection test

→ Detailed guide: Initial Setup

Step 3: Test without infrastructure (sandbox)

Enable Sandbox Mode to test BORD512 generation and label printing without SFTP/Azure. Use Generate Test File to download a sample BORD512 file.

Step 4: Create your first shipment

  1. On the sales order, set the shipping agent to RHENUS
  2. In the Create Label dialog, capture the packages (Colli), pick a packaging material and — for FIX services — a delivery date
  3. Create the shipment: the BORD512 file and the label are generated

→ Detailed guide: Create a Shipment

Step 5: Run the end-of-day close

At the end of the day, consolidate all shipments into a manifest file and transfer it to Rhenus.

→ Detailed guide: End of Day

Supported Rhenus services

Code Service Use
STANDARD Standard Freight Standard LTL freight
EXPRESS Next Day Delivery on the next day
EXPRESS08 / 10 / 12 Next Day 08:00 / 10:00 / 12:00 Next day by the stated time
FIX Fixed date Delivery on a fixed date
FIX08 / 10 Fixed date 08:00 / 10:00 Fixed date by the stated time

Delivery date for FIX services

A delivery date is mandatory for all FIX* services. It must be in the future and must not be a Sunday (Rhenus delivers Mon–Sat).

→ Detailed description: Rhenus Services

Technical details

Property Value
Format BORD512 (FORTRAS EDI), position-based flat file
Transfer SFTP through a customer-hosted Azure Function (HTTP → SFTP)
Record types @@PH, A00, B00, B10, D00, F00, G00, H00, J00, Z00, @@PT
Label formats PDF (Word layout) or ZPL (thermal pallet label)
Tracking No online end-customer tracking (not provided by Rhenus)
Prerequisite merchantCENTRAL hub app (version 2.14.0.0 or later)

More topics