What the documents look like
Pinduoduo low-price campaign operations revolve around low-price resource slots, campaign inventory and refund-rate fluctuation. The documents handled day to day are campaign registration forms, product cost calculation sheets, after-sales refund records and platform site messages. This page addresses only one step of product and marketing copy drafting: citation source and traceability. It asks whether prices, inventory, campaign status and after-sales promises that appear in a draft sentence can be matched to wording in the materials supplied for checking. Campaign rhythm advances by session, and materials may be updated daily or per campaign; that frequency does not change the tracing method, it only affects which version is selected during checking.
Two features of this category shape the task. First, campaign status and campaign price are recorded in separate documents, so a draft sentence can mix a status field from one document with a price field from another. Second, after-sales promises and inventory figures often appear in platform site messages as notices about future arrangements, not as confirmed quantities or terms. Both conditions mean that a sentence can look internally consistent while lacking a matching field in any supplied material.
The retrieval step obtains citation content through the knowledge base search node. That node outputs citations as an array, and the length may be zero; an empty array does not mean the workflow has errored or terminated. The citation limit is counted in tokens. The minimum relevance value is a filtering threshold and takes effect only under semantic retrieval or result reranking; it does not perform permission or entity isolation. Linked knowledge bases must share the same vector model, so cross-model linking is not possible; during checking, verify the identifier first and exclude those that do not match.
Constraints at the citation tracing step
Citation tracing requires that each externally facing copy sentence can be traced back to a specific material. The product cost calculation sheet supplies cost and campaign price range. The campaign registration form supplies registration status and campaign scope. The after-sales refund record supplies after-sales facts. The platform site message supplies platform notification content.
Hypothetical paper exercise sample. The materials supplied for checking are three sentences. The first comes from a campaign registration form: "The registration status for this campaign is submitted; the platform has not yet issued a review result." The second comes from the product cost calculation sheet for the same campaign: "The campaign price range for this product is 9.9 yuan to 12.9 yuan, the cost is 8.5 yuan, and the quotation is valid until 30 June 2025." The third comes from a platform site message: "The display time for this resource slot is subject to later platform notice." The draft sentence to be judged is: "This product has passed platform review, the campaign price is 9.9 yuan, inventory is sufficient, and seven-day no-reason returns are supported."
The judgment requires the same subject, the same period and the same field. The registration status field reads "submitted, not reviewed"; the draft sentence writes "passed review". Mutually exclusive values in the same field constitute a contradiction. The campaign price of 9.9 yuan falls inside the material range and is supported. Inventory and the return promise do not appear in the materials; they are unsupported and the evidence gap must be recorded. A pending review does not demonstrate a lack of operating permission, and it does not equal review approval. The quotation validity date does not represent a supply period. An unsigned termination is not a completed termination, and an offered option is not execution.
Configuration and implementation checks
| Configuration or check item | Value or practice on this page | Basis and explanation |
|---|---|---|
| Linked knowledge bases | Select libraries that contain the campaign registration form, cost calculation sheet, refund record and site message and that share the same vector model | Same vector model is required for joint linking; verify the identifier first |
| Citation limit | Hypothetical exercise starting value of 2000 tokens, adjusted after comparison with the length of a passage containing complete campaign terms | The citation limit is counted in tokens; this is not an official default |
| Minimum relevance | Hypothetical exercise starting value of 0.4, compared with scores of samples judged relevant by hand | Takes effect only under semantic retrieval or result reranking |
| Search mode | Use hybrid retrieval for queries containing campaign numbers and status, merged through RRF | RRF is a fusion process, not a toggle |
| Citation handoff | Pass the citation array to the answering step and check each answer sentence against the cited source text | Output length may be zero; an empty array still completes the chain |
| Manual checking action | Compare the draft sentence with the source text by same subject, same period, same field | Fields not stated are recorded as unsupported |
Three common errors
- Writing registration status "submitted, not reviewed" as "passed review". The input is the registration form text and the draft sentence; compare the value of the same status field, and mutually exclusive values are judged contradictory. A pending review does not demonstrate a lack of operating permission, and it does not equal review approval.
- Treating inventory and the return promise, which the materials do not state, as supported. The input is the cost calculation sheet and the site message; compare whether an inventory quantity or return clause field appears, and record absence as unsupported while preserving the evidence gap.
- Treating the quotation validity date as a supply period. The input is the cost calculation sheet text; compare "the quotation is valid until 30 June 2025" with the supply wording in the draft sentence. These are different facts and cannot substitute for each other.
How to verify the setup
- Input the three source sentences above and the draft sentence, then compare the registration status field. Mutually exclusive values in the same field satisfy the contradiction-detection condition; the expected outcome is that the contradiction is flagged and the sentence is returned for revision.
- Input the cost calculation sheet text and the draft sentence, then compare whether the campaign price falls within the 9.9 yuan to 12.9 yuan range. A value inside the range satisfies the condition for a supported price; the expected outcome is that the sentence is retained with its source attached.
- Input a paper-based empty citation array and compare whether the downstream answering step still executes and states truthfully that no citation was obtained. The expected outcome is that the chain completes without fabricating a source. Whether retrieval hits is affected by data and parameters; a first-position hit or an empty result for an unrelated query is not guaranteed.
Retrieval is not authorization. Forms collect values, and business verification, approval, database writes and external synchronization require their stated downstream implementation. Where a document field is not provided, it remains unknown.