Order rules
In Floormode, an order rule watches for one moment in an order’s life, checks its conditions, and acts: it adds or removes a tag, holds the order, sets its priority, sends it to another warehouse, tells the packer something, sends you an alert, or tells your own tools. Rules are in Settings → Orders & dispatch → Order rules.
On this page
Section titled “On this page”- Start from an example
- When a rule starts
- What a rule can check
- What a rule can do
- Stop processing more rules
- Holds that release themselves
- Rules on the moments on the warehouse floor
- When a rule could not apply
- Rules on a schedule
- Run on all open orders
- Condition groups
- Run a rule by hand
- Test rules on an order
- When a rule waits
- A rule’s own effects
- Test a rule
- The run log
- Describe a rule
- See also
Start from an example
Section titled “Start from an example”With no rule yet, the page shows examples under the empty list; once you have rules, Start from an example opens the same list. An example opens in the editor filled in, for example “Hold high-risk orders” or “Late orders first”. Change what you need, then Create: nothing is saved before that. Amounts are in your store’s currency.
To start from a rule you already have, open its ⋯ menu and choose Duplicate. The editor opens with a copy named “Copy of …”; the copy is saved switched off, so it never runs beside the original until you change it and turn it on.
When a rule starts
Section titled “When a rule starts”| Trigger | Starts when | How often |
|---|---|---|
| Order created | A new order arrives | Once per order |
| Order paid | An order arrives paid, or turns paid | Once per order |
| Order routed | Shopify assigned the order to a location | Once per order |
| Risk changed | Shopify changed the order’s fraud risk | Once per order |
| Tags added | Tags were added to an order in Shopify | Once per set of added tags |
| Address changed | The order’s delivery address changed | Once per change |
| Return requested | A customer asked for a return, in your returns page or in Shopify | Once per return |
| Return received | The goods of a return arrived and were checked at your warehouse | Once per receipt |
| Delivery problem | The carrier reported a problem with a parcel | Once per problem |
| Order late | An order passed its fulfil-by time, or the end of its packing day, and has not shipped | Once per due time it misses |
| Order put on hold | A hold was placed on the order in Shopify | Once per hold, so once for each part of a split order that is held |
| Order hold released | A hold Floormode placed on the order was released | Once per hold |
| Order backordered | Part of the order started waiting for stock (your warehouse sells on backorder) | Once each time a part starts waiting, never while it waits |
| Backorder resolved | A backordered part of the order is fully reserved again | Once each time a part stops waiting |
| Pick short | A picker found fewer units in a location than the pick asked for | Once per pick line |
| Order cancelled | The order was cancelled in Shopify or in Floormode | Once per order |
| Parcel packed | A packer finished a parcel of the order | Once per parcel |
| Parcel fulfilled | Shopify confirmed the fulfillment of a parcel | Once per parcel |
| Label bought | Floormode bought a shipping label for the order | Once per label |
| Delivered | The carrier delivered a parcel | Once per shipment |
| On a schedule | At the times you choose, on every open order | Once per run, or once per order (you choose) |
| Only when run by hand | Never on its own: only when someone runs it on chosen orders | Once per run |
A rule runs at most once for each moment. Some details:
- Tags added counts the set of tags one change added. If a tag is removed and added again, that is the same set, so the rule does not run a second time. Two rules that add and remove each other’s tags stop after one round.
- Return requested: a return asked for in your returns page and then answered in Shopify is one return. The rule runs once.
- Return received: goods that came back without an order start no rule, because there is no order to act on.
- Delivery problem: a parcel that was moving again and then runs into a new problem is a new problem, so the rule runs again.
- A new order’s own tags are not “added”: use Order created with a tag condition.
- Order cancelled knows how far the order’s work had come: not started, picking, picked, packing or packed. A cancel you start in Floormode records it when it stops the work, so the rule sees “picking” even after the work was stopped.
- After packing (Parcel packed, Parcel fulfilled, Label bought, Delivered, Order cancelled) a rule can add or remove tags, send an alert or tell your webhooks and Flow. Holding, routing or packing instructions mean nothing there. Order put on hold can also set the priority, but never hold again.
- Order backordered starts once when a part of the order begins to wait for stock. While it waits, more or less stock missing starts nothing; once it is reserved again (Backorder resolved) and runs short again later, it starts again. When Shopify splits the order or moves part of it, the new part begins its own wait. Use Units short to act only on bigger shortfalls. Neither moment can hold the order: it already waits, and it reserves itself when the stock arrives. Backorder resolved can release the holds a rule placed while it waited.
- Pick short knows the units the picker could not find (Units short). A line booked short again starts nothing. It can add or remove tags, send an alert or tell your webhooks and Flow.
- Warehouse on these moments is the order’s warehouse, as on Order put on hold: on an order split across two warehouses, a Pick short in one also matches a rule that names the other.
- Order hold released knows the hold’s reason. It can do everything an open order takes except hold or release again.
- Order late counts from the first rule, webhook or Shopify Flow workflow that listens for it: an order that was already late then starts nothing. An order split over several shipments is late at its earliest due time; a due time moved later is a new due time, so the rule can run again. An order that asked for a delivery day is due by the end of its packing day in the warehouse’s time zone. The rule runs within 15 minutes after the due time passes.
What a rule can check
Section titled “What a rule can check”Each trigger offers the conditions it can answer. The editor shows only those. If you change a rule’s trigger, every condition stays: the ones the new trigger cannot answer are marked “Not available for …”, and the rule cannot be saved until you remove them or pick another trigger. The same check runs for rules saved through the API.
| Condition | Offered by |
|---|---|
| Channel, tag, SKU, order total, destination country, shipping option, risk level, weight, line count, dangerous goods | Every trigger |
| Store (only when you have more than one store) | Every trigger |
| Order source (Shopify’s source: online store, point of sale, draft order, an app) | Every trigger |
| Priority | Every trigger |
| Warehouse | Order routed, Risk changed, Tags added, Address changed, Order late, Order put on hold, Only when run by hand (a change before routing waits and is decided once the order is routed, with what it changed; not on returns or delivery problems: the order has shipped) |
| Tags added | Tags added |
| Return reason, units returned | Return requested, Return received |
| Return value | Return requested |
| Condition on receipt (sellable, damaged) | Return received |
| Carrier, problem (failed attempt, returned to sender, other) | Delivery problem |
| Due by (fulfil-by time, packing day), minutes late | Order late |
| Units, product vendor, product type, state or province, postcode, day placed, time placed, order is held for | Every trigger |
| Backordered | Order routed and every trigger after it |
| Hold reason | Order put on hold |
| Packed at (the parcel’s warehouse) | Parcel packed, Parcel fulfilled |
| Carrier | Delivery problem, Label bought, Delivered |
| Work stage | Order cancelled |
Each condition offers the comparisons its value takes: is any of, is none of, contains, starts with, is empty, is not empty, at least, at most, and for the order’s lines all lines are. A rule saved before these existed keeps its comparisons.
Some details:
- Money (order total, return value) is compared in each order’s own store currency. The editor shows the currency code beside the amount. With stores in more than one currency it shows every code until the rule names one store; add a Store condition for an amount meant for one store’s currency.
- Warehouse on an order split between warehouses: “is” matches when any of its warehouses is the one you chose, “is not” when none of them is. An order with nothing left to ship has no warehouse to check: a rule that asks is skipped, and the order’s timeline says why.
- Priority is read when each rule is checked, so a later rule in the list sees the priority an earlier rule just set.
- Tags do not chain within one moment: a tag a rule adds reaches the order through Shopify, as Tags added. Use that trigger to act on a tag a rule added.
- Return value is known only for returns asked for in your returns page. A rule that checks it skips a return from Shopify, and the order’s timeline says why. The same goes for any fact a moment does not state.
- Product vendor and product type are read from your catalog. A line whose product has not synced yet cannot tell: “is none of” and “all lines are” wait until it syncs, while “is any of” already matches when another line has the value. A custom item has no vendor, which counts as empty.
- State or province is the code Shopify stores, such as
US-AK,AU-TASorDE-BY. - Postcode (“starts with any of”, “starts with none of”) names one country and its postcode prefixes, for example
GB: HS, IV, KW, ZEfor the Highlands and Islands orUS: 995, 996for Alaska. Spaces and hyphens do not matter. “Is none of” also matches orders to other countries: add a Destination country condition to limit it. The postcode itself never shows in a run log or a test, only whether it matched. - When Shopify does not share an order’s address with Floormode, a state or postcode rule is skipped for that order and its timeline says why: it never guesses.
- Day placed and time placed use your store’s time zone (UTC until Shopify has told Floormode the zone).
What a rule can do
Section titled “What a rule can do”The action list is grouped: what happens to the order, what the packer is asked, and who is told. A trigger offers only the actions that fit it.
| Action | What it does | Triggers |
|---|---|---|
| Add tag, Remove tag | Adds or removes the tags on the order in Shopify | Every trigger |
| Hold fulfillment, Set priority, Route to warehouse | As their names say. A hold can release automatically (below) | Every trigger |
| Release holds | Releases the order’s holds that a rule placed, of one reason or any. With Also release holds not placed by a rule, people’s and risk checks’ holds too | Order triggers, and runs by hand |
| Pack in box | The bench starts the parcel in this box; the packer can still choose another | Order triggers |
| Add pack note | A note the packer reads at the bench, up to 500 characters. With Packer confirms on, the packer taps Got it before the parcel goes on | Order triggers |
| Require pack step | Makes the photo, the weight or the check required for this order’s parcels | Order triggers |
| Add to the parcel | A flyer, card or sample (a Floormode item) goes in the order’s parcels, confirmed by the packer, taken from stock at the fulfil. See Add to the parcel | Order triggers |
| Send alert | Sends you an alert | Every trigger |
| Tell webhooks and Flow | Sends “Rule matched” to your webhooks and, while Also start Shopify Flow is ticked, to Shopify Flow, with the rule, the trigger and the order. Unticked, it tells your webhooks only. It never starts another rule | Every trigger |
The packing actions fit the order triggers only (created, paid, routed, risk, tags added, address changed, late): after a return or a delivery problem there is no parcel left to pack. If you change a rule’s trigger, an action that no longer fits stays in the list, marked, and the rule saves once you remove it.
At the bench. A rule’s note shows in the parcel’s instructions with the rule’s name (“Order note · from the rule Gift wrap”). When it asks to be confirmed, Got it is saved for that parcel. A device that is offline keeps the tap and sends it when it is back online. Each parcel of a split order confirms the note on its own. At the desk station the note has a Confirm button.
A required step names its rule too (“The rule Express check asks for a photo on this order”). A photo can be required anywhere, and a lead can still let a parcel go without it. The weight and the check can only be required where the warehouse already weighs or checks parcels. Elsewhere the rule skips the step, the editor names those warehouses, and the run log says why.
Once packing starts, the order’s packing instructions are fixed. After the first parcel of an order is started, a rule can no longer change its box, note or steps. The run log says the rule was skipped because packing had started. An order no rule marked looks the same at the bench as before.
Stop processing more rules
Section titled “Stop processing more rules”Tick Stop processing more rules for this order under a rule’s trigger. When that rule acts on an order, the rules after it in the list do not run for that order on the same trigger. A rule that runs later in the list, for another trigger, is not affected.
- Only a rule that changed something stops the others. A rule that matched but changed nothing (“No change”) stops nothing.
- When the stopping rule waits for a fact (for example the order’s fulfillment orders for its hold), the rules after it wait behind it. Their run log says “Waiting behind Express first”. When the fact arrives, the stopping rule runs first, and the others follow what it did.
- Its run log shows Stopped later rules, and Test rules shows “Stopped by Express first” on a rule it stopped.
- A rule you switch off, delete or untick no longer stops the others, from its next moment.
- A rule run by hand runs alone, so there is nothing after it to stop.
Holds that release themselves
Section titled “Holds that release themselves”A hold can end by itself. In a rule’s Hold fulfillment action, and in the Hold fulfillment dialog on the order and the orders list, choose Release automatically:
- Release after a number of minutes, hours or days (up to 90 days), counted from when the hold is placed;
- Release on a date and time in your main store’s time zone (UTC until Shopify has told Floormode the zone), the same for every store’s orders.
The hold shows “Releases 14:00 Tue” on the order. Its Change release sets another time, or Keep holding until someone releases it. Release ends it now.
- If the order is already on hold, it keeps that hold as it is: a rule’s timer is never added to a hold that waits for a person, and its run log says “Already on hold”.
- A rule that holds again later may move its own release later, never earlier. You can move a rule’s release later too, or release it now.
- A release time that has already passed when the rule runs places no hold.
- Tells the customer about the delay: a hold for “Waiting for stock”, “Waiting for production” or “Waiting for supplier stock” sends the customer the delay notice, whether a person or a rule placed it. The templates use reasons that send none.
When Shopify still lists a released hold
Section titled “When Shopify still lists a released hold”Sometimes Shopify puts a hold back on an order after Floormode released it. This happens when a request to place the hold was slow to answer and Shopify finished it late. When Floormode next reads the order and sees its own hold listed again, it checks with Shopify and releases it again. The hold on the order says Checking with Shopify meanwhile. This works the same whether the hold was released by its timer, by a person or by a rule.
- Floormode only releases holds it placed itself, never another app’s.
- After three such releases, Floormode only checks: if Shopify has put the hold back
again, or refuses to release it, the hold says Needs a person. Use Open in
Shopify to release it there, or Try again. If you can’t use Shopify admin, ask
someone who can. The
holds_listAPI lists these holds withdrift: "stopped".
Rules on the moments on the warehouse floor
Section titled “Rules on the moments on the warehouse floor”Pick short, Order backordered, Backorder resolved, Parcel packed, Label bought, Parcel fulfilled, Delivered and Order cancelled each take at most 20 switched-on rules. Their rules run in the same moment as a scan on the floor (a short pick, a putaway that brings stock for a backorder, the bench), so the cap keeps picking and packing fast. When Backorder resolved rules are on, a putaway reserves stock for fewer waiting orders at once and Floormode reserves the rest a moment later, so the scan stays fast. A 21st rule can be saved switched off; the editor says “This moment already has 20 rules switched on” before you save, and switching it on waits until you switch another off. Deleted and switched-off rules do not count. A rule on these moments names each action once: put its tags in one action.
Up to 5 of a moment’s rules can Tell webhooks and Flow or Send alert (an alert reaches your webhooks too). Events reach your webhooks a few seconds after the moment, in order for each order, and a failed delivery is retried for up to three days (Settings › Webhooks). The 5 keep a webhook that was down for three days caught up within a day; the moment’s other rules tag without telling anyone. At most 3 of them can also start Shopify Flow: each Flow start uses the store’s Shopify budget, the one fulfilments use too. When a moment already starts Flow from 3 rules, a new event comes with Also start Shopify Flow unticked and tells your webhooks only; ticking it again says why it waits. The editor says either bound before you save. A moment’s Flow starts go out together, so two of one order may reach Flow in either order, as Shopify’s own Flow starts may.
When a rule could not apply
Section titled “When a rule could not apply”When a rule cannot do one of its actions for a reason you can fix (the box it names was
deleted, an action has nothing set, it asks for a pack step the warehouse does not use), you
get one alert, Rule “…” could not apply on order …, in Alerts, through Alertified
and on a webhook that listens to alert.raised. It stays one alert while the reason stands;
it closes by itself once the rule applies again on an order of the same store (and, for a
pack step, the same warehouse), or when you change the rule’s actions, switch it off or delete
it. A reason that comes back opens a new alert. Things that are fine
(the tag was already there, nothing to release) never alert.
Rules on a schedule
Section titled “Rules on a schedule”Pick the trigger On a schedule and the rule runs at the times you choose, on every open order: for example “every weekday at 09:00, alert me to orders placed more than 48 hours ago and not started”. A new scheduled rule starts as Every weekday at 09:00; the line under the schedule says it in words and when the next run is.
- Runs: once a day at a time (on the quarter hour), or every 1, 2, 3, 4, 6, 8 or 12 hours, optionally between two times. Pick the days it runs on.
- More options: the time zone (the store’s by default, or one of your warehouses’), Act on an order once (the default: an order the rule acted on is left alone at later runs) or Act on every run (up to 100 times an order across scheduled rules), and what happens when a run was missed: Run it late (the default) or Skip it when it is more than 15 minutes late.
- A scheduled rule can check what a run knows of each order: Hours since placed and Work stage (not started, picking, picked, packing, packed), besides the order’s own facts.
- At most 10 scheduled rules can be switched on at once.
- A rule switched on, or whose schedule changes, counts from then on: it never runs the times it was off.
- When a run is still busy at the next time, the next time is folded into one run and the run’s card says so.
- Run now in a scheduled rule’s ⋯ menu runs it at once, as at its next time.
Run on all open orders
Section titled “Run on all open orders”A rule’s ⋯ menu offers Run on all open orders…: the rule is checked on each order that is open when the run reaches it, about as many as the dialog says. An order that changes during the run may be checked again, but the rule never acts twice on it in one run. The run’s progress is in the rule’s Runs: “Checked 1,200 of about 8,000 open orders”.
- A run waits while a scheduled run goes first (“Paused behind the scheduled run”), and while Shopify is still taking earlier changes (“Waiting for Shopify to catch up”).
- Stop run stops it. Orders already handled keep what the rule did; orders waiting for a missing fact are still decided when that fact arrives, and the card says how many.
- A rule that checks something only its moment knows (for example the tags just added) cannot run this way.
- One run a rule at a time; at most 10 such runs at once.
Condition groups
Section titled “Condition groups”Add group beside the conditions’ heading puts the conditions you have into group 1 and opens group 2. Each group matches All or Any of its conditions, and Match groups says whether all groups or any group must match: “(Germany and express) or (Austria and over €200)” is two groups of All, matched by Any. Up to 5 groups and 20 conditions. Removing a group down to one makes the rule flat again. A group that cannot tell yet (for example the order’s shipping option is not known) waits; a group already decided never makes the rule wait.
Run a rule by hand
Section titled “Run a rule by hand”Select up to 50 orders on the Orders list and choose Run rule…, or open an order’s ⋯ menu and choose Run a rule…. Pick the rule and confirm: Floormode runs it now on those orders and shows what each one did. A rule’s Test also offers Run on these orders for the examples it would match.
- Any switched-on rule can run by hand, unless its conditions check something only its moment knows (for example the tags just added). The picker says why such a rule is greyed.
- A run by hand never uses up the rule’s own trigger: running “Express first” by hand today does not stop it from running when the next order is paid.
- A rule with the trigger Only when run by hand runs only this way.
- Running a rule needs the rights of what it does: for example a rule that tells your webhooks needs the right to manage integrations.
- If you run the same selection twice by accident, the second run repeats the first answer and changes nothing.
- One order can be run by hand at most 100 times; after that each rule stops for it.
Test rules on an order
Section titled “Test rules on an order”On an order’s ⋯ menu, Test rules… shows every switched-on rule against that order now: whether it would match, each condition with a ✓, ✗ or ?, and the order’s own value for it (never the postcode), whether the rule is waiting on the order, how often it ran on it, and what it would do, including an action that would not apply and why. A condition on something only its moment knows is “decided when the trigger happens”. Nothing changes.
When a rule waits
Section titled “When a rule waits”Some actions need facts Shopify sends a little later, such as the order’s fulfillment orders for a hold. Until they arrive, the rule waits and the order’s timeline says so. When the facts arrive, the rule runs for each moment it waited for, as the rule is then. An order keeps at most 20 such moments waiting; a later one is noted on its timeline and skipped.
A rule’s own effects
Section titled “A rule’s own effects”A rule’s change never starts another rule in the same moment. It can start one later:
- a tag a rule added comes back from Shopify as Tags added;
- a hold a rule placed counts as the order being held once Shopify confirms it.
When several rules add tags to an order for the same event, Floormode sends them to Shopify together, once.
One order runs rules at most 100 times on each trigger that can repeat by itself (tags added, address changed, delivery problems, holds, late orders and runs by hand). Every run counts: one that changed something, one that found nothing to change, and one skipped for a fact no later update will give. A rule that is only waiting does not count. After 100, each rule stops for that order on that trigger, its run log says so, and you get one alert. The moments that come with a new parcel, label or return (packed, fulfilled, label bought, delivered, returns) are never stopped: an order with 30 parcels runs its rules for each.
Test a rule
Section titled “Test a rule”Open a rule’s ⋯ menu and choose Test. Pick one of your newest examples of the rule’s trigger: an order, a return, a return receipt, or a shipment with an open delivery problem. The test shows whether the rule would match, the facts the trigger gave it, and what it would do. It changes nothing.
- Tags added is tested with an order’s current tags, as if they had just been added. Floormode does not keep a list of recent tag changes, so this is an approximation.
- Cannot tell means the example is missing a fact the rule checks, such as a shipping option Shopify has not sent yet. The live rule skips such an order instead of guessing.
The run log
Section titled “The run log”Open a rule’s ⋯ menu and choose Runs to see every time it ran or was skipped, newest first. A run names its order, when it ran and what came of it:
- Applied: what it changed;
- No change: it matched, but nothing changed, and why (a target that no longer exists, packing that had started);
- Skipped: a fact it checks was not known yet, and when it is decided again (it says whether it is still waiting or was decided since), or a fact no later update will give (“Not decided”);
- Stopped: the order reached the limit of 100 runs, or too many of its moments were waiting at once.
It also names the moment it ran for:
- Tags added: the set of tags it ran for. A very long set is shown as the trigger alone.
- Delivery problem: when the problem began.
- Order late: the due time it missed, and whether it was a fulfil-by time or a packing day.
- Only when run by hand and a run by hand of any rule show as runs by hand.
- The other triggers run once per order, parcel, label, hold, return or receipt, so the run’s order is enough.
A rule runs once for each moment, so each applied run in the log is a different moment. The order’s timeline shows the same outcomes. A rule that has not run yet offers Test this rule instead.
Describe a rule
Section titled “Describe a rule”Describe in the rule editor drafts the conditions from your sentence, for example “orders with more than 5 units”, “orders placed before 2 pm”, “orders to California”, “UK orders to postcodes starting IV or KW”, or “cancelled orders that were already packed”. It knows every condition except the store, the warehouse, the checkout source, the priority, the carrier and the packing warehouse, which you pick in the editor. A vendor or a product type is read only when your sentence says “vendor”, “brand” or “type”. A region is read for the US, Canada and Australia; another country’s region is named as something a rule cannot test. Describe sends only your sentence and the trigger, never an order or a customer’s details.