Knowledge Base Retrieval and Recall for Condiment Marketing

What the data for this category looks like

Condiment marketing content data primarily comes from internal brand marketing material libraries, e-commerce platform product page copy, authorized content documents from partnered KOLs, and electronic print materials for offline promotional events. Update frequency aligns with new product launch cycles. Regular materials are updated weekly during new product launch phases, and monthly during standard cycles. Typical document structure includes material title, core promotional selling points, applicable consumer scenarios, compliance labeling requirements, and associated product SKU information. Fields include material unique identifier, delivery channel type, audit approval status, last update time. Some documents include packaging specification units such as bottle, bag, and similar terms.

What constraints these characteristics impose on retrieval and recall

The high-frequency update nature of condiment marketing materials requires the retrieval system to support incremental synchronization and scheduled update configurations, to avoid resource consumption from full retraining. Dispersed data from multiple sources needs unified metadata mapping rules, to ensure materials from different channels can be filtered and recalled using consistent dimensions. Compliance labeling requirements must be enforced as retrieval filter terms, to prevent recalling content that has not completed audit or carries compliance risks. Differences in copy style across delivery channels require classified display of recall results by channel type, to improve adaptability of marketing content. The requirement for associated SKU fields means the retrieval system must support metadata binding, to enable precise recall of targeted marketing content by product category.

How to set configurations

Configuration Item	Recommended Value	Rationale
`segment length`	`800–1200 characters`	Condiment marketing copy uses short paragraph structures. This segment range preserves contextual information linked to selling points, avoiding semantic fragmentation from excessive splitting
`recall count`	`Top 6–8 results`	Marketing scenarios need to cover selling points across multiple categories such as home cooking and commercial catering. This range balances recall coverage and result display efficiency
`similarity threshold`	`0.72–0.85`	This interval balances precise matching of core selling points and recall of relevant scenario content, avoiding missing applicable scenarios from overly high thresholds, or introducing irrelevant results from overly low thresholds
`reorder return count`	`Top 3–5 results`	Marketing content display needs to focus on core selling points. This range quickly presents the most relevant copy content, adapting to scenarios where users make rapid decisions
`PARSE_SPLIT_IMAGE`	`Enabled`	Condiment marketing materials often include product photos and packaging images. Enabling this parameter extracts OCR text from images as retrieval indexes, covering marketing content that combines text and images
`UPLOAD_META_FIELDS`	`Bind delivery channel, SKU`	This allows filtering recall results by delivery channel and associated product, improving scenario adaptability of marketing content

The parameter values provided on this page are common recommendations used as a starting point for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.

Three common configuration mistakes

Symptom: Enabling reorder return count set to Top 10 results without configuring an initial recall count limit causes retrieval responses to exceed 30 seconds, returning a 504 Gateway Timeout status code. Cause: The reorder model must process too many initial candidate documents, exceeding the system's preset response time threshold.
Symptom: After uploading marketing materials that include product packaging images, retrieval results do not match promotional selling points in the images. Cause: The PARSE_SPLIT_IMAGE parameter was not enabled, so OCR text from images was not extracted and added to retrieval indexes.
Symptom: Marketing materials uploaded via external API cannot be filtered for recall results using the SKU field. Cause: The SKU metadata to be synchronized was not declared in the UPLOAD_META_FIELDS configuration, resulting in incomplete metadata binding to the knowledge base index.

How to confirm configurations are properly set

Upload one condiment marketing copy document that includes text descriptions and product packaging images, check if parsed document fragments include OCR text content from the images.
Initiate a query that includes a specific consumer scenario, such as "cold dish seasoning copy for family gatherings", check if the number of returned results falls within the configured recall count range.
After enabling the reorder return count configuration, initiate multiple retrieval requests, confirm that single response latency does not show significant fluctuations.
Call the external upload interface to submit materials with delivery channel metadata, check if the metadata fields for this document are fully displayed in the knowledge base.
Call the search API to initiate a query, confirm that returned results comply with configured recall rules, and check if the conversation export function in the team edition backend is available.

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.