Supplying a Japanese Customer: What Changes Once You Are In

Most writing about Japan is addressed to a company deciding whether to go. It weighs market size, it explains distribution, it lists the things to understand before committing.

That is not the situation a lot of European companies are actually in. A Japanese customer approached them, or won them through a tender, or acquired the business that already served them. The decision was made elsewhere and the timetable belongs to somebody else. They are not entering a market. They are already inside one, as a supplier, and what they need is not an assessment of Japan but an operating manual for the relationship they now have.

Almost none of the market-entry material speaks to that. This does.

The reporting is not status updates

Inside Japanese organisations there is a continuous upward flow of information that has a name. Hou-ren-sou compresses three words: hokoku, to report progress to superiors and stakeholders; renraku, to share factual updates without opinion attached; sodan, to consult a superior when a decision is hard to take alone. Staff align at their level, it moves up to project managers, then to department and general management, and something becomes official only when the senior level gives its assent.

Two things are worth knowing about it before you try to use it.

The first is that in its original conception it was not a compliance target for junior staff. It was a tool for managers, a way to build a workplace where people can bring bad news upward early. Read as a stick, it produces exactly the defensive silence it was invented to prevent.

The second is where the documentation stops. Every documented account of hou-ren-sou describes actors inside a single organisation: superiors, stakeholders, colleagues, staff levels. None of them describes it running across a company boundary to a supplier. It is the internal norm Japanese organisations hold themselves to, and in our experience the same expectation carries to their suppliers. That is practice, not a research finding.

What is documented for suppliers specifically is narrower and more useful for it. Information tends to flow upward, from suppliers to customers, which is why a Japanese customer can ask a great deal and send comparatively little back. The practical guidance that comes with it: be ready to provide information that seems irrelevant to you, and when the same question arrives several times, make sure your reply is consistent every time.

That last instruction is easy to skim past, and it carries most of the weight. Your answer is being carried upward by people you never meet, and it has to reach them unchanged. Give a slightly better answer on the third asking and you have put a contradiction in somebody's file.

The approval is moving through people you will not meet

You know your own qualification cycle better than we do, and you know how it compares to the same work elsewhere. What is worth adding is where the time goes on the other side, because that is what makes the waiting readable.

The decision you are waiting on is being assembled below the person you are talking to, and it is being assembled in writing. Inside Japanese organisations there is a formal circulation, the ringi, that carries a proposal for approval, and an informal consultation that precedes it and does most of the work. By the time the document circulates, the substance has usually been settled.

What a thin document signals

One difference is worth naming because it changes how a document should be read, not because it tells you anything about procurement.

Cross-cultural training describes the two contracting norms like this: contracts in Japan as brief, not attempting to foresee conflicts or their resolution, and negotiable if external conditions change; contracts in Europe as detailed, foreseeing conflict and its resolution, and not negotiable when conditions shift. That is a teaching comparison rather than a study, and it is offered as a framing.

The framing is the point. A European reads a thin contract as an incomplete contract, and reaches for the clause that is missing. If the document is thin because the obligation is understood to live in the relationship rather than in the paper, then the missing clause is not an oversight to be corrected. It is where the other party expects the discussion to happen later.

Neither reading is naive. They are different places to put the same weight.

Quality is enforced at receipt

Japanese customers reject cosmetic defects that European suppliers consider minor and negligible. It is common enough that many European suppliers end up running an extra quality-check chain purely for their Japanese customer.

The point is not that the standard is higher, which every supplier has already been told. It is where the standard is enforced. It does not arrive as a clause you can negotiate at signing. It arrives as a rejection at goods-in, after you have shipped, on a batch you considered fine.

Whether that changes what you quote is your commercial judgement and not ours. What is worth knowing before the first shipment is that the standard is not going to arrive as a negotiable clause.

That evidence comes from a trainer's account rather than a survey, and "many" is uncounted. It is offered as a pattern to check against your own experience, not as a measured proportion.

When approval stalls, ask what the ringi needs

When a decision on the Japanese side appears to have stopped moving, ask your counterpart, one to one and informally, whether a ringi is in place, how to feed it, on what timing, and what data it needs. The reason to ask early is that the counterpart often will not ask you for specific input before the process starts, and once it is running it is too late to add anything to it. Decisions then drag out, and from the outside that looks like disinterest or internal opposition when it is neither.

Silence during that period is also not what a European reader assumes. Within Japanese firms, information is shared with as many people as possible, where Dutch managers in the same study shared only with those who needed it for their own task. That finding is from interviews conducted in 1999 and 2000, inside firms rather than between them, so it does not transfer directly to your situation. It does explain why your own selective updating, which feels efficient and considerate, can read as withholding.

Both sides say trust and mean different systems

In the version of this case Martin Glisby gave in an EU-Japan Centre webinar, top management of a European pharmaceutical company and of its largest Japanese supplier were each asked what trust meant. The European answers: living up to the agreement, proceeding according to plan, demonstrating full transparency, telling the truth up front, being direct and engaging in open discussion. The Japanese answers: being considerate and sympathetic, having compassion; sharing visions; close communication and knowledge sharing; knowing when to take a conversation out of the office; and communicating around themes agreed in advance, so that nothing arrives as a surprise.

Neither list is wrong and neither side was being evasive. They were describing different systems with one word, and the last items collide directly: open discussion on one side, agreed themes and no surprises on the other.

Note the roles in that case were the reverse of yours. The European company was the customer. The mismatch belongs to the pairing rather than to either side of it, which means your customer may be assessing the relationship on criteria that never appear in your review meetings.

When something goes wrong

A quality claim from a Japanese customer usually arrives with three questions: why did it happen, what are you going to do to solve it, and what will you do to stop it happening again. Guidance for European suppliers published by the EU-Japan Centre, from Olivier van Beneden of Japan Consulting Office, sets out the response in five steps:

1. Apologise.
2. Listen to the problem and acknowledge it.
3. Find the root cause and report it, with photographs where possible.
4. Put a workaround or a fix in place and report it.
5. Confirm by testing that the problem is resolved, and report that too.

The first step is the one European suppliers resist. In the same guidance, an apology given straight away, before responsibility has been established, signals that you care about the relationship; it does not mean you accept that you are responsible. The guidance also advises against answering with probability arguments, such as how rare the defect is.

Two questions without a documented answer

How long trust takes. No study gives a figure. Practitioner accounts in EU-Japan Centre material speak of months, if not years, before the first business, and note that each change of European contact person means building the relationship again.

What it is like for your engineers on their site. The available accounts describe office assignments, general expatriate adjustment, and Japanese manufacturers sending their own engineers to suppliers. None describes a supplier's engineers working inside a customer's plant.

The closest description is a metaphor, and only a metaphor: European roles as bricks, sharply defined with clear interfaces, and Japanese roles as cloud, overlapping and less clearly bounded. An engineer sent from a brick organisation into a cloud one will experience meetings that report rather than decide, and copied correspondence that looks like noise and is actually participation.

Where this sits

If any of this is familiar, the useful next step is usually not more reading about Japan. It is working through your own live relationship with someone who can tell you which of these patterns is actually in play and which is a distraction, which is what our cross-cultural training for Japan is for.

For the layer underneath, on how decisions actually get made and where authority sits, start with our guide to Japanese business culture. If the question is more about the emotional register of these relationships, amae and the expectations it creates is the closest companion to this piece. And before applying any of it to a specific colleague, the difference between a tendency and a truth is worth ten minutes.