How Much Does Demurrage and Detention Software Cost in 2026?
Demurrage and detention management software runs $60,000 to $350,000, and the decision that moves the number most is whether you buy container event data or try to build it.
On this page
Demurrage and detention management software runs $60,000 to $350,000, and the decision that moves the number most is whether you buy container event data or try to build it. Terminal49, Vizion and Container xChange already maintain terminal and carrier feeds, and subscribing to one of them keeps a first release inside the lower band. Teams that decide to scrape terminals themselves add engineering that never finishes, because every terminal changes its site on its own schedule, and in our delivery experience they run out of budget before reaching the contract and tariff model, which is the part that actually recovers money.
The bands a demurrage and detention build falls into
The first release band is $60,000 to $130,000 over 10 to 14 weeks. That covers container records created at booking rather than at arrival notice, event ingestion from a visibility provider, computed free time clocks with last free day alerting, and an evidence log. It is the release that retires the import desk spreadsheet, and it is enough to run an import operation on.
The full platform band is $150,000 to $350,000 phased over 6 to 10 months. That adds tariff and free time modelling per carrier and per contract, appointment attempt capture, empty return restriction tracking, automated dispute packet generation, daily accrual posting to finance, and cause analytics.
There is a narrower opening move for teams whose immediate problem is that they cannot see exposure at all. Container records, purchased event data and one screen showing every box you currently own with days remaining and accrued dollars runs $30,000 to $55,000 over six to eight weeks. In our delivery experience that screen changes behaviour inside a week, because most importers have never seen a live exposure figure and warehouse teams reprioritise the moment they do.
What drives a demurrage build up
Carrier count is first, and the reason is not obvious until you read the contracts. Free time is a term of your service contract, not a property of the port. It varies by carrier, by trade lane, sometimes by commodity, and it gets amended mid year. Every carrier is a rule set with effective dates, and the rules have to be modelled well enough that a charge from last March is evaluated against the terms that applied last March, not against today's.
Port and terminal count is second. Terminals differ enormously in what they expose and how reliably, and the ones that publish almost nothing still have to appear in your alerting. Even when you buy the event feed, coverage per terminal is uneven and the gaps become manual process you have to design around.
Drayage partner integration is third. Each partner is its own conversation, its own system and its own level of technical maturity, and the partners who will only send an email still have to produce evidence you can attach to a container.
Document quality is fourth. If your service contracts and their amendments are scattered across procurement, logistics and legal, assembling the current set is discovery work that happens before any modelling starts. Several importers we have worked with could not produce a complete contract set in under three weeks.
Merged demurrage and detention arrangements are fifth. Separate meters against the same container are straightforward. Arrangements where the two are merged, or run sequentially rather than concurrently, need their own treatment in the accrual model and in the invoice match.
What keeps the number down
Buy the container event data. Terminal49 and Vizion exist and maintaining your own terminal scrapers is a permanent cost with no competitive value. Every dollar you do not spend there goes into the obligation model, which is the half nobody sells.
Start with your two highest volume ports and your three largest carriers. Those usually account for most of your exposure, and the rule engine you build for three carriers extends to the fourth cheaply.
Assemble your service contracts before kickoff. This is free, it is the single most common pacing item on projects in this category, and no developer can do it for you.
Defer accrual posting to finance to phase two. The daily exposure figure on a screen delivers most of the behavioural change. Posting it into your ledger with site, supplier and carrier dimensions is valuable, but it can wait until the numbers have been trusted for a quarter.
Take a structured feed from your largest drayage partner only, and keep the rest on a simple capture form your own team completes. Partner integrations are priced per partner and the long tail rarely pays back.
A worked example that adds up
An importer moving roughly 9,000 containers a year across four ports, with six carrier contracts, subscribing to a visibility provider rather than building terminal integrations.
- Discovery, including assembling free time terms across six carrier contracts and their amendments: $9,000
- Container record model created at booking, with event ingestion from the visibility provider: $18,000
- Free time rule engine per carrier and contract, with effective dates and historic evaluation: $22,000
- Computed last free day, tiered alerting and the live accrued exposure figure: $16,000
- Evidence capture: appointment attempt logging, restriction notices, structured feed from two drayage partners: $24,000
- Dispute packet generation with tariff applied, contract terms, event timeline and contested days: $17,000
- Exposure reporting by site, supplier, carrier and cause: $11,000
- Testing, deployment and import desk training: $8,000
That totals $125,000, near the top of the first release band, and the two line items pushing it there are the evidence capture and the six carrier contracts. The same importer running two carriers through one port, with no drayage feed in phase one, lands closer to $70,000. Adding empty return restriction tracking, daily accrual posting and a year of cause analytics takes the full platform to roughly $210,000 to $280,000 across the following year.
How the spend phases
Discovery is two to three weeks and around 7 percent. It is mostly contract archaeology and a walkthrough of how a container currently reaches somebody's spreadsheet.
The container and event model is roughly 15 percent, weeks two to five. Insist that the record is created at booking or bill of lading issue. A developer who creates it on arrival notice has built you a tracker, and every clock it produces will start late.
The free time rule engine is around 18 percent, weeks four to nine, and it is where domain understanding shows. Rules need versions and effective dates so that a dispute filed today about a charge from March is evaluated correctly.
Clocks, alerting and the exposure figure carry roughly 13 percent. Build the single exposure screen early even when the underlying data is partial, because it is what makes operations adopt the system.
Evidence capture is the largest single block at around 19 percent, weeks seven to twelve. It is unglamorous integration and form work, and it is the part that wins disputes.
Dispute packet generation is around 14 percent and is the fastest commercial return, because more disputes get filed at all once the packet assembles itself.
Reporting, testing and training take the remainder. Train the import desk on live containers, not on sample data.
The ongoing costs nobody quotes
The visibility subscription is your largest recurring line and it is priced per container or per shipment by every provider in the market, so get it quoted against your actual annual volume before you approve a build. It scales with growth in a way software licences usually do not.
Contract rule maintenance is the standing effort. Every amendment, every new trade lane and every carrier change is a rule version, and if nobody owns that job the engine quietly drifts out of agreement with your contracts within two quarters.
The evidence archive only grows. Timestamped terminal observations, appointment attempt logs and document attachments accumulate against a retention need measured in years, because a dispute or an audit can reach back well beyond the current season. In our delivery experience the storage line settles at $150 to $500 a month for an importer at this volume.
Drayage partner onboarding recurs. Each new partner needs its feed mapped, which is a few days rather than a project, but it happens every time procurement changes a lane.
Support and enhancement typically runs 12 to 18 percent of build cost annually, weighted towards enhancement in year one as new carriers and terminals arrive.
Comparing a build against your current renewal
There is usually no renewal to compare against here, because most importers are not paying for anything except the visibility subscription they are keeping. The comparison is your demurrage and detention spend, and three numbers make the case. All three are yours to measure and none require a vendor.
First, total demurrage and detention billed over the last twelve months. Your accounts payable team can produce it, and it is frequently larger than the logistics team's estimate because charges are coded to freight expense across several accounts.
Second, the share of that you formally disputed. Importers who cannot assemble evidence quickly typically dispute a minority of what they are billed, and the untested remainder is the recoverable pool.
Third, your win rate on the disputes you did file. Under the Federal Maritime Commission billing rule that followed the Ocean Shipping Reform Act, invoices must carry defined information and there are windows for issuing charges and raising disputes. Confirm the current detail with your counsel. The practical effect is that a hard dispute window protects everyone except the party whose evidence takes three weeks to assemble.
Compare any realistic improvement on those numbers against the first release band. This is one of the few software categories where the saving is measured in the same units as the cost and shows up within one billing cycle.
When buying beats building
Buy if you move under roughly 1,500 containers a year. A Terminal49 or Vizion subscription with last free day alerting, plus one organised person and a disciplined spreadsheet, will capture most of the available value, and your annual exposure almost certainly does not justify an engineering project. Container xChange is worth a look if your problem is equipment availability rather than free time.
Buy the event data regardless of what else you decide. Nobody should be building and maintaining terminal integrations in 2026, and a developer who offers to is proposing a maintenance obligation dressed as a feature.
Build when two or more of these are true. You move over roughly 5,000 containers a year across multiple ports. Your finance team can quote your demurrage figure and dislikes it. You dispute less than half of what you are billed because assembling evidence takes too long. You carry distinct free time terms across several carriers and nobody can state them from memory. Or you are a forwarder intending to sell prevention as a service, which is a product decision with a different return profile entirely.
The failure mode to avoid is spending the budget on visibility, which is purchasable, and running dry before the obligation model, which is not. If a proposal spends more than a fifth of the money on getting terminal events into your system, the scope is upside down.
If you would rather scope this before committing budget, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Inventory carrying cost commonly runs about 20% to 30% of inventory value, covering capital cost, storage/warehousing, insurance, taxes, handling, shrinkage, and obsolescence - a recurring cost that better inventory and warehouse software aims to reduce. Source: APQC (2023) →
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
- Retailers connecting point-of-sale and loyalty data in an omnichannel strategy reported up to 15% lower cost per purchase and nearly 20% higher incremental store revenue. Source: Deloitte (2024) →
Frequently asked questions
What is the total cost of custom demurrage and detention software?
A first release covering container records created at booking, event ingestion from a visibility provider, computed free time clocks with last free day alerting and an evidence log runs $60,000 to $130,000 over 10 to 14 weeks in our delivery experience. A full platform adding per carrier tariff modelling, appointment attempt capture, automated dispute packets, daily accrual posting and cause analytics runs $150,000 to $350,000 over 6 to 10 months.
Carrier contract count and drayage partner integrations drive most of the range, not container volume.
What does this system cost to run each year?
The visibility subscription is the largest line and is priced per container or per shipment, so quote it against your real annual volume before approving a build. It grows as you grow.
Beyond that, the evidence archive typically settles at $150 to $500 a month for an importer moving around 9,000 containers a year, contract rule maintenance has to be somebody's job, and support and enhancement runs 12 to 18 percent of build cost annually.
How long does it take to build demurrage software?
Ten to 14 weeks for a first release. The pacing item is almost never engineering, it is assembling your own service contracts and their amendments so free time terms can be modelled per carrier with effective dates.
Importers who gather that document set before kickoff routinely finish two to three weeks ahead of ones who start the project and then go looking. It costs nothing to do first.
Is a Terminal49 subscription cheaper than building our own system?
Far cheaper, and you should subscribe to it or to Vizion regardless of what you build. Maintaining terminal and carrier integrations yourself is a permanent engineering cost with no competitive value.
What a visibility subscription cannot do is tell you the state of your obligation, because free time terms live in your service contracts rather than in terminal data. Knowing a box discharged on Tuesday is not the same as knowing which tariff applies, how many free days that carrier owes you and what your accrued exposure is in dollars right now.
Why does each additional carrier add cost?
Because free time is contractual rather than geographic. Each carrier brings its own free day counts, its own treatment of weekends and holidays, its own trade lane variations and its own amendment history, and the engine has to evaluate a March charge against March terms.
The first three carriers carry most of the modelling effort. Once the rule engine handles versioned terms with effective dates, the fourth and fifth cost a fraction of the first.
Can we build just the exposure dashboard first?
Yes, and it is often the sharpest opening move. Container records, purchased event data and one screen showing every box you own with days remaining and accrued dollars runs $30,000 to $55,000 over six to eight weeks.
The effect is behavioural rather than technical. A warehouse team that can see today's delay generating a specific dollar figure across nine containers reprioritises without any policy meeting, and that usually happens within the first week of the screen existing.
How much does the dispute packet generator add?
Typically $30,000 to $50,000 once the evidence capture is already in place, covering the packet assembly with tariff applied, contract terms, event timeline, attempt log and the specific days contested with a reason for each.
Its value is mostly volume rather than persuasion. Teams that had to assemble packets by hand filed a minority of possible disputes because the effort was not worth a small charge, and automation removes that filter.
Does this replace our transport management system?
No, and it should not try. Your transport management or enterprise resource planning system stays authoritative for bookings, costs and invoicing, and the demurrage layer reads from it and writes accruals back with site, supplier and carrier dimensions.
A one directional read integration is usually $10,000 to $20,000. Two systems both claiming to own the container record is a reconciliation problem you will be managing for years.
What is the cheapest credible version of this system?
Around $60,000 for an importer running two carriers through one port, buying event data, with free time rules, last free day alerting, an evidence log and no drayage integration in phase one.
Be sceptical of anything cheaper from a developer who cannot immediately discuss whether the clock starts at discharge or at availability. That distinction is tariff dependent, it decides which event the counter fires on, and getting it wrong makes every number the system produces defensible only by accident.
What tech stack is best for custom supply chain software?
Boring and mainstream wins: a typed backend such as Node with TypeScript, Python, or C#, PostgreSQL for transactional inventory data, a React web frontend, and hosting on AWS, Azure, or GCP. Real-time needs like scanner feeds or live shipment tracking add a message queue such as Redis or RabbitMQ. Be wary of any agency pitching an exotic stack; in Digital Heroes handover work, systems built on niche frameworks are consistently the hardest and most expensive for a new team to take over.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
We are a growing distributor. Should we pick SAP Business One or go custom?
If you need full accounting, purchasing, and inventory in one system today, SAP Business One is the faster path; if your pain is operational workflows the ERP handles badly, custom is usually the better spend. Business One gives you a proven ledger and stock control, but changing its workflows means paying certified consultants, and the customization quotes Digital Heroes clients share commonly run $150 to $250 per hour for changes you never own. A pattern Digital Heroes builds often is Business One or QuickBooks as the financial core with a custom order, warehouse, or logistics layer on top.
Should I hire a freelancer or an agency to build supply chain software?
For anything past a single-user internal tool, use an agency or an established team, because supply chain systems need backend, frontend, integration, and QA skills that rarely live in one freelancer. A solo developer can build a $10,000 inventory tracker; a system that talks to your ERP, carriers, and warehouse scanners fails badly when its only author is unreachable during a shipping cutoff. In the proposals Digital Heroes sees clients compare, agencies cost 20 to 50 percent more but give you continuity, code review, and someone answerable when order data stops flowing.
Who owns the code when an agency builds my supply chain software?
You should own it outright, with full IP assignment on payment written into the contract, and you should walk away from any agency that only licenses the software to you. Insist on the code living in a repository under your own GitHub or GitLab account from day one, not handed over at the end. Digital Heroes contracts assign all custom code, database schemas, and documentation to the client; the only carve-outs should be clearly listed open source libraries.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
Why do companies replace generic SCM software with custom systems?
The usual trigger is workflow mismatch: generic SCM tools model a standard distributor, so anything unusual, like mixed lot and serial tracking, consignment inventory, or customer-specific routing rules, ends up managed in spreadsheets beside the system. Companies also leave when per-user pricing punishes growth or the vendor's API cannot support needed integrations. In Digital Heroes projects, the number of spreadsheets living around the official system is the most reliable signal a team has outgrown its off-the-shelf tool.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
Who can build a custom supply chain software system?
Digital Heroes builds custom supply chain software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other supply chain software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Ryan.
Senior UX Designer · APAC · Sydney · 3 posts on the site
Published · Last updated .
