Descartes Pricing in 2026: What It Actually Costs

Descartes pricing is one of the harder numbers to pin down in logistics software, and not because the company hides it especially well. Descartes Systems Group holds strong review coverage across G2, Capterra, and Gartner Peer Insights, with individual products rated between 4.1 and 4.5 out of 5. The problem is that Descartes does not publish a rate card for its platform, and the third-party sites that fill the gap disagree with each other by a factor of ten. This guide breaks down what is actually published, what is quoted, why the public figures conflict, and how to model your real cost before you take a sales call.

Inside you will find:

• Every Descartes product with a published price, with the source and date attached
• The five cost drivers that make up a Descartes contract
• Why the per-user figures on aggregator sites contradict each other
• The post-signature costs that reviewers report most often
• A five-step framework for modeling total cost before you negotiate
• The questions to get answered in writing before you sign

TL;DR: Descartes Pricing in 2026

Descartes prices as a modular subscription. A base platform fee, per-module fees, committed transaction or declaration volume, and concurrent-user licenses combine into a negotiated contract. Only four products in the portfolio carry published pricing. The platform itself does not.

Every figure above is sourced and dated because pricing pages for this vendor go stale fast. Verify current numbers on the source before you build a business case.

Understanding the Descartes Pricing Model

Descartes prices as a modular subscription rather than a per-seat product. Your contract combines a base platform fee, fees for each module you activate, a committed transaction or declaration volume, and concurrent-user licenses. Professional services are scoped and quoted separately.

That structure is not guesswork. Descartes publishes it on its EU e-Customs pricing page, which is the one corner of the portfolio where the company sets out its cost drivers in plain terms. The same five-part shape appears in how its other products are described commercially, which makes it the most reliable framework available for anyone modeling a contract in another product line.

The Five Cost Drivers

• Base platform fee: A fixed monthly charge for access to the software, before any functional module is switched on. On the EU customs product, this starts at 200 euros per month with an 800 euro plus VAT setup fee.
• Modules: Each functional capability is priced and added separately. On the customs product, individual modules run between 170 and 1,050 euros per month. This is where cost compounds over a multi-year term.
• Committed volume: You commit to a monthly transaction or declaration volume in exchange for a lower unit rate. Overages are allowed rather than capped, so exceeding your commitment costs money instead of stopping operations. Descartes notes that volumes pool across most modules, which is a genuinely well-designed piece of the model.
• Concurrent users: Licensing is based on how many people are logged in at the same time, not how many accounts exist. For shift-based operations, this is meaningfully cheaper than named-user licensing. Additional concurrent users run 66 euros per month on the customs product.
• Professional services: Implementation, integration, data migration, and project management are scoped separately. This line carries the widest variance and the least published guidance.

If you have priced other logistics software subscription models, the structure will look familiar. The broader shift toward SaaS-delivered logistics platforms has made base plus module plus consumption the default commercial shape across the category. What makes Descartes harder to model is that the values behind those five drivers change from product to product, because the products came from different companies.

Why There Is No Single Descartes Price

There is no such thing as a Descartes price. There are dozens, and the reason every published figure contradicts every other one is that each figure describes a different acquired company.

Descartes Is a Roll-up and Says So in Its Own Filings

Descartes reported revenue of $729.0 million in fiscal 2026, up 12 percent from $651.0 million the previous year. Of that, 93 percent came from recurring services, 7 percent from professional services, and under 1 percent from license revenue. In the same filing, the company disclosed eight acquisitions completed since the beginning of fiscal 2025, and described acquisition-related expenses as an ongoing feature of what it calls its consolidation strategy.

That is a company describing itself as a roll-up in regulatory language. Aljex, Pacejet, Finale Inventory, MacroPoint, Roadnet, QuestaWeb, and 3GTMS were all separate businesses with separate pricing models before they carried the Descartes name. In most cases those pricing models came along with them.

The 93 percent recurring services figure matters for a different reason. It tells you the negotiation that determines your cost is the multi-year subscription structure, not the upfront number the aggregator sites are arguing about.

Where the Published Figures Fall Apart

Three examples, all currently live:

• One directory publishes three incompatible rates: ITQlick's Descartes Global Logistics Platform pricing page states a basic license starting at $50 per user per month in one paragraph, then $100 per user per month in another. Its own head-to-head comparison pages repeatedly state $500 per user per month. No source is given for any of the three.
• Another is serving 2020 data: SaaSworthy lists Descartes Aljex at $290 per month across three plans, with a disclaimer that the pricing was pulled from the vendor site in February 2020. It is also an unclaimed profile, meaning Descartes has never verified it. A six-year-old price is presented with the same visual confidence as a current one.
• Prices inside the portfolio span two orders of magnitude: Finale Inventory starts at $99. Pacejet starts at $6,500 per feature, per year. Both are Descartes products. Neither number tells you anything about the other.

This is what happens when a directory template expects one price and the vendor has dozens. It is not dishonesty on anyone's part. It is a structural mismatch between how Descartes sells and how software directories catalog them.

Descartes Pricing by Product

Four Descartes products carry published pricing. Here is what each one actually costs, with the billing model and source attached, because the billing model is what makes these numbers difficult to compare.

Read that table sideways rather than down. A flat-rate product and a per-feature product cannot be compared on headline price, and neither tells you what a platform contract costs. The Aljex figure is the most current published number in the portfolio, listed on Capterra in July 2026. If you are evaluating the TMS layer specifically, or comparing against carrier-side TMS options, note that none of the Descartes transportation products publish a rate at all.

The One Place Descartes Publishes Its Full Structure

The EU e-Customs product is the exception, and it is worth studying even if customs is not what you are buying, because it shows the shape of a Descartes contract.

Two things stand out. Concurrent rather than named-user licensing is genuinely favorable for shift-based operations. And committed volume with overage allowance is a well-built commercial structure, because it gives you predictable monthly cost without a hard operational ceiling.

Descartes Global Logistics Platform Pricing

Descartes does not publish pricing for the Global Logistics Platform. The per-user figures circulating on aggregator sites are unattributed estimates that contradict each other on the same page, and none of them should go into a business case.

What is knowable is the structure. A platform contract will combine the same five drivers as the customs product, applied at a larger scale: a base platform fee, per-module fees for each capability you activate, a committed transaction volume across the network, concurrent-user licenses, and a separately scoped professional services engagement.

The negotiation levers that follow from that structure are more useful than a made-up number:

• Module count at signature: Every module you activate at signature is priced into the base term. Modules added later are priced against a contract you have already signed, which is a weaker position.
• Volume commitment level: Higher commitments buy lower unit rates. Commit to your realistic floor rather than your peak, since overages exist precisely to absorb the difference.
• Concurrent-user count: Count simultaneous logins during your busiest shift, not headcount. The gap between the two is often large enough to matter.
• Services scope definition: This is the line with the widest variance and the least published guidance, which makes it the line most worth pinning down in writing.
• Term length against uplift: Longer terms typically buy lower rates. Get the renewal uplift mechanism written into the original contract terms rather than left to a later conversation.

The Costs Buyers Underestimate

The subscription is the part you negotiate. The costs below are the ones that show up after signature, and they come from what reviewers actually report on G2, Capterra, and Gartner Peer Insights rather than from vendor marketing.

1. Customization Is Quoted Separately and Lands High

This is the most concrete post-sale cost signal in the public record. A G2 reviewer of Descartes Sellercloud describes requesting what they considered basic customizations, being quoted a fee they judged unreasonable, and having a waiver request declined outright while core advertised features were still not working as promised.

The lesson is not that Descartes overcharges for custom work. It is that the boundary between configuration, which is included, and customization, which is billable, gets defined after you sign unless you define it before.

2. Implementation Timelines Run Long on Multi-module Rollouts

Reviewers consistently praise capability depth while questioning timeline realism across multi-product deployments. A G2 reviewer of the Descartes Forwarder Enterprise Suite describes a steep learning curve driven by the sheer number of features and modules available, and notes that training new employees takes considerable time. Cross-platform review synthesis at Technology Evaluation Centers reports the same pattern: strong routing and visibility capability, paired with complexity in initial setup and configuration.

Integration is where most of that time goes. If you are connecting a new platform to an existing ERP, WMS, and carrier network, the integration challenges are well documented across the 3PL and TMS category and they are not unique to this vendor. What is specific to a modular portfolio is that each module you activate is potentially its own integration surface.

Timeline overrun is a cost line, not a scheduling inconvenience. Every additional month is internal admin time, delayed benefit realization, and in many cases parallel running of the system you were meant to retire. If you are replacing a legacy routing system, the migration effort itself belongs in the budget as its own line.

3. Ratings and Pricing Both Fragment by Module

Review synthesis across platforms notes that Descartes product ratings vary significantly across individual modules rather than resolving into a single platform score. Practically, that means a strong vendor-level rating tells you very little about the specific module you are buying, and the research you did on the company does not transfer to the product.

The same is true of price. Research Descartes at the module level, or you are researching a different product.

4. The Structure Does Not Flex Downward

A G2 reviewer of Descartes Transportation Management names pricing as the only real downside, specifically for smaller operations, and separately asks for a tiered subscription structure. That request is itself evidence: the current model is not tiered in a way a buyer can self-serve into.

5. Module Stacking Compounds at Renewal

Year one is knowable. Year three is where modular pricing does its real work. Each module added mid-term is priced against a contract you have already signed, and each renewal applies an uplift to a base that has grown. Two organizations signing identical year-one contracts can be 40 percent apart by year three purely on module-addition pace.

This is the single most under-modeled line in the category, and it is the reason last-mile cost forecasting should always run on a three-year horizon rather than an annual one.

How to Model Total Cost Before You Talk to Sales

You can build a defensible cost model for Descartes without a quote. Work the five drivers in this order, and you will walk into the first call with a number rather than a question.

• Inventory the modules you actually need: List the capabilities your operation cannot run without, then list the ones you would like. Price only the first list. The second list is your year two and year three exposure, and it should be modeled separately, not bundled into year one optimism.
• Set your committed volume and your peak separately: Take your realistic monthly transaction floor, not your annual average and not your peak. Then calculate what your peak months would cost in overages. Committing at your peak is the most common way to overpay on this model.
• Count concurrent users, not headcount: Walk your busiest shift and count how many people are genuinely logged in simultaneously. In shift-based operations, this is frequently half of headcount or less, and it is the number that drives your license line.
• Price integration against the systems you already run: Count your ERP, WMS, carrier connections, and any custom middleware. Every one of those is an integration point that gets scoped as professional services. If you are already investing in supply chain visibility tooling, map the overlap before you pay to integrate two systems that do the same job.
• Add a realistic implementation window and cost it: Take the vendor timeline and extend it based on the consistent reviewer signal that multi-module rollouts run long. Cost the extra months as internal admin time plus parallel running of the system you are replacing. This is how you stop operational cost overrun from arriving as a surprise in month seven.

Run that model on a three-year view. Year one tells you whether you can afford to start. Year three tells you whether you can afford to stay.

Two inputs are worth getting right before you start. Understanding which segments of the journey actually drive your cost tells you which modules are genuinely load-bearing versus nice-to-have. And framing the output as return rather than spend is what gets a logistics software business case through finance, since a three-year cost number on its own reads as a liability.

Descartes Versus Single-Platform Delivery Orchestration

A disclosure before this section: FarEye competes with Descartes, and FarEye does not publish list pricing either. Our contracts are quoted, same as theirs. What follows is an architectural comparison, not a claim that we are more transparent on price.

The difference that matters commercially is not the rate. It is whether you are buying one system or a portfolio of separately acquired ones.

A portfolio assembled through acquisition gives you breadth, and for organizations with heavy cross-border customs exposure alongside transportation needs, that breadth genuinely replaces multiple vendors. The trade is that each product carries its own pricing model, its own configuration surface, and in many cases its own underlying architecture. The cost of that shows up in integration scope, in module-by-module contracting, and in the year three compounding described above.

A single platform prices differently because it contracts differently. There is one commercial relationship rather than several, and capabilities that would be separately licensed modules in a portfolio model are part of the same system.

FarEye's dispatch automation, for example, has delivered a 95 percent reduction in dispatcher hours and 17.5 percent lower cost per delivery for enterprises running it at scale, without those being three separate line items on a contract. Posti, the Finnish postal operator, reached a 97 percent on-time delivery rate on the platform. Hilti runs its field distribution operation on it. That consolidation is the defining characteristic of modern last-mile delivery software relative to portfolio suites assembled over two decades of acquisition.

That does not make one model correct. If your primary problem is customs and trade compliance depth, Descartes has capability that is hard to source elsewhere and the portfolio breadth is the point. If your primary problem is delivery execution across owned fleets and outsourced carriers, a portfolio contract is a lot of commercial complexity to carry for capability you may not use. The build-versus-buy calculation applies to portfolios too: breadth you do not use is still breadth you are paying to integrate.

What to Ask Descartes Before You Negotiate

Get written answers to these before pricing is discussed. Each one closes a gap that otherwise gets defined after signature. If you are running a formal evaluation, fold these into your standard vendor selection criteria rather than treating them as a separate pricing conversation.

• Which specific modules are in this quote, priced individually, and which are bundled?
• What is the committed volume, what is the overage rate, and which modules does the volume pool across?
• Is licensing concurrent or named, and how is concurrency measured and enforced?
• Where exactly is the line between configuration, which is included, and customization, which is billable?
• What is the price to add a module mid-term versus at renewal, and is that rate fixed now?
• What is the renewal uplift mechanism, and is it capped?
• What are the rules on reducing user count, dropping a module, or scaling volume down mid-term?
• What is the implementation scope in writing, and what happens commercially if the timeline extends?
• What data export and API access do you retain, and what does bulk export cost at term end?

Is Descartes Right for Your Situation?

Price alone should not decide this. The structure fits some operations well and others poorly, and the deciding factor is usually breadth of need rather than budget.

Descartes Is a Strong Fit When

• You have significant cross-border customs and trade compliance exposure alongside transportation needs, and the portfolio genuinely replaces three or four vendors.
• You have procurement capacity to run a multi-module negotiation and manage a staged rollout across product lines.
• Your operation is shift-based, which makes concurrent-user licensing meaningfully cheaper than named-user alternatives.
• Your transaction volume is predictable enough to commit to, so you capture the committed-volume discount rather than living in overages.

Look Elsewhere When

• You need one capability done very well rather than nine done adequately.
• You do not have the procurement or IT capacity to run a multi-module contracting process and integrate several separately architected products.
• Your delivery operation is the core problem and customs compliance is not, in which case you are paying for portfolio breadth you will not use.
• You need cost certainty across a three-year horizon and cannot model module-addition pace with confidence.

Frequently Asked Questions