SupplierChase: Compliance Document Chasing for UK Importers

Opportunity snapshot

SupplierChase is a tool for small UK importers that tracks which compliance documents each supplier has been asked for, has sent, or still owes, chases them with approved reminder emails and files every version against the right product and model. It is an idea report: the tool is not built, and this page gives the research, the verdict and a free build prompt so anyone can build it.

Executive summary

SIGNAL: GOV.UK guidance says businesses that make, import, distribute or sell consumer products in the UK are all responsible for their safety. Manufacturers and importers are told to generate and keep records of technical documentation, and retailers must keep records identifying the suppliers of the products they sell so origins can be traced.

SIGNAL: for electrical apparatus under the Electromagnetic Compatibility Regulations 2016, the official guidance says the importer must keep a copy of the declaration of conformity and the technical documentation for 10 years after the apparatus is placed on the GB market. Other product rules set their own periods. Either way this is a records job that lasts years, not a one-off upload.

SIGNAL: ProductIP, a supplier-document and technical-file platform, publishes an Essential tier at €55 per credit, an Advanced plan at €1,750 a month and a Professional plan at €6,450 a month (excluding VAT). Expiration Reminder, a generic document-expiry tool, is listed on Capterra from $49 a month. Compliance services such as EcoComply sell written assessments from €399 per product.

ASSUMPTION: small importers who already know which documents they need lose real time chasing suppliers, matching files to the right model and finding the latest version, and would pay £19 to £99 a month to stop. No interviews, search data or payments have been collected yet.

Where this idea came from: the gap between what UK guidance asks importers to keep and the tools priced for brands and retail chains. The Office for Product Safety and Standards published 571 product safety reports and 244 product recall notifications in its 2025 to 2026 delivery year. Those figures count government publications, not software buyers, but they show the area is actively policed.

The problem: paperwork that arrives late, wrong or not at all

A supplier promises a test report by Friday. Another emails a certificate for last year’s model. A third sends a PDF with no product identifier on it. When a marketplace, a retailer or a Trading Standards officer asks for evidence, the files are spread across inboxes, a shared drive and a spreadsheet nobody has touched since spring.

The legal side is not the gap. Consultants and compliance services already sell help deciding what a product needs. The gap is operational: who was asked for what, when they replied, which version was accepted and who reviewed it.

The tool

The core is a status register. A user imports a CSV of products and supplier contacts, picks the document types they already know they need, and assigns a reviewer. Every request then carries one of seven states: not requested, requested, received, under review, accepted, rejected or expired. Reminder emails are drafted on a schedule and sent only after the user approves them. Suppliers upload through a single-purpose link that expires and cannot see the rest of the account. The output is an exportable evidence index showing what has been collected, what is missing, when each file arrived and who reviewed it.

A worked example, using hypothetical figures: an importer sells 80 household products from six suppliers and needs three document types per product, which creates 240 requests. SupplierChase shows that 12 products are missing at least one document and drafts six follow-up emails, one per supplier, each listing what is still owed. These figures illustrate the workflow and are not results from a real customer.

ASSUMPTION: the tool never decides what a product legally needs and never shows a “compliant” badge. A reviewer, the importer or their consultant, accepts each document. If the tool implied compliance wrongly, the legal risk would land on its customer.

Competitors and pricing

The opportunity and the gap

The gap is price and scope:

• a wide price gap between $49 generic reminders and supplier-compliance platforms at €1,750 a month and up;
• generic expiry tools do not understand products, models, batches or per-supplier chasing, while full platforms bundle technical-file building and expert services a small importer may already buy from a consultant;
• consultants are a channel, not a competitor: they decide the requirements, SupplierChase does the chasing and keeps the trail across all their clients;
• the wedge is supplier follow-up first, with per-supplier or per-product pricing and clean emails suppliers actually answer.

None of this is a moat. ProductIP or a reminder tool could add a lighter tier, so speed and a consultant channel matter.

Monetisation (hypotheses, not built)

ASSUMPTION: buyers pay a monthly subscription. Proposed plans: Starter £19/month for one user and a small catalogue, Team £49/month for several reviewers and supplier reminders, Agency £99/month for consultants working across clients. At £49 a month, 20 customers would produce £980 of monthly recurring revenue before hosting, support, payment fees, insurance, acquisition and tax.

An importer that chases documents only twice a year may prefer a one-off setup service, an annual audit or a per-supplier fee, so the manual pilot should test service pricing as well as a subscription.

MVP

To build

• A CSV import for product names, identifiers and supplier contacts.
• A request register with status, due date and assigned reviewer.
• Single-purpose supplier upload links that expire and cannot see the rest of the account.
• Scheduled reminder drafts, sent only after the user approves them.
• A downloadable evidence index and activity history.

DON’T BUILD YET

• AI-written declarations, automated legal conclusions or any product safety score.
• A requirements engine that tells users which documents a product needs.
• PDF extraction of model numbers. Useful later as an unverified flag for a human reviewer.
• Integrations with marketplaces, ERPs or accounting tools.

Risks

• ProductIP and similar platforms already cover supplier requests, so the difference has to come from price and simplicity.
• Requirements vary by product and market, and any hint that the tool certifies compliance is a liability.
• Test reports, designs and supplier details are sensitive, so access controls, backups, retention rules and a deletion process are needed before the first real customer.
• Some importers chase documents only occasionally, which favours a done-for-you service over a subscription.
• Small importers are fragmented and costly to reach directly; consultants are the cheapest route found.

Kill criteria and 30-day validation

This is a B2B idea, so the test is paid pilots, not traffic. The thresholds below are proposals, not proof of demand.

1. Days 1 to 10: book ten to fifteen calls with UK importers and independent product-compliance consultants. Ask them to show how they collect supplier documents today, with confidential details removed, and count how many documents are outstanding right now.
2. Days 5 to 15: offer the manual pilot at a small fixed fee. Do not handle customer files until security and contracts are ready.
3. Days 15 to 30: run the pilot for whoever pays, and log every request for automation in their own words.

Pass: at least three organisations pay for the pilot and their workflows substantially overlap, or at least one consultant wants to run it across several clients.

Kill: fewer than three paid pilots, most prospects chase documents less than quarterly, or prospects keep asking whether their products are compliant. That means they want advice, not software.

Founder fit

Good fit for someone who already knows UK product compliance or has a consultant partner, is comfortable with patient B2B sales calls and takes data security seriously. Poor fit for someone hoping to ship a quick self-serve SaaS from search traffic, because the buyers are hard to reach and slow to trust a new tool with sensitive files.

Final score

Total: 70/100. Research confidence: 50/100. Verdict: 🟢 PROMISING.

🛠 FREE AI BUILD PROMPT

COPY BUILD PROMPT

You are a senior front-end engineer. Build "SupplierChase Register" as a single self-contained page in plain HTML and vanilla JavaScript.

PRODUCT PRINCIPLE
One job: show which compliance documents each supplier still owes a small UK importer, and draft the follow-up emails. It tracks documents only. It must never state or imply that a product is legally compliant. Say so in the footer of every screen.

DATA
Store everything in localStorage under one versioned key. Wrap every read and write in try/catch and show a visible error banner if storage fails or is full.
Products: id, name, SKU or model, supplier id.
Suppliers: id, name, contact email.
Document types: a user-defined list, for example test report, declaration of conformity, instructions.
Requests: id, product id, document type, status (not requested, requested, received, under review, accepted, rejected, expired), due date, reviewer name, file reference (text only, a filename or shared-drive path, no uploads), notes, and a history of timestamp, from status, to status and user.

RULES
1. CSV import for products and suppliers with a preview step. Validate headers, report row-level errors (missing name, invalid email, duplicate SKU) and import only valid rows.
2. Generate requests by applying chosen document types to selected products, skipping duplicates.
3. Accepted and rejected need a reviewer name. Accepted also needs a file reference. Every status change appends to history.
4. Follow-up drafts: one plain-text email per supplier with outstanding requests, listing product, model, document type and due date. Show it for editing with a copy button and a mailto link. Never send automatically.
5. Export an evidence index CSV (product, model, document type, status, file reference, reviewer, last change) and a full JSON backup. Importing a backup validates the schema and asks before overwriting.

PRIVACY
Run entirely in the browser. No network calls, no analytics, no file uploads. Escape all user text before inserting it into the page.

TESTS
Write test cases first and work out the expected results by hand. Cover CSV parsing with quoted commas and bad rows, every allowed and blocked status change, duplicate request generation, an empty catalogue, storage full, and the exported CSV for a known sample of 3 products, 2 suppliers and 2 document types.

DO NOT BUILD YET
Accounts, supplier upload links, automatic email sending, PDF reading, AI checks or any compliance verdict.

Sources

• GOV.UK, product safety advice for businesses
• GOV.UK, Electromagnetic Compatibility Regulations 2016 (Great Britain) guidance
• GOV.UK, OPSS Delivery Report 2025-2026
• ProductIP, service overview and prices
• ProductIP, platform features
• DocBits, supplier portal
• Capterra, Expiration Reminder listing
• EcoComply, pricing

Research date: 2 November 2026. Guidance and prices come from the linked pages as read on that date; prices exclude VAT where stated and may change. Two competitors named in the original draft (ProductCompliance.com and DPP Grid) could not be verified and were left out. No keyword volumes were collected and Google positions were not checked. The worked example uses hypothetical figures. No customer interviews, conversion rate, market size or revenue forecast has been invented. Nothing here is legal advice on product compliance.