How Much Does Digital Product Passport Software Cost in 2026?

The bands a passport build falls into

Two bands, and the split is identity granularity plus how far up your supply chain the claims have to come from.

• $110,000 to $240,000, fourteen to twenty weeks. A first release: identifier assignment, a supplier claim collection workflow, the passport record store, and one public market view. That is a live resolver serving real product data on your own domain, not a pilot on a slide. Identity is usually batch level at this price.
• $300,000 to $750,000, nine to eighteen months. The full programme: unit level serialisation with factory confirmation, product lifecycle management and enterprise resource planning (ERP) integration, automated evidence extraction from certificates and lab reports, restricted views for repairers, recyclers and authorities, and a post sale write path so repairs and resale events can land on the record.

The Ecodesign for Sustainable Products Regulation came into force in 2024 and delivers passport requirements through delegated acts by product group, with textiles named as an early priority. The European Union Battery Regulation carries its own battery passport obligation for the categories it names from February 2027. Have your exact scope and dates confirmed by regulatory counsel rather than by a vendor, because delegated acts move and your budget should be sized against the act that actually applies to you.

What drives a passport build up

Supplier tier depth is the first driver and it is barely a software cost at all. If your passport fields must be assembled from tier two and tier three suppliers you have no contract with, you are funding a change management programme with software attached. Sending a request and storing an answer is modest engineering. Getting a spinner three companies away to produce a transaction certificate on schedule is the actual work, and it consumes account management rather than developer hours.

Unit level serialisation is the second, as covered above. The cost is not the serial generator. It is the loop: allocating ranges to production orders, producing print files in whatever form your factories or label vendors can consume, receiving confirmation of what was actually applied, reconciling that against what was planned, and only then activating codes in the resolver. Each of those touchpoints involves a party outside your building.

Category count is the third. Each product group brings its own field set, its own evidence types and its own disclosure rules, so a brand selling apparel and small electronics is building two field models rather than one with a flag. Market count works the same way through language and disclosure obligations, though the multiplier is smaller.

The driver nobody budgets for is existing product data quality. If the bill of materials in your product lifecycle management system does not match what the factory actually cut, the passport publishes that mismatch to the public internet under your brand. Finding and fixing those discrepancies appears in no vendor quote and lands in the middle of your build.

Finally, the resolver must stay available for years after the last unit is placed on the market, long after the campaign, the season and possibly the agency. That means a small, boring, extremely available service that is never coupled to the system authoring the data.

What keeps the number down

One category, one market, batch level identity, and your top vendors by volume rather than all of them. That combination is the cheapest credible starting position and it produces a live resolver serving real data, which is the thing that matters.

Batch level first is the largest lever. It avoids dragging your factories into serial printing during phase one, which removes the dependency most likely to slip. The condition is non negotiable: the record model has to be unit ready from the beginning. If repair, resale or authentication matter commercially, go unit level immediately, because you will end up there and re-tagging goods in the market is the most expensive way to change your mind.

Keep the resolver separate and small. One job at very high read volume is cheap to build and cheap to run for a decade. A resolver entangled with your content management system is neither.

Send short tasks rather than long questionnaires to suppliers. A ninety field form gets one honest pass and then autocomplete forever, so you pay for collection software and receive fiction. A request tied to one purchase order and one claim, requiring a document rather than a typed number, costs no more to build and produces usable evidence.

A worked example that adds up

An apparel brand with 340 active styles, 40 direct vendors, no serialisation in production today, selling into two European markets, with product data in an established product lifecycle management system. They are going unit level because resale and repair are part of the commercial plan.

• Discovery, claim and evidence data model, plus field mapping against the applicable delegated act: $18,000
• Identifier scheme and resolver on the brand's own domain, built for long term availability: $34,000
• Passport record store as an append only event log with versioning and correction history: $38,000
• Supplier claim collection workflow with tasks tied to purchase order lines: $52,000
• Automated extraction over certificates and lab reports with certificate number, scope, issuing body and expiry checks: $44,000
• Public market view, role scoped, first market: $28,000
• Second market language and disclosure handling: $12,000
• Restricted views for repairers, recyclers and authorities: $26,000
• Unit level serialisation: range allocation to production orders, print files, applied confirmation, activation: $68,000
• Product lifecycle management integration for bill of materials: $32,000
• Enterprise resource planning integration for production orders and shipments: $24,000
• Post sale write path with per party permissions: $30,000
• Supplier onboarding, training and the first full collection cycle: $22,000

That totals $428,000 across thirteen months, inside the full programme band. Take the first four lines plus the first market view and you have $170,000 shipping in about eighteen weeks, which is a live passport for one market at batch level with real supplier evidence behind it. The $68,000 serialisation line and the $56,000 of system integration are what separate the two, and both can wait.

How the spend phases

Discovery first and paid for separately, with a deliverable that is not a document. You want a written statement of which delegated act applies to which of your categories, what your product lifecycle management system actually holds versus what the passport needs, and which of your 40 vendors can realistically reach tier two. If the third answer is grim, that is a scope decision rather than a reason to stop.

Then sequence identity, record, collection, view. The resolver and record store come first because everything else writes to them. Collection follows, and it needs a real season of use before you widen it. The public view comes next. Only then does serialisation start, once you know the record model is right and you are not going to re-tag goods against a schema you regret. Hold fifteen percent back for the period after your first market view goes live, because that is the first time anyone external reads your data closely.

The ongoing costs nobody quotes

Resolver hosting is the permanent line and unusual in shape: very high read volume, very low write volume, and an availability requirement measured in years rather than quarters. It never stops, and it must be budgeted for the full retention period after the last unit is placed on the market rather than for the life of the campaign.

Record storage grows monotonically because corrections are versions rather than edits. That is the correct design, since an authority asking what you published on a given date needs an answer in minutes, but it means storage is a growing line rather than a flat one.

Budget a maintenance retainer at fifteen to twenty percent of build cost per year. In this category the retainer is doing something specific: delegated acts are still arriving and existing ones are amended, so field sets and disclosure rules change on a regulator's timetable. A system that cannot absorb a field change without a release cycle is a system you will pay for twice.

Then the recurring cost people forget: certificate collection is seasonal. Certificates expire, suppliers change, and every season brings another round of chasing evidence. That is headcount, not software, and it continues for as long as you sell the products.

Comparing a build against your current renewal

If you already have a quote from a passport platform, put the two side by side properly rather than comparing a licence to a build price. Take the platform fee across five years, including whatever it scales on in your contract, whether that is active styles, units published or resolutions served. Add the internal cost of supplier collection, because no platform does that for you either. Add the integration work to get your bill of materials into their model, which is rarely included.

Then set that against the build cost plus five years of resolver hosting, storage and retainer. For a small style count in one market the platform wins clearly and you should take it. As style count, category count and market count rise, the platform's scaling term is what closes the gap rather than the build getting cheaper.

There is one line that does not appear on either side of that comparison and should. If your product identity lives inside a vendor namespace, changing providers later means re-tagging physical goods already in the market. Price that exit before you sign, because it is the only cost in this category that is genuinely impossible to reduce after the fact.

When buying beats building

Buy if you have under roughly 200 active styles, a supply chain short enough that you can phone the mill, no serialisation in production and a single European market. EON or TrusTrace will get you compliant faster and cheaper than a build, and the platform fee will cost less than the discovery phase of a custom project. That is a real answer and we give it regularly.

TrusTrace is built around supply chain data collection and chain of custody documents and does that competently. EON is genuinely strong on identity and the consumer facing experience, and if you are willing to adopt someone else's identity infrastructure wholesale it is a serious option. Circularise suits material flow and mass balance problems, which fits chemicals, plastics and batteries better than a forty vendor apparel base.

Build when two or more of these are true. Your passport fields must be assembled from tier two and tier three suppliers you do not contract with. You already serialise units for another reason, so half the identity work exists. You sell across several categories falling under different delegated acts, so a single vendor data model will fit one and fight the rest. Your product data of record sits in a system the business will not replace. Or the passport is commercially interesting beyond compliance through resale, repair or authentication, in which case renting the record is the wrong trade.

If you would rather scope this before committing budget, 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.