CERM is a solution provider in Business Management and Automation Solutions for the narrow web printing industry. They offer a complete solution for this niche market, including estimating, job processing, product catalog, shipping and invoicing, works schedule, raw material management, job costing, and shop floor data collection.

CERM has developed an integration to Shipment Server API which makes it possible for their customers to integrate nShift Ship with their CERM software and take advantage of nShift's extensive carrier library, track and trace, and easy transfer of data to carriers.

Contents of this article:

• Requirements
• Workflows
• Documentation and related articles
  
  

Requirements

CERM is able to integrate to Shipment Server. To set up this integration, you need a Shipment Server account and a Portal user with Ticket access. Printing is done using Drop Zone.

The Shipment Server setup is done by a technical consultant from nShift while the integration setup in CERM is done on their side. If you would like to set up a Shipment Server account to use with CERM, please contact nShift Customer Service. 

Workflows

This section will explain the overall workflow in the CERM nShift Ship integration. For more detailed information on how sales orders are created in CERM, we refer to CERM's documentation and Help pages.

Auto-print flow

1. Sales order is created in CERM.
2. Transport requirements for the sales order are exported from CERM to nShift Ship.
3. Data are validated in nShift Ship and a label is printed using Drop Zone.
4. A shipment is placed in the Outbox in Ticket.
5. The tracking URL is returned to CERM and the shipment can be found in Portal.
6. Data is transmitted to the carrier from Ticket.
7. Return data is available in Portal and CERM (if supported by the carrier). 

Manual flow

1. Sales order is created in CERM.
2. Transport requirements for the sales order are exported from CERM to nShift Ship.
3. A shipment is placed in the Inbox in Ticket, awaiting manual processing.
4. Missing data are added to the shipment using Ticket. 
5. Label is printed using Drop Zone.
6. The tracking URL is returned to CERM and the shipment can be found in Portal.
7. Data is transmitted to the carrier from Ticket.
8. Return data available in Portal and CERM (if supported by the carrier).

Documentation and related articles

Read the documentation written by CERM: http://www.cerm.be/hd/onlinehelp/Modules/Transport/Consignor_transport_EDI.htm 

Sign up for CERM's free online course about the nShift Ship integration:

https://academy.cerm.net/courses/take/whats-new-in-version-v723/lessons/14149239-consignor-intergration

Relevant articles about Ticket, Portal, and Drop Zone:

• Getting started with Ticket (web based solution)
• Transmitting EDI files to carriers in Ticket
• Printer setup in Ticket (configuration of Drop Zone)
• Getting started with Portal