Which Registration Dossier Pages Come From the Manufacturer

Ask the factory for one named, signed, page-numbered manufacturer technical package, and ask for a written statement of which pages it can issue and which it cannot. The manufacturer normally owns the pages that describe who it is and what it built: legal manufacturer identity and site list, product identification and configuration, the quality system certificate with its scope, verification and validation reports, the risk file, the manufacturing and process summary, final labels and instructions for use, regulatory history, and the signed declarations. You own the pages that describe your position in your own market: the application form, your importer or establishment details, translations, legalization or apostille, and the local administrative paperwork. A dossier rarely stalls because one page is missing. It stalls because the two stacks describe the same product differently, and the reviewer notices.

Draw the ownership map before you collect a single page

Treat the dossier as two stacks with a boundary that runs through every section. A page belongs to the manufacturer if only the manufacturer can issue it or sign it: certificates, test reports, the risk file, the manufacturing summary, the declaration of conformity, the final artwork. A page belongs to you if it exists because you are the applicant: the registration form, your licence, your establishment details, the local agent appointment, the translation, the legalization chain, the fee receipts. Everything else needs a decision, and the decision should be written down rather than assumed.

The practical way to draw that boundary is a page-level list that names an owner for each item. Not a folder of brochures, and not a folder of certificates either. Ask for the list with three columns: page name, who signs or issues it, and whether it exists today. That third column is the one that keeps a submission moving, because the answer to it is usually a mix of pages the factory already holds and pages that only exist once your order is frozen.

A single ISO certificate is not a technical file. It proves that a quality system was audited, not that your product was tested, classified, and labelled for your market. Treat it as one page in the stack, useful mainly because its scope tells you which products and which site the factory can claim. When buyers ask what documents are required from the manufacturer for product registration, the honest answer is a stack of roughly thirty to sixty pages spread across six sections, and only some of them come from the factory.

Request it in stages, beginning before the order

Most stalled submissions were assembled in the wrong order. The technical package was requested at the end, when the container was already booked, and the factory then had to find, sign, translate, and legalize pages while a vessel waited. Move the request to the front and split it across three moments, so that the manufacturer provided documents for regulatory submission arrive as a planned set rather than as a trickle.

At the quotation stage, ask for the page list described above, the scope page of the quality certificate, two or three sample controlled documents so you can see the format, and a short written availability statement saying which pages the factory can release to you, which it can release only to an authority, and which it does not hold because a supplier or a contract laboratory keeps them. None of this requires a contract, and none of it commits you to an order.

At order confirmation, freeze the configuration and ask for the controlled copies: the authorization letter that names the exact models, the manufacturing sites, the territory, and the validity period; the complete product identification file; the full reports behind any summary you were given earlier. What you are buying here is a snapshot that matches the units being built, not the catalogue.

Before shipment, ask for the as-built confirmation, the label and instructions revision that will actually travel with the goods, and a change statement listing anything that moved since the supporting reports were issued. A page that says the product is unchanged is worth more than a page that repeats the specification, because it is the page that answers the reviewer’s first question.

Legal manufacturer, sites, and the letter that authorizes you

The name printed on your label has to be the name on the certificate, the name in the dossier, and the name in the authorization letter. Where a factory builds for several brands, the legal manufacturer is not always the company that answers your emails, and a certificate issued to a related entity or to a different factory will not support your registration. Ask directly: who is the legal manufacturer for this configuration in this market, and is that the same entity named on the documents you are sending me?

Next, list every site that touches the product. Component machining, welding, painting, assembly, software loading, packaging, labelling, testing, sterilization, and warehousing can sit at different addresses, and regulators ask for the addresses of the sites involved in producing the device. If a page names a site you did not declare, the reviewer will ask why, so collect the site list before you write the application rather than after.

The authorization letter deserves its own check. It should identify you by legal name, name the product and the models or catalogue numbers it covers, name the manufacturing sites, state the territory and the validity period, and describe what you are authorized to do with the documents, which normally means submit them to the authority and reference them in your application. It needs a signature from someone with the authority to bind the company, a printed name and title, a date, and letterhead. A one-line letter on plain paper is the cheapest page in the dossier and the most common reason a reviewer stops reading.

For the quality system page, ask for the certificate with its scope, not the decorative front sheet. The scope is where you see whether the audited activities actually cover the product family and the site you are importing from. If the factory holds an ISO 13485 certificate, that scope page also tells you the issuing body and the expiry date, both of which belong in your ledger.

Evidence pages: reports, risk file, and the model they cover

Ask for full reports rather than one-page summaries, and read them for the four items that make a report usable: the tested model, the sample or serial number, the method and acceptance criteria, and the name and signature of the person who approved the result. A report that cannot be tied to the exact configuration you are registering is evidence for a different product, however impressive the cover page looks.

Where a report or a declaration cites a standard, the cited edition has to match across the pages that mention it. That single mismatch, between a report issued against one edition and a declaration written against another, generates more reviewer queries than almost anything else in the technical stack.

For medical equipment, the evidence stack usually includes electrical safety and electromagnetic compatibility reports, a risk management file, and, where the device is supplied sterile, sterilization and packaging validation. Patient contact materials bring their own documentation. Transport, shelf life, and cleaning instructions round out the list for the items that are cleaned or stored between cases. A risk management file follows the same logic in most markets, and distributors are asked for it often enough that it is worth treating as a standing request rather than a surprise; our note on ISO 14971 risk management files covers what such a file contains and how to check that it covers your configuration.

Some factories will not hand over process detail, and that refusal does not have to end the registration. Ask whether the page can be submitted through a confidential manufacturer file that the authority holds and references, with a letter authorizing the authority to use it in support of your application. The page still has to exist and still has to be current, but it does not have to sit in your folder.

Labels, instructions, and the configuration you register

Final artwork is the part of the stack most likely to be out of date, because labels change for commercial reasons long before anyone tells the registration team. Ask for the primary and secondary labels, the instructions for use, the packaging artwork, the symbols, the lot, batch, and expiry formats, and the language that the market accepts. Where the market requires editable files for local language versions, ask for the source file rather than a flat image, and agree in advance who translates and who certifies the translation.

Then run one comparison across the whole stack. The intended use, the indications, the warnings, and the model numbers should read the same in the technical file, the certificate or its annex, the label, the instructions, the product brochure, and your application form. Promotional wording is not exempt: a marketing claim that reaches past the intended use recorded in the technical file becomes a reviewer question about which version is true.

The configuration you register and the configuration you import are the same thing. If the factory changes a component, a supplier, a site, or a label revision after the reports were issued, the affected pages have to change with it. Ask the factory to state, in writing, whether the product supplied under your order is unchanged from the product described in the pages you are submitting. That statement costs the factory one paragraph and saves you a round of correspondence with the authority.

Build a page ledger, then freeze the revision

Keep the whole exercise in one table, because the alternative is a submission assembled from memory. Use a row for each page and columns for the dossier section it answers, the page name, the owner, the signer, the revision number, the effective date, the expiry date, the language, the legalization status, and the open question about it. Add a column for the regulator checklist item the page answers, so that you can see at a glance which requirement has nothing behind it yet.

Before submitting, compare the pages against each other for the faults that reviewers find most often: a manufacturer name or address that differs between a certificate, a label, and an authorization letter; a model number that appears on the order but not in the certificate scope; a certificate, authorization letter, or free sale document that has expired; a report issued for a different model, site, or process; instructions that do not match the units being shipped; and missing signatures, translations, legalization, or confidentiality markings.

Keep the shipping and commercial pages out of the registration file. The invoice, the packing list, the certificates of origin, and the wood treatment marks belong to the export pack, and mixing them into a dossier confuses the reviewer and your own index. If you are dividing responsibilities for those, our note on the export document pack sets out who normally prepares which page and where the handovers happen.

Finally, agree a revision freeze. Tell the factory that once a page is submitted you want advance notice of any change, with the reason and the new revision number, and give them a single named contact who owns the dossier on their side. Practical guidance on compiling a registration dossier manufacturer section comes down to one habit: send the factory your regulator’s checklist, ask them to map their existing pages to it line by line, and ask them to flag in writing anything they cannot supply. Decide what to request from the factory for a product registration dossier once, in writing, and reuse that list with each new product and each new market, because the pages that the manufacturer owns do not change shape between regulators even when the forms do. Gaps you know about in week one are solvable. Gaps the reviewer finds in month six are the ones that cost you the season.