How to Create Automations

The Automations page lets you create rules that automatically move orders from one tab/status to another.
This is useful for streamlining workflow, reducing manual admin, and ensuring orders progress at the correct time.

If no rules are set, you will see:
“No rules found…”

Below is a detailed breakdown of every field and how to use this feature.

  1. What Automations Do

Automations allow you to automatically:

  • Move orders between warehouse/booking tabs
  • Trigger workflow changes based on time
  • Ensure orders progress through stages without manual clicking

Examples of what you can automate:

  • Move orders from “New Order”“Sent to Warehouse” 24 hours before the booking start
  • Move orders from “Quoted”“Invoiced” automatically after a set time
  • Move orders from “Invoiced”“Completed” after a booking ends
  • Remind the warehouse by moving incoming orders to a preparation stage before the handover
  1. Channel

The Channel dropdown defines where this automation applies.

Example channel:

Warehouse

This means the automation will move orders between warehouse/booking tabs (the same ones you set in “Warehouse Tabs”).

Your platform may support other channels in future (e.g., notifications, emails), but here it refers specifically to order movement.

  1. Event

The Event defines when the automation should activate.

Common event options include:

  • Before Order Start
  • After Order Start
  • Before Order End
  • After Order End
  • On Creation
  • On Payment

(Your screenshot shows Before Order Start.)

Example:

If you select Before Order Start, the automation will trigger before the booking begins, based on the duration you define.

  1. Move From

This is the current status/tab where the order must be for the rule to activate.

Example:

  • New Order
  • Invoiced
  • Quoted
  • Sent to Warehouse
  • Completed
  • Bin

Only orders in the “Move From” tab will be affected.

  1. Move To

This defines where the order will be moved once the automation triggers.

Example:

  • Invoiced
  • Sent to Warehouse
  • Completed
  • New Order
  • Any custom tab you created
  1. Duration

This determines when the automation will run relative to the event.

The fields are:

  • Days
  • Hours
  • Minutes

Examples:

Example 1 — Move 2 hours before booking starts

  • Duration:
    • Days: 0
    • Hours: 2
    • Minutes: 0
  • Event: Before Order Start

Example 2 — Move 1 day after order ends

  • Event: After Order End
  • Duration:
    • Days: 1
    • Hours: 0
    • Minutes: 0

Example 3 — Move immediately when created

  • Event: On Creation
  • Duration: all fields 0
  1. Add Rule

Once all fields are completed:

Click Add

This creates the automation and adds it to your active rules list.

You will now see it displayed in the upper section of the page.

Rules can include:

  • Rule name (auto-generated or displayed as details)
  • Channel
  • Event
  • Movement (From → To)
  • Trigger timing

You can create unlimited automation rules.

  1. How Automations Work in Real Life

Here are practical examples of common usage.

Automatically prepare orders 1 day before they start

  • Channel: Warehouse
  • Event: Before Order Start
  • Move From: New Order
  • Move To: Sent to Warehouse
  • Duration: 1 Day

Move a booking to “Completed” 1 hour after it ends

  • Channel: Warehouse
  • Event: After Order End
  • Move From: Sent to Warehouse
  • Move To: Completed
  • Duration: 1 Hour

Move unpaid invoices to “Quoted” after 48 hours

  • Event: After Order Start or On Creation
  • Move From: Invoiced
  • Move To: Quoted
  • Duration: 2 Days

Send an order back to ‘New Order’ immediately if incorrectly placed

  • Event: On Creation
  • Move From: Any Tab
  • Move To: New Order
  • Duration: 0
  1. Deleting / Editing Rules

Once rules appear, you can:

  • Edit them
  • Delete them
  • Temporarily disable them (depending on your platform’s options)

This keeps automation tidy and prevents conflicting rules.

  1. Save Changes

Automations generally save instantly when added.
No extra save button is required unless your platform version shows one.