Workflows

July 20, 2026

Summary

Workflows are event-based rule sets that pair conditions with actions to automate order, inventory, and listing behavior in Flxpoint, with per-event fields and actions and a built-in tester.

OVERVIEW

Workflows are sets of rules that fire on Flxpoint events — an order importing, a fulfillment request generating, pricing and quantity updating, and so on. Each rule pairs conditions (the criteria) with actions (what happens when they are met).

Conditions — criteria that must be met for an action to run. Optional — use Always Run to apply to every entry.
Actions — what happens on a match: modify statuses, transform data, or send custom alerts.
And / or logic — combine multiple fields and conditions with and/or operators for dynamic comparisons.
Testing — preview how a set of rules affects sample data before relying on them.

HOW A WORKFLOW RULE READS

Part	Example
Event	Order Importing
Use case	Mark international orders on hold and send an alert
Conditions	If Shipping Address, Country Code is not "US"
Actions	Set Order Status to "Hold" and send Custom Alert "International Order Alert"

The fields available to a workflow depend on its event. An order import workflow exposes order fields; the order routing workflow’s only action is to choose a Routing Group.

IMPORTANT NOTES

Note: Conditions are optional. If an action should apply to every entry in the workflow, set the condition to Always Run instead of building an if/then.

Note: Available actions depend on the event. The order routing workflow can only choose a Routing Group, while the order import workflow can manipulate order data including the order status. Do not expect the same actions across every event.

Note: New rules are enabled by default. A newly created rule is active once you save (Update) the workflow. To bypass a rule without deleting it, disable it — it is then skipped in both the workflow and the workflow tester.

Note: Test before you rely on it. Use the workflow tester to preview how rules interact. The tester only needs the fields a given rule uses.

COMMON ISSUES

A rule set to "Always Run" reports "Conditions failed to pass so no actions were taken"

First confirm the rule is enabled and that you saved the workflow (Update / Save and Complete) so the change is on the Live workflow, not just a Draft. If the UI shows rules but the workflow the import actually runs has none (they can diverge between Draft and Live), the rules are not on the live workflow — re-save, and if the UI and the running workflow still disagree, raise it with support.

A rule change only affects new or changed items, not the existing catalog

Scheduled inventory jobs process changed items only, so an edited rule does not retroactively re-map variants that did not change. Use the Inventory Created/Updated Workflow Manual Re-Sync (or a full re-pull) to force existing variants through the rule again.

FAQS

Are conditions required?

No. Set a rule to Always Run to apply its action to every entry the workflow processes.

Why is my Always Run rule not firing?

Check that the rule is enabled and that the workflow was saved to Live rather than left as a Draft. Draft and Live workflows can differ, and the import runs the Live one.

What actions can a workflow take?

It depends on the event — broadly, modifying statuses, transforming data, and sending custom alerts. Some events (like order routing) expose only a single action.

How do I bypass a rule without deleting it?

Disable it in the workflow. Disabled rules are skipped in both the workflow and the tester.

Back to Mapping & Workflows