A manual is not paperwork accompanying the product. In European product law it is part of the product, which has a consequence most exporters have never been told: if the information that makes the thing safe to use cannot be read by the person using it, the product is non-compliant even though the product itself is perfect. Nothing has to break. An inspector who finds a machine with instructions only in English, in a country whose language is not English, has found a defect, and the correction happens on the pallet rather than in the next production run.
Which language does the manual have to be in?
The rule is written from the user's side, not the exporter's: safety information and instructions must be supplied in a language easily understood by users in the member state where the product is made available. The Union does not name the language. Each member state does, in its own transposing rules, and the answers differ — some accept more than their national language, some demand the national language only, and some treat consumer products more strictly than professional equipment. Which means your language list is a function of your distribution map, redrawn every time a distributor in a new country places an order, and not a property of the product. The practical consequence is that the question belongs to whoever opens markets, who has to answer it before the print run and not after.
A single multilingual booklet covers several markets at once and is the normal industrial answer, right up to the point where it becomes unreadable. The same sentence repeated down a column of languages, set in a size nobody reads, with the warning that matters to this particular user buried in a block they will not find, satisfies a checklist and fails the purpose. Some member states object to that form for exactly that reason. The workable compromise is to group the booklet around the markets you actually serve rather than every language you might one day need, to keep the safety section at the front in each language instead of at the back of a sequence, and to let the long reference material — detailed maintenance, exploded views, specifications — live somewhere the user can reach but does not have to carry.
Can we put the manual online instead of in the box?
Sometimes, and the answer depends on the category rather than on your logistics. Digital instructions are accepted for some product categories under conditions that are always the same in shape: the information stays available for the life of the product, the product or its packaging carries a visible way to reach it, and a paper copy is supplied on request at no extra cost and within a short time. For other categories digital is not an option, and almost everywhere the safety part — warnings, residual risks, what to do when something goes wrong — is expected on paper in the box, on the reasoning that a user who needs a warning may have no network and no device. Consumer products are treated more strictly than equipment sold to professionals. Settle this per category from the family's own text; arguing it with a distributor who already knows the answer wastes the only person who was going to tell you.
What has to be in the manual
- The intended use, stated plainly. What the product is for, in what conditions, within what limits of load, environment and user. This sentence is the one everything else is judged against, including whether an accident happened inside or outside the use you described.
- The uses to rule out. Foreseeable misuse, named explicitly, because a risk you could have predicted and did not warn about is treated as a risk you accepted. This is the section an exporter is most tempted to shorten, and the one a liability claim reads first.
- Warnings and residual risks. What remains dangerous after the design has done what it can, where it is, and what protects the user. Each warning says what the hazard is, what happens if it is ignored, and what to do instead.
- Assembly, installation and connection. The steps, the order, the tools, the torque where it matters, and the checks before the first use. Written for the person who will actually do it, who is often not the person who bought it.
- Use, maintenance and the parts that wear. How it is operated, what has to be cleaned, inspected or replaced, what a user may do and what requires a professional. The line between those two is where most warranty arguments start.
- Disposal at the end of life. How the product is taken out of service, what has to be removed before it is discarded, and which collection channel it belongs to. This paragraph is short and it is checked.
- Who made it and who answers for it here. The manufacturer's name and postal address, and the name and address of the party established in the Union who is responsible for the product. A contact form or a mailbox is not an address, and this is the easiest non-conformity in the whole document to spot from outside.
Pictograms, and why they are not decoration
A safety symbol is a sentence written in a code the user has been taught, and that only works if you use the code rather than invent one. Standardised symbols have defined shapes, defined colours and defined meanings, and the shape carries part of the message — a prohibition does not look like a warning, which does not look like a mandatory action. An icon drawn by your designer to match the brand may be clearer to you and carries nothing to the user, because nothing taught them what it means. Two rules save most of the trouble: take symbols from the standards that apply to your product family rather than from a font, and explain each symbol in a legend in the manual, because a symbol replaces text only when the manual has taught it.
Why a machine-translated manual is a safety risk
A warning that has been mistranslated is not a typographical problem; it is a defect in the information supplied with the product, and liability regimes treat inadequate instructions as a reason a product is considered defective. Machine translation fails in the exact places that matter: it inverts negations, it turns a prohibition into a recommendation, it renders a technical term with a everyday word that means something else in a workshop, and it does all of this fluently, so nobody who reads the output hears anything wrong. The commercial cost arrives earlier than the legal one — a European buyer reads a clumsy manual as the measure of everything they cannot inspect, and a distributor reads it as the support calls they will take.
What works is unglamorous. Freeze an English or Chinese source text, written by someone who knows the product, before anything is translated, because translating a moving document multiplies the errors by the number of languages. Have each language reviewed by a native speaker who works in the trade — a technician, not a literary translator — and give that reviewer the product or at least photographs of it. Keep a translation memory so the next model does not restart from nothing. And keep the version of every language file in the technical file, because the manual a court or an authority will read is the one that shipped, not the one you corrected afterwards.
Build the manual from the distribution map, not from the product. List the countries where the product will actually be made available, find out for each one which language its own rules require and whether digital instructions are accepted for your category, and only then decide what goes on paper in the box. Doing it in the other order produces the classic expensive outcome: a beautiful booklet, printed in volume, missing the language of the market that placed the first real order.