What this workflow tool solves
Use the routing planner when an observable order attribute selects a different controlled pack instruction. Typical conditions may include a gift flag, channel code, promotion tag, item-count band, or an approved product variant. The tool orders rules by user-entered priority, identifies the narrow case where identical written conditions point to different instructions, and provides a default route. It replaces an informal operator choice with a reviewable draft matrix; it does not connect to an order system.
How to choose the inputs
Enter the product or order family, one controlled default instruction, and at least one condition-to-instruction rule. Write conditions using the exact data an operator or system can observe. Give lower priority numbers to rules that must be evaluated first. If two conditions can both be true, describe the intended combined condition or confirm through the responsible process which rule wins. The optional action field can name a handling note or record requirement after the route is selected.
How the workflow logic works
The planner ignores fully blank rows, requires both a condition and route for every active row, and accepts whole-number priorities from one through ninety-nine. Active rows are sorted from the lowest priority number upward. Conditions are compared without letter-case differences; when the same condition names different instructions, a conflict is listed. The tool does not infer overlap between differently worded conditions and cannot inspect live order attributes.
Worked example
A standard candle order defaults to PK-014 Rev B. Priority 10 sends orders tagged GIFT to PK-014-G Rev A, while priority 20 sends a three-unit bundle to PK-014-3 Rev C. The generated matrix shows the evaluation order and fallback. If another GIFT row points to PK-014-X, the output identifies the duplicate-condition conflict for resolution.
How to interpret the output
Resolve every reported conflict before the sheet reaches an operator. Then test normal orders, each individual condition, combinations of conditions, and an order with no listed condition. Confirm the source data uses the exact terminology in the sheet and that every referenced instruction is current. Retain who approved the routing logic and when it becomes effective.
Common mistakes
- Using conditions that cannot be seen in the order record.
- Assuming different wording prevents two rules from overlapping.
- Leaving no controlled default instruction.
- Pointing a rule to a superseded or unverified method.
Assumptions and limitations
This lightweight checker finds only exact duplicate-condition conflicts. It cannot parse Boolean logic, query inventory, read orders, check instruction status, or authorize an exception. User-entered priority is planning data, not an automated routing guarantee. Review privacy, product, channel, marketplace, facility, and regulatory constraints before applying any route.
Related workflow
- For Pack Variant Routing Planner, begin at the Pack Instruction & Job Release hub and keep its reusable-method data separate from batch execution.
- Use How to Write and Release Pack Instructions to prepare, trial, route, and close the record.
- Check field meanings in Pack Instruction and Job Record Fields before release.