Freight platform loads in one intake queue
Transporeon loads land as draft orders beside your email orders. A planner answers each one from the order, and every decision is logged.
We set up your 30-day trial after a short call. No card.
A load from Transporeon arrives in Druma as a draft order in Orders, Intake, with a badge naming the platform, next to the forwarded emails and scanned PDFs. The planner checks it and plans it from the same list as every other order.
The connector is built to Transporeon's published Carrier Interface and tested on recorded examples. Its first live account waits on the customer's technical API user. Everything below describes what it is built to do, not something a haulier has run in production.
A Transporeon load, as the connector handles it
On Friday evening a shipper posts a load on Transporeon: Timișoara to Munich, 33 pallets, loading Wednesday, an answer wanted by 14:00 on Monday. It lands in Orders, Intake as a draft. The shipper is matched to your client by its Transporeon account or an exact VAT number, never by name. With no exact match, the draft waits for a planner to link the client. If Transporeon sends the same load twice, there is still one order.
On Monday morning the planner filters the intake list to loads waiting for an answer. The Munich load is there with 14:00 beside it. The planner opens it and accepts. Druma never accepts a platform load on its own: automatic acceptance is switched off and cannot be turned on yet.
The other answers sit in the same place: ask for a change, withdraw that request, place or withdraw an offer. Druma sends each one to Transporeon, so nobody has to log in to the platform and click the same button there.
On Tuesday the shipper moves the unloading to Friday. What Druma does depends on where the order stands. On a draft, the change is applied and noted in the history. On an order you confirmed, it waits for a planner, who applies or rejects it. On a closed order nothing is written, and the key user, who corrects closed orders, gets a task instead.
During the trip Druma sends the platform the status events and any change to the planned time. The proof of delivery goes back only after a planner has approved it.
Saying no
Refuse is one action with a reason. It cancels the order in Druma and sends the decline to the platform; on Transporeon the reason goes with it as a code plus a comment. The cancellation happens at once. If the decline cannot reach the platform, for example because the Transporeon connection is switched off or has no credentials, the screen says the shipper was not told, and someone has to tell them another way.
Once the load is planned, or the shipper already has your acceptance, Refuse is no longer offered. Pulling out then is a cancellation under the platform's own rules, and the order says so.
The order's timeline records how the order arrived and every decision taken on it, with the person or system behind each entry.
Questions we get asked
Does accepting a load confirm the order in Druma?
No. Confirming the Druma order is a separate step. Whether it happens without a planner depends on a company setting and an exact client match, the same rule as for email orders.
Can we refuse an email order the same way?
Yes. The same Refuse action works on an order that came in by email, and the planner can tick a short reply to the sender.
What about sennder?
sennder sends no loads into Druma. It is connected for self-billing only: you register the credit note sennder issues on your behalf.
What about TIMOCOM and Trans.eu?
Both are freight exchanges, and both are still waiting for access, so neither sends loads into Druma today. The TIMOCOM connector is built and has only run against a mock. TIMOCOM will need your own contract, and Trans.eu will work from each planner's own login. The integrations page shows the status of each connector.
Our platform is not on the list. Can it be added?
A company administrator requests it in Settings, Integrations. The terms are on the page about integrations built without a development fee.