Luxclusif Buyback Platform

Appearance

B2B: Submission Translation ​

The translation feature in our application is designed to facilitate the submission of content in multiple languages. When supplier submit data that is not in English, the application can automatically translate the content, provided that certain conditions are met. This feature ensures that submissions are correctly processed and understood by the system, regardless of the language in which they were originally submitted.

How It Works ​

When a client submits data in a language other than English, they must include the culture field in their submission. The culture field specifies the language of the submission using the RFC 4646 format, which is a combination of ISO 639 and ISO 3166 standards.

RFC 4646 format:

The format for the culture name is <language code>-<country/region code>, where:

<language code> identifies the language using a two-letter lowercase code based on ISO 639. <country/region code> identifies the subculture or region using a two-letter uppercase code based on ISO 3166.

For example:

  • es-CL for Spanish as spoken in Chile.
  • en-US for English as spoken in the United States.
  • en-AU for English as spoken in Australia.

This format allows the system to accurately identify both the language and its regional variation, ensuring that the appropriate translation is applied.

Coverage of Translation ​

The translation feature will be applied to the following properties of a submission:

  • Model: any descriptive text provided in the submission..
  • Description: any descriptive text provided in the submission.
  • Attributes of Type Free Text: any attribute within the submission that are designated as Free Text, where users can input arbitrary text.

Requirements for Translation ​

  • Culture Field: The culture field is mandatory for the translation feature to be activated. The value provided must comply with the RFC 4646 format <language code>-<country/region code> (e.g., "en-US" for English as spoken in the United States, ).

  • No Culture Provided: If the culture field is not provided, the submission will not be translated. In such cases, the data will be processed in its original language, and any non-English content may not be correctly understood or displayed by the system.

Sample Payload ​

Submission payload with culture filled.

json
{
  "externalId": "SUPPLIER_EXTERNAL_ID",
  "customerInformation": {
    "culture": "ja-JP",
  },
  "countryOfOrigin": "JP"
  "items": [
    {
      "externalId": "SUPPLIER_EXTERNAL_ITEM_ID",
      "categoryId": "ONE_OF_CATEGORY_IDS_FROM_CATEGORIES_ENDPOINT",
      "brandId": "ONE_OF_BRAND_IDS_FROM_BRANDS_ENDPOINT",
      "model": "This is a test model",
      "description": "Any relevant additional details",
      "price": { ///
       },
      "attributes": [
        {
          ///other properties
        }
      ],
      "files": [
        {
          ///other properties
        }
      ]
    }
  ]
}