What the documents look like
Refund-only dispute handling differs from ordinary return-and-refund cases in one structural way: most matters have no returned-goods warehouse entry, so the evidence concentrates on dispatch, delivery and item value. Materials arrive from the platform after-sales console, carrier tracking, customer-service chat and warehouse outbound records. The daily documents are refund-only applications, dispatch vouchers, proof of delivery and appeal submissions. These materials often sit in different languages and different systems, and the same order can carry different identifiers across them. Citation tracing addresses a narrow question: can each quoted passage in an answer be mapped to specific source text, and does that source text fall inside the scope of this dispute.
Two industry facts shape this page. First, because there is usually no warehouse intake record, a delivery event and a named recipient are separate facts; tracking can confirm the former while leaving the latter unstated. Second, multilingual retrieval makes cross-language matching possible, so a Chinese question can surface an English-language knowledge item, but a similarity score reflects content relatedness only. It does not filter by order, party or authorization.
Constraints at the citation tracing step
The knowledge base search node can associate one or more knowledge bases that share the same vector model, and it outputs citations as an array whose length may be zero. An empty array means the output path still runs; it does not by itself show that the workflow stopped with an error. Semantic search supports cross-language understanding, which helps with multilingual dispute material, but the score is not a permission, party or validity filter. Hybrid search merges multiple retrieval paths through RRF, and reranking produces a 0–1 relevance score. The minimum relevance setting takes effect only under semantic search or when reranking is used. The citation limit is measured in tokens and is a separate matter from a thinking budget, which belongs to model reasoning.
Hypothetical drill sample: a cross-border store's after-sales specialist receives a refund-only application, order number A-2024-0871, application date 3 June 2024, item wireless earphones, amount 320 yuan. Source text reads: "Carrier tracking shows delivery completed on 28 May 2024; the recipient field is blank." And: "Warehouse outbound records state that one unit of this order's item was dispatched on 26 May 2024." The draft sentence under review reads: "The buyer personally signed for this order's item on 28 May 2024, and the appeal submission can proceed on that basis." The phrase "buyer personally signed" has no support in the source text; the recipient field is blank, so only the delivery event is confirmed, not the signing party.
Configuration and implementation checks
| Configuration item | Hypothetical starting value | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | Two bases sharing one vector model | Official text allows joint association only for the same vector model; check model identifiers first and exclude mismatches |
| Search mode | Hybrid search | Dispute material contains exact fields such as order numbers plus natural-language description; compare recall coverage against semantic search alone |
| Minimum relevance | 0.3 | Hypothetical trial starting value; compare against no threshold to observe whether unrelated fragments decrease |
| Citation limit | 2000 tokens | Hypothetical trial starting value; compare against 1000 tokens to observe whether key delivery information is truncated |
| Question optimization | Enabled | Multi-turn follow-ups often lack a subject; compare hit results against the disabled state |
| Reranking | Enabled | Use rerank scores to filter when candidates are numerous; compare ordering stability against vector scores alone |
Three common errors
- Treating a delivery tracking event as personal signing by the buyer. Input is the tracking source text above; the comparison point is whether the recipient field names a specific party; the observable result is that a blank recipient field cannot yield a personal-signing conclusion.
- Treating retrieval output as authorization. Input is the citation array returned by the knowledge base; the comparison point is whether that citation passed business review; the observable result is that a retrieval hit does not mean the appeal was approved or the material may be submitted.
- Treating minimum relevance as a party or permission filter. Input is material for other orders in the same knowledge base; the comparison point is whether the relevance threshold excludes content outside this order; the observable result is that similar content can still be recalled and requires manual order-number checking.
How to verify the setup
- Check the draft sentence against the tracking source text in the hypothetical sample. Input is the source line "the recipient field is blank" and the draft line "the buyer personally signed"; the comparison point is whether both point to the same fact; the observable result is that the draft exceeds what the source supports and should be rewritten to state the delivery event only.
- Check downstream handling of an empty citation array. Input is a clearly labelled paper output []; the comparison point is whether the downstream node continues execution on an empty array; the observable result is that the path runs through and produces no citation content. No claim is made that any fictional rule search must return empty.
- Check the association condition using two knowledge bases with different vector models. Input is the model identifiers of the two bases; the comparison point is whether the identifiers match; the observable result is that mismatched bases are excluded, and no cross-model retrieval is run to compare missed recall.
This page covers only: refund-only dispute handling / cross-border material and multilingual retrieval / citation tracing. Whether material, operations or requests are in an authorized state at handover cannot be decided by retrieval or a form.