Welcome to a quick introduction to the most important features in nShift On-premises (former Consignor). Each section will provide a short description and links to more in-depth articles.

Go to the topic of your interest:

• Installation and system requirements
• The Main menu
• Creating a shipment and printing a label
• Transmitting data to the carrier
• Integration

Installation and system requirements

nShift On-premises is the Windows/SQL based version of nShift Ship installed on your own server environment.

Your system should match these minimum requirements:

See our full description of system requirements, ports, and web services for the entire nShift Ship platform here:

nShift Ship (Consignor) system requirements and webservices

To install nShift On-premises, download and run this file as administrator:

• SetupSRVC.exe

For more information about the installation process, please read these articles:

Installing nShift On-premises Server with your own SQL Server

Installing nShift On-premises Client

A technical consultant from nShift usually takes care of the installation process and setting up new carriers.

The Main menu

nShift On-premises has a menu on the left-hand side. The most used menu items are found in the Main section. The screen dump below shows the Production view where new shipments are produced. (Click the image to see a larger version)

A short explanation of each item in the Main menu:

Creating a shipment and printing a label

The Production view is where you fill in shipment data and print a label. Follow these steps to make a standard shipment (see the image with numbers below the steps):

1. Go to Main > Production and start by selecting a carrier and a product which is the carrier service.
   
   
2. Check any add-on services needed on the shipment. It varies from carrier to carrier which services are available.
   
   
3. Fill in Receiver and Sender addresses. As a minimum, fill in Name1, Address1, Country code, PostNo, and City. If you have a default sender address on your installation, this might be prefilled. Note that some carriers also require data in the Attention, Mobile, Email, and Phone fields.
   
   
4. Fill in References and Messages fields if needed. The References fields vary from carrier to carrier but the most commonly used fields are Ordernumber and ReceiverRef. Not all carriers support the message fields.
   
   
5. Fill in Goods Information. It depends on the type of the goods and your carrier how much information is needed. Number, Contents, and Weight are often mandatory.
   
   
6. Click the Print button. The carriers have different validation rules and requirements for mandatory fields. When you click the Print button, On-premises will tell you if you are missing mandatory data on your shipment. If this is the case, fill in the missing information and click Print again.

If no printer has been added to nShift On-premises, you will see the Document Printer Wizard:

1. Select your printer from the list of available printers.
   
   
   
   
2. Choose the printer type.
   
   
   
   
3. Click Check Status and then OK.
   
   
4. The label is now printed and the shipment is placed in Outbox, ready for transmit.

Transmitting data to the carrier

It is very important to transmit your EDI files. If a carrier has not received the EDI files before they handle the goods, they may need to handle it manually and some will charge a fee for this. (Note that some carriers use a web service integration in nShift On-premises and do not require EDI files. Ask nShift customer service if in doubt).

Follow these steps to manually transmit EDI-files:

1. Go to Main > Outbox.
   
   
2. Check the stack containing the shipments you want to transmit. You may select multiple stacks and if you check Installation, you will select all stacks. The number in brackets next to a stack shows how many shipments are waiting to be transmitted.
   
   
   
   
3. Click the Transmit Checked button.
   
   
4. Click Yes in the alert box.
   
   
   
   
5. The transmit window is displayed briefly while the shipments are transmitted.
   
   
6. Upon successful transmit, all shipments disappear from Outbox (or the ones checked).

Read more about auto transmit, transmitting selected shipments, and retransmitting in these articles:

Transmitting EDI files to carriers in On-premises

Setting up auto transmit of EDI files in On-premises

Integration

Many customers have some kind of integration between nShift On-premises and their ERP, WMS, or other systems. Filedrop integration is an easy and popular integration method that has many advanced possibilities and can be tailored to fit almost any setup.

nShift On-premises can import orders from any system that is able to provide a file and drop it in a shared folder that both systems have access to. In the import setup in On-premises, you specify which fields your file contains and how they should be mapped to fields in On-premises.

Read this article to learn more about filedrop integration:

Getting started with filedrop integration

See our standard file in CSV and XML format with an explanation of each field:

Standard file for filedrop integration (import setup)