Enquiries from Asian customers: distinguish a demand signal from a catalogue request
Assess enquiries from Korea, Japan and China through content, contact role and actions, and choose a useful next reply.
Article language: English

In this article
“Please send a catalogue” sounds promising. It is easy, however, to add an order that does not yet exist to the notes. Assess an enquiry from Korea, Japan or China through its content, the contact's role and the agreed next step. A catalogue request, a description of use and readiness for a trial are different events. Do not treat them as equal evidence of demand. Record what was actually received, what is missing and how a response can help both sides assess the value of continuing. Only then can cases be compared.
A demand signal need not mean an immediate order. It may indicate a particular problem, a need for clarification or willingness to take another action. Do not add more than the material confirms. This guide concerns analysing messages and organising replies. The examples are hypothetical; adapt the suggested statuses to your product and actual process.
Start with what was written
Keep the enquiry, date, channel and materials the contact refers to. Describe the request in one sentence without interpreting intent. “Asks for a model sheet” is an observation. “Is preparing a purchase” is a hypothesis unless the person said so. Separating these records lets you assess how the decision on the next step arose and whether it still has a basis.
GOV.UK's guide to analysing research separates observations, findings and proposed actions. It describes service research, not measurement of Asian sales. Apply similar discipline to enquiries: message first, your understanding second and a decision only afterwards. A good summary should not promote a polite file request into confirmed purchasing need along the way.
Check the person's role and organisation
Establish whether the person is asking as a user, integrator, distributor, supplier or someone collecting information for another team. Do not infer the entire process from a job title. Ask what assessment the material will support and which question it should answer. That context helps tailor a reply without collecting unnecessary data. Someone who does not make the final decision may still understand the task well. In a conversation about working with Coupang (in Polish), clarify whether the subject is selling through the platform, buying goods or a service preparing an offer. The distinction changes the meaning of the enquiry.
At a more consequential stage, use Asian partner verification (in Polish) suited to the planned cooperation. Do not replace it with an assessment of message tone or signature appearance. At the same time separate identity confirmation from product fit. A correctly identified entity may ask about a use you do not support. The record should show both findings rather than hide them under one contact-quality label.
Give a status to an action, not a promise
Prepare statuses for what happened: general question received, use clarified, data supplied for assessment, trial agreed or its result discussed. This is an example to adapt. Each status needs a condition and supporting material. If moving stages depends only on a salesperson's impression, similar cases soon acquire different descriptions that cannot be compared.
Do not automatically assign a purchase probability percentage to each status. Without an appropriately defined history of your own, it would be decoration, not measurement. For a Korean sales pilot (in Polish), reconstructing the whole path matters more: what was done, who assessed the result and what condition remains open. A status should help choose an action. A nicer system colour is not proof that a case has matured.
Separate general interest from a specific task
A catalogue request can mean many things. There is no need to decide by guessing. Send the appropriate material and ask which use or model matters to the recipient. If they describe their current process, you have a basis for further assessment. If they remain general, keep that scope in the note. A lack of detail does not entitle you to assign a hidden intent.
The SBA's market-research material distinguishes using existing sources from directly researching audience needs. This general method does not specify customer behaviour in a particular country. It does help ask whether the enquiry says anything about an actual task or merely starts a material exchange. Demand verification in Asia (in Polish) should preserve that distinction in its findings.
Ask one question that opens the right next step
Instead of sending a form asking for every possible detail, choose the information needed now. It might be the use, variant, recipient's role or expected assessment method. Explain why you are asking. If a model code is enough to reply, do not immediately request documentation for the entire process. A limited, specific request helps the contact understand what to prepare and why.
When the case matures into a comparable technical enquiry, use the RFQ guide for work with Asia (in Polish). Before that, mark what has not been determined. Do not send a quote as if all variants had been agreed when the answer depends on your own assumptions. Those assumptions should be visible to the recipient so they can correct them before moving ahead.
Practise analysing three messages
In the first exercise a contact asks for a catalogue. You record the request's scope and ask about the intended use. In the second, they specify a model and a problem with the current process. This reply may require a technical person and clarification of conditions. In the third, they propose assessing a sample but do not specify how to check it. That is a reason to agree a plan, not confirmation that the trial will be meaningful.
Prepare a different action for each message. The first need not receive the entire technical presentation. The second should not get stuck in a generic reply about company strengths. The third needs a sample evaluation plan (in Polish), so everyone knows what the test should clarify. A shared reply template may help keep order, but should not obscure differences between the contacts' tasks.

Compare your notes with the messages. If each says the person is ready to buy, revisit the criteria. The system may reward optimistic labels instead of precise records. There is no need to take enthusiasm away from the team. It simply should not act as evidence on its own. An accurate note provides more options because it shows what remains to learn.
Record why a case stopped
If contact does not progress, separate a known reason from your own guess. Confirmed mismatch of use, absence of a required variant and no reply are different situations. Do not combine them under “no interest” if the material does not justify that. Determine whether the case needs a question, better material, postponement or closure within a defined scope. Give each choice a short reason.
Analysing a Korean customer's lack of reply (in Polish) helps organise possible gaps without assigning intent. Return to the last confirmed step: what was sent, what was asked and what response was expected. If you gave the recipient no clear task, another identical attachment may not solve the problem. Improve the question or scope of material instead of merely increasing reminder frequency.
Compare channels using the same definitions
Before comparing events, forms and referrals, define the unit: unique company, case or individual message. The same entity can return through several channels. Do not count each reply as a new recipient. State the period, recording method and stage criterion. Also record how contacts were reached. Do not assume voluntary enquiries are a representative sample of every company in the market. Otherwise a channel collecting brief questions may look better than one with fewer but more specific cases.
When working through an intermediary, check who conducts the conversation and what a reported status means. Choosing a distributor or direct sales (in Polish) changes the division of work and observations available. Do not ask more of data than it actually shows. If you know only that an intermediary sent material, do not record that the user read it and accepted the use.
Use questions to improve the offer
Group recurring topics: choice of variant, documentation, service, test or next-step conditions. Check whether information is missing from material or a new use has appeared. These are different tasks. The first may call for a better description; the second may need a product check. For technical textiles offered in Korea (in Polish), a question about material function may require different data from one about fibre composition. Do not automatically add every response to the catalogue before the owner confirms its scope.
Keep consistent versions of the multilingual offer (in Polish) so a reply does not refer to an outdated model. Preparing an Asian product for Polish audiences (in Polish) shows the same need from the other side. Customer questions help improve communication and identify uses. They are not automatically an instruction to develop every suggested feature or proof that every company needs the same thing.
Prepare a review card for one case
Record the recipient's request, role, use, last confirmed step and one most important unknown. Add the response given and the person responsible for the next action. There is no need to copy the entire history into every summary. It is enough to be able to return to it and check the summary's basis. Separately identify information from an intermediary so it is not later mistaken for a direct user reply.
In a working example, a company asks whether it can receive a demonstration. It has not specified the use or evaluation method. The card should not say a test has been agreed. The next question may ask what the recipient wants to check and which conditions matter. When they reply, change the particular unknown and the status corresponding to the action taken. The history grows with the evidence rather than jumping several stages after each friendly email.
During review ask four questions:
- Does the message justify the case's current status?
- Is it known who needs the material and for which assessment?
- Can the next step be taken with the current data?
- Was a lack of response described without inventing a reason?
If a card fails the check, correct the record or choose a question to clarify. Do not change status solely because a summary meeting is approaching. The quality of analysis lies in its usefulness for action. Sometimes that means honestly leaving a case at an earlier stage so the team knows which information to obtain. That is a better basis for work than a formally advanced case with no agreed use.
With more enquiries, include unusual cases in shared reviews. If you see only conversations that progressed smoothly, you may miss a problem with material or qualification rules. Record whether a change concerns one case or the entire classification method. In the second case, check similar records so two contradictory definitions of the same status do not remain after correction.
Accept the analysis by reconstructing the case
Choose several enquiries with different paths, including a postponed case. Check the content, status, interpretation and next step. Someone outside the correspondence should understand the reason for the choice. If every label requires an oral explanation, improve the definitions. Keep data-use boundaries too: analysis for the team's needs does not require collecting every possible detail about contacts.
When closing market research (in Polish), show what enquiries confirm and what remains unsettled. At Aeneia Oriens, such a review can start with a limited sample of messages, product criteria and a question about the next action.











