Extended Producer Responsibility Reporting: Build or Buy at Your Jurisdiction Count
The line is roughly three or four jurisdictions, and whether your packaging data already exists in structured form.
On this page
The line is roughly three or four jurisdictions, and whether your packaging data already exists in structured form. Report extended producer responsibility (EPR) in one or two jurisdictions on a few hundred stock keeping units with stable packaging, and Ecoveritas or Lorax EPI will handle it for less than a build would cost you to specify. Above that, with submissions assembled by hand each period from supplier documents nobody has read, a first release runs $55,000 to $120,000 in 10 to 16 weeks. The number that usually decides it is not the fee bill, it is the overpayment hiding inside your conservative defaults.
When is off the shelf genuinely the right call here?
Buy if you report in one or two jurisdictions, hold a few hundred stock keeping units and your packaging is stable. Ecoveritas and Lorax EPI do this work competently, and the maintained regulatory content is genuinely worth paying for given how often rates and category definitions are revised. At that size a custom build would cost more than the fees it could recover, which is the whole argument.
Outsource the obligation entirely if you would rather it was handled as a service. Reverse Logistics Group is a reasonable route for producers who have concluded that packaging compliance is not a capability they want to own. That is a legitimate position rather than a failure of ambition.
Buy if your obligation is new and you do not yet know your own numbers. Running one or two reporting cycles through a service teaches you what your exposure actually is, and it is a far cheaper way to learn than a build specified from assumptions you have not tested.
The test for buying is whether your submission is a lookup or a reconstruction. If your packaging specifications are already structured, your sales data already carries market of sale, and filing is a matter of applying a rate to a weight, a service will do that better and cheaper than anything you commission. The build case appears when the submission is assembled by a person from four sources that do not agree, and only then.
When does a custom build actually pay off?
The thing worth building is not a rate calculator. It is the two joins your business has never made: a per stock keeping unit packaging component master with a provenance flag on every field, and an allocation layer that turns shipment data into a defensible placed on market figure.
Provenance is the whole argument. When you do not know a component's weight or material, the safe assumption is the conservative one, and conservative assumptions accumulate across thousands of products and every new launch. Over reporting is the more common failure and the quieter one, because no regulator has ever written to a producer to say they paid too much. Marking every field as supplier declared, internally measured or estimated makes the overpayment visible, and once it is visible you can attack the highest volume estimates first.
In Digital Heroes delivery experience a first release covering the component master, supplier data collection with document extraction, sales allocation by market of sale and fee calculation with submission output runs $55,000 to $120,000 over 10 to 16 weeks. A full platform adding eco modulation modelling and design comparison, multi entity submissions, immutable audit packs and restatement workflow runs $140,000 to $320,000 across 6 to 12 months.
Build when two or more hold. You report across more than three or four jurisdictions with hand assembled submissions. Your packaging data sits unread in supplier documents. Your fee exposure makes the gap between estimated and measured weights worth six figures a year. Or an audit has already shown you cannot reproduce a submitted number.
How do they compare on the things that matter in this industry?
On regulatory content, the services win and it is not a close call. Packaging EPR laws have been enacted in United States states including Maine, Oregon, Colorado and California under SB 54, with Circular Action Alliance operating as the producer responsibility organisation in several of them. The United Kingdom has packaging data reporting obligations, the European Union continues to tighten requirements, France applies eco modulation and marking rules, and Canadian obligations run provincially. Keeping that current is real work that a service already does for you, and if you build you now own it. Confirm your own position with a compliance advisor rather than any published list, including this one.
On the component master, the difference is shared components rather than storage. A business with 12,000 products where forty carton specifications are reused across them needs components modelled as shared objects, so a specification change updates every product using it instead of requiring thousands of edits. That is a data model decision, and it is the one that determines whether the system is maintainable in year three.
On supplier data, the hard part is collection rather than storage, and this is where a build earns its place. Suppliers will not fill in your spreadsheet, or they will fill it in wrongly. A portal that shows each supplier only their own components and validates at entry rejects a weight in the wrong unit immediately rather than in an audit two years later. Document extraction reads the specification sheets they already send and proposes records a person confirms, which means you stop asking suppliers to work in your format.
On allocation, no service can fix your source data. Fees are owed where packaging is placed on market and your systems record where you shipped. Distributor volumes flow onward, exports need excluding on documentary evidence rather than assertion, and direct to consumer sales attribute by delivery address, which often sits in carrier data rather than your enterprise resource planning (ERP) system.
On audit evidence, a submission needs to be reproducible: these products, these components, these weights, from these sources, allocated by this rule at these rates. A spreadsheet edited forty times since filing cannot reproduce it.
What does total cost of ownership look like at your scale?
Take a food and household goods producer with 3,200 products, roughly 180 shared packaging components, obligations in five jurisdictions, and packaging data spread across supplier documents and one compliance spreadsheet.
A first release prices at about $107,000: discovery, sales data mapping and a reconciliation of one prior submission $9,000, the packaging component master with shared components, roles, materials, weights and a provenance flag on every field $18,000, a supplier portal with scoped access and unit validation $16,000, a document extraction pipeline proposing records for human confirmation $14,000, the sales allocation layer with per channel rules and export exclusion on evidence $22,000, the jurisdiction configuration engine with rates, categories, effective dates and thresholds $17,000, and fee calculation with frozen filing snapshots $11,000. Eco modulation modelling in phase two adds roughly $30,000 to $45,000.
Running costs are 15 to 20 per cent of the build per year, weighted towards regulatory content rather than infrastructure, since this is not a high traffic system. The recurring work is maintaining rates, category definitions, thresholds and modulation adjustments across every jurisdiction. If jurisdictions are configuration, that is a compliance analyst's afternoon. If they are code, it is a development ticket every time, and that single design decision is most of your annual cost.
Against that, put your service fee, any per submission charges, the consultancy days you buy each year, and the internal weeks your compliance manager spends assembling files and chasing suppliers at loaded cost. Then estimate the overpayment: take the share of your packaging weight currently carried by estimated rather than measured values and apply a conservative correction to what you paid last year on those products. In our delivery experience that recoverable number is frequently larger than the build.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. In packaging compliance this is the shape most producers should aim at, because the two halves of the problem have different owners.
Concretely: keep your service or platform for the regulatory content and the submission itself. That is the part you would otherwise be maintaining forever, and rates change on their own cycles across every jurisdiction. Build only the component master with provenance, the supplier collection portal and the allocation layer, and feed the result into whichever filing route you use.
That split works because the value is in the inputs rather than the arithmetic. A service applying an accurate weight to a correct placed on market volume gives you the right answer. The same service applying a conservative default to a shipment figure gives you a wrong answer that nobody will ever correct. Fixing the inputs is a fraction of a full platform and it attacks the overpayment directly.
Sequence the supplier outreach at kickoff rather than at handover. The engineering is usually ready before the data is, and the timeline is set by suppliers responding rather than by developers finishing. Starting early routinely saves a month of calendar time.
Which should you choose, by operator size and stage?
One or two jurisdictions, a few hundred products, stable packaging: buy Ecoveritas or Lorax EPI, or hand the obligation to a service, and spend the difference on something that grows the business.
A newly obligated producer of any size: buy for two cycles. You will learn your real exposure, discover which of your assumptions are wrong, and write a far better specification if you do eventually build. Nobody has ever regretted this order.
Three to five jurisdictions with data spread across supplier documents: build the component master, supplier portal and allocation layer at $55,000 to $120,000, keep your existing filing route, and start with the jurisdictions carrying most of your fee exposure and your highest volume products. Fees follow volume closely, so a minority of your catalogue carries most of the liability.
A multi entity group across six or more jurisdictions with meaningful eco modulation exposure: expect the full $140,000 to $320,000 programme. Sequence eco modulation modelling into phase two rather than release one, because comparing two closure or film options across every jurisdiction makes no sense until the component master is complete and trustworthy. That feature is usually what gets the project approved, since it converts compliance from a cost centre into an input to product decisions, and it is also the one that fails hardest if built on estimates.
If you want that decision made properly rather than quickly, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. 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.
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
Frequently asked questions
What does it cost to move off Ecoveritas or Lorax EPI?
The exit cost is lower than in most categories, because what you take with you is your own packaging and sales data rather than a configured workflow. Ask what structured export you can obtain of component records, submission history and the calculation behind each filing.
The real switching cost is regulatory content. Once you leave, maintaining rates, categories, thresholds and effective dates across every jurisdiction becomes yours, and that is an ongoing commitment rather than a migration task.
What happens if our compliance provider changes its pricing?
Services in this category usually price on some combination of product count, jurisdiction count and submission volume, so your exposure grows as you launch products and enter markets rather than staying flat.
The protection is owning your inputs. A producer whose component master, provenance flags and allocation rules sit in its own system can change provider as a procurement exercise. A producer whose packaging data only exists inside the provider's platform is negotiating with nothing in hand.
How long does an EPR reporting build take?
Ten to sixteen weeks for a first release, and the timeline is set by data collection rather than engineering. The build is usually ready before the supplier data is.
Producers with existing structured packaging specifications move fastest. If your weights sit in supplier documents, start the outreach at kickoff rather than at handover and expect collection to run in parallel with development. Reconciling one prior submission end to end during discovery tells you more about your data than any workshop.
Are we over reporting or under reporting?
Over reporting, in our delivery experience, and it is the failure nobody catches because no regulator writes to say you paid too much. It happens because missing component weights and unknown recyclability statuses get conservative defaults, and those defaults accumulate across thousands of products.
The fix is provenance on every field so estimated values are visible. Take the share of your packaging weight currently carried by estimates and apply a conservative correction to last year's fees on those products. That figure is often larger than the build.
Does adding another jurisdiction cost much?
Far less than the first, provided the build treats jurisdictions as configuration. A jurisdiction is a record holding material categories, rate per tonne or per unit, effective dates, exemption thresholds and modulation adjustments, and adding one should be a task for a compliance analyst.
If a developer tells you a new jurisdiction is a code change, price every future rate revision into the total, because rates are revised annually at best. That one design decision is worth more over five years than most feature choices.
Can we keep our provider and build only part of this?
Yes, and for many producers that is the right answer. Keep the service for regulatory content and filing, and build the component master with provenance, the supplier portal and the allocation layer.
The value sits in the inputs rather than the arithmetic. A correct weight applied to a correct placed on market volume gives the right answer through any filing route, and a conservative default applied to a shipment figure gives a wrong answer nobody will ever correct.
Why is sales allocation such a large line item?
Because fees are owed where packaging is placed on market and your sales data records where you shipped. Distributor volumes may flow onward into several jurisdictions, exports need excluding on documentary evidence rather than assertion, and direct to consumer sales attribute by delivery address, which often sits in carrier data.
The allocation layer holds explicit rules per channel and per customer with supporting evidence attached to each. That evidence is exactly what an auditor asks for and exactly what a spreadsheet cannot show.
What does eco modulation modelling add?
Roughly $30,000 to $45,000 as a phase two block, depending on how many design variables you want to compare. It is a calculation engine rather than a report, because it evaluates a proposed packaging change across every jurisdiction at current and proposed volumes.
It is usually the feature that gets the project approved, since a product team can compare two closure options with the annual fee difference on screen. It also makes no sense until the component master is complete, which is why it belongs after release one rather than in it.
We already pay for Microsoft 365. When does building custom actually beat Power BI?
Keep Power BI for internal reporting; at $14 per user per month for Pro it is hard to beat for employee-facing analytics. Custom wins in three cases: you are showing dashboards to customers, since embedded Power BI is priced on capacity and gets expensive fast, you need a fully white-labeled experience inside your own product, or your team keeps fighting the tool to support a specific workflow. Most companies we build for keep Power BI internally even after launching a custom customer-facing dashboard.
Is Tableau worth $75 per user per month, or should we build our own dashboard?
If you have analysts who explore data visually all day, Tableau Creator at $75 per user per month earns its price, and Viewer seats at $15 keep the total reasonable for a small team. The math flips once you have hundreds of viewers or need dashboards inside a customer-facing product, because per-seat pricing scales with your audience while a custom build does not. Run the 3-year seat cost before deciding; that horizon usually makes the answer obvious.
What do I need to prepare before contacting an agency about a dashboard project?
Bring three things: a list of your data sources with who controls access to each, the 5 to 10 recurring decisions the dashboard should support, and examples of the reports or spreadsheets it will replace. That package lets an agency quote in days instead of weeks, and in our discovery work it cuts the audit phase roughly in half. You do not need wireframes or a technical spec; a good agency produces those with you.
Do I need a data warehouse before building a custom dashboard?
Not for a small build; a dashboard reading from 1 or 2 sources can query them directly or use a plain Postgres database as its store. You want a real warehouse like BigQuery or Snowflake once you are joining 3 or more sources, keeping history beyond what source systems retain, or serving many concurrent users. Adding the warehouse costs around 2 to 4 extra weeks and is usually the single best investment in the project's future.
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.
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.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
How do I vet an agency or developer for a BI dashboard project?
Ask them to walk you through the data model of a past project, not a portfolio of pretty charts, because dashboard failures are almost always data modeling failures. Good answers mention specifics like star schemas, dbt, incremental refresh, and how they handled a source schema change after launch. Then ask for a fixed-scope discovery phase with a written data audit as the deliverable, so you judge their real work for a small spend before committing to the build.
How does a custom dashboard handle compliance requirements like SOC 2, HIPAA, or GDPR?
A custom build gives you direct control over the controls auditors ask about: single sign-on, role-based access, audit logs, encryption, data residency, and deletion workflows. For HIPAA specifically, you can keep protected health information inside your own cloud account under a business associate agreement with your host instead of trusting a third-party BI vendor's handling. Expect compliance work to add 2 to 4 weeks and roughly 10 to 15 percent to the build, so raise it in the first conversation, not after design is done.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards 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 business intelligence dashboards 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 .
