Initial Setup
This guide walks you through the first-time configuration of the Rhenus connector using the setup wizard. The wizard has 7 steps and first checks whether the merchantCENTRAL hub is already configured.
Prerequisites
- The merchantCENTRAL hub app is installed and configured
- You have a Rhenus freight contract with a Customer Code and Partner Code
- You have credentials for the Rhenus SFTP server
- An Azure Function (SFTP bridge) is deployed or will be created during setup → Azure Function & SFTP
Test without infrastructure first
Want to verify the format and labels before the Azure Function is ready? Enable Sandbox Mode (the Advanced section of the setup card). The Azure/SFTP fields then become optional and no file is transmitted.
Opening the wizard
Start the wizard in one of these ways:
- Assisted Setup (search: Assisted Setup) → merchantCENTRAL: Set up Rhenus
- Rhenus Dashboard → action Setup Wizard
Hub first
The wizard first calls the central Platform Guard. If the hub is not yet configured, you are redirected to the hub setup and can only continue afterwards.
The 7 steps
Step 1 — Welcome
The wizard lists the prerequisites (Azure Function data, SFTP data, Rhenus codes, shipper address). Click Next.
Step 2 — Connection (Azure Function & SFTP)
Enter the transfer details here:
| Field | Description |
|---|---|
| Azure Function URL | URL of the Azure Function for the SFTP transfer |
| Azure Function Key | Authentication key (secure input on click) |
| SFTP Host | Hostname/IP of the Rhenus SFTP server |
| SFTP Port | Default: 22 |
| SFTP Username / Password | SFTP credentials (secure input on click) |
| SFTP Remote Path | Target directory on the SFTP server |
Use the Set up Azure Function action to open the deployment guide if the function does not exist yet.
Secure storage
The Azure Function Key, SFTP username, and password are stored exclusively in the hub's central Credential Store — never in the database. The fields only show Configured / Not configured.
Step 3 — Connection test
Click Test Connection. The connector checks HTTP access to the Azure Function and the SFTP login. The result is shown as a status.
Step 4 — Rhenus configuration
| Field | Description |
|---|---|
| Customer Code | Rhenus customer number in the BORD512 header (e.g. RKDBSP) |
| Partner Code | Rhenus partner code in the BORD512 header (e.g. RDEDUI) |
| File Format Version | BORD512 format version (default: 35) |
| Depot Code | Depot number printed on the ZPL pallet label |
Step 5 — Shipper address
Enter the shipper details (name, street, postal code, city, country code …). Use Load from Company to take the address from the Business Central company information.
Step 6 — Default settings
| Field | Description |
|---|---|
| Shipping Agent Service | Default service (e.g. STANDARD), pre-filled in the Create Label dialog |
| Packaging Material | Default packaging material (e.g. RH-EP Euro pallet) |
| Default Weight (kg) | Default weight if not specified on the order |
| Default Label Format | PDF or ZPL |
Pre-configured packaging material
On installation, the connector creates one default packaging material per BORD512 package type (RH-EP…RH-CO). On an empty system the Euro pallet is set as the default. See Packages.
Step 7 — Finish
Review the summary (connection, connection test, Rhenus codes, shipper address) and click Finish. The connector is activated.
After setup
- Check the Dashboard — while sandbox mode is active, a banner is shown.
- Use Generate Test File to produce a sample BORD512 file for a format check.
- Create your first shipment → Create a Shipment.
Setup incomplete
As long as mandatory fields are missing, the setup card shows a red Setup incomplete banner at the top. In production (sandbox off), the Azure Function URL and SFTP host are mandatory.
→ Full field reference: Setup (Reference)