LogicCalc FAQ / Help

Everything LogicCalc does — explained simply.

Use this page as the product manual. Each section tells you what a feature does, where it fits in the workflow, how to use it and a simple real-world example.

34 feature sectionsreal examplesstep-by-step

2-MINUTE QUICK START

Your first useful route

If you remember only one workflow, remember this: route points → fleet → cargo if needed → Calculate → inspect the result.

1 Add two stops Origin and destination.

2 Check Fleet Profile Use the actual vehicle type.

3 Add cargo Needed for LDM/weight/physics.

4 Calculate Build route and downstream data.

5 Inspect before quoting Route, tolls, timing and price.

What is LogicCalc?

A single workspace for planning a European truck trip from route geometry to a customer-ready price.

IN PLAIN ENGLISH

LogicCalc combines truck routing, route costs, country and regional pricing, toll estimates, fuel planning, cargo data, driver-time planning, physics checks and output tools in one calculation.

SIMPLE EXAMPLE You need a quote for Kufstein → Paris. Build the route once; the same final route is then used for distance, countries, tolls, driver time and economics.

GOOD TO KNOW Think of the route as the source of truth. If the route changes, route-dependent results must be recalculated.

Your first calculation

The fastest possible way to understand LogicCalc is to run one simple two-stop route.

IN PLAIN ENGLISH

You only need two valid locations to start. Everything else can stay on the default profile for the first test.

SIMPLE EXAMPLE Origin: Kufstein. Destination: Milan. Calculate. Now inspect distance, route, countries, tolls, transit time and price.

GOOD TO KNOW If a result panel is empty, first check that both route points are valid and that the calculation completed.

Route Builder

This is where the physical stop sequence of the trip is created.

IN PLAIN ENGLISH

Every stop in Route Builder becomes part of the route sequence. The order matters because it changes kilometres, countries, tolls, cargo sequence and driver time.

SIMPLE EXAMPLE Kufstein → Munich → Stuttgart → Paris is a four-point route. LogicCalc routes through all four points in that exact order.

GOOD TO KNOW Do not use a vague city name if you know the real loading address. Precise endpoints produce more useful truck routing.

Stops, multi-stop and stop types

Use multiple stops for real dispatch work instead of forcing everything into origin and destination.

IN PLAIN ENGLISH

A trip can contain several pickup, delivery and intermediate route points. Each point is treated as part of the route rather than as a separate calculation.

SIMPLE EXAMPLE Pickup in Verona, second pickup in Milan, delivery in Lyon and final delivery in Paris. Build four stops instead of four separate routes.

GOOD TO KNOW Changing one stop can change every downstream number, so recalculate after the route sequence changes.

Select a route point from the map

You do not always need to type an address.

IN PLAIN ENGLISH

Map point selection lets you choose a location directly on the map. LogicCalc then resolves the selected point and uses it as the route input.

SIMPLE EXAMPLE A warehouse has a poor postal address but you know its exact gate. Select the gate directly on the map.

GOOD TO KNOW An unsupported map click should not silently replace a previously valid route point.

Plan Date and loading windows

Dates turn a simple route into a dispatch plan.

IN PLAIN ENGLISH

Plan Date / Window Start adds timing context to a stop. Driver-time and appointment-related information becomes more useful when the route has real operational dates.

SIMPLE EXAMPLE Loading Monday 08:00 in Milan, delivery Tuesday 14:00 in Munich. The date context helps you judge whether the trip timing makes sense.

GOOD TO KNOW Use dates for operational planning, not only for prettier output.

Truck routing

LogicCalc does not intentionally route a truck like a passenger car.

IN PLAIN ENGLISH

The route is built with the truck routing engine and fleet restrictions. That is why a valid truck route can look different from Google Maps or a normal car navigator.

SIMPLE EXAMPLE A car route uses a small mountain road, but the truck route goes around it because of weight, access or vehicle restrictions.

GOOD TO KNOW A longer truck route is not automatically a bug. The first thing to check is vehicle restrictions.

Fleet Profile and truck restrictions

The active vehicle profile tells LogicCalc what kind of truck it is planning for.

IN PLAIN ENGLISH

Fleet Profile stores vehicle/trailer characteristics used by routing, physics and operating-cost logic. The selected profile can affect where the truck may drive and how cargo is evaluated.

SIMPLE EXAMPLE A standard Euro-Tent and a Mega trailer should not be treated as the same physical vehicle. Use the profile that matches the actual operation.

GOOD TO KNOW Wrong vehicle data can make a technically neat calculation operationally wrong.

Large map / Focus Mode

Use the large map when route geometry matters more than forms and tables.

IN PLAIN ENGLISH

Focus Mode expands the map, keeps route controls available and gives you more room to inspect the physical corridor.

SIMPLE EXAMPLE A route looks suspicious near the Alps. Expand the map, zoom into the area and inspect the exact corridor before changing anything.

GOOD TO KNOW The large map is for inspection and route work; it is not a separate copy of the trip.

Route Alternatives

Compare realistic alternative corridors without rebuilding the trip from zero.

IN PLAIN ENGLISH

After a route is calculated, Route Alternatives can show other route candidates. The point is to compare physical route options together with their downstream impact.

SIMPLE EXAMPLE The default route is 680 km. An alternative is 705 km but avoids a difficult corridor. Compare both before quoting the customer.

GOOD TO KNOW The selected final route should be the route used by tolls, pricing and economics.

Manual route dragging

Use manual shaping when you want the truck to pass through a specific corridor.

IN PLAIN ENGLISH

You can drag the route line and create shaping points. Dragging changes the draft geometry first; the final calculations are refreshed when you deliberately recalculate.

SIMPLE EXAMPLE You want the trip to pass via a preferred motorway instead of the suggested corridor. Drag the line there, then recalculate once.

GOOD TO KNOW Old route-dependent numbers should not be trusted after manual geometry changes until recalculation finishes.

Reverse, Clear Trip and Reset manual route

Small route actions save time during repetitive dispatch work.

IN PLAIN ENGLISH

Reverse flips the route direction, Clear Trip resets the current job, and Reset manual route removes manual shaping so the normal routed geometry can be rebuilt.

SIMPLE EXAMPLE You quoted Vienna → Warsaw and now need Warsaw → Vienna. Reverse the trip instead of typing every stop again.

GOOD TO KNOW Reverse can change tolls, timing and price, so treat it as a new route calculation.

Stop Order Optimizer

For multi-stop work, LogicCalc can test whether another stop sequence makes more sense.

IN PLAIN ENGLISH

The optimizer evaluates candidate orders for routes with several points and can propose a feasible or better order instead of forcing you to test combinations manually.

SIMPLE EXAMPLE You have five stops around southern Germany. Instead of guessing the shortest order, let the optimizer evaluate the sequence, then verify operational constraints.

GOOD TO KNOW A mathematically better order is not automatically operationally valid when appointments or loading dependencies are fixed.

Avoid Countries

Use this when a transit country should not be part of the planned route.

IN PLAIN ENGLISH

Avoid Countries is a routing option, not a pricing filter. When it changes the route, the final route geometry and all route-dependent values need to follow the new corridor.

SIMPLE EXAMPLE A job should not transit Switzerland. Add Switzerland to Avoid Countries and inspect the replacement truck corridor.

GOOD TO KNOW Do not interpret “avoid” as “remove this country from the bill while keeping the same physical route.”

Unsupported countries and routing warnings

LogicCalc should tell you when a route falls outside supported truck-routing coverage.

IN PLAIN ENGLISH

Unsupported origin, destination, waypoint or transit situations are shown as warnings instead of pretending the route is valid.

SIMPLE EXAMPLE The origin is supported but one waypoint is outside the current truck graph. Fix or remove that waypoint before trusting the calculation.

GOOD TO KNOW A clean-looking line on a map is not enough; coverage must also be valid.

Country €/km tariffs

Country rates are your commercial revenue-pricing layer.

IN PLAIN ENGLISH

You can set a €/km rate for each supported country. LogicCalc applies the rate to the route distance that belongs to that country.

SIMPLE EXAMPLE Germany 1.35 €/km, Austria 1.55 €/km, Italy 1.45 €/km. A route through all three countries uses the relevant rate for each segment.

GOOD TO KNOW Commercial €/km pricing is different from fuel cost and different from tolls.

Regional €/km rates

Use regional overrides when one country is too large to price with one number.

IN PLAIN ENGLISH

For supported countries, regional pricing zones can override the country rate. Empty regional fields fall back to the country default.

SIMPLE EXAMPLE Northern Italy uses 1.35 €/km and a difficult alpine region uses 1.60 €/km. The rest of Italy can keep the country default.

GOOD TO KNOW Use regional rates only when they represent a real commercial rule. Do not create differences just because the feature exists.

Fuel Planning

Fuel Planning estimates when the vehicle may need to refuel along the calculated route.

IN PLAIN ENGLISH

The tool uses the selected Fleet Profile consumption together with tank capacity, departure fuel percentage and reserve percentage to estimate range and refuel points.

SIMPLE EXAMPLE Tank 900 L, departure 70%, reserve 15%, consumption 28 L/100 km. LogicCalc estimates usable range and whether a refuel stop is needed.

GOOD TO KNOW These are planning estimates, not live fuel-station availability.

Tolls and toll breakdown

Tolls are calculated separately from your €/km revenue price.

IN PLAIN ENGLISH

The toll layer estimates tolled route segments and exposes a country/segment breakdown. LogicCalc can also show “Not classified” when toll status is not known with enough confidence.

SIMPLE EXAMPLE A Germany → Austria → Italy route may have different toll treatment in each country. Review the breakdown instead of looking only at one grand total.

GOOD TO KNOW “Not classified” does not mean free and does not mean tolled. It means LogicCalc did not guess.

Economics, internal cost and client price

Economics turns route data into a business calculation.

IN PLAIN ENGLISH

The economics layer can combine route-based pricing with internal operating costs, tolls, surcharges and margin to produce a customer-facing price.

SIMPLE EXAMPLE Commercial route revenue is €1,450, tolls are €180, internal operating cost is €920 and you apply your chosen margin rule. LogicCalc shows the resulting offer logic in one place.

GOOD TO KNOW Do not mix up revenue pricing, internal operating cost and tolls; they answer different questions.

Operating-cost inputs

Use operating-cost inputs when you want more than a simple €/km selling price.

IN PLAIN ENGLISH

LogicCalc can keep separate operating-cost components such as fixed cost per kilometre, fuel, AdBlue, maintenance and tyres.

SIMPLE EXAMPLE Two carriers can quote the same lane differently because their finance, fuel and maintenance costs are different. Enter your numbers, not someone else’s.

GOOD TO KNOW Internal cost is company-specific by design.

Cargo, weight and LDM

Cargo data describes what is physically loaded, not just where the truck drives.

IN PLAIN ENGLISH

Add cargo items, quantities, dimensions/space usage and weight. LogicCalc uses this data for LDM totals, weight totals and physics/balance workflows.

SIMPLE EXAMPLE 10 pallets at 700 kg each and 0.4 LDM each produce 7,000 kg and 4.0 LDM before any other cargo is added.

GOOD TO KNOW A price can look correct while the truck is physically overloaded. Cargo data is what catches that class of problem.

Physics & Balance

Physics checks whether the cargo arrangement makes sense for the selected vehicle.

IN PLAIN ENGLISH

The physics workspace goes beyond total weight. It can visualize cargo placement and evaluate load distribution, centre of gravity and axle-related balance information.

SIMPLE EXAMPLE Two loads can both weigh 18 t, but one can create a poor axle distribution because the heavy items sit too far forward or rearward.

GOOD TO KNOW Total weight alone does not describe load balance.

Driver Time

Driver Time converts kilometres into a practical single-driver planning timeline.

IN PLAIN ENGLISH

The planning model uses route duration together with driving breaks, daily driving/rest and weekly/two-week limits to build a dispatch-oriented view of the trip.

SIMPLE EXAMPLE A route may be only 9 hours of pure driving but still require a break or overnight rest before the driver can legally finish it.

GOOD TO KNOW Use Driver Time as a planning model and still verify special cases, national derogations and exceptional operations when they apply.

CO₂ / ESG estimate

Use the ESG toggle when you want an emissions estimate alongside the transport calculation.

IN PLAIN ENGLISH

LogicCalc estimates route-related CO₂ from route and vehicle/fuel assumptions. It is intended as an operational estimate, not a certified emissions audit.

SIMPLE EXAMPLE Compare two route options: one is shorter but slower, another is longer. The emissions estimate adds another data point to the decision.

GOOD TO KNOW Treat it as an estimate derived from the calculation inputs.

Saved Locations

Save addresses you use repeatedly so dispatchers do not type the same warehouse every day.

IN PLAIN ENGLISH

Saved Locations are account-based reusable route points. They can store a familiar name/alias and appear first in route address suggestions.

SIMPLE EXAMPLE Save “Customer DC — Munich North Gate” once, then select it instead of searching the full address every time.

GOOD TO KNOW Use operational names your team understands, not only company legal names.

Workspace: Recent Work, Quotes and Saved Routes

Workspace is the place to continue work instead of starting from zero every time.

IN PLAIN ENGLISH

The Workspace menu contains recent calculations, quotes, saved routes and saved locations. Recent Work keeps the latest activities visible while saved items can be reused later.

SIMPLE EXAMPLE Yesterday you priced Milan → Paris. Open Recent Work today, resume it, change the delivery window and create a revised quote.

GOOD TO KNOW Saved and recent work are different concepts: recent activity is history; saved items are deliberate reusable records.

AI Autofill

AI Autofill helps turn unstructured order information into route/cargo inputs.

IN PLAIN ENGLISH

You can provide text, an image or a document. AI Autofill extracts usable order details and prepares route points/cargo fields for review.

SIMPLE EXAMPLE Paste: “Pickup tomorrow 08:00, Kufstein; deliver Paris Friday; 12 pallets, 8,200 kg.” AI Autofill prepares the fields so you do not type everything manually.

GOOD TO KNOW AI Autofill changes inputs; it should not replace your review of addresses, dates, cargo and commercial values.

Gemini route advice

After a route exists, AI can provide contextual route advice instead of only filling inputs.

IN PLAIN ENGLISH

Gemini route advice works from a calculated route and produces an additional AI explanation/advice layer for the current trip.

SIMPLE EXAMPLE You already have a final route and want a quick second look at possible operational concerns. Use route advice after, not before, the calculation.

GOOD TO KNOW AI advice is supplementary. The route engine and your operational checks remain the source of truth.

Quote Mode

Turn a finished calculation into a customer-facing offer without rebuilding the data manually.

IN PLAIN ENGLISH

Quote Mode can pull route, customer/reference, cargo, distance, transit time, internal cost, margin and offer price into an editable quotation workflow.

SIMPLE EXAMPLE After calculating Kufstein → Paris, open Quote Mode, keep route, cargo, transit and offer price, hide internal-only details, then export the customer PDF.

GOOD TO KNOW A quote is only as current as the calculation it was built from.

Copy, PDF Export and reports

Use the output tools when the calculation needs to leave LogicCalc.

IN PLAIN ENGLISH

Copy gives you a fast text/shareable result, PDF Export creates a formatted document, and reporting/output views turn the calculation into something usable outside the workspace.

SIMPLE EXAMPLE A dispatcher needs the numbers in chat: use Copy. A customer needs a formal offer: use Quote Mode + PDF.

GOOD TO KNOW Always export after the last route recalculation, not before.

Settings, units, language and display options

Settings controls how LogicCalc presents and persists your working preferences.

IN PLAIN ENGLISH

The settings area includes items such as distance units, language, ESG/CO₂ display and other persistent workspace options.

SIMPLE EXAMPLE A UK customer asks for miles while your internal work is normally kilometres. Change the display unit when needed instead of recalculating the physical route.

GOOD TO KNOW Changing a display unit is different from changing the underlying route.

Parking data

Parking data is a planning layer for finding candidate truck-parking locations.

IN PLAIN ENGLISH

LogicCalc’s parking database is built from sourced datasets. Where a field is not confirmed by the source, the interface should not present it as guaranteed.

SIMPLE EXAMPLE A driver will need a rest near the route. Use the parking data to find candidate truck parking near the corridor, then verify the real-world situation.

GOOD TO KNOW Parking coverage and route integration are being expanded; source-backed data is preferred over invented completeness.

Country Rules and methodology pages

Use the reference pages when you need context behind the calculator.

IN PLAIN ENGLISH

LogicCalc includes supporting pages for country rules, regional pricing zones and toll methodology/sources. They explain assumptions that are too detailed for the main calculator UI.

SIMPLE EXAMPLE You see an unexpected toll classification in Austria. Open the toll methodology/reference material before assuming the calculator is wrong.

GOOD TO KNOW Reference pages explain the model; they do not replace official legal sources.

Why does my route look strange?

A strange route is not automatically a routing bug. Check the physical and configuration reasons first.

Truck restriction The truck profile may be excluded from a road that a car could use.

Destination-only / access road Some roads can be valid only near the actual destination.

Height or weight Vehicle dimensions or weight can force a detour.

Unsupported coverage A route point or transit area may be outside current truck-routing coverage.

Manual shaping An old shaping point may still be forcing the route through a corridor.

Avoid Countries An active avoid rule can create a much longer route than expected.

Current limitations — what not to assume

LogicCalc is designed to show uncertainty instead of inventing a perfect-looking answer.

Unsupported truck-routing coverage can make an endpoint, waypoint or transit scenario invalid.
Toll segments can remain Not classified when LogicCalc cannot determine toll status with enough confidence.
Parking capacity, services or security should only be treated as known when the underlying source actually provides those fields.
Driver-time output is a planning model; special legal cases and national exceptions can require separate verification.
AI Autofill and AI route advice must be reviewed by the user before the result is used operationally.

Ready to try it? Open LogicCalc and build one simple route while keeping this guide in another tab.

Open LogicCalc →