What the documents look like
Supermarket supplier onboarding and settlement usually runs on purchase-and-sale or consignment payables rather than a staffed in-store counter. That distinction shapes what workflow routing has to handle: the correspondence between delivery documents and payable records, not on-site counter management. The main data sources are ERP purchasing, the supplier portal, POS sales, and the finance system. The everyday documents are the purchase contract, the delivery acceptance note, the rebate agreement, and the statement of account. Updates arrive weekly or monthly.
Three steps consume the most time: reconciling accepted quantities, calculating rebate deductions, and handling return differences. An operating report and exception review workflow therefore has to organize its inputs and its decision points around those three reconciliations. The purchase contract, delivery acceptance note, rebate agreement, and statement of account each carry different fields, and a workflow that treats one document as a substitute for another will route on the wrong basis.
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 execution continues only after the user completes the interaction. After the user submits the required information, the node collects what was entered and passes it to later nodes. The user selection node is also a user interaction node. It enters the interaction state in the same way, and when the user makes a choice, the node evaluates that choice and executes the corresponding "yes" branch.
These two nodes collect values and route branches. They do not write orders, backfill documents, or synchronize external status. Those actions require a separate business interface or a later process. Retrieval and form collection do not constitute authorization. Approval status, signature status, and contract effectiveness status are separate facts, and a pending request is not an approval.
Hypothetical exercise sample: a delivery acceptance note reads "Supplier A, delivery date 12 March 2024, accepted quantity 480 units, acceptance officer has signed." A statement of account reads "Supplier A, March 2024 settlement period, accepted quantity 500 units." The proposed handoff request is "Please generate the March settlement report on the basis of 500 units." The subject, period, and field needed for the judgment are all stated, and the two materials carry mutually exclusive values in the accepted quantity field.
Configuration and implementation checks
The table below uses that sample to list documented node behavior or implementation checks relevant to this page's primary task. The numeric value is a hypothetical test starting point used to explain the comparison method; it is not an official default.
| Configuration or check item | Value or practice on this page | Reason and comparison object |
|---|---|---|
| Form input node | Collect supplier name, settlement period, accepted quantity | Compare field by field against the delivery acceptance note and the statement of account |
| User selection node | Set a "yes" branch for the quantity difference | After the user makes a choice, execute the corresponding branch |
| Interaction state | Triggered and recorded by the interaction node | Check whether execution continues downward after submission |
| Output handoff | Pass collected values to later judgment nodes | Compare output against input item by item |
| Quantity comparison starting point | Hypothetically use the acceptance note value of 480 units as the baseline | Compare against the statement value of 500 units; the difference is 20 units |
| External action split | Report generation and order writing connect to separate interfaces | The node itself does not perform writes or synchronization |
Three common errors
- Treating form submission as settlement authorization. In the sample, the draft request asks for a report on the basis of 500 units. The submission action only completes information collection. The difference between the statement and the acceptance note has not been verified, so the settlement basis cannot be treated as established on that basis.
- Treating the user selection branch as automatic judgment. In the sample, the quantity difference requires a human to choose a branch. The node does not decide on its own which material governs.
- Treating retrieval or form collection as permission isolation. In the sample, the two materials share the same subject, the same period, and the same field, and their values are mutually exclusive, which is a contradiction. If materials are missing or only show a related stage, the correct record is unsupported or pending verification.
How to verify the setup
- Enter the delivery acceptance note and the statement of account from the sample, compare the accepted quantity field values of 480 units and 500 units, and observe whether the system presents both side by side without automatically selecting one. Side-by-side presentation that preserves the difference satisfies the condition.
- Enter the draft sentence "Please generate the March settlement report on the basis of 500 units," compare that request against the quantities stated in the two materials, and observe whether the system flags the quantity inconsistency and waits for a human choice. A flag followed by entry into the interaction wait satisfies the condition.
- Enter an explicit paper-based empty result [] and compare whether downstream nodes accept it as designed for empty input, then observe whether an unsupported report output appears. Downstream handling of empty input without producing a settlement conclusion satisfies the condition. An empty retrieval result, a miss, or irrelevant returned items are observable phenomena and do not support an inference about permissions or entity scope.
A pending request is not an approval, an offered option is not execution, and an unsigned termination is not a completed termination. Where a document field is not provided, it remains unknown.