Logistyx Integration

Logistyx is a cloud transportation management system which outputs labels in Zebra Printer Language (ZPL) format. The Logistyx TME multi-carrier shipping solution uses Pierbridge shipping technology.

Best Practices

eFORMZ can be used to move and enhance data between other third-party applications and Logistyx. This process is triggered by the release of ZPL labels and database queries. Depending on the complexity of the existing business process, eFORMz may use a combination of integration methods, including web service calls, relational database queries and printing to a virtual printer. For more information on how these methods generally work with eFORMz, consult the following: eFORMz Integration

Sample process

Using Logistyx’s rate-shopping service, the request to create a carrier label passes a “rate group” instead of a specific carrier and service level. Logistyx finds the best shipping rate in that “rate group” and returns the selected carrier and service level. This information is then passed in a “Create Shipment” call to Logistyx to create the actual label. The tracking number and shipping charges coming back from Logistyx are stored in the third-party WMS, ERP or Order Management application database.

Several processes will combine to provide complete handling of the creation of carrier shipping labels (in Ship To Hold status), release of those carrier shipping labels and end-of-day processing for the various
carriers.

Wave process

The wave process sends a wave of multiple cartons to eFORMz to process, resulting in shipping labels stored as ZPL files. This wave process is initiated by generic shipping labels in ZPL format printed to a
virtual printer. These ZPL files are picked up by a Director queue.

Print a label

To print a label generated in the wave process, a generic label is written to a specific eFORMz virtual printer, which writes a ZPL file to the configured directory. When an eFORMz project processes this label, the carton ID is pulled from the label. eFORMz then looks for the completed carrier label in the location where the shipping labels are stored in the “Wave process” step. The label is printed on the physical printer corresponding to the virtual printer to which the original trigger label was printed.

Tags: multi-carrier shipping