Enterprise DNA

Instead of OptimoRoute

Stop renting OptimoRoute. Own your delivery dispatch system.

We build your version around your delivery rounds, bring your OptimoRoute records across and run it for you. Road routing, driver tools and customer updates are scoped around what your operation needs.

OptimoRoute Pro lists US$44.10 per driver per month with annual billing, or US$49 on monthly billing.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

The bill follows the drivers you plan for

OptimoRoute charges by driver. Pro costs US$529.20 per driver for a year on annual billing. The owned base starts with the dispatch record and paperwork. Your required live services are built into the agreed version.

paid

A fee for each planned driver

Lite lists US$35.10 per driver per month when billed annually. Adding planned drivers grows the subscription.

route

Planning capacity by plan

Lite supports 700 orders at once, Pro 1,000. These are planning limits, not monthly delivery totals.

analytics

Analysis in Pro

Pro includes analytics and weekly planning. Your owned record can answer your own questions across route work, delivery failures and overdue orders.

local_shipping

Driver and tracking services

The vendor supplies a driver app and tracking. Enterprise DNA scopes the driver experience and live connections your version needs.

fact_check

Delivery confirmation

Pro lists proof of delivery and customer feedback. Your base keeps recorded outcomes and evidence references. Photo capture and signatures are custom work.

inventory_2

Custom routing requirements

OptimoRoute quotes its Custom plan privately. Your owned version starts with a clearly agreed dispatch process and the integrations it requires.

Your owned dispatch record

A dispatcher can follow the whole delivery

Before departure

Plan a run with reasons you can inspect

Build a draft sequence from your supplied journey estimates and delivery requirements.

  • check Check load against vehicle capacity
  • check Fit service and return travel inside the shift
  • check Keep delivery windows and planned rest visible
  • check Name orders that did not fit and explain why

After the run

Keep the outcome and its evidence together

Reconcile deliveries with the plan instead of losing the reason behind a failed stop.

  • check Record a delivered or failed outcome
  • check Require an evidence reference
  • check Keep the dispatcher name and change history
  • check Review failures beside overdue customer orders

At the dispatch desk

Make the paperwork match the record

Produce route sheets and read-only weekly reports under your business name.

  • check Print the ordered stops and service times
  • check Include planned travel and rest periods
  • check Show unresolved deliveries in one view
  • check Compare planned driver workload across recorded runs

When rules change

Own the checks around your records

Start with New Zealand work-time threshold checks and extend the process around your operation.

  • check Review recorded work against break thresholds
  • check Flag expired licence and inspection dates
  • check Keep imported information separate until confirmed
  • check Change your fields, evidence rules and reporting with Enterprise DNA

Make it yours

Design your own OptimoRoute replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from OptimoRoute. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your OptimoRoute replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your OptimoRoute data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Delivery Routes for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Delivery Routes for Claude Code

Connected to your own database

Which deliveries and eligibility records need attention?

Lee North

Reason
driver licence expired

Valley Cafe

Reason
overdue delivery

Van Two

Reason
vehicle inspection expired

Westside Bakery

Reason
failed delivery

Ask it anything

Ten questions your dispatch record can answer

Each question is supported by the free base today. These are examples of your own analysis, not a claim that OptimoRoute cannot report them.

chat_bubble Which deliveries have passed their due date?
chat_bubble Which orders still need a route?
chat_bubble Which failed deliveries need a retry decision?
chat_bubble Who has the most planned work across our recorded runs?
chat_bubble Which customers have failed or overdue orders?
chat_bubble Which driver licences or vehicle inspections have expired?
chat_bubble What is the stop order and planned service time?
chat_bubble Which recorded work intervals cross a work-time threshold?
chat_bubble What evidence supports each delivery result?
chat_bubble Who recorded the plan, release or delivery outcome?

Switching

How to switch from OptimoRoute

A move usually involves exporting your dispatch records, checking and mapping them for import, then proving the new workflow alongside OptimoRoute before you switch.

  1. 1

    Export your dispatch records

    In OptimoRoute, export the Raw data worksheet and save it as a UTF-8 CSV. Prepare the dates and durations using the replacement guide. Decide how much history to bring across, and keep the original export and delivery evidence separately. The import preserves original fields and matches stable order identifiers, so keep those identifiers intact.

  2. 2

    Test the import first

    Load the export with the import’s test run before bringing records into your working database. Use a fresh database for real records, not one seeded with demo data. The test run lets you check the import before committing it. If you are unsure how to get the Raw data worksheet from your account, check with OptimoRoute.

  3. 3

    Review and confirm the records

    Check what the test run reports, then correct the export and test again if needed. Confirm each imported order’s address, capacity and delivery window before planning. Imported orders stay blocked from planning until those details are confirmed. Normalize dates and durations as described in the guide, and reconcile changed source records rather than overwriting local work.

  4. 4

    Run both systems side by side

    Keep using OptimoRoute while you test the new dispatch workflow with real operating needs. Check that orders, planned sequences, route sheets, delivery outcomes and the records your dispatcher relies on are handled as expected. Prove a complete delivery run before retiring the current service. Check any needs for road routing, live positions, driver access, photos or customer updates, since these require separate work.

  5. 5

    Switch off OptimoRoute

    Once the new workflow has passed your checks and the team is ready, stop using OptimoRoute for dispatch. Keep the exported records and original delivery evidence according to your own recordkeeping needs. Do not treat the new register as a replacement for live routing or driver services unless those have been scoped and built for your version.

construction

Where the real effort goes

The real work is usually mapping your own fields and dispatch rules, then deciding how much history to bring across. Dates and durations may need preparation, and addresses, capacity and delivery windows need checking before orders can be planned. Photos, signatures and live services need their own migration plan. If Enterprise DNA runs the setup, it does this mapping and preparation with you.

Not ready for a call?

Get your OptimoRoute switch plan by email

We will send you the step-by-step plan for moving your business off OptimoRoute, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and runs your version

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo and inspect the fictional deliveries
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Read the replacement guide, save the Raw data worksheet as CSV and test import optimoroute
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your load units, delivery rules and branded paperwork
  • check Your OptimoRoute records mapped and reconciled
  • check A web front end or different technology choice when you need it
  • check Road routing, driver tools and updates built to the agreed scope
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check We install the system and bring your records across
  • check We run it inside Omni by Enterprise DNA
  • check We maintain the agreed connections, backups and dispatch rules
  • check You have someone to call when delivery operations change
Book a call

Questions

Instead of OptimoRoute, answered

Is this already a complete replacement for OptimoRoute? expand_more

The free base covers the dispatch record, planned sequences, route sheets, outcomes and checks. It uses journey times you supply and does not calculate the shortest road route. Enterprise DNA scopes road routing, live positions, driver access and customer updates in your version. Test those requirements before switching.

Can we bring our existing delivery history across? expand_more

Yes. Export the Raw data worksheet, save it as a spreadsheet text export and prepare dates and durations using the guide. The import preserves every original field and matches stable order identifiers. Confirm addresses, load units and delivery windows before planning. Photos, signatures and live services need their own migration plan.

Will this tell us our drivers are legally compliant? expand_more

It flags work-time thresholds in the recorded intervals and identifies missing history. It is not an approved logbook or a legal clearance. The dispatcher still checks the actual logbook, other work, rest, road access and vehicle requirements. Australian operations need their own rules configured.

What do we pay Enterprise DNA? expand_more

There is one setup fee, then a retainer based on the version and ongoing operation we agree. The base is free and open source. Hosting, coding assistance and any live routing or messaging services have their own costs.

Can the team keep using phones and familiar delivery screens? expand_more

Yes, as part of a custom version. Enterprise DNA builds or connects the driver screens, navigation, photos and customer updates your team needs. Agree those requirements during setup and prove a complete delivery run before retiring the current service.

Build the dispatch system your rounds need

Book 30 minutes with Sam. Bring your OptimoRoute bill, a sample export and one typical delivery run. We will work through the records, driver tools and connections your own version needs.

Book a call Get the free version

Delivery Routes for Claude Code is free and open source, published by Enterprise DNA.

Done paying for OptimoRoute?

Get your version built