What the documents look like
A fresh-food concession counter inside a hypermarket is commonly operated by a supplier who stations staff on site and shares sales revenue with the store. This structure means order fulfilment and after-sales answering must reconcile materials from three parties at once: the hypermarket fresh-food department, the concession supplier and the store manager. The working documents are the concession contract, daily sales reports, shrinkage sheets and food purchase inspection records. The data sources behind them include the POS system, supplier delivery notes, food-safety ledgers and store stock counts. Errors carry consequences in food-safety penalties, gross-margin disputes and customer claims, so workflow routing has to keep material reconciliation separate from authorization status.
Constraints at the workflow routing step
The form-input node is a user-interaction node. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and after the user fills the required information and submits, the node passes the collected form information to later nodes. The user-selection node is also a user-interaction node. When it triggers, the conversation enters the interaction state, and when the user makes a choice the node evaluates that choice and executes the corresponding "yes" branch. Both nodes can be added repeatedly and trigger execution. The recorded interaction state is behaviour of the interaction node; no separate global state-recording switch is documented. Collected information must be explicitly passed to later retrieval, judgement or interface nodes. Order writing, document backfill and external status synchronization require a separate business interface or a later workflow. Retrieval and forms do not by themselves constitute authorized execution.
Hypothetical paper exercise: the source material reads "Party A is the fresh-food department of a hypermarket; Party B is a leafy-vegetable concession supplier; the two parties share daily sales revenue for the leafy-vegetable counter, contract period 1 March 2025 to 28 February 2026; the daily sales report for 10 April 2025 records leafy-vegetable sales of RMB 3,860, the shrinkage sheet records shrinkage of RMB 212 for that day; the food purchase inspection record for 10 April 2025 records three leafy-vegetable batches, inspected by Party B's on-site staff." The draft sentence to be assessed is: "On 10 April 2025 the leafy-vegetable shrinkage is borne in full by Party B, and Party A's sales share payable for that day is RMB 3,860." This draft sentence involves two business judgements, shrinkage allocation and sales-share settlement. It requires the shrinkage-allocation clause and the sales-share calculation method in the concession contract. The source material does not state either clause, so the authorization status and the settled amount remain to be verified.
Configuration and implementation checks
| Configuration item | Setting for this page | Verification method |
|---|---|---|
| Form-input node | Enters interaction state on trigger, collects required information | After submission, check whether the information is passed to later nodes |
| User-selection node | Executes the corresponding "yes" branch after the user chooses | Verify branch connections against each choice result |
| Interaction-state check | The interaction node records workflow state when triggered | Observe the conversation entering interaction state and resuming execution |
| Output hand-off check | Passes collected information to later retrieval, judgement or interface nodes | Compare each node output against its input |
| External-action separation | Order writing, document backfill and external status synchronization require a separate business interface or later workflow | Check whether a downstream implementation is declared; treat retrieval or a form as execution only when declared |
Hypothetical trial starting value for this page: set the leafy-vegetable shrinkage allocation ratio to 50% for paper comparison. The reason for choosing this value is that it makes the difference between the allocated shrinkage amount and the sales-share amount easy to observe, comparing the shrinkage-sheet amount of RMB 212 against the sales amount of RMB 3,860. This value is a hypothetical trial starting point only, not an official default, and does not represent a contract term.
Three common errors
- Treating the shrinkage amount collected by the form-input node as confirmed shrinkage allocation. The input is the RMB 212 shrinkage amount in the draft sentence; the comparison object is the shrinkage-allocation clause in the concession contract. When the contract clause is not stated, the allocation bearer and ratio for that amount remain to be verified.
- Treating the "yes" branch of the user-selection node as authorized execution. The input is the judgement request in the draft sentence that "Party A's sales share payable for that day is RMB 3,860"; the comparison object is the sales-share calculation method in the concession contract. When the contract does not state it, that settled amount is unsupported.
- Treating a retrieval result or a form submission as completed order writing or external synchronization. The input is the business action in the draft sentence concerning settlement and allocation; the comparison object is whether a downstream business interface or later workflow is declared. When none is declared, that action remains pending connection to another system.
How to verify the setup
- Input the source material and the draft sentence from the hypothetical paper exercise. Compare the shrinkage-allocation bearer in the draft sentence against the shrinkage-allocation clause in the concession contract. If the contract clause does not state that Party B bears the full amount, the allocation bearer remains to be verified and cannot be judged as full bearing by Party B.
- Input the source material and the draft sentence from the hypothetical paper exercise. Compare the sales-share amount of RMB 3,860 in the draft sentence against the sales-share calculation method in the concession contract. If the contract does not state calculation on the full sales amount, that settled amount is unsupported and the contract clause must be supplied before further checking.
- Input the source material and the draft sentence from the hypothetical paper exercise. Compare the business action in the draft sentence against any declared downstream implementation. If no order-writing or external-synchronization interface is declared, that action remains pending connection to another system, and neither the form submission nor the retrieval result constitutes completed execution.