Skip to content
crossVault
Contact

HomeServicesERP & Logistics Software

ERP & Logistics Software

Dispatch, delivery and invoicing rarely fit together smoothly. We build them as one workflow rather than three separate systems.

Route planning by your rules

You define the constraints that matter, such as time windows, vehicle types, weight or customer preferences. Dispatchers use these rules in a live system to plan deliveries to more than 4,000 sales outlets.

Data capture by drivers

Deliveries and returns are recorded through EAN or QR scans on iOS and Android. The same process previously ran on portable MS-DOS mini PCs, with USB sticks for data exchange and a receipt printer in the delivery van.

Back-office coordination

Configurable views and reports for route status, driver performance and stock movements.

Invoicing the end customer

Multiple payment methods, from direct debit to bank transfer, plus accounting exports, SEPA direct debits and invoice exchange through EDI. An end-customer portal is available on request.

Integration

Automated data exchange with customer management, inventory and accounting.

The path of one delivery

Something can be left behind at every handover between these stations, and usually nobody notices on the same day.

  1. Dispatch

    Orders, stock and your own rules turn into a sequence. The dispatcher decides what goes out today and what waits.

    Where it breaks: Some of those rules sit in no field of the legacy system and only in the head of whoever has planned the round for years.

  2. Delivery and data capture

    Drivers record deliveries and returns by scanning on iOS or Android. Their confirmation provides the basis for every subsequent step.

    Where it breaks: Mobile coverage is not available everywhere, and whatever is captured meanwhile has to find its way back when the driver is already at the next stop.

  3. Feedback

    The back office can see the status of a delivery round while it is still in progress. Returns and stock movements are recorded alongside it.

    Where it breaks: If the state only arrives in a batch, the company works with figures from the previous day and cannot answer a customer until the van is back in the yard.

  4. Invoicing

    Confirmed deliveries become the basis for invoicing the end customer, including the payment method, invoice delivery and portal access if required.

  5. Accounting

    The accounting entries are transferred to your accounting system; customer records and stock are reconciled by the same transaction.

    Where it breaks: If invoicing and accounting keep separate states, the company argues at month end about which one applies.

It is rarely the application itself that causes these replacements to fail. It is the edge cases: a document printed twice, a direct debit that needed special handling in the old system, a driver without a signal. We ask about these cases before we build.

Understand your situation. Agree the next steps together.

Tell us what works today and what you would like to change. The first conversation is free and without obligation; afterwards, you receive an initial assessment or possible next steps. You incur costs only when you accept a proposal. For a more detailed business and technical assessment, we agree a separate engagement in advance, with a clear scope and limits on time and cost.

Discuss your project