The majority of our customers use nShift Ship via integration to their back-end system. nShift Ship can be integrated into your ERP, WMS, or e-commerce solution in several ways, and it relieves you of manual re-entry of order information when producing shipments.

Filedrop integration

The most basic and widely used way of integration is filedrop (known as Import in Ship). It works with any system that can create and drop a file in a shared folder. It is described in several dedicated articles in our Filedrop Integration section.

Plugins

A plugin is installed in your backend system and connects to nShift's Shipment Server API. Plugins are developed by nShift and are ready for use, so no development is needed on your part. Read more about plugins in our nShift Plugins section.

Database (SQL) integration 

If you use this type of integration, both nShift Ship and the other system must run locally at your site. Database integrations make queries directly to the order system's SQL database and show the data in nShift Ship's production view. Database integrations are often used in a manual way where the user types an order number from the other system into nShift Ship to fetch information and use this to produce a shipment. Please contact nShift Customer service if you are interested in this integration method.

Web integration

With this type of integration, nShift Ship and the other software do not need to be physically located together. Our web service integration allows your order system to export orders so nShift Ship can fetch them through our web service, and you will be able to look up any orders or contacts in nShift Ship's production view. Please contact nShift Customer service if you are interested in this integration method.

Overview of integrations sorted by 3rd party system

The table below shows the integrations maintained by nShift.

Abbreviations:
NOP=nShift On-premises 
SS=Shipment Server 
TIC=Ticket

*Also available as a 3rd party standard integration, read more here.