Instead of M2X
Waiting on an M2X quote? Own your carrier system.
We build your version around your lanes, your customers' rates and the way your drivers close out a load, bring your M2X jobs across, and run it for you.
M2X publishes no price. Its website offers a demo booking, not a price.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the quote covers
An enterprise platform, priced behind a sales call
M2X sells to shippers, carriers and logistics providers across livestock, dairy, bulk, fuels and containers. A carrier's daily work is narrower: who booked what, which truck took it, who signed, and what to bill. Much of the rest is screens and modules around that record.
No price until you talk to sales
There is no pricing page. You book a demo, describe your fleet, and wait for a number. Comparing it with anything else means doing that dance every time.
Built around the big shipper
Much of the platform serves the shipper: network planning, supplier bookings, site congestion, emissions reporting. A carrier subcontracting into that network pays for a system shaped around someone else's plan.
Optimisation you may not run
Route and fleet optimisation is the headline. A carrier with set rounds and a dispatcher who knows them gets little from it, and it is still part of what the platform is built to sell.
A module for each part of the job
Planning, dispatch, the driver app, dockets, tracking, finance and billing, compliance and integrations are each listed as their own piece of the platform. Each one is more to set up between you and a working day.
Dashboards someone else designed
You see the analytics the vendor chose to build. Which customer keeps booking under the minimum, or which unsigned loads hold up the month's billing, is your question to ask, not a tile on their screen.
Your job history on their servers
Years of jobs, dockets and rates sit in M2X's cloud. Jobs can be exported as a spreadsheet file, but the full working record (who drove it, when it was signed, what it was billed at) has to be pieced back together when you leave.
What you run instead
The carrier's side of the job, owned outright
Loads
Every load priced the minute it is booked
A job checks the customer's own rate card first and your standard tariff second, and writes down which one it used. One question gets you the morning picture.
- check Loads that matched no rate show up loudly, so nothing gets carted free by accident
- check Late against the date the customer needs it, booked but on no run, stuck at the door
- check Ask about one job and get the lane, the truck, the driver, the docket and the invoice together
- check Questions in your own words, not only the reports someone else built
Dockets and money
Unsigned work cannot reach an invoice
The days between a delivery and a bill are where carriers lose cash. Every unsigned load sits on one list with its value, and the invoice run skips it until it is signed.
- check The unsigned list, oldest first, with the driver who owes the paperwork
- check One invoice drafted per customer, a line per load, the fuel levy shown on its own
- check Due dates from each customer's terms, and overdue invoices on the same attention list
- check Delivered in full and on time, per customer, from your own delivery record
Trucks and drivers
Mass, hours, dangerous goods and renewals checked first
The rules a New Zealand carrier works under are checks against your records, and each rule names the regulation it comes from.
- check A run loaded past the truck's rated payload is refused
- check Dangerous goods stay off a run whose driver lacks the endorsement
- check Drivers' days checked against the continuous-driving and daily work time limits
- check COF, registration and road user charges distance tracked per unit, flagged before they lapse
Yours
Your rules, your paperwork, no sales cycle
Nothing to quote, nothing to renew. Your records in a database you own, and changes made by describing them.
- check Add a field, a check or a report by asking for it
- check Invoices, con notes and run sheets printed with your logo and business name
- check Cargo claims tracked and decided inside the legal time windows
- check Open source under the MIT licence: no contract term, no vendor to give notice to
Make it yours
Design your own M2X replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from M2X. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your M2X data across and run it for you.
Switching
How to switch from M2X
A move usually means exporting the records your M2X account allows, mapping them to the new database, checking exceptions, then running both systems briefly before you cut over.
- 1
Export your M2X records
Jobs can come out of M2X as a CSV export. Ask M2X what else your account can export, such as customers and rate cards, and whether you can get the files as CSV or Excel. Choose the history you want to bring across, including the consignment records you need for ongoing work, and keep a copy of each export.
- 2
Map and test the records
Load the exported records into the new database after matching M2X's columns to the fields it expects. The column names and structure differ, so check the mapping before writing anything. Run a test import first, then review its results. If you are handling the move yourself, use that test to catch mapping problems before loading the records for real.
- 3
Review what the import flags
Check every row or field the import flags, and work out whether the cause is a missing value, a different format or a mapping that needs correction. Compare a sample of loaded customers, jobs and rates with their M2X records. Fix the source data or mapping, then test again before relying on the imported information for live work.
- 4
Run both systems briefly
Keep M2X available while you run the new system alongside it for a short period. Use the same incoming work to check that jobs, customer details and rates are represented as expected, and that your team can handle the new process. Note any gaps or rules that need attention, and resolve them before you make the new database the main record.
- 5
Switch off M2X
Once you have checked the imported records and are comfortable with live work in the new system, stop using M2X for your own operations. Keep any exports you need for reference. If a customer or processor uses M2X to send you jobs, confirm that arrangement before closing your access. Their system can stay in place while your own records live in the new database.
Where the real effort goes
The main work is usually mapping your own fields and rules, then deciding how much history to bring across. M2X jobs can be exported as CSV, but what else you can export depends on your account, so check with M2X. If Enterprise DNA runs the move for you, they handle the mapping and import checks as part of it.
Not ready for a call?
Get your M2X switch plan by email
We will send you the step-by-step plan for moving your business off M2X, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your M2X switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to switch
Run the free version, or have Enterprise DNA build and run yours
Open source
Do it yourself
Free
- 1 Clone freight-ops-for-claude-code from GitHub
- 2 Run npm run demo and open the folder in Claude Code
- 3 Type /attention to see what needs doing on the demo data
- 4 Export your jobs from M2X as CSV, ask Claude Code to map the columns, then import with a dry run first
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a monthly retainer
- check We bring your M2X customers, rates and job history across and check the totals against the old system
- check We add what your work needs: a driver app with dockets, signatures and photos, tonnage or per-head rates, the shipper's job feed
- check We connect the invoice run to your accounting system and write the checks for the roads and loads you run
- check It runs inside Omni, our managed Command Centre, alongside the rest of your business
Questions
Instead of M2X, answered
The processor we cart for sends our work through M2X. Can we still use this? expand_more
Yes. The shipper's system can stay theirs while your own records live with you. Jobs that arrive from them can be brought in from an export, and when Enterprise DNA builds your version we can connect to their job feed so loads land in your database without retyping.
M2X optimises our routes. Does this? expand_more
The free version does not plan routes. Runs are built in drop order by whoever knows the round, which is how many carriers with set rounds already work. If optimisation genuinely pays for itself in your operation, the call will say so honestly, and Enterprise DNA can add route planning to your version.
We cart milk, stock or fertiliser, not parcels. Does it fit? expand_more
The free version is built around jobs, runs, weights, rates and signed proof of delivery, which is the spine of most bulk and rural cartage. Per-head, per-litre or per-tonne rates, farm pickups and weighbridge tickets are what Enterprise DNA sets up in your version, in your own words.
Can we bring our M2X history across? expand_more
As far as M2X lets you export it. Jobs can come out as a spreadsheet file; ask M2X what else your account can give you, such as customers and rates. Those columns differ from what the free version expects, so they are mapped first. We do that as part of the move, or you map them yourself and do a test run before anything is written.
How does the cost compare? expand_more
M2X does not publish a price, so we cannot put one next to it here. The free version costs nothing per truck, per driver or per job. Your own version is one setup fee and then a monthly retainer, and on the call we put that beside your M2X quote line by line.
Own the system your trucks run on
Thirty minutes with Sam. Bring your M2X quote or invoice. We look at what you actually use day to day, what the shipper's side does for you, and what your own version would look like. If it fits, we build it and run it. If it does not, the free version is yours to keep.
Freight Ops for Claude Code is free and open source, published by Enterprise DNA.
Done paying for M2X?
Get your version built