Rhenus Shipment Setup
Central setup for the Rhenus Freight Logistics Connector. This is where Azure Function/SFTP credentials, Rhenus configuration, shipper address, and default settings for LTL (less-than-truckload) shipments in BORD512 format are configured.
The setup is embedded as a part directly on the central merchantCENTRAL shipping provider card (section Rhenus Settings). For the initial configuration, a guided assistant (Setup Wizard) is also available.
Opening the Page
- Via the merchantCENTRAL Dashboard → Shipping Providers → Rhenus → Rhenus Settings
- Via the Rhenus Dashboard → action Setup
- Initial setup: Assisted Setup → Rhenus Freight Logistics Setup or the Dashboard action Setup Wizard
Setup Order
The Setup Wizard first checks, via the central Platform Guard, whether the merchantCENTRAL Hub is already configured. If not, you are redirected to the Hub setup.
Fields
Azure Function
Credentials for the Azure Function that serves as middleware for the SFTP upload.
| Field | Description |
|---|---|
| Azure Function URL | URL of the Azure Function for SFTP file transfer |
| Azure Function Key | Authentication key of the Azure Function. Entered via a secure input dialog on click; only the status Configured / Not configured is shown |
Middleware Architecture
Since Business Central (SaaS) does not have direct SFTP access, an Azure Function is used as middleware. The BORD512 file is sent via HTTP to the Azure Function, which then forwards it via SFTP to the Rhenus server. The Azure Function runs in the customer's own Azure subscription — the action Set up Azure Function opens the deployment guide (Azure Cloud Shell).
SFTP Connection
Connection details for the Rhenus SFTP server (passed to the Azure Function).
| Field | Description |
|---|---|
| SFTP Host | Hostname or IP address of the Rhenus SFTP server |
| SFTP Port | Port of the SFTP server (default: 22) |
| SFTP Username | SFTP username. Entered via the secure input dialog on click (Configured / Not configured) |
| SFTP Password | SFTP password. Entered via the secure input dialog on click (Configured / Not configured) |
| SFTP Remote Path | Target directory on the SFTP server for the BORD512 files |
Secure Credential Storage
The Azure Function Key, SFTP username, and password are stored exclusively in the Hub's central Credential Store (not in the database). These fields therefore never show clear text, only the status Configured / Not configured.
Rhenus Configuration
Rhenus-specific configuration for the BORD512 format.
| Field | Description |
|---|---|
| Customer Code | Rhenus customer number used in the BORD512 transmission header (e.g. RKDBSP) |
| Partner Code | Rhenus partner code used in the BORD512 transmission header (e.g. RDEDUI) |
| File Format Version | Version of the BORD512 format (default: 35) |
| Depot Code | Rhenus/CargoLine depot number printed on the ZPL pallet label |
Shipper Address
Shipper address for all Rhenus shipments (BORD512 record B00..SHP). In the wizard, the address can be taken from the company information via Load from Company.
| Field | Description |
|---|---|
| Shipper Name | Name of the shipper (line 1) |
| Shipper Name 2 | Additional shipper name (line 2) |
| Shipper Street | Street of the shipper |
| Shipper Post Code | Postal code of the shipper |
| Shipper City | City of the shipper |
| Shipper Country Code | Country code (e.g. D for Germany, A for Austria) |
| Shipper Customer No. | Shipper's customer number at Rhenus |
| Shipper Contact Name | Contact person at the shipper |
| Shipper Phone | Phone number of the shipper |
| Shipper Email | Email address of the shipper |
Default Settings
Default values for shipment creation.
| Field | Description |
|---|---|
| Shipping Agent Service | Default shipping agent service (e.g. STANDARD, EXPRESS, FIX). Passed to the Hub and pre-filled in the Create Label dialog |
| Packaging Material | Default packaging material. The BORD512 package type is derived from the material mapping |
| Default Weight (kg) | Default weight in kilograms if not specified on the order |
| Generate Label Report | Generates and stores a shipping label per shipment |
| Default Label Format | Label output format: PDF (visual label) or ZPL (thermal printer / pallet label) |
| Parcel No. Series | Number series for unique parcel numbers (ZPL barcode) |
| Default Incoterm BORD512 Code | Default Incoterm/franking code for the BORD512 G00 record (e.g. 02 = carriage paid) |
| File Name Pattern | Pattern for the file name ({DATE} = date, {NO} = sequence number, e.g. BORD512_{DATE}_{NO}.txt) |
| Next File No. | Next sequential file number (automatically incremented) |
Deprecated Fields
The former enum fields Default Service Type and Default Package Type are deprecated and have been replaced by Shipping Agent Service (service code) and Packaging Material respectively.
Pre-configured Packaging Material
On installation, the connector creates one default packaging material per BORD512 package type in the hub (RH-EP Euro pallet, RH-FP flat pallet, RH-HP half pallet, RH-GI mesh box / Gitterbox, RH-KO collo, RH-PA parcel, RH-KA carton, RH-CO container). The Packaging Material field can be preset directly with one of these materials; on an empty system the Euro pallet (RH-EP) is set as the default. Existing materials are never overwritten.
Advanced
| Field | Description |
|---|---|
| Sandbox Mode | Enables test mode. No file is transmitted to the productive SFTP server; the BORD512 generation can be tested without any Azure infrastructure |
Status
Current status information for the Rhenus integration.
| Field | Description |
|---|---|
| Last File Uploaded | Date and time of the last uploaded BORD512 file |
| Files Uploaded Today | Number of files uploaded today (highlighted in green) |
| Last Error Message | Last error message (red when an error occurred) |
| Last Error Date/Time | Timestamp of the last error |
As long as the mandatory fields are incomplete, the card shows a red Setup incomplete banner at the top.
Actions
| Action | Description |
|---|---|
| Set up Azure Function | Opens the deployment guide to provision the required Azure Function (SFTP bridge) in your own Azure subscription |
| Test Connection | Tests the connection to the Azure Function and the Rhenus SFTP server (HTTP access and SFTP login) |
| Generate Test File | Creates a sample BORD512 file with test data for download without transmitting it to Rhenus. Useful for verifying the file format |
| Upload Test File | Creates a sample BORD512 file and uploads it to the Rhenus SFTP server via the Azure Function. Tests the complete transfer chain |
Creating a Shipment (Create Label Dialog)
When creating a Rhenus shipment, the Hub dialog shows additional fields:
| Field / Section | Description |
|---|---|
| Delivery Date (Fixed Delivery) | Mandatory for all FIX* services. Must be in the future and must not be a Sunday (Rhenus delivers Mon–Sat) |
| Avise (Recipient Notification) | Optional value-added service: the recipient is notified in advance by phone/email about the delivery (BORD512 record H00) |
| Packages (Colli) | Capture multiple packages per shipment. A separate shipping label with its own tracking number is created for each package |
Label Formats
| Format | Description |
|---|---|
| Visual shipping label from a Word layout report | |
| ZPL | CargoLine/Rhenus pallet label for thermal printers — one label per package, with barcode parcel number (from Parcel No. Series), Modulo-10 check digit, depot, delivery date (for FIX), and umlaut conversion |
Notes
Manifest / End of Day
The Rhenus Connector supports an end-of-day closing (Manifest): all created shipments are consolidated into a single BORD512 file and transmitted as a batch file to Rhenus (Hub Manifest function). Individual shipments can be excluded from the manifest via Exclude/Include Manifest on the shipment label list (excluded rows are dimmed). The Rhenus Dashboard additionally offers Download Manifest Preview (preview of all open shipments) and Download Last Manifest (re-download the last closing).
BORD512 Format
Rhenus does not use a REST API but instead the BORD512 flat-file format (EDI standard for LTL freight). The file contains position-based record types (@@PH, A00, B00, B10, D00, F00, G00, H00, J00, Z00, @@PT) with fixed record lengths.
No Online Tracking
Rhenus does not offer online tracking for end customers. Shipment status inquiries must be coordinated directly with Rhenus.
Singleton Page
The Rhenus setup has exactly one record. When opened for the first time, the record is created automatically.