Creator sales campaigns: citation tracing for procurement

Review citation tracing for procurement in Creator sales campaigns. Check document scope, failure paths and source evidence through controlled tests.

What the documents look like

Creator-hosted sales campaigns depend on external creator fulfillment and commission settlement. Procurement and supplier records for these campaigns are checked against four document types: creator cooperation agreements, commission setting sheets, sample shipment forms, and livestream performance reports. The main data sources named in the brief are the selected alliance, the creator marketplace, creator historical data, and store transaction details. Records update per session or per week.

For procurement and supplier materials, the purpose of citation tracing is to provide a traceable source so that purchase quantities, supplying entities, sample dispatch records, and settlement bases can be checked line by line. The update frequency itself does not change how citation sources are checked, and this page does not infer batch synchronization or real-time triggers from it. A retrieval result is not an authorization, and it does not confirm supplier qualification or cooperation status.

Constraints at the citation tracing step

The knowledge base search node selects one or more knowledge bases that share the same vector model and outputs cited content as an array whose length may be zero. When the array is empty, the output path still completes. The citation upper limit is controlled in tokens. The minimum relevance value takes effect only in semantic search or when result reranking is used. Hybrid search merges multiple retrieval paths through RRF. Reranking requires a rerank model and must be enabled by configuration. Image retrieval requires image input and the corresponding model capability. These conditions together mean that citation source checks must return to the selected knowledge bases and the record version. Retrieval is not authorization.

Hypothetical paper exercise: On 10 June 2025, a brand business operator prepares creator-hosted procurement records for checking. The source material to be checked consists of three sentences. First sentence: "Supplier A submitted a sample shipment form on 20 May 2025, shipping 30 units, with creator B as the recipient." Second sentence: "The commission setting sheet states a commission rate of 20% for this session, effective 1 June 2025." Third sentence: "The creator cooperation agreement is in pending review status, and the signing date field is empty." A draft sentence to be judged is: "Supplier A has completed supply, creator B has confirmed the commission rate, and the cooperation agreement is in effect." This draft sentence involves three distinct facts: sample shipment completed, commission rate stated, and cooperation agreement pending review. The sample shipment form can support the shipment act only, not completed supply. The commission setting sheet states a rate, not creator confirmation. Pending review status is not equivalent to being in effect.

Configuration and implementation checks

The table below centers on the exercise above and lists officially documented settings or implementation check items relevant to this feature and primary task. The values are starting points for this hypothetical exercise only, used to explain the reason for selection and the comparison object. They are not official default values.

Configuration or check itemHypothetical exercise starting pointReason for selection and comparison object
Associated knowledge basesSelect the procurement and supplier records base and the creator cooperation agreement baseBoth bases must share the same vector model; verify the identifier before deciding whether to associate them together
Search modeHybrid searchSupplier names and document numbers coexist with natural language descriptions; compare the recall difference between semantic search and full-text search
Citation upper limitSet to 3000 tokensA starting point for this exercise only; compare against the combined length of the three source sentences plus the draft sentence to observe whether truncation occurs
Minimum relevanceSet to 0.3A starting point for this exercise only; compare the increase or decrease in cited entries when enabled and disabled
Result rerankingEnabled by configurationA rerank model is required; compare the ranking position of the same supplier entry before and after reranking
Cited content outputCheck array elements one by oneCompare array elements against the source sentences to confirm that subject, object, and status match

Three common errors

  1. Treating pending review status as already in effect. In the exercise, the creator cooperation agreement has an empty signing date field, and the draft sentence states "the cooperation agreement is in effect." Check method: input the agreement source text, compare the status field with the draft sentence wording, and observe whether both point to the same fact.
  2. Treating a sample shipment form as proof of completed supply. In the exercise, the shipment quantity is 30 units, and the draft sentence states "has completed supply." Check method: input the sample shipment form source text, compare the shipment act with the supply act, and observe whether the draft sentence exceeds what the source supports.
  3. Treating a stated commission rate on the commission setting sheet as creator confirmation. In the exercise, the commission rate is 20%, and the draft sentence states "creator B has confirmed the commission rate." Check method: input the commission setting sheet source text, compare the unilateral statement with bilateral confirmation, and observe whether a creator confirmation record exists.

How to verify the setup

  1. For the first source sentence, input "Supplier A submitted a sample shipment form on 20 May 2025, shipping 30 units, with creator B as the recipient," compare the draft sentence "Supplier A has completed supply" against the source, and observe whether the draft sentence extends the shipment act into completed supply. If the draft sentence retains the shipment wording, the condition is met.
  2. For the second source sentence, input "The commission setting sheet states a commission rate of 20% for this session, effective 1 June 2025," compare the draft sentence "creator B has confirmed the commission rate" against the source, and observe whether the source contains a creator confirmation record. If the draft sentence is changed to "the commission setting sheet states a rate of 20%," the condition is met.
  3. For the third source sentence, input "The creator cooperation agreement is in pending review status, and the signing date field is empty," compare the draft sentence "the cooperation agreement is in effect" against the source, and observe whether pending review status has been rewritten as in effect. If the draft sentence retains the pending review wording, the condition is met.

These three verification items use the same hypothetical exercise, describing input, comparison object, and observable phenomenon item by item, without claiming that testing has been performed. When the retrieval result is an empty array, check the downstream handling design using the explicit paper input [], without claiming that a fictional rule retrieval necessarily returns an empty array. Knowledge bases with different vector models cannot be associated together; verify the identifier first and exclude non-matching ones, rather than performing cross-model retrieval to compare missed recall.