Tank Terminal Management Software: Build vs Buy
Buy. A single product terminal with a handful of tanks, one or two customers and a rack that already works should license Implico OpenTAS, Toptech or Honeywell Enraf, because the custody transfer mathematics in those products is already correct.
On this page
Buy. A single product terminal with a handful of tanks, one or two customers and a rack that already works should license Implico OpenTAS, Toptech or Honeywell Enraf, because the custody transfer mathematics in those products is already correct. Build when you store for third parties across multiple products and your tariff is billed from a spreadsheet every month.
What Implico OpenTAS, Toptech and Honeywell Enraf actually do well
Most terminals should buy, and this is one of the categories where that advice is easiest to give honestly. The packaged products exist because measurement is hard and getting it wrong is expensive.
Implico OpenTAS, Toptech and Honeywell Enraf all handle custody transfer properly. Volume correction to standard conditions using the API Manual of Petroleum Measurement Standards, the choice between gross standard volume, net standard volume and mass in air, sediment and water handling, density from a laboratory certificate or an inline densitometer: it is implemented, it has been argued over by people who do this for a living, and reproducing it to save a licence fee would be a poor use of your money. They also carry rack automation that has been proven at real terminals in real weather, and the integration surface to batch controllers is work either way.
They come with the unglamorous parts too. Bill of lading generation that a driver and a customs officer both accept, meter proving registers, and enough reporting to satisfy a routine audit.
So buy if you run a single product terminal with a handful of tanks and one or two customers, and buy if you are part of a major with a group standard, because fighting a group standard is not a software decision. We say this even when a build has already been approved internally, because the alternative is selling somebody a measurement engine they already own.
Where they stop: the tariff and the tank that is not a bin
It is month end. The inventory clerk is reconciling a 5,000 cubic metre tank holding gasoil for two storage customers. Automatic tank gauging says one figure. Receipts less rack loadings say another, roughly forty cubic metres apart. Somewhere in that gap sit a temperature correction applied at the wrong observed density, a line displacement from a product change nobody journaled, a meter that drifted since its last proving, and a manual dip taken at 03:00 and rounded to the nearest centimetre. The clerk picks a number, books a loss, allocates it pro rata, and one customer will query it.
That query is the business risk, because third party storage is a custody business and every discrepancy is either a claim against you or a gift to a customer.
Two gaps produce most of the pain. First, generic and packaged inventory logic treats a tank as a bin with a quantity. A tank is a resource with a service history, a compatibility rule about the last product stored, a roof type appropriate to vapour pressure, heating coils or none, a customer allocation that changes monthly, an inspection due date, and a connection topology that decides which manifold and pump can move product where. A nomination should fail validation on Thursday because the only compatible tank is being cleaned, not after the vessel is alongside.
Second, the tariff. Storage per cubic metre per month on contracted capacity, throughput per tonne with tiered rates, minimum guaranteed throughput with a shortfall charge, heating by day and temperature band, blending and additisation, nitrogen blanketing, line displacement, vessel and barge handling, demurrage. Each customer's contract varies these, and most terminals compute the invoice in a spreadsheet from an inventory report, which means every ambiguity is resolved in favour of whoever argues fastest.
The arithmetic: per tank and per loading fees against a build
Terminal systems are usually licensed per site with modules priced by tank count and rack lane, plus annual support at a fifth of licence value, plus a separate integration project against your automation. Ask for all four numbers, because the integration line is frequently larger than the licence and it is quoted last.
Run it on your own sites. Suppose you operate two terminals, 46 tanks and eight rack lanes, and the packaged quote is $220,000 of licence with $44,000 a year of support. Add an automation integration project at $180,000 and you are near $620,000 across five years. A first release build at $250,000, plus $50,000 of migration, plus 18 percent a year from month thirteen, lands close to $525,000 over the same five years, and the tariff engine is yours rather than a configuration you maintain forever.
The crossover sits near 40 tanks across two or more sites, or roughly 60,000 rack loadings a year, or eight third party storage customers, whichever you reach first. Below 20 tanks with two customers, buy without argument. Between 20 and 40 tanks the packaged product usually still wins unless your tariff cannot be expressed in it. Above 40 tanks with third party storage and a contested berth, the build starts winning on the tariff alone, because shortfall charges that never get raised and heating days that never get counted are pure margin walking out.
What a custom terminal platform actually costs
Across more than 2,000 delivered projects, Digital Heroes prices liquid bulk terminal work in two bands. A first release covering nominations, tank allocation with compatibility rules, inventory by product and customer, custody transfer calculation and reconciliation runs $120,000 to $250,000 and ships in 16 to 24 weeks. A full platform adding rack automation integration, driver and carrier management, blending, throughput and storage billing, laboratory results and regulatory reporting runs $350,000 to $900,000 phased over 9 to 18 months.
Two lines belong in the budget and rarely appear in a proposal. Data migration runs 10 to 25 percent of build cost, and at a terminal it sits high because historical movements, tank service histories and customer allocations arrive from three systems and a filing cabinet. Year two onward runs 15 to 20 percent of build cost annually, covering support, tariff changes as contracts renew, and the automation work that follows every equipment replacement.
What drives the number up: the number and vintage of automation systems, because integrating a modern setup is not the same job as a twenty year old controller on a serial link. Marine interface, since vessel and barge operations with ship and shore figure reconciliation are a distinct module. Rail loading with its weighbridge and car sequencing. Multiple terminals with diverging product slates. And hazardous area constraints, which turn a driver tablet into a certified device conversation.
What holds it down is one terminal, the truck rack and your top ten customers by throughput in release one.
The four situations where building wins
Measurement and audit fit. Every quantity needs full provenance stored with it: observed volume, temperature, observed density with its source, the correction table applied and the resulting standard volume and mass, all immutable. Add a meter proving register with validity dates so a transaction measured on an out of proof meter is flagged at the time rather than discovered in an audit, and a reconciliation engine that names each component of the gauge to book gap instead of showing one unexplained loss line. That is what you produce when a customer disputes forty cubic metres.
Scale economics. Past roughly 40 tanks across two sites, or 60,000 rack loadings a year, licence plus integration plus support exceeds the five year cost of owning the system.
A workflow that is your competitive advantage. Your tariff is the commercial product. Modelled as versioned rate cards tied to the contract and applied automatically to movement events you already capture, the invoice becomes a report over facts rather than a monthly project, and disputes get answered in minutes with the underlying records attached.
Integration sprawl across three or more systems. Gauging, batch controllers at the rack, the laboratory system, the enterprise resource planning (ERP) package and a spreadsheet holding tariffs. Five boundaries, and the reconciliation between them happens in one analyst's head at month end.
How to decide in a week, using one tank and one month
Pick your most contested tank and last completed month. Then run five short exercises.
Day one: reconcile that tank yourself and write down every component of the gap by name, not as a single loss figure. Day two: take the three largest storage customers and rebuild their invoices from movement records alone, then compare against what you actually billed. Day three: list every tariff term in your contracts that your current system cannot express, and who resolves each one manually. Day four: check whether any transaction in that month was measured on a meter that later failed proving, and decide how you would restate it. Day five: ask your automation vendor in writing what an integration to any new system would cost, and set every number above against the bands in this guide.
If day two finds unbilled shortfall or heating charges, and day three runs past five terms, the conditions are met. If the reconciliation was clean and the invoice matched, keep the packaged product.
When you do cross the line, buy a paid discovery phase before a build. Digital Heroes writes a signed product requirements document covering the tank and quantity model, correction standards, tariff structures, automation interfaces and acceptance criteria before any code exists, and the specification is yours whichever supplier delivers. We build and maintain our own products, including ShopScore, HeroCheckout and Section Vault, so the team has run software past launch rather than only shipping it.
We are the wrong firm if you want a measurement engine rewritten from first principles, or if your automation vendor will not talk to a third party.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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) →
- 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) →
- U.S. retailers lost an average of 1.6% of sales to shrink in FY2022 (up from 1.4% the prior year), equating to $112.1 billion in inventory losses - the benchmark case for POS-integrated loss prevention and inventory accuracy. Source: National Retail Federation (NRF) (2023) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
Frequently asked questions
How much does terminal management software cost to license?
Expect a per site licence with modules priced by tank count and rack lane, annual support at roughly a fifth of licence value, and a separate automation integration project. The integration line is frequently larger than the licence and is usually quoted last. Ask for all four numbers in one document, and ask what a second terminal adds before you sign anything for the first.
How long does a custom terminal system take to build?
Sixteen to 24 weeks for a first release covering nominations, tank allocation, inventory by product and customer, custody transfer calculation and reconciliation. Rack automation, driver and carrier management, blending, billing and laboratory results add nine to eighteen months. Automation work sets the pace, because equipment on a hazardous area site cannot be tested on the same schedule as a web application.
Who owns the code and the movement data if we commission a build?
You should hold the repository, the infrastructure accounts and the right to bring in any other supplier, settled before kickoff. At Digital Heroes the client owns the code from the first commit. On a system that computes the quantities you invoice on and the figures a customer may dispute years later, owning both the logic and the records is part of the commercial position rather than a nicety.
What happens if a meter fails proving after transactions have been billed?
This is a design decision, not an afterthought, and it should be settled in discovery. The system needs a proving register with validity dates, the ability to identify every transaction measured on that meter inside the affected window, and a defined process for restating or crediting. Terminals that discover this question during an audit end up negotiating with customers from a weak position.
Can we build only the tariff and billing layer?
Yes, and for terminals whose measurement is already handled well it is the highest return starting point. The billing layer reads movement events from your existing system, applies versioned rate cards tied to each contract, and produces the invoice as a report over facts. It typically pays for itself on shortfall charges and heating days that currently go unbilled because nobody counted them.
Should a single customer terminal build anything?
No. One product, a few tanks, one or two customers and a working rack is exactly the case the packaged products were designed for, and your custody transfer exposure does not justify a platform. Put the money into meter proving discipline and into a written reconciliation procedure with named components, which is where most single customer terminals actually lose money.
What is the difference between terminal automation and terminal management software?
Automation drives the physical layer: gauging, batch controllers, preset authorisation at the rack, valves and pumps. Management software holds the commercial layer: nominations, allocations, inventory by customer, tariffs and invoices. The gap between them is where the reconciliation lives, and terminals that automate halfway, with a human keying presets in the middle, generate errors that surface at month end.
Can the loading rack keep working if the software goes down?
It has to, and any developer who has not thought about it has not worked on a terminal. The rack needs a genuine offline mode where trucks continue to load against locally held authorisations, with reconciliation once connectivity returns. A design that assumes the network is available at 02:00 will produce either stopped trucks or manual keying, and both cost more than the outage itself.
What happens to our automation integration if we change software vendors?
It is usually the most expensive thing to redo, which is a reason to own the integration layer rather than rent it. Ask any prospective supplier which vendors and protocols they have actually worked with by name, and insist the interface code sits in your repository. Terminals get locked in through automation interfaces far more often than through the application itself.
Is it worth building if we operate two small terminals?
It depends on tariffs rather than size. Two small terminals with straightforward throughput and storage charges are well served by a packaged product. Two small terminals with minimum guaranteed throughput, blending arrangements, a joint venture ownership split and contested berth demurrage frequently are not, because those terms end up as manual adjustments and manual adjustments are where margin quietly leaves.
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.
How do I vet a software agency for an inventory project specifically?
Ask three technical questions before discussing price: how they stop two simultaneous orders claiming the same last unit, whether stock is stored as an append-only movement ledger or a single overwritable quantity field, and how they test channel sync under load before launch. A team that answers fluently has built inventory systems before; one that steers the conversation to screens and design has not. Then ask for a reference from a client whose system has survived at least one peak season.
How do I work out whether custom inventory software will pay for itself?
Add three numbers: the subscriptions and per-user fees the system replaces, the hours your team spends on manual counts and reconciliation, and the cost of oversells and dead stock caused by bad counts. Most systems Digital Heroes has delivered reach payback in 18 to 36 months, faster when they replace a subscription stack above $500 per month. If all three numbers are small, custom is premature and an off-the-shelf tool is the honest recommendation.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
Is building custom cheaper than paying for Cin7 over time?
Usually yes once you pass the three-year mark. Cin7 Omni plans start around $999 per month on its published pricing, roughly $36,000 over three years before add-ons, which overlaps the cost of a full custom build you then own outright with no per-user fees. If you are on a lower Cin7 tier and your subscription runs below roughly $500 per month, staying put normally makes more financial sense than building.
Should I hire a freelancer or an agency to build my inventory system?
For a simple single-user stock tracker, a strong freelancer works and costs roughly half as much. Once real revenue flows through the system, choose an agency, because inventory software fails in production rather than in the demo, and a solo developer is a single point of failure during your busiest week. The most expensive engagements Digital Heroes takes on are rescues of freelancer builds after an oversell incident.
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.
Who can build a custom inventory management software system?
Digital Heroes builds custom inventory management 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 inventory management 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 Pari.
Senior QA Engineer · Automation · Delhi · 2 posts on the site
Published · Last updated .
