A ship can carry thousands of containers and still need somebody ashore to chase a quotation for a spare part. Before the equipment moves, information has to travel: a specification, a price, an approval, an order. ShipServ built its business inside that less photogenic journey. Its subject is maritime trade. Its recurring enemy is the same detail being entered into another system by another person.
Today, parent company Marcura puts annual trade through its procurement network at about $7 billion, across 11,000 trading vessels and 50,000 connected suppliers. Those are company-reported activity figures. The dollar total is gross merchandise value, the value of goods and services traded, rather than ShipServ’s own sales. It describes the traffic passing through the business.
ShipServ serves professional purchasing teams at shipowners, managers and operators, alongside the companies supplying them. Buyers find suppliers and exchange commercial documents. Sellers gain visibility and tools to handle incoming demand. The product’s appeal lies in making an ordinary purchase require fewer extraordinary administrative efforts.
Annual gross merchandise value reported by Marcura. Customer trade, not platform revenue.
The customer’s software was staying
Paul Østergaard founded ShipServ in 1999 after a career that included shipping company J. Lauritzen, Boston Consulting Group and Oracle. He brought experience of both shipping and enterprise software. An SEC filing later recorded the company’s 2008 Red Herring Europe award and its 2009 First Tuesday technology award. Recognition arrived after the product had confronted an awkward customer preference.
In a 2008 interview, Østergaard recalled imagining a web marketplace resembling eBay. The early assumption that failed was that buyers would start over online. Shipping businesses already had purchasing systems tailored to their operations. They were unwilling to discard them for a newcomer’s preferred interface.
“starting from a clean slate was not a feasible option”Paul Østergaard, recalling ShipServ’s early approach in 2008
ShipServ redirected its effort toward connecting those systems. It helped develop Marine Trading Mark-up Language, or MTML, adapting an older electronic-data standard for internet exchange, and encouraged software vendors and the International Marine Purchasing Association to adopt it. Buyers could keep working in familiar applications while transaction information travelled through ShipServ.
The lesson was unusually concrete: customer resistance revealed a product requirement. Software that connects established habits has a different sales conversation from software that requires everyone to abandon them.
The valve seller and the shared inbox
W&O Supply offers a smaller, more recognisable view of the business. The marine valve supplier relied on email, telephone calls and referrals to reach customers. In Marcura’s account, incoming requests for quotations were handled by one person. Before there was an ambitious data problem, there was a queue on somebody’s desk.
ShipServ gave the wider team access to those requests. W&O also used pricing information and order updates to improve its responses. The company reports a 25 percent increase in purchasing customers over five years. That is a customer-count result, not a revenue growth figure or a controlled experiment proving that software caused every additional sale.
Still, the operational change is easy to understand. Discoverability brought prospective buyers closer; shared access made the resulting work less dependent on one employee. A supplier buying exposure without fixing its quotation process could simply purchase a longer queue.
Purchasing customers over five years at W&O, as reported in Marcura’s customer story. A useful result with a specific denominator.
RMS Marine describes a related challenge across a larger organisation. Its customer story identifies 13 offices in China and five international locations. Expansion made consistency harder: more branches meant more opportunities for information to fragment. RMS adopted a common digital procurement workflow with ShipServ to connect customers and suppliers and reduce administrative work. Its testimony is qualitative, but the underlying need is familiar to any business that has outgrown the office where everybody could hear the telephone ring.
One portal too many
Scorpio’s complaint is about the industry’s collective workload. Paolo Magonio, its head of procurement, describes shipowners and managers developing separate onboarding procedures and platforms. Each buyer may see a useful local improvement. Suppliers inherit the combined burden of serving them all.
“The data is not consistent, the data is not shared”Paolo Magonio, head of procurement at Scorpio
Scorpio’s work with ShipServ has included automating quotation and RFQ exchanges. Its argument for standardisation reaches further: supplier credentials and commercial information should be easier to validate and reuse. That position helps explain why the network matters alongside the individual features. A connection becomes more useful when the other party already uses it.
ShipServ occupies the space between a company’s internal purchasing system and its external trading partners. SeaProc competes in this territory with cloud procurement and fleet-management integrations. Procureship offers maritime purchasing automation, supplier recommendations and related tools. Buyers also have the option of continuing with their existing portals and processes.
Integration alone therefore does not settle the competitive question. The practical comparison is which network reaches a buyer’s actual suppliers, how well it exchanges their documents and whether its costs fit the purchasing workload. ShipServ’s established marine supplier base and its position within Marcura make a specific case; they do not remove the need to test it.
- 01Request
Specify the requirement - 02Quote
Supplier prices the work - 03Approve
Buyer chooses and orders - 04Exchange
Systems retain the record
Illustrative procurement sequence. The commercial decision stays with the trading parties.
The price of being found
ShipServ’s supplier offering separates visibility from transaction handling. Free registration provides a limited search presence. Paid profile tiers expand the categories, brands and ports a supplier can target, then add richer material such as catalogues and video. Platform tiers concern the work arriving after discovery: transaction views, reporting, APIs and integration support.
That distinction gives a prospective customer two questions to answer. Does the business need more relevant enquiries, or does it need to process existing enquiries with less effort? A supplier can need both, but spending on one does not automatically solve the other. Current paid plans lead to a sales conversation, so the buying decision involves a quote rather than a universal published subscription price.
For a buyer, ShipServ’s broader tools include expert-assisted sourcing through SpotSource, supplier vetting and procurement analysis. Marcura advertises connections with more than 30 ERP and third-party accounts-payable systems. The commercial proposition is to support the purchasing work around an order as well as transmit the order itself.
The paperwork gets a longer life
d’Amico’s experience adds a different reason to care about purchasing data. In its Marcura customer story, the group describes managing a mixed fleet of 75 owned and third-party vessels across technical offices in Rome, Mumbai and Singapore. Handling supplier documentation manually had become a recurring administrative problem.
Its use of ShipServ includes Inventory of Hazardous Materials tools and supplier vetting. Material declarations and supplier declarations of conformity can be collected during RFQ and purchase-order activity. Staff gain a common place to organise records and follow supplier information. The useful shift is timing: ask for documentation while a purchase is being arranged, when the supplier is already engaged.
That makes procurement relevant to colleagues beyond the purchasing department. A commercial document can carry information that technical and compliance teams will need later. The organisational payoff depends on those teams agreeing what to collect and who checks it. A convenient upload field does not itself establish whether a declaration is accurate.
From routine orders to dry-dock projects
Marcura announced its agreement to acquire ShipServ in August 2023. The announcement counted 126 ShipServ employees and said the business would retain its brand and operate separately. Marlin Equity Partners, which had invested in Marcura in 2022, supported the combination.
The stated logic was to bring procurement closer to payments, compliance information and settlement processes. A purchasing record becomes more valuable when the people checking and paying an invoice can use it too. Marcura already served other departments inside shipping businesses; ShipServ brought relationships with their purchasing teams.
In January 2025, Marcura announced another acquisition: VesselMan, whose vessel-management and dry-docking software would complement ShipServ. Its team was to join ShipServ. Dry-docking brings planning, maintenance tasks, project workflows and purchasing into the same operational discussion. The acquisition set out an expansion of capabilities rather than a published measurement of the combined product’s results.
ShipServ’s own careers language is more everyday than the acquisition vocabulary. It names passion, innovation, accountability and fun as values, and emphasises talent over CVs. That is the employer’s stated culture. The work described across its customer stories suggests a business where understanding how a purchasing department actually operates remains central to building useful software.
Copy the connection, measure the result
The transferable idea is to find where information gets copied, delayed or stranded between organisations. Start with one recurring purchase. Record how long a quotation takes, how often someone re-enters a field and how many requests wait for missing details. Then test whether connecting the systems changes those numbers. This is an editorial recommendation drawn from the customer examples, not a promised ShipServ return.
The conditions matter. Low purchasing volumes may leave little manual work to remove. Suppliers outside the network still need onboarding. Inconsistent product information can travel faster without becoming more accurate. And a team that continues doing every step in parallel by email may preserve much of the old workload.
ShipServ’s history gives those caveats some weight. Its formative discovery was that the customer’s existing way of working deserved attention. The opportunity was in making that work travel across company boundaries. For a business built around ships, learning to meet customers where they already were proved a useful navigation skill.