Skip to content
Interface language: English
Oriens / Signal

A product catalogue for Korea and Japan: make technical assessment and first contact easier

Prepare a B2B catalogue with applications, variants, qualified parameters, consistent language versions and a test based on a reader task.

Article language: English

A woman at a workbench holds a curved white piece at the opening of a cylinder.
In this article

The catalogue has dozens of pages, beautiful photographs and everything except an answer to one question: which model fits my task? For a reader in Korea or Japan, start with three actions: recognising the application, comparing the variant and asking a specific question. Choose length and languages afterwards. A good catalogue leads to a product conversation; it does not require the customer to become curator of your assortment first.

There is no single mandatory catalogue structure for an entire country. Needs depend on the product, the reader's role and the stage of the conversation. An integrator may need different data from a distributor browsing an offer. Here is one way to build a B2B catalogue whose content can be checked and maintained. The examples are exercises, not descriptions of real products or sales results.

Choose when the catalogue should help

Write down who will open the material and what they should do after reading it. Are they comparing solutions, checking fit with an installation or preparing questions for their team? Do not try to serve every situation at one level of detail. A short overview can lead to a model sheet, then to documentation and a technical conversation. Each transition needs a clear purpose and consistent product identification.

Connect the catalogue to a B2B offer for Japan. The guide to a B2B offer for Japan (in Polish) discusses shaping it for the reader. The offer explains the proposition for a particular audience; the catalogue organises information on products that may deliver it. There is no need to repeat the whole company history on every sheet. If readers must pass several pages of innovation claims before finding a model, check whether the material is obstructing the task it was meant to support.

If the team lacks knowledge of the reader’s tasks before the catalogue project and decides to commission research, define that work separately. The guide to commissioning market research in Asia (in Polish) helps frame the decision and acceptance of the research; it does not replace editing or testing the sheets.

If the company has not yet chosen a market, the guide to comparing Korea, Japan and China (in Polish) can help organise criteria for the specific product. This choice is not a required stage of every catalogue project.

Build a model sheet around the application

Start with what the product is for, the problem it helps solve and conditions requiring further verification. Then give the model designation, variant and source of detailed data. The description should distinguish the product from similar items. A family photograph of five machines can present a range well, but will not identify which has a particular connection or operating range. The model name should remain legible when a single page is shared separately.

The JETRO e-Venue manual lists material, technology, application, production capacity and quality control among the information in a product description. These are requirements and guidance for a proposal on a particular platform, not a universal catalogue template. They do show that a slogan alone is not enough to understand a potential cooperation. Base your sheet on what the intended reader needs and on information you can substantiate.

The manual is an example of a description structure. At the check on 3 November 2026, JETRO's home page carried a 27 October notice of temporary e-Venue unavailability. Check the platform's current status before planning activity there. An available manual does not itself prove that the tool is operating.

Organise parameters together with conditions

For each parameter retain its name, value, unit, conditions and source. If data relates to a particular configuration or measurement method, do not separate it from that qualification. The reader should not need to assemble the correct information from three footnotes. Distinguish a confirmed product value from an example test result and data requiring consultation. It is better to name missing information than fill it with a value from a similar model.

The NIST SI guide explains the relationship between numerical values and units and unambiguous notation of quantities in tables and graphs. Use consistent notation: quantity name, appropriate unit and a clear description of the condition. Do not carry a number between languages without checking that it still refers to the same feature and product variant.

Create a technical glossary connecting each term to its definition. Agree separate rules for model codes and symbols. Automatic replacement of a name or character throughout a document may help editing, but check it in context. The same abbreviation may form part of a product name and also appear as a separate designation in a drawing. The goal is consistent meaning, not mechanically identical typography. The guide to preparing a technical glossary (in Polish) explains how to organise such terms.

Show differences between variants without a guessing game

Choose features that actually change product selection: application, installation, operating range or availability of an element, for example. A comparison should help identify the variant, not display every parameter from the documentation. If a specialist must explain a difference, say what information to send. A catalogue need not decide every case by itself, but should honestly indicate the limits of independent selection. If it runs on a website, design a comparison of models selected by the customer, using the same units and clearly identified missing data. The article on comparing selected products (in Polish) also discusses choosing which products to compare.

In an exercise, a series has two variants: one for an existing workstation, the other requiring additional integration. Do not simply call the second more advanced. Describe the condition of use and the task needed before assessment. This gives the reader a basis for discussion. Standard and premium labels alone do not explain the technical difference, however convincing they look in a presentation.

Separate product data from the conditions of a particular proposal

A catalogue can describe a product family for longer than the terms of one conversation remain valid. Decide what belongs in it and what must be confirmed in a separate proposal: configuration, availability, scope of delivery or a test plan. Do not publish one value as universal if it depends on the reader's circumstances. Equally, do not hide every detail behind a generic invitation to ask about everything. Readers need enough to recognise whether further contact makes sense.

A supplier RFQ depends on information that makes answers comparable. Prepare the catalogue so the reader can refer to a model and name its application. If presenting test results, documents or markings for a particular scope, check their connection to the variant. Do not assume that a document for one product covers an entire series or every market. The guide to supplier RFQs in Asia (in Polish) also considers quantities and recording responses.

Aeneia conceptual photography

Prepare language versions from one source of data

Decide where all language versions get product information. An organised source sheet may suffice; it need not be an extensive system. What matters is that each parameter correction has an owner and reaches every material needing an update. Record a data date or version for each model. Readers should be able to identify the material they used, and your team should be able to check whether anything has changed since.

Versioning a multilingual offer connects the catalogue to detailed sheets and the website. Before publication, review the Korean and Japanese translations, including meaning, language and the finished material. Pay attention to text in drawings and captions. Not all of it reaches a translation spreadsheet, yet it can determine the application. The guide to multilingual offer versions (in Polish) and the article on reviewing Korean and Japanese translations (in Polish) discuss those two checks.

Plan material for the intermediary and the user

A distributor may need to know how to present the product and when to send a question to the manufacturer. A user may want to check the application and scope of support. An integrator will look for data needed to connect the solution to their own project. These are example roles to verify, not fixed rules. One material can lead to several routes if it clearly identifies where to find an answer and what information will be needed next. For a Rakuten Ichiba store, the catalogue can also supply information for daily operations: someone must connect the variant, customer question and current answer from the manufacturer. The article on operating a Rakuten Ichiba store (in Polish) describes that daily work.

When choosing a distributor or direct sales in Asia, check who will actually use the catalogue. Do not ask an intermediary to supply parameters absent from the material. Establish how questions reach a specialist and how the variant is identified. If separate pages are forwarded, make sure every sheet retains the product name, data source and contact route. For the division of sales roles, see the guide to distributors and direct sales in Asia (in Polish).

Test it with a customer's question

Give the material to someone who did not create it. In the exercise, they must find a product for a specified application and say what still needs checking. Ask them to identify the model, parameter source and contact method. Do not assess appearance alone. A reader may find the catalogue attractive and still select the wrong variant or miss a condition requiring an additional module.

Then change the task: the reader is not the user, but someone collecting material for a technical team. Can they forward the page and frame a question without retyping the whole description? This test shows whether information stands alone. A catalogue often travels further than the first message. Prepare for that journey: the model, conditions and contact route should remain understandable without the author at the desk.

Finally, check that the proposed next step is feasible. If the reader is to assess a sample, they should know what scope needs agreement first. A product-sample assessment plan connects interest with a specific task. If they must send application data, name the minimum needed to answer. A catalogue should reduce messages caused by missing basics, not merely increase downloads. The guide to planning product-sample assessment (in Polish) explains how to prepare that plan.

If the reader’s tasks first need investigation, the guide to B2B customer interviews in Asia (in Polish) can help reconstruct their previous experience. Those interviews do not replace a separate test of a finished sheet with a specific task.

Check the boundary between useful brevity and missing information

An overly long catalogue can make a variant hard to find, but excessive shortening has a cost too. Remove repetition and claims that do not help assessment, while retaining conditions of use and links to details. The short phrase different configurations available needs an explanation of how to identify the right one. Brevity helps when readers can still complete the task. It should not become a contest for the least information per page.

When entering a new market, compare readers' questions with the current catalogue. Record information that regularly needs separate explanation. It may reveal a gap in the material or a difference in application that needs investigation. Do not automatically add every answer to every sheet. In a list of potential partners in Asia, mark roles and needs so you know for whom the next version is being prepared. The article on listing potential partners in Asia (in Polish) discusses the criteria for such a list.

If the questions reveal missing knowledge about the recipient or application, the guide to testing demand before selling (in Polish) can help plan a separate trial. A gap in the catalogue does not itself confirm demand.

Practise a sheet with a simple furniture component

Imagine a company preparing a fittings catalogue for furniture manufacturers. This is a fictional exercise. In the old material, every variant has a similar photograph and a general strength description. Readers must compare drawings to find differences in dimensions and installation. In the new sheet you state the application first, then the variant code and features needed for selection. You do not add new claims; you organise information already confirmed in the documentation.

Test the sheet with two tasks. One reader must identify a component matching a drawing. The other must assess what information to provide for a different variant. If both tasks lead to the same generic contact button, state what specifically to ask. One person should send a code and indicate a quantity for discussion. The other may need an application drawing and description of constraints. Agree these information sets with the product team instead of inventing them during editing.

Record these questions on a checklist:

  • When a single page is printed, can the model and variant still be identified?
  • Does each dimension state which part of the drawing the value concerns?
  • Is a condition requiring consultation visible next to the relevant application?
  • Can a question be sent without guessing which documents are needed for an answer?

If the test is weak, improve the order and connections between data. Do not begin by adding another page of company benefits. One missing designation may be the problem, not a lack of persuasion. The lesson applies to more complex products too: a catalogue should help the reader identify the right question before the team tries to answer it.

Accept the catalogue together with an update rule

At acceptance, identify the current set of models, data source, approved language versions and people responsible for changes. Check links and whether contact details reach the team serving that language or the agreed communication method. If a question goes through a contact form, follow the whole route and ensure the message retains model information. A correct address in a file does not prove a request was received. The guide to the B2B contact-form journey (in Polish) follows a message to its recipient.

A sound catalogue brief starts with a specific reader task. Aeneia Oriens describes possible support; the material's usefulness can be tested before it reaches the first partner.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear