What the documents look like
Marketplace promotion registration and price management turns on price, stock and campaign timing. That focus separates it from product-title compliance review, which examines promotional wording. The documents handled day to day are campaign registration forms, promotional price approval sheets, stock lock sheets and campaign review sheets. Source data sits in platform marketing back ends, activity back ends, ERP stock records and historical transaction prices. The comparison task aligns the registration form, the approval sheet and the lock sheet field by field: subject, object, price, locked quantity and campaign period.
This page covers only the contract-and-transaction-material comparison inside this category, and only the tool call and plugin step. Documented node behaviour sets the execution boundary. After the tool call node decides to call a tool, it returns the tool result to the AI for summarised output by default. The tool call termination node can force the current tool call to end, so no further tools are called and the AI is not asked to answer from tool results. Custom variables extend the variable input of a tool.
Three industry facts shape this step. Promotion registration centres on price, stock and campaign rhythm, so the material to align is numeric and state-based rather than wording-based. The documents update weekly and per campaign, which means a comparison must state the period it covers rather than assume one current version. Errors here carry campaign loss, loss of a resource slot and price complaints, so a draft sentence that reads as approved execution deserves a field-level check rather than a summary judgement.
Constraints at the tool calls step
A tool introduction tells the model what the tool is for. Parameter descriptions and whether a parameter is required both affect the call decision. Where a required parameter has no suitable value in context, the model may not call the tool; prompt wording can guide the user to supply the parameter. In advanced orchestration, available tools connect to the tool call module, and a small number of tools is the recommended starting point before tuning further. When the termination node sits after a tool, workflow execution reaching that node forces the current tool call to end.
Retrieval or a form collecting values is not authorisation to execute. Business verification, approval, database writes and external synchronisation each need their own downstream implementation. A similarity setting does not carry permission or entity isolation. The same-vector-model requirement for knowledge base association does not extend to external systems. Knowledge bases built on different vector models cannot be associated together; check the identifier first and exclude those that do not match.
Hypothetical paper exercise sample. The material text supplied for checking is three sentences. Sentence one: "Subject: a brand sales planning group; object: product A; status: promotional price approval sheet submitted, approval status pending review; effective scope: 1 June 2025 to 30 June 2025." Sentence two: "Subject: a platform activity operator; object: product A; status: stock lock sheet generated, locked quantity to be confirmed; effective scope: 1 June 2025 to 30 June 2025." Sentence three: "Subject: a finance business partner; object: product A; status: historical transaction price record exported, lowest net price under calculation; effective scope: 1 May 2025 to 31 May 2025." The draft sentence to be assessed is: "Product A promotional price approval has passed, stock is locked, registration can proceed." This draft sentence depends on the approval status and the stock lock status.
Configuration and implementation checks
The table below relates only to this feature and this primary task, using documented settings or implementation checks. The values are starting points for this hypothetical exercise, with the reason for choosing them and the comparison method.
| Configuration item | Hypothetical exercise starting point | Reason and comparison method |
|---|---|---|
| Tool introduction | State the input conditions and the situations in which the tool should not be called | The introduction tells the model what the tool is for; check it against the actual request |
| Tool parameters | Check system module parameters and configurable plugin parameters separately | A parameter description is not a guarantee of execution |
| Required parameters | Where a suitable required parameter is absent, the model may not call the tool | Complete the value through interaction and check the actual request |
| Tool connection | In advanced orchestration, connect available tools to the tool call module | Start with a small number of tools before tuning |
| Tool call termination | Placed after a tool, it forces the current tool call to end | No further tools are called and the AI does not summarise |
| Custom variables | For nodes not treated as tool parameters or not callable as tools | Supply the parameter description and check the actual call |
Three common errors
- Treating pending review as passed. In the sample, the promotional price approval sheet status is pending review, while the draft sentence says approval has passed. The input is the approval sheet text and the draft sentence; the comparison is the approval status field. Pending review is not passed, so the draft sentence is unsupported on that field.
- Treating a quantity to be confirmed as locked. In the sample, the stock lock sheet shows locked quantity to be confirmed, while the draft sentence says stock is locked. The input is the lock sheet text and the draft sentence; the comparison is the locked quantity status field. To be confirmed is not locked, so the draft sentence is unsupported on that field.
- Treating calculation in progress as a completed lowest net price. In the sample, the lowest net price is under calculation, and the draft sentence does not mention that field directly, yet "registration can proceed" depends on the price calculation being complete. The input is the historical transaction price record text and the draft sentence; the comparison is the calculation status field. Under calculation is not complete, so the draft sentence is unsupported on that dependency.
How to verify the setup
- Check the approval status. Input the first sample sentence and the draft sentence "Product A promotional price approval has passed". Compare the approval status field: the source says pending review, the draft says passed. Expected observation: the two take different values on the same field, so the claim is unsupported. The support condition is met only if the source states passed and the effective scope matches.
- Check the stock lock status. Input the second sample sentence and the draft sentence "stock is locked". Compare the locked quantity status field: the source says to be confirmed, the draft says locked. Expected observation: the two take different values on the same field, so the claim is unsupported. The support condition is met only if the source states locked and the quantity is explicit.
- Check the price calculation status. Input the third sample sentence and the draft sentence "registration can proceed". Compare the calculation status field: the source says under calculation, the draft depends on calculation being complete. Expected observation: under calculation is not complete, so the claim is unsupported. The support condition is met only if the source states calculation complete and the lowest net price is explicit.
All three checks use the hypothetical source text and draft sentence given above, and each states the input, the comparison object and the expected observation. Fields that are not stated, or that carry only a related stage of evidence, remain to be verified and are not judged as denial or conflict. Pending review does not show a lack of operating authority. Signing, reaching agreement and contract effectiveness are three distinct facts. A quotation validity period does not indicate a supply period. No test, deployment, approval, refund or other business action is claimed here.