The Order Management Rules (OMR) engine for Rule Sets has been fully rebuilt in techSHIP 2025, enabling you to visually build more complex logic with improved flexibility and clarity.

 

NOTE: This article focuses exclusively on Rule Set OMRs. Client-level and Client Template-level OMRs remain unchanged. OMRv1 and OMRv2 refer to the previous and new versions, respectively.

 

This guide highlights the key UI changes introduced in OMRv2.

 

NOTE: To learn about the OMRv1 logic, refer to How to Set Up Portal Global OMR Rules [Step-by-Step Guide]. While the article is based on the previous OMR engine, it remains a valid reference until the updated version is published.

 

This article is divided into the following sections

  1. OMR v1 vs. v2: Conversion Process
  2. Trigger
  3. Clients
  4. Visual Rule Builder
    1. Conditions
    2. Actions
    3. Decision Tree
  5. Import and Export


 

NOTE: For a full overview of all new features, see: What's New in techSHIP 2025: A Guide to the Latest Features [Information].

 

I. OMR V1 VS. V2: CONVERSION PROCESS


While techSHIP 2025 is in beta, each portal can be accessed through either the previous or the new interface. Thus, both OMRv1 and OMRv2 rules are visible in both interfaces, but each rule can only be managed in a single version:

  • OMRv1 rules can only be edited in Legacy, and appear in techSHIP 2025 with a conversion icon.
  • OMRv2 rules can only be edited in techSHIP 2025, and appear in Legacy with a link to techSHIP 2025.


   
techSHIP LEGACY
techSHIP 2025
OMRv1
OMRv2

 

WARNING: Converting an OMRv1 to OMRv2 cannot be undone. 

 


II. TRIGGER


In OMRv1, each rule could be triggered by a different event. In OMRv2, the entire rule set is triggered by a single event, defined in the rule set's main properties.




III. CLIENTS


In OMRv2, assigned Clients are visually managed through the Clients tab, allowing for easier overview and modification.

 

NOTE: If no Clients are assigned, the rule applies to all Clients within the Portal.

 


IV. VISUAL RULE BUILDER


From the Actions tab, you can visually build the rule logic using the Add Action button to insert Conditions or Actions and assemble them into a Decision Tree.

 

NOTE: The Decision Tree is built step by step, following the logic flow you define. For best results, we recommend outlining your rule structure in advance.

 


OMRv2 introduces a modular, atomic structure for Actions and Conditions. Each element operates independently and defines its own properties. The following subsections explain this in more detail.


i. Conditions


Conditions in OMRv2 are structured as logic trees, where operands are grouped under logic operators (e.g., AND, OR). This allows you to build complex evaluation paths visually.



Each operand also defines its own properties, enabling mixed logic conditions. For example, you could create a condition that checks whether:

  • the total order quantity is 10, and

  • any line contains a SKU that includes AA.



ii. Actions


OMRv2 follows the same atomic logic for Actions. Each action defines its own properties and scope, enabling actions at both the line and order level.



iii. Decision Tree


As you build nested Conditions and Actions, a Decision Tree is formed. This visual representation helps you understand the rule's logic flow, cover edge cases, and quickly identify where actions should be placed.


Conditions appear as dark cyan trapezoids, with the left branch representing the True path and the right branch representing the False path.


Actions are color-coded based on their position in the tree:

  • Green for those on the left (True) branch.
  • Red for those on the right (False) branch.
  • Blank for those not linked to a Condition.



Click any + icon to add an Action or Condition at that location.



V. IMPORT AND EXPORT


You can Import and Export OMRv2 rules from the Actions tab using the corresponding buttons.



Exported OMRv2 files use the YAML format, allowing you to edit them externally and re-import into any OMRv2 rule set.

 

WARNING: Take into account that:
  • Importing a file completely overwrites the current OMR Actions and Conditions.
  • The import process does not validate rules for conflicts. Overlaps or contradictions may cause unexpected behavior.

 

Exported OMRv1 files have limited compatibility. You can import them into OMRv2 using the Convert From OMR V1 Format option. During this process, only rules whose trigger matches the current rule set will be imported.

 

WARNING: If an OMRv1 file is listed and available for conversion, as described in the previous sections, use the conversion process instead of direct import.