What the documents look like
Promotion registration and price management centers on price, inventory and campaign rhythm. The main data sources are the Tmall marketing console, the JD campaign console, ERP inventory and historical transaction prices. Day-to-day documents include the campaign registration form, the promotional price approval form, the inventory lock table and the campaign review table. Practitioners in this category include platform campaign operations staff, brand sales planners and finance business partners. Compared with product title compliance, the review focus here falls on the lowest net price, campaign inventory and multi-platform price synchronization; advertising wording review is not the primary task on this page. Errors in this category lead to campaign losses, loss of resource slots or price complaints.
In the inventory procurement and supplier materials task, documents carry purchase quantity, supplier quotation, supply validity period and authorization status. These fields determine whether the workflow can continue to the next step. The campaign registration form records which products enter which campaign window. The promotional price approval form records the requested campaign price and its approval stage. The inventory lock table records how much stock is reserved for a campaign. The campaign review table records outcomes after the campaign closes. None of these documents by itself authorizes procurement, inventory write-off or external synchronization; those actions require separate downstream implementation.
Constraints at the workflow routing step
The Form Input node is a user-interaction node. When it triggers, the conversation enters an interaction state and the workflow state is recorded; execution continues only after the user completes the interaction. When the user fills in the required information and submits, the node collects the submitted form values and passes them to subsequent nodes. The User Selection node is also a user-interaction node. When it triggers, the conversation likewise enters an interaction state and the workflow state is recorded. When the user makes a selection, the node evaluates that selection and executes the "yes" branch. Both nodes can be added repeatedly and both trigger execution.
Hypothetical paper exercise sample: the source material states, "Supplier A issued a quotation on 1 March 2025; the quotation states a unit price of 12 yuan for Type A stock goods and is valid until 31 March 2025. The brand sales planner submitted a promotional price approval form on 5 March 2025, applying for a campaign price of 13 yuan for Type A goods, with the campaign period running from 10 April to 12 April." The draft sentence to be assessed is: "Supplier A has confirmed supply at 12 yuan through 12 April 2025." This draft extends a quotation valid only through 31 March into a supply confirmation covering 12 April. The subject and object match, but the validity scope differs, so the draft is unsupported. A quotation validity period does not represent a supply period. Signing, reaching cooperation and contract effectiveness are three distinct facts.
Inventory lock tables and purchase quantities must be written by a business interface or a subsequent process; the form only collects values. Retrieval and similarity scores do not carry authorization or entity-isolation duties. Retrieval is not authorization.
Configuration and implementation checks
| Configuration item | Setting or check on this page | Relation to the sample |
|---|---|---|
| Form Input node | Triggers into interaction state, collects required information, passes it to later nodes after submission | Collects supplier quotation and campaign period fields |
| User Selection node | Executes the "yes" branch after the user makes a selection; verify branch connections one by one | Assesses whether the quotation falls inside the campaign period |
| Interaction state check | Recorded state is behavior of the interaction node; no separate global state-recording switch is set or claimed | Awaits supplementary validity explanation |
| Output handoff check | Passes collected information explicitly to subsequent retrieval, judgment or interface nodes | Compares quotation validity against campaign period |
| External action division | Order writes, document backfill and external status synchronization require a separate business interface or later process | Inventory lock and purchase writes do not occur at this node |
| Hypothetical trial starting point | Use 31 March 2025 as the quotation validity comparison baseline, because the source text states that date | Compare against the campaign period of 10 April to 12 April |
Three common errors
- Reading the quotation validity of 31 March 2025 as a supply period covering 12 April. The input is the sample source text; the comparison is the quotation validity against the campaign period; the observable result is that the two do not overlap and the draft sentence is unsupported. Do not supply authorization or effectiveness clauses to force a definite answer.
- Treating the quotation value collected by the Form Input node as a completed inventory lock or purchase write. The input is the submitted form value; the comparison is the node output against downstream interface actions; the observable result is that the node only passes values, and database writes and external synchronization require separate implementation.
- Using retrieval similarity or vector-model association results as a substitute for authorization judgment. The input is returned retrieval records; the comparison is record identifiers against the target retrieval scope; the observable result is that non-matching records are excluded, and retrieval produces no permission conclusion. Libraries across different vector models cannot be associated together; check identifiers only and record the actual observation.
How to verify the setup
- Using the sample source text as input, compare the quotation validity of 31 March 2025 against the draft claim of supply through 12 April 2025. Same supplier, same product, different validity scope; the finding is unsupported. The expected phenomenon is that the draft sentence fails the check, and the evidence gap remains.
- Using the draft sentence as input, compare its subject, object and status against the source text, observing whether confirmation wording appears that the source does not contain. The condition is met when the draft sentence is marked as pending verification, without producing a negative or conflicting conclusion.
- Using an explicit paper input of [] to check the downstream design, observe whether the empty-result handoff path is handled as designed, without claiming that a fabricated rule retrieval necessarily returns []. Cross-model retrieval is not executed; check identifiers only, exclude non-matching records and record the actual observation.
A pending review does not demonstrate a lack of operating permission, and a pending review status does not constitute approval.