Port Terminal Software: Buy a Terminal Operating System or Build the Layer Above
Buy the terminal operating system and never build one. Navis N4, Tideworks Mainsail and Octopi are good at core inventory and move execution, and replacing that is a multi year project with a poor record.
On this page
Buy the terminal operating system and never build one. Navis N4, Tideworks Mainsail and Octopi are good at core inventory and move execution, and replacing that is a multi year project with a poor record. Build the layer above it instead, and only once gate exceptions, evidenced billing or cross terminal reporting are costing you more than the licence.
What the off the shelf products actually do well
Navis N4 is the reference product in this category for good reason. Yard inventory, stacking rules, vessel planning against a bay plan, work queue generation for cranes and handlers, and a data model that has survived thousands of berth windows. Tideworks Mainsail and Traffic Control carry the same job for a lot of North American terminals and are notably easier to configure. Octopi is a credible answer for smaller and mid sized facilities that would drown in an enterprise deployment, and RBS TOPS has real depth in multipurpose and breakbulk terminals where container products struggle.
Say it plainly. Do not build a terminal operating system. Most terminals that believe they need a custom one actually need a consultant to finish the configuration they abandoned three years ago, and be honest about which you are. The reshuffles you blame on the software are frequently stacking rules nobody has revisited since commissioning.
What you are buying is execution discipline under load. A terminal does not close, so the product has to survive a failover during a vessel operation, keep the gate moving when the network partitions, and reconcile afterwards without losing moves. That behaviour took the vendors twenty years and it is the single hardest thing to reproduce. The appointment products sitting alongside, in the eModal mould, are also fine at what they claim: publishing slots, taking bookings, and enforcing a cap.
Where they stop: the appointment and the yard do not know each other
Here is the workflow nothing generic models. You sell appointment slots by hour and by move type. The yard has no idea what is coming. So at nine in the morning eleven trucks all want imports out of the same block, and your top handler spends the hour digging the same stack instead of working three blocks in parallel, while two in the afternoon sits dead because the slot cap was a static number somebody set two years ago.
Appointment products sell capacity as a flat count per hour. They cannot see stack position, they cannot see equipment availability, and they cannot know that the reefer generator technician is at lunch. The terminal system knows the yard but does not own the appointment. Nobody owns the join, and the join is where the money is.
The second place they stop is evidenced billing. Your tariff has sixty line items and the terminal system is configured for thirty, so storage, reefer plug hours, chassis flips and exam fees are invoiced from a spreadsheet the billing clerk maintains, and the free time clock start is argued by email with the line's agent every month. Reefer hours are the classic. If you are not logging plug and unplug events with a timestamp and an operator identifier, you are billing an estimate and you will lose the dispute.
The third is documents. Delivery orders, dock receipts, verified gross mass declarations and dangerous goods documents arrive as email attachments from forwarders who never onboarded to your electronic data interchange specification, and a clerk retypes container numbers and United Nations dangerous goods numbers. A typo in a hazardous number becomes a regulatory problem, not a data problem.
The fourth is consolidated truth across facilities. Two terminals, possibly one acquired on a different system, and corporate wants throughput, yard utilisation and gate performance across both. Someone builds it in a spreadsheet every Monday and the numbers never quite tie, because one site counts a move differently from the other and nobody ever wrote the definition down. Reporting modules report on their own instance. Business intelligence (BI) tools will happily connect to both databases and produce two charts that disagree.
The arithmetic: licence and volume against a build
Terminal operating systems are licensed per move or per twenty foot equivalent unit handled, sometimes with a per user component and always with annual maintenance on top. Use your own contract. Call it $0.40 per unit handled for illustration, plus $60,000 a year maintenance. A terminal at 150,000 units pays about $120,000 a year. At 400,000 units it pays about $220,000. Add a separate appointment product and an electronic data interchange translator and both numbers rise.
Now the layer above. A focused build runs $60,000 to $130,000 in twelve to sixteen weeks, and a full platform $150,000 to $400,000 phased across six to twelve months, with year two at 15 to 20 percent. Amortise a $280,000 platform over five years including support and you carry roughly $100,000 a year.
The crossover in this category is not against the licence, because you are keeping the licence. It is against the leak. On the illustration above, a terminal handling more than about 150,000 units a year with two or more facilities has enough exception volume that the build repays itself, and below that a single facility with simple stack rules almost never does. State it as transactions: once you are running more than roughly 400 gate transactions a day and generating dozens of exceptions among them, the arithmetic turns.
What a custom build actually costs
A focused first release runs $60,000 to $130,000 and ships in twelve to sixteen weeks. Focused means one capability done properly: the appointment and yard slot engine with a drayage portal, or the document intake pipeline with validation, or the cross terminal event warehouse with executive and customer dashboards. Not all three.
A full platform runs $150,000 to $400,000 phased over six to twelve months, covering gate, yard visibility, equipment telemetry, document intake and billing all reading from one event model with electronic data interchange and customs feeds wired in.
Data migration sits at 10 to 25 percent, and the real work is not moving rows. It is agreeing definitions: what counts as a move, when a free time clock starts, what a reefer plug event is. Those definitions live in one person's head today, and that is the actual migration risk.
Year two runs 15 to 20 percent annually, and for a terminal that must include on call cover, because you cannot take a maintenance window. What drives the number up: how stubborn your terminal system integration is, since a modern instance with licensed interface services is straightforward and a fifteen year old instance read directly from the database is not; the depth of electronic data interchange coverage, because every additional transaction set such as 322, 315, 300 and 304 is real work and every trading partner speaks its own dialect; customs filing paths; gate camera hardware; and round the clock uptime, which changes your architecture from day one.
The four situations where building wins
Regulatory fit. Customs filing, dangerous goods handling under the International Maritime Dangerous Goods code, verified gross mass under the Safety of Life at Sea convention, and identity credential checks at the gate all carry audit trail obligations. A document pipeline that validates a container number against ISO 6346 check digit arithmetic and a dangerous goods number against the code table, then stores the source image cropped to the field, is the difference between answering a regulator in an hour and answering in a week.
Scale economics. Above roughly 150,000 units a year, or across two or more facilities, exception volume alone justifies the layer. Below it, configure what you own.
A workflow that is your competitive advantage. Predictability. Draymen do not choose a terminal on average turn time, they choose on variance, because variance is what breaks their day. A slot engine that reads live stack position and scores each candidate by the work it will actually create is a commercial product you can sell against the terminal two berths over.
Integration sprawl across three or more systems. A terminal system, an appointment product, a translator, a maintenance database and a billing package, reconciled by spreadsheet every Monday. If a spreadsheet or a database built by one person would take down operations should its author resign, you already have the answer.
How to decide in a week
Five days of evidence, then a decision.
- Monday: pull thirty days of gate exceptions and classify them by cause. Amended bookings, failed validations, mismatched container numbers, documents not received. Count the minutes each cost a truck.
- Tuesday: take last month's reefer billing and try to evidence ten charges with a timestamped plug and unplug event and an operator identifier. However many you cannot evidence is your dispute exposure.
- Wednesday: ask your terminal system vendor for your licensed module list and interface services. That list decides how expensive every later phase is.
- Thursday: count the documents your clerks retyped last week and the fields in each one.
- Friday: ask your two largest drayage customers whether they want programmatic booking. If they do and you are saying no, that is a commercial answer rather than a technical one.
If the week argues for a build, buy discovery before code. Two to three weeks at a fixed fee, and you hold a written specification covering the canonical event model, the integration method for each terminal system by version, the tariff rules as configuration, and acceptance criteria stated as exceptions cleared per day. Digital Heroes signs that product requirements document before development starts, and you keep it whether you hire us or hand it to another firm on your shortlist. We are the wrong firm for a single berth terminal that needs its stacking rules revisited, and we would rather say that than sell you a platform.
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.
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- McKinsey estimates that digitizing the supply chain (Supply Chain 4.0) can cut lost sales by up to 75%, reduce inventories by up to 75%, and lower supply chain operational costs by up to 30%, with up to 30% lower transport and warehousing costs. Source: McKinsey & Company (2016) →
- Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
- Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
Frequently asked questions
How much does custom port terminal software cost for a two terminal operator?
A focused first release covering one capability, such as the appointment and yard slot engine or the document intake pipeline, runs $60,000 to $130,000 and ships in twelve to sixteen weeks. A full platform spanning gate, yard, equipment, documents and billing across both facilities runs $150,000 to $400,000 phased over six to twelve months. For two terminals the cross facility event warehouse is usually the cheapest first release.
Should we replace Navis N4 with a custom terminal operating system?
No. Replacing the core is a multi year, multi million dollar project with a poor success rate, and N4 is genuinely good at inventory and move execution. Build the layers above and around it instead: appointment intelligence, document intake, equipment telemetry, cross terminal reporting and the rating engine. That is where off the shelf has nothing to sell you and where the money is actually leaking.
How long does it take to integrate with Navis N4 or Tideworks?
A modern instance with licensed interface and data services typically adds two to four weeks to a project. An older Tideworks or legacy instance where you read the database directly or scrape reports can add six to ten weeks, because you are reverse engineering a schema and building your own change capture. Get your version and licensed module list in front of any developer before accepting a quote.
Who owns the code if a firm builds our terminal software?
You should own the repository, the cloud accounts and the intellectual property outright, from week one rather than at handover. This matters more here than in most categories, because a system touching customs filing paths and dangerous goods declarations holds data a regulator can subpoena. At Digital Heroes the client owns the code from the first commit, and contracts run through entities in India, the United States or the United Kingdom.
What happens if the terminal system goes down during a vessel operation?
Any layer you build has to keep working, which means queued writes, an offline gate mode and a reconciliation path when the core returns. Ask every developer this question directly. The answer you want involves durable queues and replay. The answer you do not want is a promise about uptime, because terminals do not stop and a four hour gap in gate events is an operational incident rather than a technical one.
Can software actually reduce document handling and gate exceptions?
On documents, yes, and the reason is validation rather than extraction. A model pulls the fields, then your own rules check every container number against ISO 6346 check digit arithmetic, against expected inventory, and every dangerous goods number against the code table and the booking. What passes posts straight through, and what fails routes to a clerk with the failing field flagged and the source image attached.
Is it worth building anything if we run a single facility?
Usually not. A single terminal below roughly 150,000 units a year with simple stack rules and a stable customer mix should configure what it already owns properly. Build anyway if you have a person whose job is retyping documents, if reefer or chassis billing is estimated rather than evidenced, or if a spreadsheet would take down operations should its author quit. Those three are worth fixing at any volume.
What is the difference between a terminal system and an appointment product?
A terminal operating system manages yard inventory, stacking and move execution inside your fences. An appointment product sells and enforces gate capacity to the trucking community outside them. Neither owns the join, which is the knowledge that eleven trucks booked into the same hour all want boxes from one block. That join is what a custom slot engine exists to hold.
How do we migrate yard and equipment data off spreadsheets?
Less painfully than you fear, usually two to three weeks inside a larger build, with 10 to 25 percent of the budget covering it. The real work is agreeing definitions rather than moving rows. Book a working session with your yard planner and your billing clerk to write down what counts as a move and when a free time clock starts, because today those rules live in two people's heads.
Can we start with billing rather than the gate?
Yes, and in several terminals it is the fastest payback. A rating engine sitting on a canonical event stream, where every billable event carries its evidence including the gate read, the plug event, the operator and the timestamp, closes disputes in one email instead of three weeks. Recovered reefer hours and chassis handling are almost always the leaking line items, and tariff rules should be configuration rather than code.
How long does it take to build and roll out a custom WMS?
A working first version takes 12 to 16 weeks in Digital Heroes projects, and full rollout with data migration, scanner setup, and floor training lands at 5 to 7 months. Enterprise packages run much longer; clients who come to Digital Heroes after evaluating Manhattan report partner-led implementations of a year or more. The slowest part is rarely the code; it is documenting how receiving and picking actually work today, so start mapping those flows before you sign anything.
What does it cost to maintain a custom WMS after launch?
Budget 15 to 20 percent of the build cost per year, so a $120,000 system runs $18,000 to $24,000 annually for bug fixes, dependency updates, carrier API changes, and small feature requests; that figure comes from Digital Heroes retainers across 2,000+ projects. Hosting for a single-warehouse system adds roughly $200 to $600 per month on AWS or Azure. Weigh that against subscription fees that grow every time you hire another picker.
Can a custom WMS work with the Zebra scanners and label printers we already own?
Almost always yes. Modern Zebra and Honeywell handhelds run Android, so the floor app installs on your existing devices, and label printers speak the standard ZPL language a custom system prints to directly. Digital Heroes also builds camera scanning into the same app so ordinary phones work as backup scanners during peak season, and if you do need extra units, new rugged handhelds typically run $1,200 to $2,000 each.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
Should I hire a freelancer or an agency to build our WMS?
An agency, for anything that will run a live warehouse. A WMS needs backend, scanner app, integration, and QA work happening in parallel, plus someone reachable when receiving stops at 6 a.m., and a solo freelancer is a single point of failure on a system your shipping depends on. Freelancers are the right call for a bolt-on report, a one-off integration script, or maintaining a system that already works.
How do we migrate off spreadsheets or our old WMS without stopping the warehouse?
Run old and new in parallel on one zone or product line, then cut the rest over once a physical count validates the new data. Digital Heroes migrations import SKUs and locations weeks ahead, freeze the old system for a single weekend, and reconcile counts before Monday receiving, so floor disruption is measured in days rather than weeks. The riskiest data is not quantities but location mappings and unit-of-measure conversions, so audit those twice.
Who can build a custom warehouse management software system?
Digital Heroes builds custom warehouse 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 warehouse 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
Published · Last updated .
