Integration between Ongoing WMS and nShift Delivery
Introduction
nShift Delivery (formerly Unifaun Online) is the solution to use if your need is to create shipments with one or several different transporters, print transport documents and have an overall efficient way of administering your shipments. Integrating nShift Delivery with Ongoing WMS enables you to further automate your repetitive transport tasks by performing them automatically from the Ongoing WMS. Using Ongoing Printer Service. you can for example print the labels automatically on demand.Features
Make transport bookings directly from Ongoing WMS
All information about a shipment (address and number of packages) can be entered into Ongoing WMS, and then transferred to nShift Delivery at the click of a button. After nShift Delivery has received all information, a transport label can be printed. For this feature, there is no need to log on nShift Delivery.
The integration with nShift Delivery also handles:
- Customs documents
- Printing favorites
Make tracking information visible in Ongoing WMS
If the transport booking for an order was made using the nShift Delivery integration, Ongoing WMS can read back the following tracking information and display it:
- Tracking link
- Waybill number
- Package numbers
nShift Checkout
With nShift Checkout each customer in your webshop can choose between different shipping alternatives that you have predefined. In this way, customers can decide whether they want their packages to be delivered to their office, to a pickup point or to their home.
To use this feature, each prepared shipment's prepareId will have to be provided to Ongoing WMS in the PreparedTransportDocumentId field.
Split shipment
With split shipment it is possible to send several packages addressed to different receivers through the customs as one single consignment. This means that you can reduce your transportations costs and simplify tracking.
Consolidated shipments
With consolidated shipments you can use several parcels in one shipment. This feature both simplifies tracking and means that you can reduce your transport costs.
If you for example have several orders in your Ongoing WMS which should be sent to the same consignee, you can send them all as one consolidated shipment.
Read more about consolidated shipments in nShift here.
Manifests
In nShift Delivery it is possible to create and print a shipment list with available shipments for a certain manifest type. This function is possible to trigger directly from Ongoing WMS. On the Shipment List page in Ongoing, you will need to specify the manifest type. Then, when sending a shipment from Ongoing WMS to nShift Delivery, the manifest will be created in nShift Delivery and the corresponding manifest document will be stored on the shipment in Ongoing WMS.
Freight Cost Management
nShift Delivery offers Freight Cost Management, which gives you control and visibility of your freight costs. By calculating the cost of each shipment, you can get full control over your transportation costs, both before booking your transport and over time. In addition, you have the possibility of visualizing and comparing freight costs from different carriers using invoice handling. This means that electronic invoices from your carriers are uploaded to Unifaun Enterprise. If you are a 3PL and want to bill your customer for the actual freight cost incurred, Ongoing WMS can fetch the freight cost and use it while generating your customer invoice.
Verify zip code automatically
With the nShift ZipCheck feature, zip codes are verified automatically, which makes it possible for the receiver to make corrections directly in the webshop. This feature is available in Sweden, Norway, Finland and Denmark.
If you are placing manual orders in Ongoing WMS, this can also be used to ensure that the correct address is always entered.
To enable the ZipCheck service in Ongoing WMS, a license needs to be ordered separately from nShift.
Transport status updates
Ongoing WMS can read back transport statuses from nShift Delivery, which makes it is possible to for example see if an order has been picked up by the carrier or is delivered.
This also adds the possibility of tracking completion times.
Getting started
Log onto nShift Delivery and go to Maintenance ⇒ API Keys. Then click New API Key and create a new API key. The key should be of type Web Services (REST) and the value for the Developer-Id should be 0020006475. Ongoing WMS will need to know the following:
- API ID
- API secret ID
After you have gathered this information, please see this guide on how to set up an integration between Ongoing WMS and nShift Delivery.
Mapping
None* = those fields are not in the default set up, but it is easy to set them to any field in Ongoing WMS.
Mapping nShift Shipment - Ongoing WMS Order
nShift Delivery | Ongoing WMS | |
---|---|---|
agent | Agent | |
quickId | OrderInfo=>OrderServicePointCode | |
customsDeclaration | CustomsDeclaration | |
CurrencyCode | PickedOrderLines=>CurrencyCode or OrderInfo=>OrderCustomsInfo=>CustomsValueCurrencyCode | |
DeclarantDate | DateTime.Now | |
Explanation | None* | |
FreightCharges | 0 | |
ImportExportType | None* | |
InvoiceNo | OrderInfo=>InvoiceNumber | |
Lines | List<CustomsDeclarationLine> | |
Contents | GoodsItems=>GoodsCategory | |
Copies | PickedOrderLines=>PickedNumberOfItems | |
GrossWeight | PickedOrderLines=>Article=>Weight or 0 | |
NetWeight | PickedOrderLines=>Article=>NetWeight or PickedOrderLines=>Article=>Weigh or 0 | |
OtherQuantity | 1 | |
OtherUnit | None* | |
SourceCountryCode | PickedOrderLines=>Article=>CountryOfOriginCode | |
StatNo | PickedOrderLines=>Article=>StatisticsNumber | |
Value | PickedOrderLines=>OrderLineTotalCustomsValue=>Value/PickedOrderLines=>OrderedNumberOfItems or PickedOrderLines=>Article=>Price=>Value | |
ValuesPerItem | true | |
PrintSet | None* | |
Sender | None* | |
TermCode | None* | |
favorite | ReturnTransporter=>WaybillTemplate if isReturn is true, Financial=>WaybillTemplate otherwise | |
goodsDescription | None* | |
options | List<Option>() | |
id | "CONSOLIDATE" (if isReturn is false) | |
sendEmail | false (if isReturn is false) | |
key | OrderInfo=>OrderId (if isReturn is false) | |
orderNo | OrderInfo=>OrderId | |
parcel | List<Parcel> | |
copies | OrderPalletItems=>NumberOfItems or GoodsItems=>NumberOfPackages | |
packageCode | OrderPalletItems=>PalletTypeCode or GoodsItems=>PackageTypeCode | |
contents | OrderPalletItems=>GoodsCategoryTypeName or GoodsItems=>GoodsCategory | |
length | OrderPalletItems=>Length or GoodsItems=>Length | |
width | OrderPalletItems=>Width or GoodsItems=>Width | |
height | OrderPalletItems=>Height or GoodsItems=>Height | |
volume | OrderPalletItems=>Volume or GoodsItems=>Volume | |
loadingMeters | (0 if OrderPalletItems=>ParentPalletItemId HasValue, OrderPalletItems=>LoadMeters otherwise) or GoodsItems=>LoadMeters | |
weight | OrderPalletItems=>Weight or GoodsItems=>Weight | |
profileGroup | None* | |
receiver | Consignee | |
name | Consignee=>Name | |
address1 | Consignee=>Address | |
address2 | Consignee=>Address2 + "," + Consignee.Address3 | |
contact | OrderInfo=>SalesCode | |
city | Consignee=>City | |
zipcode | Consignee=>PostCode | |
country | Consignee=>CountryCode | |
state | Consignee=>CountryStateCode | |
doorCode | Consignee=>DoorCode | |
receiverReference | OrderInfo=>SalesCode | |
returnPart | None* | |
sender | OrderInfo=>GoodsOwnerEdiCode or Financial=>PriceListCode | |
senderPartner | ReturnTransporter=>TransporterCode or Transporter=>Code | |
senderReference | (GoodsOwnerInfo=>Name + "-" + OrderInfo=>OrderId or GoodsOwnerInfo=>GoodsOwnerReference + "-" + OrderInfo=>GoodsOwnerOrderNumber) + "-R" if isReturn | |
service | ShipmentService | |
id | ReturnTransporter=>ServiceCode | |
returnShipment | false if ReturnTransporter=>TransporterCode not exists or IsReturnServiceButMustBeBookedAsTrip, true otherwise | |
termsCode | None* |
None* = those fields are not in the default set up, but it is easy to set them to any field in Ongoing WMS.