How to Hire a Liner Shipping Operations Software Development Company
Hire the firm that can describe the cascade when a container is rolled. Allocation, documentation, filings, invoicing and equipment position all change at once, and a developer who has done this draws it in the first meeting rather than describing a status update.
On this page
Hire the firm that can describe the cascade when a container is rolled. Allocation, documentation, filings, invoicing and equipment position all change at once, and a developer who has done this draws it in the first meeting rather than describing a status update. Expect $110,000 to $220,000 for a first release covering one trade lane end to end, and buy discovery before you buy code.
Hiring a liner operations developer is like commissioning someone to redraft your bills of lading while the ships keep sailing. Every artefact they touch is already somewhere else: in a bank's documentary credit file, in a customs authority's inbox, in a terminal operating system on the other side of the world. There is no sandbox for a document that has legal weight, and a mistake does not arrive as a bug report. It arrives as a penalty and a hold at the discharge port.
That is the difficulty in buying here. A liner service is one long chain of legally binding documents that must all describe the same cargo in the same box under the same seal, and each one is produced at a different point in a six port rotation under a different jurisdiction's rules. Software firms who have built freight forwarding tools will tell you they understand shipping. They model a shipment as an independent job. You need a network where the unit of planning is the voyage, the constraint is the vessel, and the deliverable is a filing that arrives correct and on time in a country whose rules changed last quarter.
What a liner operations development company actually does
Booking screens are the small end. The centre of the work is a voyage and service model: service, rotation, vessel, port call with its cut off times, and allocation held per port pair and equipment type against the slots you actually control after vessel sharing arrangements. Every accepted booking checks against that allocation and every rolled box returns capacity to it.
Then equipment as a real ledger rather than a booking field. Containers are a circulating fleet with a position, a condition, a lease basis and a movement history assembled from gate events, depot reports and terminal messages, and empty repositioning cost belongs inside the booking decision. Then documentation as versioned objects: shipping instructions arriving in whatever form the shipper uses, a draft bill of lading corrected and approved and issued, amendment history preserved because a corrected bill is not a replaced record, and release mechanisms held as explicit states. Then the filing engine, dangerous goods handled inline rather than as a flag, rating with effective dated surcharge families, and machine to machine messaging with partners, terminals and depots. Most of that is invisible in a demo.
What it really costs in 2026
| Scope | Cost | Timeline |
|---|---|---|
| First release, one trade lane end to end: voyage and allocation model, booking capture, equipment inventory, bill of lading issuance | $110,000 to $220,000 | 16 to 22 weeks |
| Manifest filing engine, per jurisdiction, including amendments and acknowledgement handling | $30,000 to $70,000 each | 4 to 8 weeks each |
| Full platform: dangerous goods workflow, tariff and surcharge rating, invoicing, demurrage and detention, partner messaging | $320,000 to $700,000 | 10 to 16 months |
| Ongoing rule maintenance and support | 15 to 20 percent of build per year | Retainer |
Two line items disappear from most quotes. The first is terminal and depot integration count. Proposals say one integration; reality is one per terminal, and terminals are not uniform even within a single country. Ask a candidate to price them individually and watch what happens to the number.
The second is acknowledgement handling on filings. Almost every quote covers submission. Almost none covers what comes back. Customs authorities return acknowledgements, rejections and conditional responses that have to be reconciled against the filing that produced them, and the amendment and cancellation flows have their own rules and their own deadlines. The failure mode that costs money is silent: a submission that was accepted with a warning, ignored, and turns into a hold three weeks later at discharge. Build the response side or do not build the filing.
Signals of a strong partner
- They draw the roll cascade immediately. One rolled container changing allocation, documentation, pending filings, invoicing and equipment position, without being prompted.
- They treat a bill of lading as an instrument. Amendment history preserved rather than the record edited, because the history matters more than the current state.
- They propose filing rules as versioned configuration. Effective dated, with a test harness per jurisdiction, so last year's filings remain reproducible as they were made when a query arrives two years later.
- They ask about your slot agreements before your volumes. Allocation against partner slots is where a sailing makes or loses money, and each agreement has its own settlement terms.
- They insist on an exception queue with a named owner. Partner data quality varies enough that silent rejection eventually leaves a container missing from everyone's records.
- They want one lane proven before the second. A single rotation carried all the way through booking, documentation, filing and invoicing teaches the model, and the second lane is materially cheaper.
- They raise dangerous goods early. Declaration data, segregation constraints and approval before the booking is confirmed, carried through to the stowage instruction.
Red flags
- Equipment modelled as an attribute of a booking. That design cannot answer whether a suitable box is available near the shipper on the right day, which is the actual acceptance question.
- Filing rules written in code. Every regulatory adjustment then becomes a release, and reproducing a past filing becomes impossible.
- One line item for terminal integrations. It is never one, and pricing it as one is either inexperience or a deliberate underbid.
- Demurrage and detention described as simple arithmetic. The arithmetic is simple. The event history it depends on is not, and neither are contract specific concessions.
- Vague answers on jurisdiction and code ownership. You are building a system that issues legal documents in several countries. That is not a place for ambiguity about who holds what.
Questions to ask on the first call
- A container rolls to the next sailing. Walk me through everything that changes in your model.
- How do you record an amendment to an issued bill of lading?
- Where do filing rules live, and what happens when a customs authority changes a required field?
- How do you reconcile an acknowledgement or a conditional response back to the filing that produced it?
- How do you model slots controlled under a vessel sharing arrangement, and how is settlement calculated?
- How does empty repositioning cost enter the booking acceptance decision?
- What happens to a partner message that fails validation, and who owns the queue?
- How would you reprice an invoice and explain the surcharge difference line by line?
- Which terminals and depots have you integrated with, individually, and what did each cost?
A simple way to decide
Do not pick a developer from a proposal. Buy a paid discovery phase from your two strongest candidates, four to six weeks each, with one deliverable you can act on: a written specification covering the voyage and allocation model, the documentation lifecycle, one named jurisdiction's filing rules with its amendment flow, the terminal integrations enumerated individually, and a fixed price for the first lane. Compare the two documents. The one that raised a filing rule you had not considered is the one that will not discover it during a live rotation.
That specification is yours, and you should be free to take it to any firm on your list. Digital Heroes delivers product requirements document first for this reason, has completed more than 2,000 projects, and contracts through an India LLP, a US LLC and a UK LTD so intellectual property assigns under your own law. For a system that issues bills of lading and files manifests across several jurisdictions, that is a regulatory consideration rather than a preference. Verify us via D-U-N-S, Clutch and Trustpilot.
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.
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- Independent reporting of Gartner's 2025 survey confirms 59% of finance leaders use AI, up from 37% in 2023, with error and anomaly detection (34%) and accounts payable automation (37%) among the leading use cases. Source: CPA Practice Advisor (reporting Gartner) (2025) →
Frequently asked questions
What is the best single question to ask a liner software vendor?
Ask what happens when a container is rolled to the next sailing. A developer who has built liner operations will immediately describe allocation returning, documentation regenerating, pending filings amending, the invoice repricing and the equipment position changing. A developer who has not will describe a status field being updated. That one question separates teams who have modelled a voyage from teams who have modelled a shipment as an independent job.
How much does custom liner shipping operations software cost?
A first release covering one trade lane end to end, meaning the voyage and allocation model, booking capture, equipment inventory and bill of lading issuance, runs $110,000 to $220,000 over sixteen to twenty two weeks. Each manifest filing jurisdiction adds $30,000 to $70,000. A full platform with dangerous goods workflow, tariff and surcharge rating, demurrage and detention and partner messaging runs $320,000 to $700,000 across ten to sixteen months.
What gets left out of liner software quotes?
Terminal and depot integrations, which proposals price as one line and reality delivers as one per terminal with no uniformity even inside a single country. And acknowledgement handling on filings. Quotes cover submission; authorities return acknowledgements, rejections and conditional responses that must be reconciled against the filing, with their own amendment deadlines. A submission accepted with an ignored warning becomes a hold at discharge three weeks later.
How should filing rules be maintained so they survive regulatory change?
As versioned configuration with effective dates, held as data rather than written in code, with a test harness for each jurisdiction. When a customs authority adjusts a required field you change a rule set rather than shipping a release. Just as important, past filings stay reproducible exactly as they were made, which is what you need when a query about a shipment arrives two years after everyone involved has forgotten it.
Who should own the code for a liner operations platform?
You should hold the repository, the cloud accounts and the unrestricted right to bring in another firm, all agreed in writing before kickoff. This system issues documents carrying legal weight in multiple countries and retains the history of filings made to customs authorities, so continuity of access is a compliance question rather than a commercial preference. Any reluctance from a candidate on this point is a reason to end the process.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
How do we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
Will a custom ERP scale as we grow from 50 to 500 employees?
Yes, if it is designed for that from the start, which mostly means clean database design, permissions that handle new departments, and modules that stay separable. Adding users to software you own costs nothing in licenses, the opposite of the per-seat scaling penalty on NetSuite or Dynamics. What does need budget as you grow is new modules and integrations, so keep a small standing development arrangement rather than restarting a vendor search every two years.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
What does it cost to maintain a custom ERP each year?
Budget 15 to 20 percent of the original build cost per year, so a $150,000 ERP needs roughly $22,000 to $30,000 annually for hosting, security patches, integration upkeep, and small improvements. Across Digital Heroes maintenance contracts, third-party APIs changing is the biggest recurring work item. That total still usually sits well under the license bill for a comparable NetSuite or Dynamics seat count.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
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.
What mistakes kill ERP projects most often?
The three we see most in rescue work at Digital Heroes: recreating the old system's broken process in new software, launching everything at once instead of module by module, and having no single internal owner with authority to decide. A fourth is skipping the parallel run on data migration to save two weeks, which trades a short delay for months of distrust in the numbers. None of these are technical failures, which is why vendor selection should weigh process discipline over demo polish.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 Zoe.
Senior Brand Designer · New-york · 8 posts on the site
Published · Last updated .
