Integrations
New connections for your trucks,
your ERP and your developers
Since May, Zendera reads data straight from more trucks and tachographs, takes orders from more ERP and shipping systems, and gives integration partners sturdier webhooks and new APIs.
Hi there,
Every number you don't have to type is one less thing to get wrong. This page is for admins and integration partners: what Zendera can connect to now, what the data is used for, and what changed for developers.
1 · Telematics
Data from the truck, not just the phone
The driver app has always told Zendera where the driver is. Now Zendera can also read the truck and the tachograph directly, through the telematics provider you already use.
Each connection is set up for your organization by Zendera, using the account you have with the provider.
Zendera reads your Volvo trucks through rFMS, the industry standard for truck data. Positions come in every minute, and odometer, fuel and ignition every few minutes. If Volvo's service is down for a while, Zendera keeps trying and catches up afterwards.
If your trucks have care4all units, Zendera now also reads the tachograph: which card is in, and whether the driver is driving, working or resting. That is what powers the Drivers' Hours view, with remaining driving time per driver.
Fleets on Wialon, including JAXicloud accounts, can be connected for positions and sensors. We can also store each message whole, so more of what your units send can be used later without asking you for new data.
In workday analytics, the truck's own movement and ignition sit next to the phone's GPS, and the odometer gives a distance you can trust when the phone signal is weak.
Link devices and cards in one place
Data is only useful when it lands on the right truck and the right driver. Under Settings → Organization → Tacho and vehicle data, admins see the devices and tachograph cards that send data but aren't linked yet. Zendera suggests a match and shows why. You accept it, pick another vehicle or driver, or dismiss it.
The same page has a Vehicle data setting. Choose Off, Fill gaps (Zendera fills empty vehicle fields from your provider and flags differences) or Keep in sync (your provider's values replace the vehicle's). Every automatic change is listed, and you can undo it.
Telematics connections are set up by Zendera for each organization. Tell us which provider you use and we'll take it from there. Drivers' Hours is a module we turn on for you.
rFMS is a shared standard, so other truck makers can follow Volvo. Each maker does it a little differently, so ask us about yours.
2 · Order imports
Orders from more systems
When orders flow in from the system where they start, nobody has to type them twice. These connections are new since May. Each was built together with a customer, and the work is ready to reuse for the next one on the same system.
Confirmed sales orders are picked up every few minutes and become Zendera orders, with one colli per temperature zone and the order lines inside. When an order is cancelled in the ERP, it is cancelled in Zendera too.
Shipments exported from nShift as XML are imported every five minutes, with the delivery address details, the carrier service as order type, and the SSCC barcode on each package.
From Microsoft Dynamics 365, purchase orders now arrive as inbound orders, picked up at the supplier and delivered to your depot. Customer returns arrive as pickup orders from the customer back to the depot.
From Business Central, items that could not be picked are added to the order they belong to, together with any replacement item. Everyone looking at the order sees what is missing.
Your system isn't listed? Zendera also takes orders through the Orders Import API and CSV files. See Supported integrations for how a new connection is planned and built.
3 · For developers
Sturdier webhooks, new APIs
If you build against Zendera, these are the changes to know about.
A webhook used to be switched off after 10 failed deliveries in a row. Now Zendera waits a little longer between each try and keeps going, so a short outage on your side no longer means lost events. If an endpoint has had no successful delivery for 15 minutes, our team is alerted.
Webhook bodies, emails and SMS can now use the order's route number, the driver's internal number, and the stop's number in the driver's route with the total number of stops, the same numbers the driver timeline shows.
Post a message to the driver on an order, and read the conversation back, by Zendera order ID or your own order number. The driver gets it in the app like any other chat message. See the Order Messages API.
If an order changes after you exported it to a carrier, for example when weights arrive later from the ERP, it comes back in the export feed marked as an update, for up to 14 days. This is switched on per organization, see Re-exporting changed orders. Exports now also include the route number.
Create and update route schedules and their bookable time slots, with capacity, order types and driver skills, from your own planning system. Before, only Zendera could set them up. See the Route Scheduling API.
Statuses that external carriers send now show on the order as a timeline. And if your system sends statuses Zendera doesn't read yet, it can post them to us as they are. We keep each one exactly as received, so the mapping can be worked out with you. Talk to us before you start.
The Orders Import API takes a priority per location, which the optimiser uses to rank stops. Products can carry your own free-form metadata, and it comes back out in the carrier export.
Before we switch on re-export for you, make sure your exporter sends updates to the carrier as updates, not as new shipments. The guide explains what to look for.
Want to connect a system?
Tell us which telematics provider, ERP or shipping system you use and what you'd like to get out of it. We'll tell you what is ready today and what it takes.