> For the complete documentation index, see [llms.txt](https://supplier-center.freshdi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://supplier-center.freshdi.com/~/revisions/WeNB0Rbs7sAatsX07iTU/guideline/product-information-standards.md).
# Product information standards
## 1. Title of the Product
* **Length:** Aim for a concise 50-70 characters.
* **Components:** Include product name, brand (when applicable), and primary attributes.
* **Format:** Employ a clear and structured approach: \[Brand] \[Product Name] \[Key Features].
* **Example:** Vietnam ST25 Long-Grain Fragrant White Rice, 5% Broken.
## 2. Description of Product
* **Length:** Maintain a concise product description within 150-300 characters.
* **Structure:**
* **Overview:** Provide a succinct summary of the product's purpose and general description.
* **Key Features:** Highlight the product's primary characteristics and benefits.
* **Product Specifications:** Detail essential technical attributes such as type, maximum moisture content, origin, and brand.
* **Usage Instructions:** Offer clear guidance on product use, care, or storage when necessary.
* **Language:** Employ clear and accessible language, minimizing technical jargon unless indispensable.
* **Example**
## 3. Product illustration
* **Quantity:** A minimum of 3 to 6 images is required per product, encompassing the primary image, multiple perspectives, and distinctive product details.
* **Resolution:** High-resolution images with a minimum dimension of 800x800 pixels are essential for clarity and visual impact.
* **Format:** Image files must be submitted in JPG or PNG format.
* **Quality:** All images should be sharp, clear, and free from blurriness or other imperfections.
## 4. Technical Specifications (Attribute)
* **Core Attributes:** Encompass essential product characteristics such as dimensions, weight, color, and composition.
* **Technical Specifications:** Detail pertinent technical parameters relevant to the product.
* **Example:**
## 5. Unit, Currency, and Product Price
* **Units of Measurement:** Employ appropriate units of measurement for each product, including but not limited to metric tons (MT), kilograms, or container dimensions (20ft/40ft).
* **Currency:** All prices must be quoted in United States Dollars (USD).
* **Pricing:** Provide accurate and current selling prices for each product. Prices should be specified per unit (e.g., $/kg). Clearly indicate minimum and maximum order quantities.
* **Promotions:** Detail any applicable promotions, discounts, or special offers with clarity.
* **Example:**
## 6. Classification and labels
* **Categorization:** Assign each product to the most suitable category within the product taxonomy. For example, classify dried bananas under the "Dried Fruit" category with a specific subcategory of "Dried Banana."
* **Keywords:** Optimize product discoverability by incorporating relevant keywords or tags. For instance, the product "Dried Banana" could be associated with tags such as "banana," "dried fruit," "snack," and "healthy."
## 7. Rules for Posting product information
* **Accuracy:** All product information must be current, accurate, and truthful.
* **Consistency:** Maintain a consistent style, format, and tone across all product content.
* **Copyright Compliance:** Adhere to copyright laws by using only original content or properly licensed images and text. Obtain necessary permissions for any externally sourced materials.
## 8. Inspection and approval
* **Review:** Examine all details and images prior to publication.
* **Management Approval:** Final approval for all product content must be obtained from Freshdi management before dissemination.
* **Product Approval Time:** within 24h
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://supplier-center.freshdi.com/~/revisions/WeNB0Rbs7sAatsX07iTU/guideline/product-information-standards.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
