Carrier Setup
After downloading carrier data from nShift (see Getting Started), configure the carriers, services, account numbers, and package codes to match your shipping requirements.
Carriers
Open ECShip Carriers to view all carriers downloaded from nShift.
| Field | Description |
|---|---|
| Carrier Code | The carrier identifier in nShift (e.g., POSTI, DBSCHENKER, FEDEX) |
| Carrier Description | Carrier name |
| Enabled | Toggle to enable or disable the carrier for use in shipments |
| Default | Mark one carrier as the default for new shipments |
| Count Carrier Services | Number of available services for this carrier |
Carrier Actions
- Carrier Services — View and configure services for the selected carrier
- Carrier Package Codes — View and configure package type mappings for the carrier
- Edit Print Config — Configure carrier-specific print settings (JSON format)
Carrier Services
Open carrier services from the Carriers page or search for ECShip Carrier Services.
Each carrier has one or more services that define the type of delivery (e.g., express, economy, home delivery).
| Field | Description |
|---|---|
| Carrier Code | Parent carrier |
| Carrier Service Code | Service identifier in nShift |
| Service Description | Service name |
| Default | Mark one service as the default for this carrier |
| Pickup Booking By Default | Automatically include pickup booking when this service is selected |
| No Dispatch | Skip dispatch information to nShift — uses sender address as pickup location |
| Addons Defined | Number of addons available for this service |
Service Actions
- Addons — View and configure service addons
- Edit Print Config — Configure service-specific print settings (JSON format)
Carrier Service Addons
Addons are additional services that can be added to a shipment, such as:
- Pre-notifications (email/SMS to receiver)
- Cash on delivery
- Freight payer options (consignee pays, third-party pays)
- Delivery instructions
Open addons from the Carrier Services page or search for ECShip Carrier Serv.Addons.
| Field | Description |
|---|---|
| Carrier Service Addon Code | Addon identifier in nShift |
| Addon Description | Addon name |
| Selected | When enabled, the addon is automatically included when the service is selected for a new shipment |
| Additional Parameters Exists | Indicates that the addon requires parameter values |
Addon Parameters
Some addons require additional parameter values. For example, a pre-notification addon needs the recipient's phone number or email address. Parameters can be configured to pull values automatically from Business Central records.
Open addon parameters by drilling down from the addons page.
| Field | Description |
|---|---|
| Parameter Id | Parameter identifier in nShift |
| Parameter Code | Parameter code |
| Name | Parameter display name |
| Required | Whether the parameter must have a value |
| Constant Value | A fixed value to always use for this parameter |
| Source Table ID | Business Central table to read the value from (e.g., Customer, Sales Header) |
| Source Field ID | Specific field in the source table |
Example: To automatically fill a phone number addon parameter from the customer's phone number, set Source Table ID to the Customer table and Source Field ID to the Phone No. field.
Carrier Account Numbers
Carriers require account numbers to identify who is responsible for freight costs. Configure account numbers at ECShip Setup → Setup Unifaun Account Numbers or search for ECShip Carrier Account No.
| Field | Description |
|---|---|
| Carrier | The carrier this account applies to |
| Type | Entity type: Vendor, Customer, Location, or Company |
| No. | The specific entity (vendor/customer/location number) |
| Carrier Account No. | The freight account number registered with the carrier |
| Description | Free-text description |
| Shipment Method Filter | When set, this account is only used when the shipment method matches. For example, set FCA to use this account only for FCA shipments. |
| Account No. Issuer Code | Issuer code for the account number (e.g., Z14 for Postnord Oy) |
Automatic Account Number Selection
When a shipment is created, the system automatically selects the appropriate carrier account number based on:
- The carrier assigned to the shipment
- The customer/vendor on the source document
- The shipment method on the source document
If a carrier account number exists for the customer with a matching shipment method filter, the system sets:
- Payer Account No. Type to Customer
- Payer Account No. to the configured carrier account number
This allows different customers to have different freight payment arrangements per carrier and shipment method.
Freight Payer Scenarios
| Scenario | Addon | Configuration |
|---|---|---|
| Sender pays (default) | None needed | Standard — no addon required |
| Consignee pays | RPAY (or carrier equivalent) |
Select RPAY addon, set consignee's carrier account number as the parameter value |
| Third party pays | OPAY (or carrier equivalent) |
Select OPAY addon, set third party's carrier account number as the parameter value |
Package Codes
Package codes define the types of packages available (e.g., EUR-pallet, parcel, envelope). View all available codes at ECShip Package Codes.
| Field | Description |
|---|---|
| Code | Package type code from nShift |
| Description | Package type name |
Carrier Package Code Mapping
Map package codes to specific carriers and define default dimensions. Open from the Carriers page → Carrier Package Codes or search for ECShip Carr. Package Mapp.
| Field | Description |
|---|---|
| Carrier Code | The carrier this mapping applies to |
| Package Code | The package type |
| Package Code Description | Display name |
| Length | Default package length |
| Width | Default package width |
| Height | Default package height |
| Package Weight | Default weight of the empty package |
| Default | Mark as the default package type for this carrier |
When a new parcel is added to a shipment, the default package code's dimensions and weight are pre-filled. For example, if an EUR-pallet (1.2 × 0.8 m) is set as default with length and width defined, the user only needs to enter the height.
Next Steps
- Shipping Agent Mapping — Map Business Central shipping agents to nShift carriers
- Shipment Workflow — Create and send shipments