Your TMS or ERP
QuoteAPI
BookingAPI
OrderAPI
Validated · 40' HC
Recommended equipment1 × 40' HC
Your customerTold before booking
Shipment fileValidation on record
Equipment chosen by eye
The quote uses whatever equipment someone assumes, with no weight or stowage check.
The problem shows up at loading
If the load does not fit or is too heavy, it is already booked and the customer already has the price.
Checked outside the system
Whoever checks it uses another tool, and the result does not end up in the shipment file.
Your system sends the load
The mode, the lines with dimensions, weight, quantity and stacking, and the equipment: the one you specify, or automatic.
It gets the equipment and the verdict
The proposed equipment, the verdict (validated, validated with warnings or not validated) and each check with its note.
You show it where you already work
In the quote, before the booking is confirmed or in the shipment file: your interface decides how to present it.
Container, truck and air
The same API for all three modes, with the utilisation of each piece of equipment: weight, payload, volume and, for trucks, loading metres.
Load request
Your customer asks for a price in your system with their load: packages, dimensions and weights.
Validation
Your system sends the load to the API and gets back the recommended equipment, the verdict and the warnings.
Booking
You quote and book with the validated equipment; if the load does not fit or has warnings, you tell your customer first.
Loading
If you ask for them, the API returns each package’s position so you can pass it on to whoever loads.
Execution
The verdict stays on the file, next to the booking.
A freight forwarder with its own TMS connects the API to its quoting tool to validate every quote before it goes to the customer.
The load
A quote in a 20'
The sales rep quotes 14 non-stackable 120×100 pallets of electrical supplies in a 20' container.
The result
Not validatedThe API returns «Not validated» and the list of pallets that do not fit. The TMS shows it before the quote goes out.
The decision
A 40' is quoted
The TMS sends the load again with the equipment set to automatic, the API proposes a 40', and the quote goes out with that equipment and the validation stored in the shipment file.
Your customer
The recommended equipment, before booking.
They know which equipment their load travels in and, if there are warnings, they hear about them before confirming.
Your team
Validation without leaving the system.
Sales and operations see the verdict in the quote or the booking, without copying data into another tool.
Your shipment file
A record of every validation.
The verdict, the equipment and the checks are stored with the booking.
Frequently asked questions
Is the API already available?
Yes. Write to us and we will give you access; the full documentation is inside the app.
What do I send and what do I get back?
You send the mode, the load lines and the equipment. You get the overall and per-equipment verdict, the proposed equipment, the checks with their notes, the utilisation of each piece of equipment, the estimated VGM (not a substitute for the official one), chargeable weight for air and the packages that do not fit. On request, also the position of each package.
How many validations are included?
100 a month per company. You can add 1,000 more a month for €79, and for higher volumes we can talk.
Are there connectors for my TMS, or an SDK?
No. Your system calls the API directly with your company's key, following the documentation.
What language are the texts in?
Spanish or English, whichever you request.
Do you store my customers' data?
We do not store files. For each API validation we keep the result for a limited time, so you can look it up.