Logical
Prioritize example shipping workflow rules with IFS
Use an illustrative IFS decision tree to route special-handling flags before express requests and package-weight bands.
Put required review ahead of service preferences
This fictional workflow sends a special-handling flag to manual compliance review before considering an express request. It does not authorize a carrier service.
The weight bands and fees are invented teaching examples, not carrier limits, prices or dangerous-goods rules.
| WeightLb (A) | Express? (B) | Hazmat? (C) | Example workflow |
|---|---|---|---|
| 0.6 | FALSE | FALSE | Small parcel (<= 1 lb) |
| 4 | TRUE | TRUE | Manual compliance review (safety wins!) |
| 4 | TRUE | FALSE | Express review |
| 18 | FALSE | FALSE | Standard parcel (<= 50 lb) |
| 85 | FALSE | FALSE | Freight review (catch-all) |
Priority-ordered IFS carrier routing formula
Always place TRUE as the final test in IFS so heavy or unexpected inputs never return #N/A.
=IFS(C2, "Manual compliance review", B2, "Express review", A2 <= 1, "Small parcel", A2 <= 50, "Standard parcel", TRUE, "Freight review")Illustrative fee estimate
Pair fixed base fees with per-pound surcharges cleanly inside IFS.
=IFS(C2, 45 + A2 * 1.5, B2, 25 + A2 * 2, A2 <= 1, 5.5, A2 <= 50, 9 + A2 * 0.6, TRUE, 120)Inputs and interpretation
Validate nonnegative numeric weight and actual boolean flags before applying the example. Dangerous-goods transport depends on item classification, packaging, quantity, route and carrier approval; neither ground nor air suitability can be inferred from this single flag. Do not use these formulas to book shipments or quote actual rates.
Try the example
Use the original values or change them to test your understanding.