What the documents look like
Marketplace promotion enrollment and price management centres on price, stock and campaign rhythm. It differs from product title compliance work, which centres on review of promotional wording. The main data sources are the Tmall marketing backend, the JD campaign backend, ERP stock data and historical transaction prices. The everyday documents are the campaign enrollment form, the promotional price approval form, the stock lock table and the campaign review table. The most time-consuming steps are calculating the lowest final price, locking campaign stock and synchronising prices across platforms. In store service and internal training, these materials pass through workflow routing so that the handover becomes an interactive process that can be checked.
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. After the user completes the required information and submits, the node collects the submitted form information and passes it to later nodes. The user selection node is also a user interaction node with the same interaction behaviour. When the user makes a choice, the node evaluates that choice and executes the "yes" branch. The recorded interaction state is behaviour of the interaction node itself; no separate global state-recording switch is documented. Information collected by these nodes must be explicitly passed to later retrieval, judgment or interface nodes. Order writing, document backfill and external status synchronisation require a separate business interface or a later flow. Retrieval and form collection do not constitute authorised execution. During operations handover, the authorisation status of each material, action and request must be checked separately.
Hypothetical drill sample: a store submits a campaign enrollment form with the following text: "Campaign name: Spring full-reduction; enrollment entity: East China Region 1 store; promotional price approval form number: SP-0417-02; approval status is pending review; stock lock table status: not locked; applicable period: 20 April 2025 to 30 April 2025." A draft handover sentence reads: "Approval has passed, so stock can be locked directly and prices synchronised across platforms." This sentence is the item to be assessed.
Configuration and implementation checks
| Configuration item | Relevant setting or implementation check on this page | Relation to the sample |
|---|---|---|
| Form input node | Enters interaction state on trigger, collects required information, passes it to later nodes after submission | Collects enrollment entity, approval form number and approval status |
| User selection node | Executes the corresponding "yes" branch after the user makes a choice; verify each branch connection one by one | Sets a selection branch for "approval obtained" |
| Output handover check | Passes collected information explicitly to later retrieval, judgment or interface nodes; compare input and output item by item | Checks whether the approval status field is passed into the judgment node |
| External action separation | Order writing, document backfill and external status synchronisation connect to a separate business interface or later flow | Stock locking and price synchronisation are not executed by this node |
| Hypothetical trial starting point | This drill takes "pending review" as the starting approval status because the enrollment form states so; compare against the corresponding field of approval form number SP-0417-02 | The judgment branch is checked against this starting point |
| Interaction state check | The recorded state is interaction node behaviour; no separate global state-recording switch is documented | Checks whether execution continues downward after submission |
Three common errors
- Treating the collected "approval status is pending review" as authorisation already granted. Input is the enrollment form text; compare the approval status field against the value "pending review"; observe whether it is misread as permitting stock locking.
- Treating the "yes" branch of the user selection node as approval itself. Input is the selection result; compare the branch execution condition against the actual approval form status; observe whether the selection action is equated with completed approval.
- Treating retrieval or form output as authorisation for stock locking or cross-platform price synchronisation. Input is the collected information; compare whether later nodes connect to a separate business interface; observe whether the external action separation is missing.
How to verify the setup
- Input the hypothetical sample text "approval status is pending review; stock lock table status: not locked" and compare it with the draft sentence "Approval has passed, so stock can be locked directly and prices synchronised across platforms." Observe whether the draft sentence matches the source on the same entity, the same period and the same field. The source does not state that approval passed, so the sentence is unsupported.
- Input the hypothetical sample "promotional price approval form number: SP-0417-02; approval status is pending review" and compare it with the user selection node branch condition. Observe whether the branch executes the lock request only when the approval status is explicitly passed. A pending review status does not satisfy the execution condition.
- Input the hypothetical sample "applicable period: 20 April 2025 to 30 April 2025" and compare it with the stock lock table status field. Observe whether the lock request is submitted within the period and only after the approval status is explicit. The source states the stock lock table status is not locked, so the request remains pending verification.
The primary task of this page is workflow routing for marketplace promotion enrollment and price management in store service and internal training. Verification checks the named primary task: whether collected form and selection values are handed to later nodes correctly, and whether draft handover copy stays within the source wording. It does not drift into identity certification, report analysis or any other task. Where a field is not provided in the source, it remains unknown.