Integration between Ongoing WMS and Cargonizer
Cargonizer is a flexible, affordable and user-friendly transportation administration system made by Logistra. Integrating Ongoing WMS and Cargonizer enables more efficient processes in the warehouse, such as scanning, batch picking of orders and automatic label printing. The integration works well no matter if you run your own warehouse or outsource your logistics to a logistics provider (3PL) that runs Ongoing WMS.
Features
Make transport bookings directly from Ongoing WMS
You can create a consignment in Cargonizer either from an order or a shipment in Ongoing WMS. You find information about how the orders/shipments are mapped below.
Make tracking information visible in Ongoing WMS
When the consignment in Cargonizer has been created, Ongoing WMS will receive a response from Cargonizer. Depending on the transporter and your Cargonizer settings the response might contain the following information:
- Tracking URL
- Freight price
Note that this is not included when using shipments in Ongoing WMS.
Default settings and considerations
The integration provides default settings which are suitable in most cases. However, there are some possibilities for customization.
-
Should the consignment in Cargonizer be created based on orders or shipments in Ongoing WMS?
Default: Orders. -
When should the order/shipment be sent to Cargonizer?
Default: when the send-button is pressed in Ongoing WMS.
Getting started
The following data is required to set up an integration with Cargonizer:
- API key
After you have gathered this information, please see this guide on how to set up an integration between Ongoing WMS and Cargonizer.
Mapping Ongoing WMS Order - Cargonizer Consignment
Order Information
| Cargonizer | Ongoing WMS |
|---|---|
| Message - Carrier | Delivery Instructions |
| Reference - Consignor | Goods Owner Order Number |
| References – Consignee | Sales Code |
| OrderId | Orderid |
Items (Parcels)
An item in Cargonizer is created for every freight row on the Ongoing WMS order. An order must have at least one freight row in Ongoing WMS to create an consignment in Cargonizer.
| Cargonizer | Ongoing WMS |
|---|---|
| Type | Packaging Type Code |
| Amount | Number of Packages |
| Weight | Weight |
| Volume | Volume |
| Length | Length |
| Width | Width |
| Height | Height |
| Description | Goods Category |
Consignee
The data is mapped from the orders consignee in Ongoing WMS.
| Cargonizer | Ongoing WMS |
|---|---|
| Name | Name |
| Address1 | Address |
| Address2 | Address2 + Address3 |
| City | City |
| Post Code | Post Code |
| Country | Country Code |
| Phone | Telephone |
| Mobile | Mobile Phone |
Transporter Information
| Cargonizer | Ongoing WMS |
|---|---|
| Transport Agreement | Customer Code on Transporter Agreement |
| Product | Transport Service Code |
If MYPACK is used a service partner is added
Order Response
When the consignment has been created in Cargonizer, Ongoing WMS receive a repsone. Depending on the transporter you are using and the settings in Cargonizer the response might contain the following information.
| Cargonizer | Ongoing WMS |
|---|---|
| Tracking URL | Invoice URL |
| Kolli number | Waybill |
Mapping Ongoing WMS Shipment - Cargonizer Consignment
Shipment Information
| Cargonizer | Ongoing WMS |
|---|---|
| Message - Carrier | Delivery Instructions |
| Reference - Consignor | Shipment Order Number |
| ShipmentId | ShipmentId |
Items
Each freight row on the Ongoing WMS Shipment will create an item on the consignment in Cargonizer. The fields are mapped as the order freight rows.
Consignee
The information in Ongoing WMS is taken from the shipments consignee and is mapped as the order consignee.
Transporter Information
The information in Ongoing WMS is taken from the shipments transporter agreement set on the shipment and is mapped as the transporter information on an order.
Response
No default response handling for shipments.