What the documents look like
Marketplace promotion enrollment and price management centres on price, inventory and campaign rhythm. Promotional wording review belongs to a different kind of work. The materials handled on this page are the campaign enrollment form, the promotional price approval sheet, the inventory lock sheet and the campaign review sheet. Data sources named in the category brief are the Tmall marketing backend, the JD campaign backend, ERP inventory and historical transaction prices, with updates occurring weekly and per campaign. At the order fulfilment and after-sales question stage, the operational question is which state a given order occupies among the promotional price, the inventory lock and the after-sales request, which actions already carry authorization, and which remain at the application or pending-review stage.
The category brief marks its confidence as approximate. The specific document set, update rhythm and backend names are treated as conditional context rather than verified facts about any particular merchant.
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 fields and submits, the node collects the submitted form information and passes it 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 corresponding "yes" branch. Both node types can be added repeatedly and trigger execution. The interaction state, the hidden dialogue box and the state recording are documented node behaviours; no separate global state switch is documented.
Order writes, document backfill and external status synchronisation require a separate business interface or a downstream flow. Retrieval and form collection do not constitute authorized execution: a form collects values, and approval and writes need downstream implementation. Semantic recall and relevance scores do not carry permission or entity isolation, and the same-vector-model requirement for a retrieval library does not extend to business-registration sites or other external systems.
Hypothetical paper exercise. The campaign enrollment form text reads: "Campaign name: Spring full reduction; enrolling entity: a brand flagship store; promotional price: 129 yuan; inventory lock quantity: 500 units; enrollment status is submitted, awaiting platform review." The promotional price approval sheet text reads: "Approval sheet number: SP-0312; corresponding promotional price: 129 yuan; approval status is awaiting finance BP approval; validity period: 10 March 2025 to 20 March 2025." The handover request to be judged reads: "Please lock inventory at the approved promotional price of 129 yuan and synchronise to the JD campaign backend." In this request the enrollment status is submitted and awaiting review, and the approval status is awaiting finance BP approval. Neither shows completed authorization. Inventory locking and cross-platform synchronisation are business actions that require a separately connected system implementation.
Configuration and implementation checks
| Check item | Documented setting or implementation check point | Relation to the sample on this page |
|---|---|---|
| Form Input node | Enters an interaction state on trigger, collects required information, passes it to subsequent nodes after submission | Collects campaign name, promotional price, inventory lock quantity and enrollment status |
| User Selection node | Executes the "yes" branch after the user makes a selection; verify each branch connection | Presents a choice on whether to continue submitting for approval and checks the branch |
| Interaction state check | State recording is a behaviour of interaction nodes; no separate global state-recording switch is documented | Confirms whether the enrollment form and approval sheet sit in interaction waiting or have been submitted |
| Output hand-off check | Passes collected information explicitly to subsequent retrieval, judgement or interface nodes | Passes approval status to a judgement node and compares output against input |
| External action division | Order writes, document backfill and external status synchronisation require a separate business interface or downstream flow | Inventory locking and JD backend synchronisation belong to downstream implementation, not to node built-in actions |
No numeric configuration is set on this page. If a hypothetical trial starting value is needed, an "approval waiting observation value: 48 hours" may be set, chosen to cover approval circulation within one business week, with the comparison method being whether the approval sheet status field moves from awaiting approval to approved. That value is a paper-exercise starting point only and is not an official default.
Three common errors
- Treating the enrollment status "submitted, awaiting platform review" as enrollment already passed. The input is the enrollment form text; the comparison is the value of the enrollment status field. The observable difference is that "submitted, awaiting review" and "passed" are distinct values, and the former does not constitute authorization of a campaign placement.
- Treating the approval sheet status "awaiting finance BP approval" as price already approved. The input is the approval sheet text; the comparison is the approval status field. The observable difference is that "awaiting approval" and "approved" are mutually exclusive values, and without a recorded approval the promotional price is unsupported.
- Treating "lock inventory and synchronise to the JD campaign backend" in the handover request as a node-executable action. The input is the request to be judged; the comparison is the documented functional scope of the nodes. The observable difference is that Form Input and User Selection only collect and branch, while writes and synchronisation require a separately connected interface.
How to verify the setup
- Input the enrollment form text and the approval sheet text from the hypothetical sample; compare the values of the enrollment status and approval status fields. The condition is met when both fields show awaiting review or awaiting approval, and the handover request is not treated as authorized execution.
- Input the handover request "Please lock inventory at the approved promotional price of 129 yuan and synchronise to the JD campaign backend"; compare the actions named in the request against the documented functional scope of the nodes. The condition is met when inventory locking and cross-platform synchronisation are identified as business actions requiring a separately connected system implementation, and the authorization gap is recorded.
- Input the branch connections of the Form Input node and the User Selection node; compare whether submitted information is passed to subsequent nodes and whether the "yes" branch executes after selection. The condition is met when output and input match item by item, and interaction waiting and state recording are explained as documented, without claiming that testing or approval has occurred.
The public technical facts checked for this feature, used to identify the relevant content in the documents rather than to be copied as a fixed five-row table, are: Form Input node, enters an interaction state on trigger, collects required information, passes it to subsequent nodes after submission; User Selection node, executes the corresponding "yes" branch after the user makes a selection, verify each branch connection; interaction state check, state recording is a behaviour of interaction nodes, no separate or claimed global state-recording switch; output hand-off check, passes collected information explicitly to subsequent retrieval, judgement or interface nodes and compares output against input item by item; external action division, order writes, document backfill and external status synchronisation require a separate business interface or downstream flow.