
Award categories: Global SME Awards
For many small and medium-sized enterprises, product-safety paperwork lives in a folder and is opened only when a customer complains or an inspector arrives. A supplier declaration is filed at onboarding, a batch reference is written on a delivery note, and responsibility for a product is assumed to be understood. The arrangement works until someone asks a specific question and no one can answer it quickly.
Those questions now arrive through more channels than before. An online marketplace asks for a responsible contact before a listing can stay live. A corporate buyer adds a product-safety section to its supplier questionnaire. A regulator requests evidence that a batch can be traced to its source. Each request is modest in isolation. Together they represent a shift: product-safety documentation has become a condition of market access rather than a back-office obligation.
For a lean business, the response is not a compliance department. It is a small, maintained evidence file that can be produced when needed and reused across several audiences.
The current pattern is broader than the formal inspection regimes that product-safety scrutiny has traditionally been associated with. Marketplaces that host third-party sellers have become gatekeepers in their own right. To keep a listing active, a seller may be asked to identify a responsible person established in the relevant market, provide contact details and confirm that documentation exists. Platforms carry reputational and legal exposure for products sold through their systems, and face pressure to police listings more actively.
Corporate buyers have moved in a similar direction. A large customer onboarding a small supplier increasingly asks not only whether a product complies but whether the supplier can demonstrate it: a named contact, supplier declarations, batch references and a route for raising concerns. The questionnaire may be short, but it assumes the answers exist somewhere.
Regulators, meanwhile, ask for information in a more targeted way. Rather than inspecting every product, they may request records for a specific batch or listing. A business that can respond within days has a different experience from one that must reconstruct its supply history from emails and invoices.
An evidence file does not need to be elaborate. Its value lies in being current, consistent and quick to retrieve. Four areas cover the essentials.
Many markets require a named economic operator who can be contacted about a product. For an SME, this is usually a director, a quality lead or an authorised representative. The file should record who holds the role, how they can be reached, which products or markets it covers and what happens when the person leaves. A contact that no longer works is worse than none.
Where a product is sourced from a third party, the file should hold the declarations, test reports or conformity documents the supplier has provided, with the date they were received and the version they relate to. Documents expire, products change and suppliers update their paperwork. Recording version and date prevents an old certificate being presented as current.
Traceability depends on connecting a finished product to the materials or components that went into it. A small business does not need a sophisticated system, only a consistent reference that appears on purchase records, packing notes and customer orders. Where a product is bought and resold unchanged, the supplier's batch reference and the date of receipt are the minimum.
For businesses selling online, the product listing is part of the safety record. The file should capture what the listing claimed, which market it was published in, what warnings were displayed and when it was last reviewed. If a listing is later questioned, the business can show what it said and when.
The most common way a routine query becomes a crisis is not a missing document but a slow or inconsistent response. A customer reports a fault, the message sits with a sales contact, a supplier is asked for information and no one owns the answer. By the time a decision is taken, the issue has reached other customers or been raised publicly.
An evidence file should therefore include a short escalation route. It does not need to be a procedure manual. It needs to state who receives a product-safety query, who decides whether a batch should be paused, who contacts the supplier and who speaks to customers, and it should record a holding response that acknowledges the query and gives a point of contact.
Customer communication is part of the same discipline. If a product is questioned, the business will need to identify which customers received it, which is only possible if order records match batch references. Building that link in advance turns a recall from an exercise in reconstruction into a bounded, documented action.
A useful test is to pick one product and one complaint and trace the path from the order back to the supplier. If it takes several people searching their inboxes, the gap is visible before an incident exposes it.
The same records serve several purposes. Marketplace onboarding asks for a responsible contact and confirmation that documentation exists. Buyer due diligence asks for supplier declarations and traceability. A regulator asks for records relating to a specific batch or listing. These are different questions drawn from the same source.
That is why a single evidence pack, organised around products rather than requests, is more efficient than answering each questionnaire from scratch. A simple structure works: one folder or shared drive per product, holding the responsible-person record, supplier documents with dates and versions, batch references, listing evidence and the escalation contact, plus an index page stating what is held and who owns each item.
Maintenance matters more than sophistication. A quarterly check that confirms contacts are current, documents have not expired and listings still match the product is enough for most small businesses. It should be assigned to a named person and recorded, so the business can show when it was last done.
Product-safety documentation is often described as a burden. In practice, it falls hardest on businesses that treat it as paperwork to be produced after the fact. A small, maintained evidence file reduces the disruption of a questioned product, a suspended listing or a buyer's audit. It also gives the business something more durable: the ability to answer a specific question quickly, with a record behind the answer.