Integrating via XML files requires the OnlineConnect application.
OnlineConnect imports XML order files from your ERP system to nShift Delivery and reports back assigned parcel and consignment numbers.
The ERP system creates an order file with shipment information for the current order(s) and places it in OnlineConnect’s order directory. OnlineConnect reads the file and sends it to nShift Delivery.
If all shipment data is valid, OnlineConnect prints labels, shipment lists and customs documents depending on service, destination and configuration. Labels and documents are either printed directly after the order file has been sent to nShift Delivery or stored to be printed from nShift Delivery. Incomplete orders are stored for later completion.
OnlineConnect can also send back a text file with parcel and shipment numbers.
The order file should be in XML format. Please refer to the XML file specification.
Data transfer between OnlineConnect and nShift Delivery is TLS encrypted (HTTPS). The communication is secured by TLS v1.2.
Install OnlineConnect
The installation of OnlineConnect follows the standards for “Windows Installer”. The installation file is currently only available in English. However, the Administration of OnlineConnect is available in several different languages.
System requirements
- Windows 10 or higher
- Windows Server 2016 or higher
- Local system administrator privileges.
Run OnlineConnect
After installation, two shortcuts are created in the start menu, Administration of OnlineConnect and OnlineConnect.
OnlineConnect can be run either as a desktop application or as a Windows service.
Running the application in desktop mode requires that a user is logged in to the operating system console/desktop, while service mode does not.
OnlineConnect is designed as a server-side application and should be run accordingly, that is, as a service. It is considered best practice to have a dedicated system user account that can be used for running the application as a service. The application settings are stored in the user’s home directory, which means that the user making configuration changes and running the application should be the same.
- The dedicated user account should be excluded from the password change policy.
- The user should be a domain member, where applicable.
- The user should be appointed local administrator.
- Make sure that the user has access to the necessary printers and network folders.