What the documents look like
Supermarket supplier entry settlement revolves around four document families: purchase contracts, delivery acceptance notes, rebate agreements, and reconciliation statements. The data comes from ERP procurement, supplier portals, POS sales, and finance systems, and the work is shared among supermarket buyers, supplier sales staff, and finance settlement staff. In store service and internal training, conversations must explain how acceptance quantities are checked, how rebate deduction rates are calculated, how return variances are handled, and how the documents correspond to one another. These materials update weekly or monthly, and a single turn cannot cover the whole process, so multi-turn follow-up is the normal pattern.
A second characteristic matters for this page. The documents involve three parties and many fields, so a prompt must state the material scope, the answering task, and how to behave when evidence is missing, rather than letting the model fill in business facts. A third characteristic is that retrieval results and form values are inputs, not authorization. A knowledge base hit on a contract fragment, or a completed input form, does not by itself establish that the current operator may execute a settlement.
Constraints at the multi-turn prompts step
History records must distinguish what a new session actually carries from what a continued session carries. In knowledge base continuous conversation, coreference resolution and question expansion need checking when a knowledge base is genuinely present. Model context length and reply limits should be tested as a long-document plus follow-up combination. Reply format follows the downstream consumer; when json_schema is selected, the corresponding format requirement is filled in and the returned structure is verified.
Hypothetical drill sample: the source text for checking is "The March 2025 delivery acceptance note records 120 units of Product A accepted and 8 units returned; the reconciliation statement for the same month records 112 units of Product A settled. The rebate agreement provides for a 2% deduction rate applied to the accepted quantity." The draft sentence to be judged is "Product A is settled for March at 120 accepted units with a 2% deduction." This sentence conflicts with the 112 units recorded on the reconciliation statement, and the deduction base must be checked against the agreement field, so it is unsupported.
Configuration and implementation checks
The table below centers on that sample and lists officially described settings or implementation checks relevant to this feature and the primary task.
| Configuration item | Hypothetical trial starting point | Reason and comparison method |
|---|---|---|
| Memory turns | Keep a small number of prior turns | Store training Q&A usually needs only a few prior turns; compare against the default and adjust to actual follow-up depth |
| Reply limit | Hypothetical starting point 2000 | Must hold acceptance, return, and rebate field explanations; compare against observed truncation and adjust |
| Temperature | Low | Settlement wording requires stability; compare repeated answers to the same question |
| Reply format | Default | No downstream fixed-structure reader exists; change only if a later node must read structure |
| Multimodal recognition | Decided by model capability | If a delivery acceptance note is uploaded as an image, the model must support image recognition |
| Hide AI output | Off | Store training must display answers; during debugging it can be turned on temporarily to observe intermediate output |
Three common errors
- Treating accepted quantity as settled quantity. Input is the sample source text above; the comparison is the 120 units on the acceptance note against the 112 units on the reconciliation statement. These are different fields, and a draft sentence writing 120 units as settled is unsupported.
- Treating a retrieval result as an authorization basis. Input is a contract fragment returned by one knowledge base search; the comparison is that fragment against the current operator's authorization scope. A search hit does not mean the operator may execute settlement.
- Writing a pending-review state as completed. Input is a rebate agreement marked pending review; the comparison is the review status field. Pending review does not constitute an effective agreement or an executable deduction rate.
How to verify the setup
- Input the sample source text and the draft sentence, then compare the settled quantity in the draft against the field recorded on the reconciliation statement. The condition is met when "112 units" appears and the deduction base matches the agreement field; a draft still writing 120 units is unsupported.
- Input a follow-up that contains only the acceptance note and no reconciliation statement, then compare whether the answer states that reconciliation evidence is missing. An answer giving a definite settled quantity exceeds the material scope.
- Input a paper retrieval return of an empty result [], then compare whether the downstream node handles it as having no citation. A downstream node that outputs a settlement conclusion directly does not meet the condition. All three are paper checks and were not actually run.
The public technical facts checked for this feature are used to identify relevant content in the documents; they are not required to be copied as a fixed five-row table. Prompt and task: state the material scope, the answering task, and the handling of missing evidence, and do not let the model fill in business facts. History records: check the context actually carried in, and distinguish new-session input from continued-session input. Question optimization: check coreference resolution and question expansion when knowledge base continuous conversation is present, and do not assume every short question applies. Model and length: check the context and reply settings the model supports, and test long documents combined with follow-ups. Reply format: choose the format for the downstream consumer; when json_schema is selected, fill in the corresponding format requirement and verify the returned structure.
This page addresses only supermarket supplier entry settlement, store service and internal training, and multi-turn prompts. At operations handover, which materials, operations, and requests sit at which authorization state cannot be treated as authorized execution merely because a retrieval or a form was completed.