Contextual Product Translation

Introduction

Contextual product translation is specifically developed for e-commerce scenarios, achieving translation among more than 60 languages. It leverages e-commerce-specific data for training to enhance translation quality and is equipped with intelligent brand recognition and customizable intervention features, providing an efficient multi-language market expansion solution for e-commerce platforms and developers.

Use Cases

Contextual product translation can be used to translate product titles, product descriptions, and reviews in the international e-commerce fields. Compared to other translation products on the market, it performs better in localizing product information and in e-commerce-specific expressions.

Samples

Input	Aidge	Competitor1	Competitor2	Aidge Advantages
欧美风黑宝石珍珠钛钢男项链女高级设计感小众ins嘻哈锁骨链情侣	European and American Style Black Gemstone Pearl Titanium Steel Men's Necklace & Women's High-End Design Niche Ins Hip-Hop Clavicle Chain Couple Set	European and American style black sapphire pearl titanium steel men's necklace women's high-end design niche ins hip-hop clavicle chain couple	European and American Style Black Gem Pearl Titanium Steel Men's Necklace Women's Advanced Design Sense Niche Ins Hip Hop Clavicle Chain Couple	"黑宝石"can be translated as 'Black Gemstone.'Competitor 1 translates it as 'black sapphire' which refers to a blue sapphire and thus has a semantic deviation. "高级设计感"can be directly translated as 'high-end design'; Competitor 2 translates it word-for-word, resulting in awkward grammar.
白茶茶叶陈年老寿眉福建白茶荒山贡眉三年陈原料福鼎政和老白茶饼	White Tea Leaves Aged Old Shoumei, Fujian White Tea, Huangshan Gongmei, Three-Year-Old Raw Materials, Fuding Zhenghe Old White Tea Cake	White tea aged Laoshoumei Fujian white tea Huangshan Gongmei three-year-old raw materials Fuding Zhenghe Laobai tea cake	White Tea Tea Old Longevity Eyebrow Fujian White Tea Barren Mountain Tribute Eyebrow Three Years Old Raw Materials Fuding Zheng and Old White Tea Cake	"白茶茶叶" translates to "white tea." Competitor 2's "white tea tea" is redundant. "寿眉" should be transliterated; both competitors failed. Competitor 1 misinterpreted "白茶饼."
1/35 German Waffen Vehicle Machine Gunner Resin Figures WARRIORS #35079 Unassembled Uncolored	1/35 مركبة وافن الألمانية مدفع الراتنج أرقام المحارب #35079 غير مجمعة غير ملونة	مجسمات من الراتينج لمركبة وافن الألمانية لعام 1/35 ووريورز #35079 غير مجمعة وغير ملونة	مجسّم سيارة وافين ألمانية ، مدفعي راتنجات ، شخصيات محاربون # ، غير مُجمّع وغير ملون	The translation uses "مدفع الراتنج" to highlight "Machine Gunner" and clearly presents product features for quick e-commerce communication.
LED Strip Set 5m 10m 20m 30m 12V RGB RGBW Waterproof IP65 300LEDs 5050 Flexible LED Strip Lights LED Rope Ribbons Amplifier Kit	LED قطاع مجموعة 5 متر 10 متر 20 متر 30 متر 12 فولت RGB RGBW مقاوم للماء IP65 300 المصابيح 5050 مرنة LED قطاع أضواء LED حبل أشرطة مكبر للصوت عدة	مجموعة شريط LED 5 متر 10 متر 20 متر 30 متر 12 فولت RGB RGBW مقاوم للماء IP65 300 المصابيح 5050 شريط LED مرن أضواء LED حبل شرائط مكبر للصوت عدة	طقم شريط LED 5 م 10 م 20 م 12 فولت RGB RGBW مقاوم للماء IP65 30 أضواء LEDs شريط LED مرن عدة مضخم أشرطة LED	Beginning with 'LED قطاع مجموعة' clearly shows this is an LED strip kit. This translation also organizes information logically, making it easier for readers to understand, especially when describing product features (like 'مرنة', referring to the strip's flexibility) and technical specifications (such as '12 فولت RGB RGBW مقاوم للماء IP65'), which are more precise and clear compared to the third translation.

Key Features

1. Supported Language Pairs

The Contextual product translation API supports translation between the language pairs listed in the following table. More language pairs are continuously being added. Please contact us via navigation bar or email us ([e-mail]) if you have any specific requirements.

Source Language	Target Language	Description	Title	QA	Review
Chinese	English	Supported
Arabic	English	Supported
Japanese	English	Supported
Korean	English	Supported
German	English	Supported
Dutch	English	Supported
English	Chinese	Supported
English	Arabic	Supported	Supported
English	Urdu	Supported	Supported
English	Bengali	Supported	Supported
English	Polish	Supported	Supported
English	Ukrainian	Supported	Supported
English	Russian	Supported	Supported
English	German	Supported	Supported
English	Dutch	Supported	Supported
English	Turkish	Supported	Supported
English	Korean		Supported
English	Japanese		Supported
English	Thai		Supported
English	Indonesian		Supported
English	Malay		Supported
English	Vietnamese	Supported	Supported
Chinese	Vietnamese	Supported
English	Spanish	Supported
English	French	Supported
English	Portuguese	Supported
English	Italian	Supported
English	Hebrew	Supported	Supported
Turkish	Arabic			Supported	Supported
Turkish	English		Supported	Supported
Turkish	German		Supported		Supported
Turkish	Czech		Supported
Turkish	Romanian		Supported
Turkish	Hungarian		Supported
Turkish	Greek		Supported
Chinese	Arabic	Supported	Supported
Chinese	Urdu	Supported	Supported
Chinese	Bengali	Supported	Supported
Chinese	Polish	Supported	Supported
Chinese	Ukrainian	Supported	Supported
Chinese	Russian	Supported	Supported
Chinese	German	Supported	Supported
Chinese	Dutch	Supported	Supported
Chinese	Turkish	Supported	Supported
Chinese	Korean		Supported
Chinese	Japanese		Supported
Chinese	Thai		Supported
Chinese	Indonesian		Supported
Chinese	Malay		Supported
Chinese	Vietnamese	Supported
Chinese	Spanish	Supported
Chinese	French	Supported
Chinese	Portuguese	Supported
Chinese	Italian	Supported

2. Supported Text Format

Currently, only text and HTML formats are supported.

3. Supported Intervention Ability

You only need to associate the corresponding intervention glossary ID with the input parameter to complete the intervention on the target translation result, which can more accurately meet your translation needs in different scenarios.

Currently independent uploading of intervention glossary is not supported. If you have any needs, please contact us via navigation bar or email us ([e-mail]).

Pricing

To use the API, you are required to choose and purchase an API resource pack from us on a subscription basis.

• Each resource pack is valid for one calendar year upon successful purchase, and enables you to access the API up to the number of requests specified in the pack. No refunds can be provided.

• If you need to purchase more QPS due to business requirements, please contact us via navigation bar or email us ([e-mail]).

• Resource packs cannot be used across different products. For example, if you need to use both contextual product translation and image translation, you must purchase separate resource packs for each.

The prices are as follows:

Capacity	Price (USD)	Unit Price(USD)	Maximum QPS
10 million characters	150	$15.0 /million characters	15
100 million characters	1350	$13.5 /million characters	15
1 billion characters	12000	$12.0 /million characters	15

Quick Start

1.Sample Request

The contextual product translation API requires the input of the following five key parameters: source text to be translated, source language, target language, text format type, and an additional field (used to specify the type of text being translated, such as product title/description/review).

• The optional input is: product Intervention Glossary ID.

Java

IopClient client = new IopClient(url, appkey, appSecret);
IopRequest request = new IopRequest();
request.setApiName("/ai/text/translation/and/polishment");
request.addApiParameter("sourceTextList", "[\"Pen for iPad, 13 mins Fast Charging Stylus with Palm Rejection, Tilt Sensitivity, Compatible with 2018-2022 iPad Air 3/4/5, iPad Mini 5/6, iPad 6/7/8/9/10, iPad Pro 11, iPad Pro 12.9 (Black)\"]");
request.addApiParameter("sourceLanguage", "en");
request.addApiParameter("targetLanguage", "ko");
request.addApiParameter("formatType", "text");
request.addApiParameter("glossary", "test_glossary");
request.addApiParameter("extension", "{}");
IopResponse response = client.execute(request, Protocol.TOP);
System.out.println(response.getBody());
Thread.sleep(10);

2.Sample Response

• The output is the translation result.

Java

{
  "data": {
    "usage": 143,
    "translated": [
      "iPad용 펜, 손바닥 거부 기능이 있는 13분 고속 충전 스타일러스, 기울기 감도, 2018-2022 iPad Air 3/4/, iPad Mini 5/6, iPad 6/7/8/9/10, iPad Pro 11, iPad Pro 12.9와 호환 가능(검은색)"
    ],
    "class": "com.aidc.service.api.client.translate.dto.CommonTranslationResponse"
  },
  "requestId": "2101364017192321239846748e03d8",
  "success": true,
  "resCode": 200,
  "resMessage": "success",
  "code": "0",
  "request_id": "2101236717192321239867892",
  "_trace_id_": "2101364017192321239846748e03d8"
}

Depending on the input parameters, the model will output different translated content.

FAQ

1. What languages does the contextual product translation API support?

You can refer to the "Supported Languages" section. More languages are being added. If you have any needs, please contact us.

1. How is the contextual product translation API pricing?

It is priced based on the number of characters translated. For details, please refer to the "Pricing"section in this document.

1. Is the Intervention ability available in bulk?

Yes，it supports batch activation. You only need to associate multiple intervention glossary IDs for it to take effect. However, independent uploading of intervention is currently not supported. If you have any needs, please contact us via navigation bar or email us ([e-mail]).

1. What performance-related information needs to be confirmed during the integration?

The maximum QPS supported by the interface is 15. If the required QPS exceeds 15, please contact your account manager to confirm the following information and arrange for resource allocation in advance.

• Confirmation of SLA (Service Level Agreement) information, such as AVG RT / P99 RT / AVG QPS / peak QPS for different languages, etc.

• Confirmation of traffic proportions for different translation scenarios. For example, the traffic proportions for scenarios such as Description / Review / Title, etc.

• What should I do if an error occurs?

Please refer to the "Errors" section of the API reference for possible causes and recommended solutions.

1. What action should be taken if the translation is of an unsatisfactory quality when being tested and used?

If you meet bad cases of translation quality, we highly encourage you to provide feedback. Please contact us via navigation bar or email us ([e-mail]) for collaborative handling. We will continuously work on optimizing translation quality for e-commerce scenarios.