Integration between Ongoing WMS and Zendera
Zendera iTMS is an intelligent Transport Management System designed to optimize logistics operations. It connects seamlessly with external systems to handle orders, route planning, driver management, and delivery tracking in real time. The platform supports flexible integrations (API, XML, EDI) and provides powerful tools for staging, re-optimization, and monitoring. With iTMS, partners can ensure smooth data exchange, higher delivery precision, and streamlined transport processes across the supply chain. Use together with Ongoing WMS to gain full control of both your warehousing and transport operations.
Ongoing has built and maintains the integration with Zendera.
Getting started
To connect Ongoing WMS to Zendera, you first need to obtain an API key from Zendera. You will find this under Administration - Settings - Integrations in Zendera.
After this, please see this guide on how to set up an integration between Zendera and Ongoing WMS.
Features
Export orders from Ongoing WMS to Zendera
You can create an order in Zendera either from an order or a shipment in Ongoing WMS. You find information about how the orders/shipments are mapped below.
Fetch transport events from Zendera back to Ongoing WMS
When the order is being processed in Zendera, it will be updated with transport status events on the order/shipment in Ongoing WMS. This will for example show if the order has been picked up, delivered or cancelled in Zendera.
Default settings and considerations
The integration provides default settings which are suitable in most cases. However, there are some possibilities for customization.
-
Should the products in Zendera be created based on pallet items or waybill rows in Ongoing WMS?
Default: Pallet items if any exists, otherwise waybill rows. -
When should the order/shipment be sent to Zendera?
Default: when the send-button is pressed in Ongoing WMS.
Mapping
Mapping Zendera order - Ongoing WMS Order/Shipment
| Zendera | Ongoing WMS |
|---|---|
| Date | Today's date |
| Comment | Delivery instruction |
| Order type | Default value can be set when setting up the integration |
| Vehicle type | Default value can be set when setting up the integration |
| Customer.BusinessName | Consignee name |
Mapping Zendera products from Ongoing WMS pallet items/waybill rows. The mapping is the same regardless of if pallet items or waybill rows are used.
* Dimensions are generally in m in Ongoing but cm in Zendera.
| Zendera | Ongoing WMS |
|---|---|
| Height | Height x 100* |
| Width | Width x 100* |
| Length | Length x 100* |
| Weight | Weight |
| Quantity | Number of Packages |
| External ID | Label ID (parcel no) |
| Barcode ID | Label ID (parcel no) |
| Name | Packaging Type Code |
| Description | Goods Category |
Mapping of the pick-up address in Zendera - the data is taken from the consignor in Ongoing WMS (warehouse address)
| Zendera | Ongoing WMS |
|---|---|
| City | City |
| Name | Name |
| Address 1 | Address |
| Address 2 | Address 2 |
| Address 3 | Address 3 |
| ZIP Code | ZIP code |
| Reference | Reference |
Mapping of the delivery address in Zendera - the data is taken from the consignee delivery address in Ongoing WMS
| Zendera | Ongoing WMS |
|---|---|
| City | City |
| Name | Name |
| Phone Number | Mobile phone if any, otherwise telephone |
| Address 1 | Address |
| Address 2 | Address 2 |
| Address 3 | Address 3 |
| ZIP Code | ZIP code |
| Reference | Mark |
| Earliest | Current time |
| Latest | Delivery date if later than now, otherwise midnight between tomorrow and the day after tomorrow |