Move the warehouse rule out of someone’s memory
Name the rule, then draw the decision the way the floor explains it
Create a searchable automation, start it when an order is created, and put each condition and action on the canvas. This rule checks for one fragile SKU shipping within the US before it changes the order.
When both checks pass, Cybership turns on the fragile flag and requires a pack shot. The false branch ends without changing the order, so an ordinary order does not inherit special handling.
Create Automation
Name the process so operators can find it in the automation library.
Tags
Fragile domestic glassware
Visual workflow builder
Start when…
Order Created
Triggered when a new order is created
orders/createdCheck if…
All conditions must match
SKU equals GLASS-VASE-12
Shipping country equals US
Do this…
Set Fragile Flag
Fragile flag
On
Do this…
Require Pack Shot
Pack shot
Required
False branch: End the run without changing the order.
Prove every field and action before the rule can go live
Configure conditions from the Order Created fields and map each action back to that same order. Publish validation checks the trigger, action inputs, graph connections, and referenced fields as one workflow.
Invalid field paths, missing action values, or disconnected steps stop publication. A rule that passes becomes published version v1.0.0, giving future runs a specific version to reference.
Condition
Use fields supplied by the selected trigger.
Condition 1 · At least one line item
Field
Expected value
Available trigger path
Condition 2 · Order
Field
Expected value
Available trigger path
Actions
Both actions use the Order ID supplied by Order Created.
Set Fragile Flag
Set the fragile flag on an order
Order ID
Mark order as fragile
Require Pack Shot
Require pack shot photos before shipping an order
Order ID
Pack Shot Override
Publish validation
The rule must pass every check before it can become active.
One configured trigger
Order Created supplies the fields and variables used downstream.
Actions are fully configured
Both order actions have a resolvable Order ID and explicit value.
Every step is connected
Trigger → condition → Fragile flag → Pack shot.
Fields exist for this trigger
{{id}}, the line-item SKU path, and shipping country all resolve.
Invalid paths, missing configuration, and disconnected steps block publishing.
Version 1.0.0 created successfully
Keep every run and retry on its own record
Execution history shows status, version, start time, duration, and completed steps before an operator opens a run. The detail view then follows the trigger, condition result, and both packing actions in order.
Retry starts a separate execution from the same published version and trigger context. The original failure remains visible while the new run records its own completed outcome.
- Total Executions
- 4
- Success Rate
- 75%
- Active
- 0
- Failed
- 1
All Executions
Every run keeps its own status, version, progress, and timing.
| Status | Version | Started | Duration | Steps Completed |
|---|---|---|---|---|
Completed Selected | v1.0.0 | Jul 23, 2026 at 12:07 PM | 241 ms | 4 / 4 |
Completed | v1.0.0 | Jul 23, 2026 at 12:04 PM | 228 ms | 4 / 4 |
Completed | v1.0.0 | Jul 23, 2026 at 12:01 PM | 96 ms | 2 / 4 |
Failed | v1.0.0 | Jul 23, 2026 at 11:58 AM | 3.2 s | 1 / 4 |
Execution Details
Fragile domestic glassware · #NFO-10477
- Version
- v1.0.0
- Started
- Jul 23, 2026 at 12:07 PM
- Duration
- 241 ms
- Steps Completed
- 4 / 4
Started when…
01Order Created
#NFO-10477 supplied the order context
CompletedChecked if all conditions were met
02All conditions must match
GLASS-VASE-12 and US both matched
CompletedDid this…
03Set Fragile Flag
Order flagged for fragile handling
CompletedDid this…
04Require Pack Shot
Pack-shot requirement set to Required
Completed
Re-run history
Retry creates another execution; it does not overwrite the failed record.
Original execution
Jul 23, 2026 at 11:58 AM
New execution
Jul 23, 2026 at 12:07 PM
The completed re-run keeps version v1.0.0 and the original Order Created context. The failed execution remains visible above it.
The rule and its operating evidence stay together
Fragile domestic glassware is narrow enough to understand at a glance: two order checks, two packing actions, one published version, and a trace that shows what happened when it ran.
- conditions
- 2Line-item SKU and shipping country must both match before either packing action runs.
- packing actions
- 2Turn on fragile handling and require a pack shot against the same Order ID.
- steps completed
- 4 / 4Trigger, condition, and both actions remain visible on the selected execution.
- published version
- v1.0.0The failed original and its completed re-run keep the same version reference.
Trusted by 3PLs and brands
See it in your operation
Bring us the warehouse decision your team still repeats by hand
Show us the event, checks, and follow-up work behind one operating rule. We’ll map the workflow, publication checks, and execution history against your process.
No sales call is required to get sandbox access.
Continue exploring
Related workflows
Reports & Analytics
Analytics
Run scoped operational reports, inspect recent detail captured with each result, export table data, and schedule recurring reviews.
MerchantOS
Brand Workspace
Give each client team a permission-aware workspace for orders, available inventory, tracked warehouse requests, and team access.
Rate Shop
Shipping
Define exact service pools, delivery requirements, and a bounded preference evaluated at label purchase.
Order Orchestration
Orders
Keep fulfillment-order exceptions on the record: expose only valid actions, preserve exact quantities through plan changes, and hand ready work into picking.