From off-the-shelf to custom Your trips along Step by step

Replace MendriX with custom software

MendriX is a TMS for groupage and distribution, which transport companies use to manage orders, planning, drivers and invoicing, with a web planner, a driver app and a customer portal. For many transport companies that works well. Sometimes your planning needs something a standard package can't do well, or the transport software has to become part of your own platform. Appfront then builds custom software and carefully migrates your data from MendriX.

What is a custom alternative to MendriX?

Replacing MendriX with a custom solution means building your own transport software that fits exactly how your company plans, executes and invoices, and migrating your data from MendriX into it. MendriX describes itself as a TMS for groupage and distribution, from order to invoice and from planning to driver, with a web planner, a driver app, cross-dock, a customer portal and a BI Gateway to Power BI and Microsoft Fabric. There is a MendriX API with webhooks, and a long list of integrations with accounting packages, carriers such as DHL, DPD, GLS and UPS, on-board computers such as Webfleet and Transics, and PTV for routes. This page is for the situation where that is no longer enough.

This usually happens for one of three reasons. Your work is so specific, for example because of special cargo, fixed agreements with shippers or a combination of transport and storage, that the package only copes with it through workarounds. The transport software needs to be one with your own platform, such as a booking environment you offer to customers. Or the company is growing into multiple branches and ways of working that no longer fit in a single setup. Often an integration with MendriX is enough, and the package stays. Sometimes custom software is the better choice. We weigh that up honestly, together with you, first.

If you opt for a custom solution, we build the new software around your planning and migrate the data: customers, addresses, rates, vehicles, drivers and the history of orders and trips you want to keep. For that migration we use the MendriX API wherever possible, with the access you arrange for it. We then compare the data with the original. The switchover happens in stages: first one customer, branch or type of trip alongside MendriX, then the rest, so there is never a day without planning.

Honest advice

Integrate or replace.

Your data comes along

Migrated and verified.

Your planning

Built around your own way of working.

How we build your custom alternative to MendriX

We start with the question of whether replacing is really necessary. We map out how you use MendriX, which integrations are running, what planners do outside the package and where it falls short. Sometimes the outcome is that an integration via the MendriX API is enough. If custom is the better route, we first build the planning for one customer or type of trip, migrate its data and let it run alongside MendriX. The remaining flows follow, then the integrations with on-board computers, carriers and accounting, and finally phasing out the package.

1
Scheduling mapped out

Processes, integrations, bottlenecks.

2
Integrate or replace

An honest assessment.

3
First flow

Tested alongside MendriX.

4
Migration and maintenance

Full switchover and maintenance.

What a custom alternative to MendriX actually does

The components below come up in almost every move from a TMS package to custom software. Which ones you need depends on how you currently use MendriX.

Orders

From portal, EDI and email.

Planning

According to your own rules.

Driver app

Assignments and sign-offs.

Migrating data

Checked against the original.

Integrations

On-board computer, carrier, accounting.

Reporting

Margin per trip and customer.

Who we build custom software for instead of MendriX

This approach is meant for transport companies whose planning clearly differs from a standard package, or where transport needs to become the heart of a platform of their own. Think of a company that offers storage and assembly alongside groupage, or a carrier that wants to give shippers its own booking portal.

Groupage

Many small shipments.

Distribution

Fixed routes and customers.

Transport and storage

Two worlds in one system.

Growing carriers

Multiple locations.

Technology and integrations

If you want to keep MendriX and connect it to your other systems, see our MendriX integration. For more on a custom TMS in general, read building a TMS, and for planning, building route planning software. On the financial side, we integrate with Exact Online and Twinfield, among others.

MendriX API for the migration Own TMS Driver app On-board computers Carriers EDI Accounting Roles and permissions Reporting Audit log

Why Appfront for your custom software instead of MendriX?

Switching transport software affects every planner, every driver and every customer, every day. A morning without a plan, or rates that were not migrated properly, is noticed by everyone immediately. That is what we build around: first an honest look at whether it is necessary, then switching stream by stream, and checking the data against the original.

Honest

Integrating is often enough.

Careful

Data checked.

Without a gap

Switching stream by stream.

Security and privacy with custom software instead of MendriX

A TMS holds customer data, recipient addresses and driver data such as trips and working hours. During migration, we only carry over the data and history you need in the new software, and anything you are no longer allowed to keep stays behind. The GDPR applies to both the old and the new environment.

The new software runs in a European data centre, with encrypted connections and storage. During the migration, the data is only held in isolated environments, and API access to MendriX is revoked afterwards. We agree with you in advance who can view and change what.

Frequently asked questions about custom software instead of MendriX

Questions transport companies ask before considering replacing MendriX.

For many transport companies it is. MendriX is a TMS for groupage and distribution with many standard integrations, maintained by the supplier. Custom software only makes sense when your work clearly differs or when transport needs to become part of a platform of your own.

Yes. Often that is the better first step. On our MendriX integration page you can read how we connect the package to ERP, web shops and other systems.

Yes. We migrate relations, addresses, rates, vehicles, drivers and the history you want to keep via the MendriX API or an export. After the migration, we compare everything against the original.

No. We start with one customer, branch or type of trip, which runs alongside MendriX for a while. The remaining streams follow, and then the package is phased out.

Yes. We connect the new software to the same on-board computers, carriers and accounting. Which integrations are needed is set out in the inventory at the start.

For transport companies whose work only fits the package through workarounds, or who want to offer transport within a platform of their own. If MendriX works well for you, we advise against replacing it.

Unsure whether to integrate or replace MendriX?

Tell us how you use MendriX now and where it falls short. We will give you honest advice, and show you what a stream-by-stream switch looks like if custom software is the better route.

Edit content