Demurrage and Detention Software: Subscribe to Terminal49, or Build the Obligation Model Yourself?
Annual container volume decides this and the two thresholds are roughly 1,500 and roughly 5,000.
On this page
Annual container volume decides this and the two thresholds are roughly 1,500 and roughly 5,000. Under 1,500 containers a year, buy: a Terminal49 or Vizion subscription with last free day alerting plus one organised person and a disciplined spreadsheet captures most of the available value, and your exposure does not justify an engineering project. Over roughly 5,000 across multiple ports, with several carrier contracts and a dispute rate under half of what you are billed, build. The answer for almost everyone above the line is the same shape: buy the container event data, build the obligation model on top of it.
When is off the shelf genuinely the right call here?
If you move under roughly 1,500 containers a year, buy and stop. 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. Your annual demurrage and detention exposure at that volume almost certainly does not justify an engineering project, and a build would cost more than the charges it prevents.
Container xChange is worth a look if your actual problem is equipment availability rather than free time. Those are different problems that produce the same invoice, and buying the wrong tool for the one you have is how import teams end up with three subscriptions and the same spend.
There is a second, larger buy recommendation that applies whatever your size: buy the container event data regardless of what else you decide. Nobody should be building and maintaining terminal integrations. Every terminal changes its site on its own schedule, coverage is uneven, and a developer who offers to scrape them is proposing a permanent maintenance obligation dressed as a feature. Terminal49 and Vizion already do this and are cheaper than the team you would need to keep it working.
The honest test for whether you need anything more is a single question your accounts payable team can answer today. What did you pay in demurrage and detention over the last twelve months? If nobody can produce that number, get it before you buy or build anything, because it is frequently larger than the logistics team's estimate and it is the only figure that justifies either decision.
When does a custom build actually pay off?
Build when two or more of these hold. 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 underlying reason is that visibility data tells you the state of the box, not the state of your obligation. 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. Whether weekends and holidays count varies. None of that exists in terminal data because none of it is the terminal's business. It sits in PDFs in a procurement folder, so the operational team works off the most common carrier's terms applied to everybody and is wrong exactly where the money is.
The second reason is evidence. The strongest dispute is not an argument, it is a record: you searched for an appointment at 6am, 11am and 4pm on three consecutive days and none was offered, or the empty return was restricted so your driver could not turn the box in. Each of those is a complete defence and each is currently a memory. 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, and you should 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.
How do they compare on the things that matter in this industry?
- Where the clock starts. Free time counts from discharge or from availability depending on the tariff. A subscription reports events. It does not decide which event your counter fires on, and getting that wrong makes every number the system produces defensible only by accident.
- Contract rules with effective dates. Free time terms need to be versioned, so a charge from March is evaluated against March terms rather than today's. A configuration number in a settings page cannot do that, and a dispute filed six weeks late is judged on the old contract.
- Evidence at the time of observation. Storing a screenshot on request is not evidence. The system has to record what it saw when it saw it, automatically, so a dispute filed in March can rely on a terminal state observed in February. Terminal appointment systems allocate slots, they do not keep your case file.
- Attempt versus outcome. Products record what happened. What wins disputes is the log of what you tried and could not do, which nobody sells because it is specific to your drayage relationships.
- Accrual attribution. A monthly invoice tells finance a number. A daily accrual posted with site, supplier, carrier and cause dimensions tells a warehouse manager that today's inability to unload is generating a specific figure across nine containers. That difference changes behaviour without a policy meeting.
- Ownership of the archive. Disputes and audits reach back years. Whoever holds the timestamped observation history holds the asset that wins them, and a vendor holding your evidence is a dependency worth refusing.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience, a focused first release runs $60,000 to $130,000 over 10 to 14 weeks: 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. A full platform adding tariff modelling per carrier and contract, appointment attempt capture, empty return restriction tracking, automated dispute packet generation, daily accrual posting and cause analytics runs $150,000 to $350,000 phased over 6 to 10 months.
A worked shape: an importer moving roughly 9,000 containers a year across four ports with six carrier contracts, subscribing to a visibility provider, lands near $125,000. The two lines pushing it to the top of the band are evidence capture at $24,000 and the six carrier contracts inside a $22,000 rule engine. The same importer running two carriers through one port with no drayage feed in phase one lands closer to $70,000.
The running side has one line that behaves unlike software. Your visibility subscription is priced per container or per shipment by every provider in the market, so it scales with growth in a way licences usually do not. Get it quoted against real annual volume before approving a build. Beyond that, the evidence archive settles around $150 to $500 a month at 9,000 containers, contract rule maintenance has to be somebody's named job or the engine drifts out of agreement with your contracts within two quarters, and support and enhancement runs 12 to 18 per cent of build cost annually.
Unusually for this kind of comparison there is often no renewal to weigh against, because most importers are paying for nothing except the subscription they are keeping. The comparison is your demurrage spend, your dispute rate, and your win rate on the disputes you did file. All three are yours to measure and none require a vendor.
What does the hybrid look like, and when is it the honest answer?
Here the hybrid is not a compromise, it is the only sensible architecture. Buy the visibility, build the obligation model.
The division is clean. Terminal49 or Vizion owns terminal and carrier events, so nobody on your team refreshes eleven websites and no engineer maintains a scraper. Your build owns the container record created at booking, the free time rules per carrier and contract with effective dates, the computed last free day, the evidence log, the dispute packet and the accrual. Those are the parts nobody sells and the parts that recover money.
The failure mode this avoids is the one we see most. Teams spend the budget on container visibility, which is a solved and purchasable problem, then run dry before the obligation model. If a proposal spends more than about a fifth of the money getting terminal events into your system, the scope is upside down and you should say so.
The smallest useful version of the hybrid is smaller than most importers expect. 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. Most importers have never seen a live exposure figure, and in our experience seeing it changes warehouse prioritisation inside a week, before a single dispute is filed.
Keep your transport management or resource planning system authoritative for bookings, costs and invoicing. 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 manage for years.
Which should you choose, by operator size and stage?
Under roughly 1,500 containers a year: buy a visibility subscription, set last free day alerts, and give one person ownership of the spreadsheet.
Roughly 1,500 to 5,000 containers: buy the subscription, then build the exposure screen only. That is the $30,000 to $55,000 opening move. It is cheap, it is fast, and it tells you within a quarter whether your real problem is prevention or disputes, which decides what you build next.
Over 5,000 containers across multiple ports with three or more carrier contracts: build the first release. Free time rules, computed clocks, alerting and the evidence log. Start with your two highest volume ports and three largest carriers, because they usually carry most of the exposure and the rule engine extends to the fourth carrier cheaply.
Importers who dispute under half of what they are billed: build the dispute packet generator early, typically $30,000 to $50,000 once evidence capture exists. Its value is volume rather than persuasion. Teams assembling packets by hand filed a minority of possible disputes because small charges were not worth the effort, and automation removes that filter entirely.
Forwarders and third party logistics providers: build, and treat it as a product rather than an internal tool. Selling prevention as a service changes the requirements around multi client separation, reporting and onboarding, and those need to be in the design from the start rather than retrofitted after your second customer.
Anyone who cannot state their annual demurrage figure: do nothing until you can. Ask accounts payable, not logistics, because the charges are usually coded to freight expense across several accounts and the true number decides everything else on this page.
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 1,471 IT projects the average cost overrun was 27%, but one in six projects was a 'black swan' with an average cost overrun of 200% and a schedule overrun of nearly 70%. Source: Harvard Business Review (Bent Flyvbjerg & Alexander Budzier, University of Oxford) (2011) →
- In a survey of 113 supply chain leaders (conducted late March to mid-April 2022), 67% had implemented digital dashboards for end-to-end visibility, and those companies were about twice as likely as others to avoid supply chain problems during the disruptions of early 2022; 71% expected to revise inventory policies going forward. Source: McKinsey & Company (2022) →
- SHRM's 2025 benchmarking data puts the average cost-per-hire at $5,475 for nonexecutive roles and $35,879 for executive roles - executive hires are on average nearly 7x more expensive than nonexecutive hires. Source: SHRM (Society for Human Resource Management) (2025) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
Frequently asked questions
If we build on Terminal49, how hard is it to switch visibility providers later?
Manageable if the integration is designed as an event adapter rather than baked through the system. Your container record, free time rules, clocks, evidence log and dispute history all live in your own store, and the provider supplies discharge, availability, gate and return events into a normalised shape.
Swapping providers then means rewriting one adapter and backfilling event history, which is weeks rather than a rebuild. Insist on that boundary at design time. A build that scatters provider specific field names through the rules engine is a build that has quietly married a supplier.
What if our visibility provider raises its per container price?
Model it now rather than later, because this line behaves differently from software licensing. Every provider prices per container or per shipment, so the cost grows with your volume automatically and a rate change compounds on top of growth.
Owning the obligation model does not remove the subscription, but it does change the negotiation. Once the valuable part of the system is yours, the event feed is a commodity input with real alternatives, and you can quote a competitor without redesigning your operation.
How long does a demurrage software build take?
Ten to 14 weeks for a first release covering clocks, alerting and evidence capture, and six to ten months for a full platform with tariff modelling and dispute automation.
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. Several importers we have worked with could not produce a complete contract set in under three weeks. Doing that before kickoff costs nothing and routinely saves two to three weeks.
Is a Terminal49 subscription enough on its own?
For a smaller importer, often yes, and you should subscribe to it or to Vizion regardless of what you build. It solves a real problem well by pulling terminal and carrier events into one place.
What it cannot do is tell you the state of your obligation. Knowing a box discharged on Tuesday is not the same as knowing which tariff applies, how many free days that carrier owes you under this contract, whether weekends count, and what your accrued exposure is in dollars right now. That calculation depends on contracts you hold, which is precisely why no vendor can hold it for you.
Should we build our own container tracking rather than subscribe?
No. Terminal and carrier integrations break constantly, coverage varies by terminal, and maintaining scrapers across dozens of them is a permanent cost with no competitive value to you.
Spend the engineering budget on the obligation model, the evidence capture and the dispute engine. That is the division of labour that works, and a proposal that inverts it should be a hard no rather than a negotiation.
We move 3,000 containers a year. Build or buy?
Buy the subscription, then build one screen. Container records, purchased event data, and a live view of every box you own with days remaining and accrued dollars runs $30,000 to $55,000 over six to eight weeks.
At that volume you probably do not yet know whether your money is going on preventable delays or on disputable charges, and the screen answers that within a quarter for a fraction of a full build. Whichever answer it gives, the next phase is cheaper because you are no longer guessing.
Can software prevent demurrage, or only help us dispute it?
Prevention is usually the larger half of the return and it arrives faster. Making accrued exposure visible daily to the people who can act on it, attributed by site, supplier and cause, changes prioritisation without any policy meeting.
The mechanism is unglamorous. A warehouse team that can see today's delay generating a specific dollar figure across nine containers behaves differently from one that reads a cost line six weeks later. Last free day alerting with enough lead time to actually book an appointment is the other half, and neither needs the full platform.
Does this replace our transport management system?
No, and a build that tries will create work rather than remove it. Your transport management or resource planning system stays authoritative for bookings, costs and invoicing. 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 exercise you will be running for years, and it is entirely avoidable by deciding ownership once at design time.
What security and compliance requirements should supply chain software meet?
At minimum: role-based access control, encryption in transit and at rest, audit logs on inventory and order changes, and tested backups, because the system holds supplier pricing and customer purchase history your competitors would love to see. If enterprise customers connect to it, expect security questionnaires and possibly SOC 2 expectations; food, pharma, and aerospace add traceability rules like FDA lot tracking or ITAR data handling. Raise these in the first scoping call, since retrofitting audit trails onto a live system costs far more than designing them in.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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.
What does it cost to maintain custom supply chain software each year?
Budget 15 to 20 percent of the original build cost per year, so roughly $9,000 to $12,000 annually on a $60,000 system, covering hosting management, dependency updates, bug fixes, and small enhancements. Across its maintenance contracts, Digital Heroes sees supply chain systems need more upkeep than typical web apps because carrier APIs, EDI specs, and ERP versions keep changing underneath them. Hosting itself is usually minor, often $100 to $500 per month for a mid-size operation.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
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.
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.
Is custom supply chain software cheaper than SAP over five years?
For small and mid-size operations it usually is, because SAP costs compound through licensing, implementation partners, and per-user fees, while custom costs are front-loaded. SAP Business One's published list price has run roughly $3,200 per professional user as a perpetual license plus annual maintenance near 20 percent, and the S/4HANA proposals Digital Heroes clients share are typically in the hundreds of thousands before any customization. A $60,000 to $100,000 custom build with 15 to 20 percent annual upkeep often costs less by year three for a 10 to 30 user company, and you stop paying per seat as you hire.
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.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
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
Published · Last updated .
