Who decides on a B2B purchase in Korea and Japan? Map the roles instead of guessing
Trace a B2B purchase in Korea or Japan from the initial need to order approval. Match the evidence you share to the people assessing it.
Article language: English

In this article
A pleasant conversation with the right company does not necessarily mean you have spoken to the person responsible for a particular decision. For a B2B purchase in Korea or Japan, trace the path from the need through evaluation to approval of an order. A job title is a clue, not a complete guide to the organisation. Check who selects the specifications, who assesses the cost and whose next step a presentation will actually support. Then “I will pass it on” no longer has to be where the map ends.
A buying-participant map is a simple record of roles, questions and dependencies. It does not require obtaining a private organisation chart or guessing a hierarchy from someone's nationality. Its purpose is to reduce the chance that useful material reaches the wrong person. Here is how to build one from public documents and confirmations obtained in conversation, while leaving room for what remains unknown.
Start with the purchase, not a list of names
Choose one application and one stage of the relationship. Buying a component for a new project may follow a different route from ordering a spare part or piloting a service. Record what is being decided now: admission to a test, technical evaluation, choice of variant or an order. Combine every stage and the map may become so large that no one can find the next junction.
Write a working objective: we want to understand how the buyer decides whether to evaluate this solution and what information they need beforehand. This is a research goal, not an attempt to bypass the partner's procedures. If you have not chosen an application yet, return to B2B market segmentation in Asia (in Polish). Otherwise you may mix the buying routes of different groups and treat their differences as contradictory information about one company.
Separate roles that one person may combine
On the first map include the person who identifies the need, the user, the person evaluating the solution, the procurement coordinator and the person approving a particular step. Add someone responsible for maintenance if the product needs support after implementation. These are analytical roles to check, not a required structure for every company. In a smaller business one person may perform several functions. In a larger one some tasks may be split among teams.
Give each role a specific question. A user might assess ease of work, an evaluator the fit between specifications and application, and procurement the completeness of documents and delivery terms. Do not assume that this is how the company under study works. Add a status: hypothesis, publicly confirmed or confirmed by the person you spoke with. This small field stops a guess from being promoted to a fact. Such distinctions are useful when checking a potential Asian partner (in Polish).
Before mapping people, distinguish the purchase itself. A new machine tool, a retrofit and a machining service in Japan (in Polish) lead to different questions about users, technical assessment and maintenance. An industry label is not enough to choose the same route for all three offers.
Read supplier requirements as clues about what must be demonstrated
Public purchasing materials help identify areas of evaluation. In its published Supplier Sustainability Guidelines, Toyota lists safety, quality, delivery, cost and technological capabilities among its expectations. The published document is dated November 2021. Before a specific engagement, check the current requirements for the relevant entity and order. This example shows that supplier assessment covers several areas. It does not tell you who will attend your meeting or how every company in Japan buys.
Samsung Electronics describes its supplier code of conduct and supplier assessment activities. This is a reason to ask about assessment of the supplier organisation and required organisational documents, not just product specifications. It would be a mistake to transfer a large group's procedures to every Korean company. Use the source to prepare questions, then confirm the requirements for the particular relationship with the partner and the appropriate specialists.
Ask how material moves, rather than demanding the decision-maker's contact details
“Who decides here?” can be too broad to produce a useful answer. Refer to the task instead: who will evaluate the trial result, who will check the installation data and who should receive the service documentation? You can also ask whether your current contact collects other people's comments and what format would make answers easiest to use. This supports cooperation with the coordinator without undermining their role.
Do not bypass a contact simply because they do not sign the order. They may understand the procedure well and help collect the requirements. Establish whether they will forward the materials themselves or whether a joint meeting is needed. Prepare a conversation with a Japanese partner (in Polish) around questions about the meeting's purpose and outcome. An agenda called “company presentation” offers less guidance than one called “agreeing the data needed to evaluate a sample”.
Match each role to the material it needs
Do not immediately prepare a separate presentation for every department. First check what information is needed and what choice it supports. One case may need only a specification sheet with the scope of application. Another may require a test plan, a description of error handling or answers about delivery. The material should clearly identify the product version, assumptions and the person who can explain its limitations.
For a hypothetical packaging machine, prepare a shared description of the application and short attachments: installation requirements, an evaluation plan and the scope of support. Do not let each attachment describe a different equipment configuration. Version control for a multilingual offer (in Polish) matters when documents circulate among people and languages. The materials should be comparable before anyone tries to assemble the equipment from them.
Mark the dependencies between steps
A role map becomes useful when connected to sequence. Check whether technical evaluation can begin before supplier registration, whether confidentiality needs to be agreed and who sets the trial criteria. Do not guess the answers from another company. Record the entry condition, expected outcome and person responsible for confirming each step. Keep missing confirmations visible.
A working map may show two parallel paths: evaluation of the solution and evaluation of the possibility of working with the supplier. Agree when they meet. Specifications accepted by an engineer do not necessarily mean an order is ready. Likewise, complete formal documents do not prove the product is suitable. A sales pilot in Korea (in Polish) should go through the entire agreed process, not stop at one favourable comment.
Walk through a demonstration order
Imagine a Polish equipment supplier receives a request for a sample. In this exercise, a procurement coordinator handles correspondence, an engineer plans the test and the production team will operate the equipment. This is an invented arrangement for analysis. The first question is: what result will allow a decision about further evaluation? Without that, a sample may return with “interesting”, a pleasant answer that explains very little.

Then establish whether users will be present at the test and whether they are assessing the same conditions as the engineer. One person may check measurement accuracy, another changeover time. Both questions are valid but require different observations. Record who collects the result and until when missing data can be added. Do not set the partner's decision date yourself. Ask when it may be possible to return to the issue and which events that timing depends on.
After the trial separate three pieces of information: what was tested, what was accepted and what remains a condition for the next step. Agreement to another test is not agreement to purchase. A request for a price list is not a rejection of the specifications. Connect the sample evaluation plan for an Asian partner (in Polish) to the role map so everyone on the team knows who can give binding confirmation of a particular result.
Watch for four misleading shortcuts
The first shortcut is to treat the most senior person at a meeting as the owner of every decision. The second is to confuse a good personal relationship with authority to approve a purchase. The third is to infer the whole organisation from one person's answer. The fourth is to treat silence as an unambiguous rejection of the offer. In each case information about the process is missing, and a story about intentions fills the gap.
When contact stalls, return to the last confirmed step. Check what was to be sent, to whom and why. The guide on a Korean client who has not replied (in Polish) offers a way to organise a similar situation. A new message should clarify a specific unknown. Another generic attachment about company history will rarely resolve a missing specification or an unassigned test owner.
Maintain a map that can be updated
Record roles and relationships, and retain contact data only as needed and under your organisation's rules. The map should not become one salesperson's private notebook. Keep the date, source and scope of confirmation for each item. If a contact moves to another department, do not erase the earlier agreement. Mark which task needs to be reassigned and who should check it.
Review the map when the application changes, a new stage begins or additional requirements appear. You do not have to update the entire document after every courtesy in an email. What matters is a change affecting the materials or next step. In a project decision log (in Polish), retain the reason for your own choice: why a trial was proposed, a date moved or an offer configuration changed.
Prepare questions the other person can answer without guessing
Arrange a short sequence around the next action. Start with the purpose: are the materials to support a decision about a test or a comparison of variants? Then ask about the audience: who will review them and what questions should they answer? Only afterwards move to format, language and a possible time for feedback. Do not immediately request a complete history of every purchase. The conversation should reduce uncertainty in the current case.
Questions about a previous comparable case can help if your contact is able to discuss it. What had to be ready before the trial? Which explanation came too late? How were corrected specifications passed on? Treat the answers as an account of that case, not an unchanging rule for the organisation. A new project may have different conditions. Present your understanding and ask for a correction: we are currently preparing a technical sheet to assess the application, and delivery terms will return to the conversation after the configuration is established.
A well-prepared record makes it easier for the other person to say that something was misunderstood. Do not ask only whether everything is clear. Identify a particular dependency and check whether it matches the actual sequence. This matters when an interpreter is involved too. They need to know whether a sentence is a proposal, a confirmed agreement or a question about a possibility. The word “agreed” should have a clear basis in the notes.
Separate your team's map from the partner's
Also check who on your side answers each role's questions. A salesperson should not independently confirm an unverified equipment tolerance. An engineer need not know current availability for every variant. Assign owners for technical issues, terms of cooperation and the schedule, and establish how to bring their input into one consistent answer. The partner should not receive three answers that differ on the very detail they were trying to establish. Where needed, prepare an expert's participation in a sales conversation (in Polish) around the particular technical question they are to clarify.
When information needs checking, name the gap and say when you will respond. Do not disguise an internal consultation as a new version of a presentation. The buying map should improve cooperation on both sides. Its effectiveness can be judged by whether materials reach the right task and whether it is clear who will answer the next question. The number of contacts in a database remains just a number of contacts.
Check readiness before the next conversation
Before the meeting, ask someone outside the correspondence to read the map. They should be able to say which step is being considered, what materials are needed and which roles remain unconfirmed. If they see only a list of names, the connection between action and responsibility is missing. If everything is marked as certain, compare entries with the actual sources. If unconfirmed roles disappeared merely to make the document look tidy, put them back. The next person should know what still needs to be asked.
When investigating the buying route, work with Aeneia Oriens can begin with existing correspondence, product documents and one clearly identified partner decision. The first stage should establish the next feasible step and the conditions for evaluating it, even if the eventual purchase remains an open possibility.
Aeneia Oriens
Oriens combines market research with preparation of materials and conversations. Describe the buying stage and the roles that still need to be understood.










