What the Data for This Category Looks Like
The data for this category mainly comes from General Administration of Customs duty-free supervision filing documents, offshore duty-free store operation ledgers, brand duty-free supply price lists, and official policy interpretation documents. Policy documents are released irregularly alongside policy updates. Operational data is updated monthly or quarterly. Price lists are updated in real time when brands adjust prices. Document structures include three categories: original policy texts, structured price lists, and operation ledgers. Fields include document number, effective date, applicable region, product code, duty-free selling price, quota limit, and more. The unit for monetary amounts is uniformly RMB yuan, and the unit for quotas is yuan per person.
Constraints on Citation Source and Traceability
The document number and effective date of policy data are core traceability identifiers, which must be displayed alongside citations to ensure alignment between implementation scenarios and policy execution timelines. Structured price lists must be bound to product code and applicable store type fields to prevent traceability errors across categories and scenarios. Real-time updated supply price lists require the knowledge base to trigger a full index on a regular basis; otherwise, recalled historical data will not correspond to currently valid prices. Operational ledger data must be associated with transaction time and store ID to ensure the traceability chain covers the entire business process and avoid confusion across cyclical data.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
| Number of recalled entries | Top 6-10 entries | Duty-free investment research data mostly consists of structured entries. Too many recalled entries will cause traceability redundancy, while too few will fail to cover policy and price list association information |
| Similarity threshold | 0.75-0.85 | Policy texts and price list fields have large differences. A threshold that is too low will mix in irrelevant data, while a threshold that is too high will fail to match weakly similar content from associated fields |
PARSE_FILE_TIMEOUT_SECONDS | 300-600 seconds | Parsing large policy compilation PDFs or batch price list Excel files takes a long time. A timeout will cause file import failure and prevent completion of pre-traceability preparation |
| Chunk length | 800-1200 characters | Duty-free policy clauses and single price list record lengths are moderate. Chunks that are too long will lose contextual association, while chunks that are too short will destroy policy logic and price list entry integrity |
| Number of reordered returned entries | Top 3-5 entries | Traceability entries with strong keyword matching must be prioritized for display to avoid interference from non-core data |
UPLOAD_FILE_MAX_SIZE | 500-1000 MB | Batch imported duty-free ledgers or policy compilation files have large sizes. Too small a limit will prevent completion of batch knowledge base construction |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material format, data volume and business rules. Specific issues require specific analysis. Testing should be performed against applicable samples prior to finalization.
Three Common Misconfigurations
- Symptom: After importing a specified JSON knowledge base, the knowledge base list is empty when calling. Cause: The
KNOWLEDGE_BASE_SELECTORpermission parameter is not configured, or the "Publicly Visible" option was not checked during import. In version 4.8.22, this configuration must be manually set in environment variables; otherwise, the target knowledge base cannot be identified during calls. - Symptom: An "Insufficient citation quota" error is displayed when citing. Cause: The
MAX_REFERENCE_COUNTparameter value has not been adjusted, or the citation quota has not been adjusted to meet the multi-field association requirements of duty-free data, resulting in a single round of calls failing to cover the required traceability entries. - Symptom: Cited knowledge base content cannot download traceability files. Cause: The
ENABLE_SOURCE_DOWNLOADconfiguration item is not enabled, or the download link field of the original file was not retained during parsing, resulting in a broken traceability chain.
How to Confirm Proper Configuration
- Upload a single duty-free policy PDF, wait for parsing to complete, then check the "Citation Traceability" module on the knowledge base details page to confirm that the document number and effective date fields are displayed.
- Call the knowledge base interface, pass in the duty-free product code keyword, and check whether the returned results include the product code and duty-free selling price fields of the corresponding price list.
- Adjust the similarity threshold to 0.8, initiate a test call, and confirm that the returned results only include traceability entries with strong keyword matching and no redundant data.
- Export a backup file of the specified knowledge base, check whether the export granularity includes the three categories of policy, price list, and ledger data, and confirm that it meets business classification requirements.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.