What the documents look like
For after-sales questions in Shopify fulfillment, this page examines FastGPT citation tracing. Compare the material received with the sources used in the answer. The examples are hypothetical.
Constraints at the citation tracing step
The proposed order attachment states that the order awaits handoff and that its logistics identifier has not been supplied. Both statements should remain traceable when answering a delivery-progress question. A citation to the item or shipping address does not address handoff progress. Save the retrieval output array and compare it with the citations received by the answer step, checking whether the status and missing-identifier note arrive together. Compare the final progress wording with the attachment and record any unsupported claim that shipment occurred.
Configuration and implementation checks
| Check | Input and condition for this task | Evidence to retain |
|---|---|---|
| Associated sources | Proposed order details and refund records; matching embedding models | Separate order and refund origins |
| Citation output | Test populated and empty arrays; an empty array can continue | Value actually received by the answer step |
| Citation handoff | Compare retrieval output with answer input | Awaiting-handoff status and missing logistics identifier retained together |
| Displayed origins | Trace each status to its own source | Completion and partial refund are not treated as mutually exclusive |
| Document currency | Identify policy and order versions separately | Missing return policy remains an evidence gap |
Documented conditions
| Documented item / implementation check | Condition |
|---|---|
Associated knowledge bases | Knowledge bases associated with one search node must use the same embedding model. |
Citation output | The output is an array; an empty array can continue. |
Citation input handoff | Inspect citations actually received by the answer step. |
Citation display check | Trace displayed sources to their originals. |
Document-validity check | Inspect source identity and applicable version separately. |
Three common errors
- If pending handover without a logistics identifier becomes dispatched goods, compare the retrieval array, citations received by the answer step and progress wording to locate the added event.
- If completed order and partial refund are treated as exclusive, trace the order and refund sources separately rather than erasing one dimension.
- If a policy answer cites only goods and address, inspect support for its policy sentences. A populated array need not be relevant, and an empty array does not imply automatic chain termination.
How to verify the setup
Order details containing item information and a shipping address do not supply return-policy evidence. Test a policy question by checking which statements the returned citations support; a populated array may contain only order text. An empty array can also continue downstream, so inspect the answer input and final wording in either case. A document-request or after-sales handoff route requires separate design. Acceptance should record the policy gap, citation handoff and the receiving result for that route independently.