Order Management Rule (OMR) triggers define the exact chronological moment in the processing lifecycle when your custom automation logic executes. Understanding this sequence ensures you apply your business rules at the optimal stage to effectively manipulate orders within techSHIP.

This article explains the chronological OMR lifecycle execution points, details the exact sequence of available triggers, and outlines the corresponding error handling logic.

Prefer listening? This podcast-style audio walks you through the article's key points.

	AI-Assisted & Human-Reviewed: For general information only. Please double-check important details.

	For a broader overview of the OMR engine and general rule configuration instructions, refer to What's New in Order Management Rules (OMR) for Rule Sets in techSHIP [Guide]. To learn more about the available order statuses, see: Understanding Order Statuses [Information].

TABLE OF CONTENTS

• Trigger Execution Sequence
• Error Handling Business Logic

Trigger Execution Sequence

The platform evaluates rules sequentially based on the order's progression:

The table below outlines the Trigger points available during the OMR lifecycle:

	For the Before Shipment Booking trigger, if a Carrier is explicitly selected on the order prior to processing, the rule will still execute, but it naturally skips the rate shop evaluation phase.

Error Handling Business Logic

When an exception is thrown during rule execution, the system responds dynamically based on the specific Trigger stage where the failure occurred.

Exceptions raised at the After Rate Shopping stage immediately stop the processing workflow and mark the order status as Failed.

Conversely, exceptions triggered at the After Shipment Booking stage follow the standard post-booking failure path, initiating the normal void and cleanup procedures for the affected Shipment to ensure data integrity.