EPR Packaging Compliance Software: Keep Ecoveritas Filing, or Build the Component Master Yourself?
Jurisdiction count is the gate.
On this page
Jurisdiction count is the gate. One or two markets with a few hundred products and stable packaging: keep a compliance scheme provider such as Ecoveritas or Landbell Group filing on your behalf, because their fees are a fraction of a development budget and a spreadsheet plus a competent coordinator will beat a build. Past roughly three reporting jurisdictions, or with several obligated entities and intercompany flows, the data underneath the filing becomes the problem and building it is defensible. Note what that does not mean: almost nobody should replace the filing relationship. The question is who owns the component weights and the volume attribution.
When is off the shelf genuinely the right call here?
Buy, and be honest about scale. If you sell in one or two markets with a few hundred products and stable packaging, a compliance scheme provider handling your submissions is the right answer and a build cannot be justified. Ecoveritas and Landbell Group know the regimes, they file for you, and their fees sit well below a development budget. Building software in that situation is a poor use of capital that a well maintained spreadsheet and a competent coordinator would beat on both cost and accuracy.
Source Intelligence and similar platforms are worth buying if your immediate problem is collecting specification documents from suppliers rather than modelling them. That is a real bottleneck for groups with long supplier tails, and paying somebody else to chase documents is cheaper than building a chasing workflow.
Be fair about what the provider model is and is not. The limitation is a boundary rather than a competence problem. Providers compute from the data you hand them, so if your component weights are unverified estimates assembled each cycle by a coordinator, the output inherits that and nobody owns the fix. That is a description of a division of labour, not a criticism of the service.
The honest test is whether you can say, for any single product, where the weight of every packaging component came from and when it was last verified against a source document. While the answer exists and takes minutes, your reporting is defensible and the money belongs somewhere else in the business.
When does a custom build actually pay off?
Two or more of these usually settle it. You report into more than three jurisdictions. Your group has multiple obligated entities with intercompany flows. Packaging design changes often enough that eco modulation is a live commercial question rather than a theoretical one. You have been queried on a submission and could not reproduce the number quickly. Or your annual fee bill is large enough that a one percent data error costs more than the build.
In Digital Heroes delivery experience, a focused first release covering a packaging component master with a bill of packaging per product, a canonical material taxonomy with a versioned mapping layer per scheme, volume attribution by obligated entity and immutable submission snapshots runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding supplier document capture with extraction, recycled content evidence, eco modulation scenario modelling and group consolidation runs $150,000 to $380,000 phased over 6 to 12 months.
The argument that carries a finance director is not reporting efficiency. Fees are calculated on real volumes of real materials, so an error is a recurring overpayment or an underpayment that surfaces in an audit with interest attached. Most packaging leads already suspect they overpay on some materials and underpay on others and cannot prove either way, because the component weights behind the calculation were never verified. That uncertainty has a price and it recurs every cycle.
How do they compare on the things that matter in this industry?
Rules and submission formats are a solved service. Compare on the data underneath them.
- Component, not product. Whether the unit of record is the packaging component with its own material, weight and recycled content, referenced by a bill of packaging, so a shared closure corrected once ripples through every product using it. A weight stored as a note on a product record cannot do that.
- Whose categories are your master data. Encoding one scheme's material categories as your item data makes every additional jurisdiction a rebuild. The durable pattern is a canonical taxonomy describing physical reality plus a mapping layer per scheme per reporting year. This is the single most common architectural mistake here and it is entirely avoidable.
- Volume attribution. Whether obligation is assigned by readable rules covering intercompany sales, imports, private label, exports and marketplace channels, with the unattributed remainder surfaced rather than silently dropped. That remainder is where the money hides.
- Restatement. Whether a submission is an immutable snapshot capturing weights, mapping version, attribution rules and volumes exactly as they stood at filing, with reason coded corrections afterwards.
- Weight provenance. Whether each weight carries a source, a date, a link to the evidence document and a verified flag only a laboratory weighing or a signed supplier specification can set.
- Eco modulation. Whether a technologist can model a label or material change against the same fee engine that produces your submissions and get a delta per market in minutes.
What does total cost of ownership look like at your scale?
Take the group from our cost work: roughly 1,400 products, six reporting jurisdictions, four obligated legal entities with intercompany sales, SAP as the enterprise system, and component weights verified for perhaps half the portfolio. The components total $335,000, and with a 10 percent contingency the committed number is $368,000 across roughly ten months. The contingency is not padding, because the attribution work will surface volume nobody can confidently place and resolving that takes longer than building the rule.
The recurring side is heavier than most groups expect. Support and maintenance runs 15 to 20 percent of build, so roughly $55,000 to $74,000 a year. Scheme rule maintenance runs $6,000 to $15,000 per scheme per year, which on six schemes is $36,000 to $90,000 annually before anyone requests a feature, and it is not optional because a stale mapping produces a wrong fee. Each new jurisdiction added later costs $18,000 to $45,000, more than the in build unit cost, because a market added afterwards needs historical mapping decisions revisited. Extraction tuning runs $8,000 to $20,000 as supplier layouts change, and an enterprise system major version costs $8,000 to $25,000.
Component weight verification at $10,000 to $40,000 a year sits outside all of that. It is operations work rather than software, weights drift as suppliers change tooling, and an unverified weight is an unverifiable fee. That line is the one most often missing from a business case and the one that determines whether any of the rest is worth anything.
What does the hybrid look like, and when is it the honest answer?
Keep the scheme provider filing and build only the data layer underneath. For the large middle band of groups reporting into three to six markets, this is the right answer and it is the one we recommend most often.
The split works because the two halves have different economics. Regime knowledge, submission formats and filing relationships change on regulators' schedules and cost real money to track, which is exactly the kind of work worth renting from Ecoveritas or Landbell. The component master and the attribution rules improve with use and belong to whoever holds them, because a shared component corrected once should ripple everywhere and a resolved attribution rule should not be re-derived next October. Feeding a clean, verified component and volume set into an existing filing service captures most of the accuracy benefit at a fraction of the full platform cost.
Sequencing advice is firm. Two markets and your top 200 products by volume in release one, which usually covers the large majority of your fee exposure while surfacing every structural problem in your data, at roughly half the cost of a full portfolio launch. Never store a scheme's categories as master data, which costs nothing to do correctly at the start. Defer eco modulation modelling to phase two, because it needs a working fee engine underneath it.
And start the physical weighing programme at kickoff rather than after the software lands. It is operations work with its own budget, and starting it late is the most common cause of a delayed first submission.
Which should you choose, by operator size and stage?
One or two markets, a few hundred products, stable packaging: buy the provider relationship and keep a careful spreadsheet. Spend the difference on verifying your top thirty component weights against a laboratory scale, which will move your fee accuracy more than any platform decision.
Three to six markets, one obligated entity: keep the provider filing and build the component master with the canonical taxonomy and mapping layer. That is roughly half a full platform and it fixes the half that is actually yours.
Three or more markets with several obligated entities and intercompany flows: build, and treat the volume attribution engine at $35,000 to $62,000 as the component that decides how much you actually owe. Every group's rules differ, and returns and write offs should reduce declared volume but usually do not, because nobody wires the credit note back to the packaging calculation.
Any group where packaging design changes frequently: build the eco modulation modelling, whatever you do about filing. It moves the decision to where it is actually made, because a marketing choice about a full body shrink sleeve currently carries a recurring cost across every market that nobody can see at the moment of choosing.
Any group that has been queried on a prior submission: build the immutable snapshot first. Restating from live data is impossible once supplier weights, mappings and product ranges have moved, and that single capability turns a fee audit from a fortnight of archaeology into a morning. Whichever route you take, own the repository, the cloud accounts and any extraction models trained on your supplier documents, because in a compliance system a dependency on your developer is a regulatory risk rather than only a commercial one.
If you would rather scope this before committing budget, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey's Developer Velocity research finds best-in-class tools are the top contributor to software business success, yet only about 5% of executives ranked tools among their top-three software enablers, signaling underinvestment in developer tools (this finding originates in McKinsey's Developer Velocity study rather than the linked generative-AI article). Source: McKinsey & Company (2023) →
- McKinsey argues software developer productivity can be measured by combining system-level metrics (DORA and SPACE) with its own outcome-oriented approach, which it reports deploying across nearly 20 tech, finance, and pharmaceutical companies - a claim that sparked significant debate in the engineering community. Source: McKinsey & Company (2023) →
- 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) →
- 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) →
Frequently asked questions
What does it cost to move off Ecoveritas or Landbell?
In most cases you should not move at all, because the filing relationship is the part worth keeping. If you do, the cost is not the notice period, it is that regime knowledge and submission format maintenance transfer to you at $6,000 to $15,000 per scheme per year.
Before deciding anything, ask what a data export contains. Providers compute from what you hand them, so the valuable asset is usually already on your side of the line, which is precisely why building the data layer beneath them is the cheaper move.
What happens if a scheme or provider changes its pricing?
Provider fees are not the number that decides this and treating them as such is why these business cases usually fail. Compare against your annual producer responsibility fee bill itself, because that is what the data governs, then ask what a one percent error is worth across all markets.
Scheme fees themselves move for a different reason: several regimes now modulate by recyclability, recycled content and features that disrupt sorting, so a design decision changes your recurring cost whether or not anyone repriced anything.
How long does a build take, and what sets the schedule?
Twelve to sixteen weeks for a first release covering two or three markets and your highest volume products, and 6 to 12 months for the full platform, in our delivery experience.
The variable that moves the schedule most is not engineering, it is the state of your starting data. A portfolio with verified component weights moves fast. One built on estimates needs a physical weighing programme running alongside, which is operations work and should start at kickoff rather than when the software lands.
Is Source Intelligence enough if our problem is supplier documents?
If your bottleneck is genuinely collection, it addresses that and it is cheaper than building a chasing workflow. Groups with long supplier tails get real value from it.
What it does not resolve is what happens to a document once you hold it. Mapping the declared components to your own item master, attributing volume across your group entities and modelling design scenarios all remain yours regardless of who collects the paperwork or who files the return.
Why can we not store each scheme's categories in our product data?
Because schemes define materials differently and revise their categories between cycles, so encoding one scheme's vocabulary as master data turns every additional jurisdiction into a rebuild. One treats a laminate as a composite, another asks for the dominant material, another separates coloured from clear.
The durable pattern is a canonical internal taxonomy describing physical reality plus a versioned mapping layer per scheme per reporting year. Versioning also means a prior year submission recomputes under the rules that applied then rather than today's.
How much does each additional jurisdiction add?
Between $6,000 and $12,000 per scheme during the build, on top of a $24,000 to $40,000 mapping engine that the first scheme pays for. A market added after go live costs $18,000 to $45,000, because it requires historical mapping decisions to be revisited and a fresh obligation analysis.
Then $6,000 to $15,000 per scheme per year in maintenance. Six schemes is $36,000 to $90,000 annually before anyone asks for a feature, and skipping it produces a stale mapping and a wrong fee.
Where does artificial intelligence genuinely help here?
Document extraction, and it is the strongest use of a model in this category. Supplier specification sheets and technical data sheets arrive in every layout imaginable and contain component weights, material declarations and recycled content statements. Extraction reads them with a confidence score and flags when a new specification differs from the version you previously accepted.
What a model should not do is assign a scheme category. That is a legal interpretation with money attached and it belongs in a mapping table your regulatory lead can point an auditor at.
When should a group not build this at all?
One jurisdiction with a modest portfolio and stable packaging. A scheme provider plus a carefully maintained spreadsheet handles that well, and a build would be a poor use of capital by a wide margin.
Also hold off if nobody will own component weight verification afterwards. That is operations work at $10,000 to $40,000 a year, weights drift as suppliers change tooling, and a component master full of unverified estimates is the same problem you started with, stored more tidily.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
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 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.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
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 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.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
Who can build a custom software system?
Digital Heroes builds custom 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 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 Amelia.
Senior Brand Designer · UK · London · 1 post on the site
Published · Last updated .
