Product information
Can you find identifiers, variants, materials and manufacturer details without hunting through emails and old files?
Buyer guide
Choose the simplest setup that will still hold together when products, suppliers and published information start to change.
You may not need specialist software on day one. A spreadsheet can be perfectly sensible for a handful of products. The point is to notice when the manual setup is starting to cost more time than it saves.
Before you compare tools
A DPP is not just the page a customer sees. The harder part is usually the information behind it: where facts came from, who can update them and what was published before.
Can you find identifiers, variants, materials and manufacturer details without hunting through emails and old files?
Can you show which specification, declaration or certificate backs a fact without making private documents public?
Can you update a Passport without changing the QR destination, and can you still see the version customers saw before?
Will one person manage it, or does information need to come from suppliers, Shopify, an API or other internal systems?
Four common approaches
The right choice depends on how many products you have, how often the information changes and how important it is to keep a clear record of what changed.
When it can work well
A good starting point for a very small catalogue, especially when one person manages it and the information rarely changes.
What to check
Watch how many copies of the same fact you create. Public pages, source documents and old versions can become difficult to keep in step.
When it can work well
Useful when the main job is to put a simple public product page behind a QR code.
What to check
Check whether it can keep private source material, structured product data and published history separate from the public page.
When it can work well
Useful when product records, supporting documents, checks and publishing need to live in one workflow.
What to check
Check how the provider handles changing regulation, data export, older published versions and pricing as your catalogue grows.
When it can work well
Makes sense when you have large catalogues, several internal systems, complex supplier networks or a formal implementation team.
What to check
Check the implementation effort as carefully as the feature list. More capability is not automatically better if the day-to-day workflow becomes harder.
When manual starts to hurt
Plenty of businesses should start in a spreadsheet. The warning signs are practical, not technical: the same information appears in several places, updates take too long, or nobody is quite sure which source is current.
Questions for any vendor
Feature lists can make every platform sound the same. A short walkthrough of the real workflow usually tells you much more.
Show me what stays private and what becomes public.
Show me an old published version after the product has changed.
Show me what happens to the QR link when I publish an update.
Show me how missing information is handled. Does the tool leave a gap, flag it or encourage a guess?
Show me how a supporting document is linked to the fact it supports.
Show me how I can export my product data if I need to move it elsewhere.
Explain what makes the price go up: products, users, languages, scans, integrations or something else.
Tell me what happens to an existing published Passport if I stop paying for the service.
Where Madeivo fits
It is designed for small and growing product businesses that need a repeatable DPP workflow without turning DPP preparation into a large systems project.
Probably a good fit if
Probably not the right fit if
This guide is about choosing software. It does not decide which legal requirements apply to a particular product or business.
Start with the free readiness check. It shows how organised your product information is, and you do not need to give us an email address to see the result.
Help us improve Madeivo
We count public page views without an analytics cookie. If you allow analytics, we also use first-party visitor and session identifiers to understand journeys, traffic sources and conversions. No advertising profiles or browser fingerprinting.
Read the cookie details