Free quick analysis

3PL Dynamics TMS

Solutions

Dispatch, Tariffs, and Billing in One System — Live in 3 Months, at a Fixed Price.

Boltrics 3PL Dynamics TMS is the transport suite that runs on Microsoft Business Central and is in operational use at several hundred logistics providers worldwide. dicobis brings Boltrics 3PL Dynamics to Germany — with a preconfigured industry setup that goes live in three months. Order intake, visual route planning, tariff and contract management, driver app, onboard unit connectivity, and carrier settlement run in the same database as finance, HR, and sales. No interfaces between WMS, TMS, and accounting — one single truth.

3 Months to Productive Operations. At a Fixed Price.

Other ERP projects take nine to eighteen months because they start on a greenfield. We don't start on a greenfield. We start with a Business Central environment in which Boltrics 3PL Dynamics is already running — preconfigured for fulfillment, contract logistics, or freight forwarding operations.

You don't watch your setup being designed in a workshop. You see it running in the demo system — day one. What remains is what is truly you: your clients, your tariffs, your carriers, your special processes. We configure those onto the existing standard together with your key users. Custom development is the exception, not the rule — and it is not included in the fixed price.

The price is set in the contract. So is the go-live date. Neither is negotiable once we start running.

Methodology in Detail
  • You start with a running system, not an empty tenant
  • Adopt, don't develop
  • Every role on your side has a counterpart on ours
  • For four to six weeks after go-live, we are on it — not a support ticket system

From Order to Delivery — as a Standard Process

The entire transport process is built into Boltrics 3PL Dynamics and already set up at kick-off. Every step automatically generates the data that dispatch, carrier management, and billing need. What you configure are your tariffs, carrier rules, and client specifics — in the standard, without custom development.

Capture the Order — Route Generated Automatically
Orders come in via EDI, Customer Portal, Excel import, or manually. Boltrics 3PL Dynamics automatically creates the order structure, stops, time windows, and restrictions. Based on client profiles, the system proposes the right route, the right mode (full truckload, partial load, groupage), and the carrier options. Dispatch decides — it doesn't model.
Plan Routes Visually — Margin Live in View
Drag-and-drop on map and Gantt bars: stops are pulled onto routes; driving and rest times, capacity, and time windows are calculated along the way. At every step, the system shows buy tariff, sell tariff, and margin — dispatch sees what the route earns before dispatching. Swapping between routes or subcontractors is one click, not a re-plan.
Choose the Carrier — Tariff, Availability, Performance
The tariff engine knows your purchasing terms per carrier, lane, and volume. For every route, tariff, availability, KPI history (punctuality, damage, complaints), and service level are compared side by side. Booking runs directly from the TMS into the connected carrier platforms Transsmart (nShift), DeliveryMatch, and Sendcloud — or via EDI/API directly to the carrier.
Execute the Route — Status via Driver App or Onboard Unit
The driver receives the route on their smartphone (Business Central mobile app) or onboard unit. Route retrieval, navigation, arrival, loading, departure, and ETA status flow back into the TMS in real time. Onboard units are connected via GPRS — those without use the driver app. Clients see the route in the Customer Portal; dispatch sees deviations before the client calls.
POD Triggers Invoice and Credit Note
POD with signature, damage photo, and driver status closes the route. At the same moment, the client invoice (with tariff, surcharges, VAS items) and the carrier credit note are initiated. Disputes are handled in the system with the POD document and photo evidence, not via email ping-pong. Cash-in moves forward; month-end close runs on operational data.

Stable at Peaks, Transparent on Deviations

A TMS has to keep running when tariffs change, a subcontractor drops out, or a route falls apart. These Boltrics 3PL Dynamics modules are active at go-live — not in phase two, not in the backlog.

Tariffs & Contracts — Tiers, Surcharges, Diesel Clause
Tariffs are configured per client and carrier — tiers by weight, volume, distance, stops, or service level; surcharges for diesel (advance fuel clause), tolls, dangerous goods, or weekends. Special terms, discounts, and contract durations apply automatically to invoices and carrier credit notes. The standard setup already includes typical structures for fulfillment, contract logistics, and freight forwarding — you parameterize to your terms instead of modeling them.
Fleet & Fuel Management — Vehicles, Maintenance, Consumption
Vehicles, trailers, swap bodies, superstructures, and drivers are stored as resources in master data. Maintenance, vehicle inspections, ADR training, and license checks run with advance warnings; fuel card data comes in automatically; consumption KPIs can be analyzed per vehicle and route. Before route planning, dispatch sees which resources are available, which are in service, and which require subcontracting.
Onboard Unit Connectivity — GPRS in Real Time
Telematics providers with onboard units are coupled via GPRS in the standard — route status, position, ETA, stop times, and damage events arrive in the TMS in real time; outgoing route updates go back to the driver. Fleets without onboard units use the Business Central mobile app. Both deliver the same data points — one data foundation, two input channels.
Irregularities — Damage, Extra Mileage, Waiting Time
Damage cases, extra mileage, waiting times, and complaints are recorded by the driver or dispatcher as irregularities — with photo, reason, and affected line. These automatically generate charges or credits toward carrier and client. Service and accounting work on the same transaction; the dispute is documented in the system, not in an Outlook thread.
Customer Portal — ETA, POD, and Reports for Your Clients
In the portal, clients see their own orders, route status, ETA, POD document, KPIs (punctuality, damage rate, service level), and their invoices — in real time, without an email request. Standard reports and custom dashboards are enabled without custom development. Status inquiries, Excel reports, and service calls disappear — your staff resolves exceptions instead of looking up statuses.

One Session,
One Clear Decision

In the assessment session, we look at your dispatch operations, tariff structure, and carrier landscape, and evaluate what part of the dicobis fixed-price setup fits your operations — and where we need to configure. Written evaluation, not a sales presentation.

Book Your Session Now

Numbers That Make the TMS Tangible

Boltrics has been in the market for over fifteen years and is listed as a Notable Vendor with Boltrics 3PL Dynamics in the Gartner Magic Quadrant for WMS Europe. These magnitudes characterize the standard your setup builds on.

  • +

    logistics providers worldwide productive on Boltrics 3PL Dynamics

  • +

    carriers via Transsmart and DeliveryMatch in the standard

  • months to productive operations — at a fixed price

  • database for WMS, TMS, freight forwarding, and finance

Schedule Your Free Assessment Session

In 60 minutes, we look at your dispatch operations, tariffs, and carriers — and evaluate whether the dicobis fixed-price path with Boltrics 3PL Dynamics is right for you.

  • Quick check of your current TMS landscape and dispatch operations
  • Functional comparison with the preconfigured Boltrics 3PL Dynamics standard
  • Evaluation of carrier, onboard unit, and client interfaces
  • Fixed price and go-live date indication after the session
Book Your Session Now

FAQ

How do you get to three months when other Business Central projects need nine to eighteen?
Because we don't start from zero. On kick-off day, you receive a Business Central environment in which Boltrics 3PL Dynamics is already configured — order types, route planning, tariff structure, dispatch, driver app, standard carriers. The workshops clarify what is different in your operations. That is orders of magnitude less work than a classic Business Central project where every table and every document is designed in a workshop. Prerequisite: you accept the standard where it works. Customizing is possible, but not within the fixed price.
What's included in the fixed price — and what isn't?
The fixed price includes the implementation of Boltrics 3PL Dynamics TMS based on the preconfigured standard: workshops, configuration of your tariffs and carriers, template-based data migration, connection to the standard carrier platforms, key-user training, testing, cut-over, and four to six weeks of hypercare. Not included: custom development, individual EDI mappings beyond the standard carrier set, third-party system connections with custom logic, and Microsoft and Boltrics licenses. Licenses run directly through Microsoft and Boltrics respectively. Anything beyond the fixed price is calculated transparently before contracting.
How do you map our tariff structure — tiers, surcharges, special terms?
Through the Boltrics standard module Tariffs & Contracts. Tariffs are configured per client and carrier — with tiers by weight, volume, distance, or number of stops; with surcharges for diesel (advance fuel clause), tolls, dangerous goods, or weekends; and with special terms. The logic applies automatically in the client invoice and carrier credit note. Our preconfiguration setup already includes the typical structures for fulfillment, contract logistics, and freight forwarding — we parameterize to your terms instead of modeling them.
Which carrier and telematics connections are included in the standard?
Boltrics delivers carrier connections in the standard: Transsmart (powered by nShift, over 400 carriers including DHL, UPS, FedEx, DPD, TNT, PostNL, Dachser, Schenker, DSV, Kühne+Nagel), DeliveryMatch (150+ carrier connections, including shipping labels, packing lists, CMR, loading lists), and Sendcloud. Onboard units are coupled via GPRS — route status, position, and ETA arrive in the TMS in real time; outgoing messages go back to the driver. Fleets without onboard units use the driver app on the smartphone. We clarify the concrete connection list for your carrier portfolio in the assessment session.
How exactly does the driver app work?
The driver app is the Business Central mobile app — not a separate point solution, but direct access to the same system that dispatch and billing work in. It supports route retrieval, order details, navigation integration, POD with signature, damage photos, and status updates. Data flows back in real time — dispatch, service, and billing access it immediately. Offline mode for dead zones is included.
Can we use Boltrics 3PL Dynamics TMS without the WMS?
Yes. The TMS is a standalone module of Boltrics 3PL Dynamics and uses the same Business Central foundation as WMS, freight forwarding, and finance & billing. If you only dispatch transport today and don't operate your own warehouse, we build the platform around the TMS core. If warehouse logic becomes relevant later, the WMS module is added without an interface — one data foundation, one master data world.
How does the TMS fit with the WMS and the finance side?
Boltrics 3PL Dynamics is built as a modular platform: WMS, TMS, freight forwarding, and finance & billing share one data foundation on Business Central. Shipments, orders, tariffs, and postings are not “integrated” — they live in the same database. That eliminates the classic WMS-TMS friction — reporting across locations and modes runs without intermediate steps, and the month-end close works directly on operational data.
Do we stay release-capable if we want to customize later?
That is exactly why we insist on standard first. Boltrics delivers regular releases for Boltrics 3PL Dynamics; Microsoft delivers them for Business Central. Whoever stays in the standard adopts these releases without re-testing custom logic. Whoever builds custom takes on the responsibility of maintaining that custom code with every release. During the project phase, we mark which requirements can be solved in the standard and which cannot — and lay out the costs of both paths before any decision is made.