Product

Pollux, the digital twin of the cross-dock hall

Digital loading list, driver app, fill-level view, package search and guided problem workflows: Pollux mirrors the cross-dock hall, everything else stays in the TMS.

The digital twin of the hall: every tour, always the current state.

Pollux is the digital twin of the cross-dock hall, and of nothing else. Tours and shipments come from your system of record. Pollux mirrors what happens to them there: staged, scanned, loaded, or not.

Workplace 1

The digital twin on the screen

Dispatch sees every tour in its loading section on screen, with progress, open packages and reported problems. Every scan in the hall updates the twin the same second.

  • A digital loading list per tour, with state and history
  • Fill-level view while loading is still running
  • Package search: enter a package number, see the last scan
Tours, fill levels and reports on one screen.
Workplace 2

The driver's handheld

The driver sees exactly one tour and the next task in it: scan the package, stage it, load it, add a photo where needed. Deviations are reported where they occur.

  • Work the tour stop by stop
  • Report damage, shortage or lack of space straight from the app
  • Reports continue as a guided case, not as a shout
One tour, the next task, one scan per package.

What Pollux deliberately is not

The narrow scope is why the hall actually uses it.

  • Not a second TMS

    Orders, invoicing and customer data stay in your system of record. Pollux describes the hours between arrival and departure.

  • Not a generic platform

    There is no construction kit and no empty fields for every site to fill in itself. The process sits inside the product.

  • One role in focus

    What earns a place in the interface is what helps a dispatcher during a shift. Everything else stays out.

The pricing model

Three line items, the model needs no more. We name figures in a conversation.

  • Core licence per terminal

    The base scope with loading list, driver app and problem workflows, billed per connected terminal.

  • Add-on modules

    Fill-level view, package search and further building blocks join when a site has a use for them.

  • Paid pilot

    The way in is a three-month pilot at one terminal, with a fixed scope and a fixed end date.

Frequently asked questions

Does Pollux replace our TMS?

No. Orders, invoicing and customer data stay in your system of record. Pollux describes the hours between arrival and departure – the TMS remains the leading system.

How do tours and shipments get into Pollux?

Over standard interfaces from CargoSuite or a comparable TMS. Nothing is maintained twice, and the recorded scan state survives updates coming from the TMS.

What does getting started look like?

With a paid three-month pilot at one terminal: fixed scope, fixed end, criteria agreed up front. Then you decide.

What does Pollux cost?

The model is simple: one core licence per connected terminal, add-on modules as needed. The terms depend on terminals, modules and contract length – which is why this page carries no figure.

Who is Pollux for?

For groupage and cross-dock terminals where only a few hours sit between arrival and departure. The interface is built for dispatch, hall supervisors and drivers.