Build vs Buy: Liner Shipping Operations Software for Carriers and NVOCCs
Buy if you are a feeder operator or NVOCC on one or two lanes with simple documentation and few filing jurisdictions. Softship or CargoSmart will run that properly.
On this page
Buy if you are a feeder operator or NVOCC on one or two lanes with simple documentation and few filing jurisdictions. Softship or CargoSmart will run that properly. Build once slot allocation against partner agreements is managed in a planner's spreadsheet, or the same cargo details are keyed into two systems on one rotation.
Where the packaged liner systems are the correct answer
Softship and CargoSmart were built by people who understand the trade, and that matters more in this category than in almost any other. A liner operating system has to know that a booking becomes shipping instructions, which become a bill of lading, which becomes a manifest line filed with a customs authority, which becomes a freight invoice, and that all of them must describe the same cargo in the same container under the same seal. Nobody arrives at that model from a standing start.
If your service structure is conventional, your trade lanes are few and your documentation is straightforward, buying is the sensible choice and your competitive advantage lies in your schedule reliability and your rates rather than in your booking screen. A feeder operator running fixed rotations for a handful of principals, or an NVOCC moving a few hundred containers a month, gets a working operating system without funding a multi year programme.
There is a second buying case that has nothing to do with volume. If your operations team is small and your technical capacity is one person, a packaged system means regulatory updates, message standard changes and security patching arrive as vendor work rather than as recruitment. That constraint decides the question for many carriers regardless of what the cost model says.
The commercial arrangements that force a build
The first is slot allocation against partner agreements. Vessel sharing arrangements and slot swaps carry terms specific to each agreement: how many slots you control per port pair, how usage is counted, how settlement works. That logic is where a carrier makes or loses money on a sailing, and it is precisely the area where packaged configuration runs out. The symptom is unmistakable. The packaged system holds the bookings while a planner keeps the real allocation in a spreadsheet beside it, and at that point the system is no longer running the business.
The second is rating. Contract rates, spot quotes and surcharge families that apply by trade, commodity and equipment type multiply as you grow, and effective dating has to sit on all of them. Most carrier invoice disputes are not fraud. They are surcharge applicability arguments nobody can settle because the rate in force at booking time cannot be reconstructed. If your team corrects surcharges on invoices by hand every month, that is the cost of a model your software cannot express.
The third is filing breadth. Every jurisdiction on a rotation has its own required fields, deadlines relative to departure or arrival, transmission method and amendment flow, and those rules change on the authority's schedule rather than the vendor's. Once you file into several regimes, you want the rules held as configuration with effective dates so a change is data rather than a release, and so last year's filings remain reproducible as they were made.
The fourth is equipment. Containers are a circulating fleet with a position, a condition, a lease status and a repositioning cost, not stock. A booking is acceptable when there is space on the vessel and a suitable box at a depot within trucking distance of the shipper on the right day. Systems that treat equipment as an attribute of a booking cannot answer that, which is why certain bookings are quietly unprofitable.
What both routes cost, lane by lane
Packaged liner systems price on licence plus implementation plus support, and the implementation scales with how far your service structure sits from the vendor's defaults. Ask for a written boundary between configuration and change request before signing, because that line is where the real number lives, and it is drawn differently by every vendor.
A custom first release covering the voyage and allocation model, booking capture, equipment inventory and bill of lading issuance runs roughly $110,000 to $220,000 and ships in 16 to 22 weeks. A full platform adding multi jurisdiction manifest filing, dangerous goods workflow, tariff and surcharge rating with invoicing, demurrage and detention calculation and partner messaging runs $320,000 to $700,000 phased over 10 to 16 months. Maintenance runs 15 to 20 percent of build cost a year, weighted heavily toward filing rules and partner message formats.
Jurisdiction count drives price harder than container volume in either route, because each filing regime is separate analysis with its own test cycle. Partner agreement count comes second, since each slot arrangement has its own settlement terms. Terminal and depot integrations come third and are the least predictable, because they vary by port and are rarely uniform even inside one country.
The costs that appear at the second port
The one worth knowing before you scope anything: a manifest penalty almost never attaches to the cargo. It attaches to timing and to data consistency. A filing made after the deadline, or one where the description, weight or party details differ from the bill of lading, produces a fine and often a hold at discharge, even when everything about the shipment is legitimate. That means the expensive failure mode is a mismatch between two documents your own systems produced, which is a modelling problem rather than an operational one.
The second is amendment history. A corrected bill of lading is not a replaced record. It is a legal instrument whose prior state matters, and any system that handles a correction by editing the row has thrown away the thing a bank or a court will eventually ask for. Retrofitting versioning after go live is far more expensive than specifying it, and packaged systems differ considerably in how seriously they take it.
The third is demurrage and detention, which sounds like arithmetic and is not. Free time depends on the contract, the equipment type, the terminal, local holidays and sometimes on a concession a sales manager granted verbally. The calculation is trivial once the event history is trustworthy, so the actual work is event capture, correction and a dispute path. Budget for the dispute path.
The fourth is dangerous goods, which carriers repeatedly treat as a flag on a booking rather than as a workflow. Declaration data, segregation constraints and approval have to be settled before the booking is confirmed, then carried through to the stowage instruction so the vessel planner sees exactly the facts you accepted. When that chain breaks, loading stops at the quayside, and the cost of an hour of stopped loading is a number your operations director can quote from memory.
The fifth is partner data quality. Bookings, container status, gate events and stowage data arrive as structured messages from carriers, terminals and depots, and their quality varies enormously. Build ingestion with an exception queue and a named owner, because silent rejection is how a carrier discovers at the terminal gate that a container it believed was booked exists in nobody's system.
The duplicate keying test
Spend one rotation watching where data is typed. Pick a single voyage and follow twenty bookings from acceptance through documentation, filing and invoicing. Every time a person keys a cargo description, a weight, a party name or a container number into a second system, write it down with the reason. Then do the same for allocation: note every capacity decision made outside the software.
Duplicate keying is the reliable early symptom, and the count tells you which route you are on. Zero or one instance across twenty bookings means your packaged system is carrying its weight and the answer is to buy or stay. Repeated keying, particularly into a spreadsheet that a planner or an agent maintains, means the model in your software no longer matches the business, and every one of those transcriptions is a future mismatch penalty waiting for the right rotation.
Then ask a second question with a documented answer. Has a filing penalty in the last year traced back to a data mismatch rather than to a person's mistake. If yes, the gap is structural, and no amount of process discipline closes it. If your penalties trace to genuine human error under time pressure, better training and earlier cut offs may be cheaper than any software decision.
A first lane, then a decision
Whichever way you lean, do not scope the whole network. Take one trade lane end to end, with every document and every filing working properly on a single rotation, and treat that as the unit of evaluation. The model learned on the first lane makes the second materially cheaper, and it also exposes whether a packaged product genuinely fits before you have committed the whole business to it.
When you evaluate a developer, ask how a rolled container propagates. When a box misses a sailing, allocation, documentation, filings, invoicing and equipment position all change, and anyone who has built this will draw that cascade immediately while anyone who has not will describe a status update. Then ask how filing rules are maintained, and listen for configuration with effective dates and a test harness per jurisdiction rather than a code release each time an authority adjusts a field.
Settle ownership before kickoff. You should hold the repository, the cloud accounts and the unrestricted right to hire another firm, which for a system that issues bills of lading and files manifests is a continuity question rather than a commercial preference.
Digital Heroes builds operations platforms of this shape, works PRD first so the voyage, allocation and documentation models are agreed in writing before code, and contracts through an India LLP, a US LLC or a UK LTD so IP assignment works in the jurisdiction that holds your licences. The team is 50 plus people across 2,000 plus delivered projects, holds Fiverr Vetted Pro status, and publishes openly including a YouTube channel with 2.5 million subscribers.
When you are ready to turn this into a specification, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
- The 2024 DORA report found AI adoption significantly increases individual productivity, flow, and job satisfaction, but negatively impacts software delivery throughput and stability - a paradox leaders must manage with fundamentals like smaller batch sizes and robust testing. Source: DORA / Google Cloud (2024) →
Frequently asked questions
How much does custom liner shipping operations software cost?
A first release covering the voyage and allocation model, bookings, equipment inventory and bill of lading issuance runs $110,000 to $220,000 over 16 to 22 weeks. A full platform adding manifest filing across jurisdictions, dangerous goods workflow, tariff and surcharge rating, demurrage and detention and partner messaging runs $320,000 to $700,000 across 10 to 16 months. Jurisdiction count drives the price more than container volume does.
Is Softship or CargoSmart enough for a growing container line?
For a conventional operation on a small number of trade lanes, yes, and buying is the sensible route. Pressure appears as slot and vessel sharing arrangements multiply, because allocation against partner slots carries terms specific to each agreement, and as surcharge families grow per trade. Once allocation lives in a planner's spreadsheet beside the system, the system has stopped running the business.
Why do manifest filings generate penalties when the cargo is legitimate?
Because the penalty usually attaches to timing and data consistency rather than to the cargo itself. A filing submitted after the deadline, or one where description, weight or party details differ from the bill of lading, triggers a fine and often a hold at discharge. Generating filings from the same records that produced the bill of lading removes the entire mismatch class of failure.
How long does implementation take, and how should it be sequenced?
Sixteen to twenty two weeks for a first release covering one trade lane end to end, then further phases for additional lanes, jurisdictions and rating. Take a single rotation all the way through booking, documentation, filing and invoicing before starting the second lane, because the second is materially cheaper once the model is proven. Terminal and depot integrations are the least predictable element of any schedule.
Can we migrate historical bookings and documents into a new system?
Yes, though the useful target is narrower than people expect. Move open and recent voyages fully, and archive older records in a searchable form rather than reprocessing them through a new model. Bills of lading in particular carry amendment history that rarely survives an export cleanly, so keep the original system readable for as long as your document retention obligations require.
Who actually builds liner shipping operations platforms?
Two established liner vendors serve the category, alongside custom software firms with maritime and regulated documentation experience. Digital Heroes works in the second group and suits carriers whose allocation and rating logic is genuinely their own: a PRD first process settles the voyage and documentation model before code, delivery spans 2,000 plus projects, and contracting through an India LLP, a US LLC or a UK LTD keeps IP assignment where your licences are held.
What makes Digital Heroes different from a generic dev shop here?
A generic shop treats a bill of lading as a record to edit and a manifest as a report to print, which is exactly how mismatch penalties happen. The distinguishing practice is modelling documents as versioned objects with preserved amendment history, and filing rules as effective dated configuration with a test harness per jurisdiction. That structure is agreed in the written PRD before engineering, and the client owns the repository from the first commit.
How do we verify a development partner is legitimate before paying?
Check D-U-N-S registration to confirm the contracting entity exists in the jurisdiction on the agreement, which matters when a system files with customs authorities. Read the Clutch profile for verified reviews with project values and named clients, and check Trustpilot for how complaints were resolved over time. Then request a logistics or regulated operations reference and speak to that client directly.
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.
Is customizing Odoo cheaper than building an ERP from scratch?
Usually yes in year one, and often no by year three if your workflows sit far from Odoo's assumptions. Odoo's published pricing starts around $25 per user per month and the Community edition is free, but heavy customization means every version upgrade can break your modules and needs paid rework. If you expect to rewrite more than about a third of the core flows, a scratch build with clean ownership tends to cost less over the life of the system.
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.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
Can a freelancer build an ERP, or do I need an agency?
An ERP is too wide for one person: it needs backend, frontend, database design, integrations, QA, and someone mapping your business processes. A solo freelancer can extend an existing ERP or ship one small internal tool, but full ERP builds by single developers are the most common rescue scenario Digital Heroes takes on. If budget is tight, shrink the scope to one module rather than shrinking the team below three or four people.
Can I start with one ERP module instead of the full system?
Yes, and it is how most successful custom ERP projects at Digital Heroes begin. We build the single module causing the worst pain first, typically inventory or order management, get it live in 10 to 14 weeks, and let it prove ROI before the next phase gets funded. Starting with one module also derisks data migration because you move one dataset at a time.
How do I calculate the ROI on a custom ERP?
Add up three lines: hours of manual work removed at loaded labor cost, subscription licenses you cancel, and error costs like mispicks and double entry that disappear. In Digital Heroes delivery experience, mid-market ERP builds typically reach payback in 18 to 30 months, faster when they replace a per-seat platform at 30 or more users. Run the math over five years, because that is where a one-time build beats recurring licenses decisively.
How much does a custom ERP cost for a small business?
A small-business ERP covering two or three core modules typically runs $40,000 to $120,000, with inventory, ordering, and accounting sync being the usual starting set. Across 2,000+ Digital Heroes projects, integration count and user roles drive cost far more than screen count. A full mid-market ERP with six or more modules usually lands between $150,000 and $400,000.
Who owns the source code if an agency builds my ERP?
You should, in full, and it must be written into the contract as work for hire with IP assignment on payment. At Digital Heroes every client receives the complete repository, database schemas, and deployment documentation, so they could hand the system to another team tomorrow. Walk away from any ERP proposal built on the agency's proprietary platform with ongoing license fees, because that recreates the vendor lock-in you were escaping.
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
Published · Last updated .
