Documents everywhere.
Test reports, declarations and specifications spread across inboxes, drives and spreadsheets.
FRAGMENTED EVIDENCEThe evidence workspace for European importers and brands. Connect product documentation, supplier requests and expert review before your next market move.
Built for importers, brands & product teamsNew markets. More suppliers. More documents. When everything lives in separate folders and inboxes, a simple question becomes a search mission.
Test reports, declarations and specifications spread across inboxes, drives and spreadsheets.
FRAGMENTED EVIDENCETeams chase suppliers for the same information, with little visibility into who owns the next step.
DISCONNECTED WORKFLOWSMissing evidence surfaces late. Decisions are hard to trace. Market entry becomes a moving target.
UNCLEAR PRODUCT STATUS
Bring the whole picture together.
From the first document to the final review.
A product stays connected to its sources and owners at every step. Your reviewer keeps the final judgement.
Define products, intended markets and an evidence checklist.
Link documents and source references to the right product.
Give supplier requests a clear owner and a visible next step.
Keep expert decisions, context and outstanding questions together.
Connect every product to its evidence, every gap to an owner, and every decision to a record.
Every product. Every next step. In one place.
| Product | Market | Readiness ⓘ | Status | Updated | Details |
|---|---|---|---|---|---|
| Loading demo products… | |||||
Test report received Lumen Works · Arc desk lamp
Evidence request sent Everwell Supply · Everyday bottle
Clear requests. Named owners. Visible next steps.
Arc desk lamp · Electrical test report
Everyday bottle · Material declaration
Form lounge chair · Updated specification
Requests link directly to products and missing documents. This demo shows an illustrative workflow; no supplier messages are sent.
See what changed, who reviewed it, and what comes next.
Version 2 · Lumen Works · 4 Oct 2026, 09:42
Version 1 · Alex Morgan · 3 Oct 2026, 16:10
Electrical test report added. Evidence checklist updated. Technical review remains pending.
Requested document received. Technical review remains open.
Requested an updated report matching the product model.
Take a closer look. Work through a product, request missing evidence and record a demo review.
Open demo workspaceFictional companies and sample records. Local demo actions reset on reload. Readiness is not a legal assessment.
Organise product evidence, surface key fields and flag gaps for review. Keep the original document close to every extracted detail.
Assisted extraction. Human judgement.Model: AL-204 / Report: DEMO-AL-204-TESTING
Request missing evidence, assign ownership and keep supplier follow-ups connected to the right product.
See evidence completeness at a glance. Understand what is missing before your team makes its next decision.
A readiness signal, not a compliance guarantee.Build a reusable product data foundation for future Digital Product Passport workflows. Requirements vary by product and market.
Keep versions, evidence references and review history together. Make your process easier to explain and revisit.
Keep qualified reviewers in control. Surface exceptions, record decisions and distinguish evidence readiness from a final assessment.
“Model reference matches. Please confirm the intended market before completing review.”
Review in progressProduct information is business-critical. Define access, review responsibilities and data handling requirements before your pilot begins.
Discuss your requirements Security controls and availability are confirmed before a pilot begins.Scope workspace roles, supplier visibility and reviewer permissions around your team's needs.
Plan for document provenance, version history and accountable review workflows.
Discuss retention, hosting, identity and data export requirements with your pilot team.
Start with the data you already have. Scope the right connections for your systems, without adding another information silo.
Integration availability is confirmed during pilot scoping.“One place to see what we have, what we're missing, and who needs to move next. That's the visibility a product team needs.”
“The real value is the connection between a product, its documents, and the decision behind it. Nothing gets lost in an inbox.”
These quotes demonstrate intended use cases. They are not customer endorsements.
Bring a real collection, a small team and a clear objective. Together, define what a successful MarketPass pilot should look like.
Pricing based on product volume, workflow complexity and support requirements.
Importers, brands, retailers and product teams that need a clearer view of product evidence, supplier requests and market readiness across their portfolio.
No. The score indicates evidence completeness against a defined checklist. It is not a legal assessment, certification or guarantee of market access. Qualified review remains essential.
The product concept supports assisted extraction and organisation of document information. Extracted fields should be checked against source documents by your team. Pilot scope determines supported document types and workflows.
MarketPass is designed to help structure product data and supporting evidence for future DPP workflows. Product-specific requirements and implementation needs must be assessed separately.
A representative product collection, available evidence, a named team owner and an initial goal. Scope, timing, pricing and technical requirements are agreed before starting.
This website presents an interactive product concept. All companies, products, people, activity, scores and testimonials shown are fictional demo content. The workspace uses fictional data in memory. Requests and reviews are simulated locally; no supplier messages are sent.