What the documents look like
Retail checkout and loyalty promotion work centres on four document types: promotional price tags, membership points rules, checkout daily reports and exception refund slips. The materials that matter for copy drafting are the price tag and the points rule, because both carry figures and effective ranges that a draft sentence can misstate. Data originates from the POS system, the membership CRM, the payment platform and the price tag system, and it updates daily or per shift. That update rhythm matters here only in one way: a price tag's effective range can change between shifts, so a draft sentence that cites a date range needs the range checked against the tag text in hand rather than against a remembered figure.
Short-shelf-life inventory is outside this scope. Checkout promotion work concerns price expression and membership benefit expression, and the drafting task inherits that focus. The consequence of getting it wrong is a price complaint, a cash shortfall or surplus, or a membership benefit dispute, which is why the drafting step needs the source wording kept alongside the draft.
Constraints at the workflow routing step
Two documented interaction nodes shape routing. 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 downward after the user completes the interaction. The user selection node behaves the same way on trigger, and when the user makes a choice the node evaluates that choice and executes the "yes" branch. Both are documented node behaviours. The interaction state and the branch execution are properties of these nodes, and no separate global state-recording switch is documented.
A hypothetical paper exercise sample for this page, labelled as hypothetical and not drawn from any real record:
Source text one: "Store membership points rule: each 1 yuan of spending earns 1 point; points may be deducted against the next purchase; the deduction ratio is 100 points to 1 yuan."
Source text two: "Promotional price tag: 1 March 2025 to 7 March 2025, a certain brand 500 millilitre beverage at a promotional price of 3.5 yuan, original price 4.5 yuan."
Draft sentence to be assessed: "A member earns 1 point per 1 yuan of spending, and the points deduction ratio is 100 points to 1 yuan; a certain brand 500 millilitre beverage is at a promotional price of 3.5 yuan from 1 to 7 March."
This sample exists to check whether the draft sentence matches the source texts on subject, object, figures and effective range. Anything the source texts do not state stays unknown. No authorisation clause or effective clause is to be supplied to make the draft look settled.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this exercise | Reason and comparison method |
|---|---|---|
| Required fields on the form input node | Promotional price tag source text; membership points rule source text | The draft sentence draws its subjects and figures from these two items; compare each draft figure against the corresponding source text |
| Branch on the user selection node | The "yes" branch used to confirm the draft sentence may be submitted | The document states the "yes" branch executes after the user makes a choice; verify the branch connection item by item |
| Interaction state check | Conversation enters the interaction state on trigger | The document states interaction nodes record workflow state; no separate global switch is asserted |
| Output handover check | Collected information passed to a later retrieval or judgement node | Compare output against input item by item to confirm the information is carried through |
| Division of external operations | Order writes, document backfill and external status synchronisation attach to a separate business interface | The document states these operations require a separate business interface or a later flow |
Three common errors
- Widening the earning condition. Input is source text one. The comparison object is the points expression in the draft sentence. The observable result is whether the draft adds a spending-type scope that the source text does not state, for example turning "each 1 yuan of spending earns 1 point" into a claim that all spending earns points.
- Extending the promotional period. Input is source text two. The comparison object is the date expression in the draft sentence. The observable result is whether the draft states a validity beyond the range recorded in the source text, such as describing the promotional price as long-term valid.
- Treating collected form information as already business-verified. Input is the form submission action. The comparison object is whether a later node performs a separate verification step. The observable result is whether the later node only carries the information forward without checking it against the source texts.
How to verify the setup
- Take source text one and the draft sentence. Compare the subject, the figure and the deduction ratio in the draft's points expression against the source text. If the draft introduces a spending-type scope or a points validity period that the source text does not state, record the sentence as unsupported and note the evidence gap.
- Take source text two and the draft sentence. Compare the product name, the pack size, the price and the date range in the draft against the source text. If the draft date range falls outside 1 March to 7 March, record it as beyond the recorded effective range and keep the source text as the comparison basis.
- Take the collected result from the form input node and the receiving record of the later node. Compare whether the information was carried through completely. If the later node did not receive a required field, or received a field that differs from what was submitted, record an output handover anomaly and check the node connection and field mapping.
Across all three checks, a pending request is not an approval, an offered option is not an execution, and an unsigned termination is not a completed termination. Where a document field was not provided, the value remains unknown.