Skip to content
§
§ · hiring guide

How to Hire a Digital Product Passport Development Company

Hire the firm that asks to see your bill of materials before it quotes. Passport work fails on data collection from tier two and tier three suppliers, not on software.

Supply Chain Software workflow illustration for How to Hire a Digital Product Passport Development Company.
The short answer

Hire the firm that asks to see your bill of materials before it quotes. Passport work fails on data collection from tier two and tier three suppliers, not on software. Expect $110,000 to $240,000 and 14 to 20 weeks for a first release, and keep the resolver on a domain you own. Confirm your delegated act scope with regulatory counsel first.

A digital product passport publishes assertions about a physical object to the open internet, under your company name, where a market surveillance authority can read them. Hiring for that is less like commissioning software and more like commissioning an audit you will have to defend every season, using evidence held by companies that do not work for you and gain nothing from replying.

That is what makes this category hard to buy. Every vendor can demonstrate a code on a label resolving to an attractive consumer page in forty seconds, and that page is roughly the last five percent of the work. The rest is the join between a purchase order line, the fabric lot cut against it, the mill's lab report, the spinner nobody in your building can name, and the units that shipped. A platform that stores documents against a supplier is not the same object as a record that stores evidence against a product instance, and telling those apart in a sales meeting is genuinely difficult.

What a passport development company actually does

The core deliverable is a data model, and a good firm will draw it before it prices anything. Evidence has to be modelled as a claim with a subject, an asserting party, a source document, a validity window and a confidence state, so every field on the published passport carries a provenance chain back to whoever asserted it. Values without asserting parties are decoration.

Then collection. Requests go out to suppliers as short tasks tied to one purchase order and one claim rather than as a ninety field questionnaire, because long questionnaires get one honest pass and autocomplete forever after. Document extraction earns its place here: certificates arrive as PDFs in a hundred layouts, and a model can read certificate number, scope, issuing body and expiry, then flag the ones that lapsed or cover a scope your claim does not match. Nobody is reading four thousand documents a season.

Then identity. Serial ranges allocated to production orders, printed by the factory or label vendor, confirmed back as applied, and only then activated in the resolver. Batch level identity is a legitimate first step, provided the record model is unit ready so the move later is a migration rather than a rebuild. Then the resolver itself, which should be small, boring and extremely available, doing one job at high read volume and never coupled to the system that authors the data. Then role scoped public views computed from a single record, versioned as an append only log so a claim asserted in March and corrected in September are both retrievable. Then the write path for repairs, resale and recycling, designed early even if you keep it closed in year one.

What it really costs in 2026

ScopeCost bandTimeline
First release: identifier assignment, supplier claim collection workflow, passport record store, one public market view$110,000 to $240,00014 to 20 weeks
Full programme: unit level serialisation with factory confirmation, PLM and ERP (Enterprise Resource Planning) integration, evidence extraction, restricted party views, post sale write access$300,000 to $750,0009 to 18 months, phased
Each additional product category with its own field set$20,000 to $60,000 each3 to 6 weeks each
Resolver hosting and record retention after the last unit is soldAnnual operating lineOngoing for years

Two costs sit outside every software quote we are asked to review. The first is supplier onboarding, which is a change management programme with software attached rather than a feature. Somebody has to phone a garment maker on a thin margin and persuade him to chase a mill he buys from occasionally. That is a coordinator's job for at least a season, and no engineering estimate covers it. Programmes that skip this line fail in the second season, when the first honest data set never arrives.

The second is product data remediation. If the bill of materials in Centric or FlexPLM does not match what the factory actually cut, the passport publishes that mismatch to the public internet under your brand. Reconciling the existing bill of materials against production reality is real work, it is discovered rather than planned, and it is the reason experienced firms ask to see your data before they quote rather than after.

Signals of a strong partner

  • They whiteboard a claim before quoting. Claim, subject, evidence document, asserting party, validity window and version, with an explanation of why the asserting party matters more than the value.
  • They insist the resolver sits on your domain. Product identity that lives in a vendor namespace cannot be moved later without re-tagging physical goods already in the market.
  • They ask which categories you sell into. Different product groups fall under different delegated acts, and a model shaped around one category will fight the next.
  • Versioning is their answer to corrections. When a claim changes after forty thousand units have shipped, you want an append only history, not an edit form.
  • They name systems and document types. Reading a bill of materials out of a PLM is a different problem from reading a spreadsheet, and confirming applied serials back from a label vendor is different again.
  • They are candid about identity granularity. A good partner will tell you when batch level is enough for now and exactly what makes the later move cheap.
  • They ask about post sale writes early. Repairers, resale platforms and recyclers will want in, and retrofitting that path costs more than designing it.

Red flags

  • The model is a products table with a sustainability column. That is a catalogue, and you are funding their first lesson in regulatory data modelling.
  • Identity is offered on the vendor's infrastructure. Convenient today, and an exit that requires re-labelling stock already on shelves.
  • They promise compliance rather than capability. Delegated acts move. A vendor guaranteeing a regulatory outcome is making a promise regulatory counsel should be making.
  • Supplier collection is described as a portal. A portal with no task design and no incentive story is a login your vendors will never use twice.
  • No question about how long records must stay resolvable. These records outlive the product, the campaign and probably the agency relationship.

Questions to ask on the first call

  1. Model a claim for me on a whiteboard. Where does the asserting party live and why does it matter more than the value?
  2. Whose domain does the resolver run on, and what happens to it if we stop working with you?
  3. A recycled content claim is corrected after forty thousand units have shipped. What does the record show a year later?
  4. Which PLM or ERP have you actually read a bill of materials out of, and which document types have you extracted from?
  5. How would you get an honest fibre origin claim out of a spinner two tiers below our direct vendor?
  6. Have you confirmed applied serials back from a factory or label vendor, and how did the reconciliation work?
  7. How do consumer, repairer, recycler and authority views get computed from one record without four copies?
  8. What is your plan for a second product category that falls under a different delegated act?
  9. What in this proposal is engineering, and what is supplier onboarding work our own team has to staff?

A simple way to decide

Buy a paid discovery phase of three to four weeks at a fixed fee, and make the deliverable a written specification you own: the claim model, the field set per category with the regulatory source noted for your counsel to confirm, the identity decision with its serialisation consequences on the factory floor, the resolver architecture and domain, the view matrix by audience and market, and an honest split between engineering scope and supplier onboarding effort. That document is worth having even if you then run a competitive tender with it, which is what we suggest.

Digital Heroes works PRD first for that reason, and contracts through India LLP, US LLC and UK LTD entities so intellectual property assigns under the law your own advisers already read, which matters when the record has to stay resolvable for years after a supplier relationship ends. The client owns the repository, the cloud accounts and the resolver domain from the first commit, and the firm is verifiable through D-U-N-S, Clutch and Trustpilot before anything is signed.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. 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) →
  2. In a survey of 579 supply chain professionals (July 31 to October 1, 2024), only 29% had built at least three of the five capabilities Gartner identifies as needed for future competitiveness (agility, resilience, regionalization, integrated ecosystems, and enterprise-wide strategy). Source: Gartner (2025) →
  3. The share of tasks performed mainly by humans is projected to fall from 47% to 33% by 2030 as human-machine collaboration expands, with 170 million jobs created and 92 million displaced (a net gain of 78 million). Source: World Economic Forum (2025) →
  4. Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
FAQ

Frequently asked questions

How much does custom digital product passport software cost?

A first release with identifier assignment, a supplier claim collection workflow, the passport record store and one public market view runs $110,000 to $240,000 over 14 to 20 weeks. The full programme with unit level serialisation, PLM integration, evidence extraction and post sale write access runs $300,000 to $750,000 across nine to eighteen months. The biggest driver is not software, it is how many supplier tiers you have to reach.

Should we buy a passport platform instead of building one?

If you have a modest number of active styles, one market, no serialisation in production and a supply chain short enough to phone directly, buy. Existing platforms will make you compliant faster than a build and cost less than a discovery phase. Build when claims must come from tier two and tier three suppliers you do not contract with, when you already serialise units, or when several categories fall under different delegated acts.

What is missing from most passport software quotes?

Supplier onboarding and product data remediation. Somebody has to persuade vendors on thin margins to chase companies they buy from occasionally, and that is a coordinator's job for a season rather than a feature. Separately, if the bill of materials in your PLM does not match what the factory actually cut, the passport publishes that mismatch publicly under your brand, and reconciling it is discovered work nobody budgets.

Do we need unit level serialisation from the start?

Batch level is a legitimate first step where unit level is not yet required, and it keeps your factories out of serial printing during phase one. The condition is that the record model must be unit ready from the beginning so the later move is a data migration rather than a rebuild. If repair, resale or authentication matter commercially, go unit level immediately because you will end up there.

Who should own the resolver domain?

You should, written into the contract before kickoff, along with the repository and the cloud accounts. Passport records have to stay resolvable for years after the last unit is placed on the market, which is longer than most agency relationships last. Any arrangement that puts product identity inside a vendor namespace creates a dependency you cannot exit without re-tagging physical goods already sitting in the market.

Can we migrate years of data out of our current system into new custom software?

Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.

What happens to my software if the agency shuts down or we stop working together?

Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.

Should I hire a freelancer or an agency for my software project?

A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.

What does it cost to maintain custom supply chain software each year?

Budget 15 to 20 percent of the original build cost per year, so roughly $9,000 to $12,000 annually on a $60,000 system, covering hosting management, dependency updates, bug fixes, and small enhancements. Across its maintenance contracts, Digital Heroes sees supply chain systems need more upkeep than typical web apps because carrier APIs, EDI specs, and ERP versions keep changing underneath them. Hosting itself is usually minor, often $100 to $500 per month for a mid-size operation.

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.

Should we start with an MVP or build the full supply chain platform at once?

Start with an MVP that fixes your single most expensive workflow, prove it in daily operations, then expand module by module. That gets working software onto the warehouse floor in about 12 weeks instead of debating a year-long spec, and real usage always reorders the roadmap; features that felt critical in planning routinely get cut after go-live. Digital Heroes typically scopes phase one at 30 to 40 percent of the total vision and lets measured results justify each next phase.

When is SAP actually a better choice than building custom supply chain software?

Choose SAP when you need a full ERP, operate in a heavily audited industry that expects standard systems, or run global operations where localization, tax, and compliance content matter more than workflow fit. SAP's strength is breadth: finance, manufacturing, and supply chain in one validated suite. Custom wins when your edge lives in a specific workflow, like how you allocate inventory or route orders, that SAP would force you to bend to its standard process. Many Digital Heroes clients keep SAP as the system of record and build custom operational tools around it.

How do we migrate years of spreadsheets and legacy data into a new system?

Migration runs as its own workstream: extract and profile the data, clean duplicates and dead SKUs, map fields to the new schema, then do trial loads and a final cutover during a weekend or slow period. Expect 2 to 6 weeks depending on how many sources you have and how dirty they are. Digital Heroes runs old and new systems in parallel for 2 to 4 weeks on most supply chain cutovers so inventory counts and open orders can be reconciled before the legacy system is retired.

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.

What security and compliance requirements should supply chain software meet?

At minimum: role-based access control, encryption in transit and at rest, audit logs on inventory and order changes, and tested backups, because the system holds supplier pricing and customer purchase history your competitors would love to see. If enterprise customers connect to it, expect security questionnaires and possibly SOC 2 expectations; food, pharma, and aerospace add traceability rules like FDA lot tracking or ITAR data handling. Raise these in the first scoping call, since retrofitting audit trails onto a live system costs far more than designing them in.

Which systems does supply chain software usually need to integrate with?

The standard set is your accounting or ERP system (QuickBooks, NetSuite, SAP), your sales channels (Shopify, Amazon, or a B2B portal), carriers and 3PLs for rates and tracking (UPS, FedEx, or an aggregator like EasyPost), and warehouse hardware such as barcode scanners and label printers. EDI connections to large retail customers are their own workstream. In Digital Heroes scoping, integration work is commonly 30 to 50 percent of total project effort, so listing every connected system upfront is the single best way to get an accurate quote.

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.

Who can build a custom supply chain software system?

Digital Heroes builds custom supply chain 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 supply chain 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.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply