A client portal in your name: tracking, documents, invoices and claims

The client portal is where a shipper follows the loads you carry for them: where the truck is, when it arrives, which documents exist and which invoices are open. It wears your company name and colours. A shipper opens it from a link in your email and confirms the address with a 6-digit code, so nobody at your office hands out passwords.

Client users cost nothing. The portal is part of the subscription, and a shipper can bring as many colleagues as it needs.

One shipment, everything the shipper asks the dispatcher

A shipment shows the status timeline (ordered, dispatched, in transit, delivered), the expected arrival and every loading and unloading place with its time window. When the truck reports its position, the ETA is live and the shipment offers a map page with the truck on it. A delay the driver reports appears there too, before anyone picks up the phone.

Below that come the cargo (weight, pallets, volume), the driver, truck and trailer, a ferry crossing if there is one, and the documents: the CMR or eCMR and the proof of delivery, each with a download button or "not yet available".

What the shipper never sees: your cost of the load, what you pay a subcontractor, internal notes and other customers' shipments.

Documents, invoices and claims

The Documents page lists every file attached to the shipper's loads, filtered by type: CMR, eCMR, POD, delivery note, bill of lading, invoice, CO2 report. Certificates of the trucks and trailers used, such as insurance, appear below when you have attached them.

Invoices come with three totals at the top: outstanding, overdue and due this month. A shipper downloads an invoice instead of asking for a copy.

A claim is filed against an order reference with a type (damage, delay, missing cargo, invoice issue, other) and a description. In Druma the claim lands in the same record your office uses for claims reported by a driver or entered by hand, so each claim has one file.

Quotes, CO2 and site instructions

A shipper requests a quote with origin, destination, dates, weight, volume, trailer type and ADR class, and accepts or declines your price in the portal or from the email.

The CO2 page gives well-to-wheel CO2e per shipment under ISO 14083: from the measured fuel where the truck reports it, otherwise estimated. A shipper exports a CSRD data file or a yearly spreadsheet for its sustainability report.

Handling instructions travel the other way. The shipper attaches site rules for access, loading, unloading and safety as a PDF or image, one file per language, and your drivers see them on every stop at that site in their own language.

The UIT for transports in Romania

For a load that needs an ANAF e-Transport code, the shipper declares the transport with ANAF and types the 16-character UIT on the shipment. The last two characters are check digits, so a mistyped code is refused on the spot. Druma then verifies the code with ANAF through your company's connection and shows the result to your planner. If the truck or trailer changes while the UIT is open, Druma reports the new vehicle to ANAF about two minutes after the change.

Druma never declares a transport. The declaration belongs to the shipper's side; a carrier with only a transport role has no duty to declare (ANAF clarifications, question 31).

Colleagues, consignees and e-mails

A shipper can share one shipment read-only with a consignee or a colleague, who signs in with an own code and sees status, route, ETA and delivery documents, without prices. Only the shipper's main portal contact can open the whole account, prices and invoices included, to another person, and that access ends after 90 days unless renewed.

Each contact picks the e-mails they want, from order confirmations to delay alerts and proof of delivery. Invoices, payment reminders and sign-in codes are always sent.

The shipper's own system

A shipper with its own software gets an API workspace in the same portal: integration guides in its language, an OpenAPI file and a Postman collection, test tokens, a message log, a webhook it sets up with test events, and a mapping screen for its own order format (JSON, XML, EDIFACT or CSV). Its developer can be invited to the workspace alone, without seeing shipments, prices or invoices.

Nothing goes live without you. The shipper asks to go live once a checklist passes, and your office approves with one click. As of November 2026 the workspace is built and tested on Druma's test environment; no shipper runs it in production yet.