DEV Community

Gavren
Gavren

Posted on

The Buyer Asked for an MHRA Certificate and Received a Registration Number

The first email from a UK buyer is usually blunt: please send your MHRA certificate. What goes back leaves a few seconds of silence — a registration number, not a stamped document. Nobody is being evasive. Two vocabularies have collided on one word. On this route a device is registered first and accepted by the market second.
Why does the word certificate mislead?
The mismatch concentrates on UK buyers because their compliance checklist templates mostly descend from the EU era, with certificate, notified body and declaration of conformity listed side by side. The market changed and the checklist did not, so the first line of that list has no counterpart on this route at all.
Because in most markets the language of access is certification: submit samples, test, issue a certificate, apply a mark. The entry step here is not the issue of a certificate. It is the recording of the device and the manufacturer in the regulator's system, which yields a searchable registration status.
Registration establishes that the information has been recorded. It does not establish that the device has been judged against a set of standards. In procurement files both are compressed into one phrase, compliance evidence, so the buyer believes a conclusion has arrived when what arrived is a filing.
A usable reply splits the certificate into three items: the registration status and number with the date checked, who holds the UK responsible person role, and which channel the label and documents follow. Supply all three and the buyer's checklist usually moves.
The practical consequence for a manufacturer is direct: what can be supplied is registration information and a number, not a signed certificate. If the contract says provide an MHRA certificate, that clause became impossible to perform on the day it was signed.
Who is the UK responsible person, and what do they carry?
A manufacturer outside the UK appoints a responsible person inside the UK. This is the most underestimated element of the route. It is not a letter of authorisation; it is a specific entity the regulator can locate, require information from, and require cooperation from when something goes wrong.
A termination clause belongs there too: how long the term runs, how much notice applies, and how documentation is handed over when it ends. Change the responsible person and the name on the label may change with it, and that cannot be left to the other party's initiative.
In practice the role is often held by the local importer, an agency, or a specialist responsible-person service. Choosing one is not only a price question. Two things matter more: whether it can produce documentation within days of a regulatory request, and whether its contract states when it must notify you.
The common misreading treats it as a customs agent or a sales representative. A customs agent deals with how the goods enter; the responsible person deals with who is answerable once the device is in the market and a problem appears. One company can perform both roles, but the obligations are not the same set.
Technical documentation deserves its own line. The file lives at your plant, but a request for it usually reaches the responsible person first. That means it has to be retrievable on short notice rather than sitting on one engineer's laptop, and the scans, index and revision numbers have to agree.
Reduced to an executable sentence, the arrangement needs three parts: who holds the role, the term and the termination condition, and the events that require replacement and notification. A line saying a responsible person has been appointed states nothing that can be checked.
Why is the Northern Ireland route different?
Transitional arrangements are the least safe thing to write from memory. Rules of this kind carry transition periods and cut-off dates, and one wrong date invalidates the whole paragraph. Any sentence involving a date should carry the date it was checked.
Great Britain and Northern Ireland run on two different channels. Northern Ireland follows the EU device rules, so marking and documentation follow the EU system; Great Britain follows the UK registration and marking system. The same unit off the same line, sold into both places, may travel with two different document packs.
The label is where this goes wrong most often. If one model ships to both markets, a mixed batch on the packing line will send wrongly marked goods to the wrong destination, and correcting it means repacking and re-declaring — far more expensive than separating the lines from the start.
This is not a footnote. It decides how the label is printed, which requirements the technical file is organised against, and who carries which obligation. Writing the two together is the most common error in this subject, and the price is a consignment held at the port for missing paperwork.
One practical caution: never put an unchecked cut-off date into a note to a customer. A wrong date damages credibility more than no date at all, and the buyer remembers it at the next quotation round.
So the specification is best split by market: one section for Great Britain, one for Northern Ireland, one for the EU. It reads longer and it removes the re-confirmation that otherwise happens before every shipment.
How should the unverified parts be written?
The rules on this route change, and on a public page the update date matters more than the prose. Where a statement cannot be pinned to a current source, write it as requiring verification against the current official page, with the date recorded.
Buyer checklists also tend to ask for a declaration of conformity. What it can state, who signs it and whether it travels with the goods or stays on file are all items to verify; treating it as the same thing as registration is the second most common confusion here.
The record does not need to be elaborate. One table suffices: item, source page, date checked, who checked it, and the conclusion as confirmed or pending. In a customer audit that table does more work than any verbal explanation.
Three habits cover most of it. Every institutional statement carries a source page and a date checked. Any process described verbally is confirmed in writing with a date. Any clause that creates an obligation is finalised only after the UK responsible person has confirmed it.
For the contract itself, one sentence is enough: the supplier provides, for the market the buyer names, a document pack that can be verified as current, with form and content following the requirements in force. It promises an action and its currency rather than a document.
Which six items should be checked?
The table below is the only one here: the item on the left, the common misreading in the middle, and what actually has to be verified on the right.
| Item | Common misreading | What to verify |
|---|---|---|
| Access document | Believed to be a stamped certificate | Registration status and number, checked against the current official page with the date recorded |
| Responsible person | Assumed to fall on the importer automatically | Appointed by the manufacturer outside the UK; scope of duties checked against current guidance |
| Label and marking | Assumed one mark covers the whole UK | Great Britain and Northern Ireland differ; verify each separately |
| Technical documentation | Assumed to stay at the factory | The responsible person must be able to supply it; agree where it is held and how retrieved |
| Changes | Assumed one registration lasts indefinitely | Update obligations after a change of manufacturer or device must be verified |
| Distribution roles | Assumed every distributor appoints a responsible person | Obligations differ by role; verify each against current guidance |
That table is worth running before every shipment rather than once. Ten minutes changes the label and documents for this consignment; run once, it changed the batch in front of you and nobody looked again. Work through the six and you hold a dated record instead of a sentence saying the customer asked for a certificate.
FAQ
Does the MHRA issue certificates?
On the public guidance, the action on this route is registration. Whether any document is issued separately, and in what form, has to be checked against the current official page. Do not write a contract that presumes a format you have not seen.
We are the factory. Can we act as the responsible person ourselves?
The role sits inside the UK. A manufacturer outside the UK normally appoints a local entity, and the eligibility and duties should be verified against current guidance before any label carries that name.
Can goods for Northern Ireland use the Great Britain documents?
Do not assume so. The two channels derive from different rule sets, so marking and documentation differ and have to be prepared separately, including the label artwork and which version of the technical file each points at.
What happens after registration?
Registration is not the end point. Update obligations when the device or the manufacturer changes, and cooperation obligations after placement, are for the responsible person to confirm. Put those obligations in your contract with that person.
Statements about the regulatory framework here are verification prompts rather than compliance conclusions; access and declaration obligations must be confirmed by the UK responsible person or a qualified regulatory affairs professional against the current official pages.

Top comments (0)