Order Manager

The Order Manager app lets your workflows create, update, find, and validate orders. These are the nodes that turn AI-extracted data into real orders in Glacis.

Order Created (Trigger)

Starts the workflow when a new order is created in Glacis — whether manually, from email, or via another workflow.

When to use it: Sending a confirmation email to the supplier, assigning an SOP, notifying the procurement team.

Output: The full order object — order number, items, seller, buyer, dates, and all fields.

Order Updated (Trigger)

Starts the workflow when an existing order is modified.

When to use it: Detecting changes to quantities or dates, triggering a variance check, updating related shipments.

Order Scheduler Check (Trigger)

Starts the workflow on a schedule to check orders that meet certain conditions — for example, orders nearing their delivery date.

When to use it: Periodic checks for overdue orders, upcoming deadlines, or orders stuck in a particular status.

Create Order (Action)

Creates a new order in Glacis using data from previous steps.

When to use it: Turning AI-extracted data from emails or documents into a structured order.

Configuration: Map data from previous steps to order fields using template variables — order type, order number, supplier, line items, dates, and terms.

Update Order (Action)

Modifies an existing order.

When to use it: Updating orders based on incoming information — price changes, quantity adjustments, delivery date changes.

Key feature — Create-or-Update mode: If the order doesn't exist yet, create it. If it does, update it. Useful when you're not sure whether an incoming PO is new or a revision.

Find Order (Action)

Searches for orders matching specific criteria.

When to use it: Looking up an order by number before updating it, checking if a duplicate exists, finding related orders for a shipment.

Create Order Change Request (Action)

Creates a formal change request on an existing order — for review and approval before the change is applied.

When to use it: When changes need human approval before taking effect — for example, a supplier proposing a price change or delivery date shift.

Sales Order Validator (Action)

Validates sales order data against business rules before processing.

When to use it: Checking that a sales order has valid quantities, correct pricing, and all required fields before it's confirmed.

Do Action (Action)

Executes a generic order-related action.

When to use it: Performing order operations that don't fit the other specific action types.

Need help?

If you have questions or run into issues, we're here to help:

• Chat with us — use the support widget in the bottom-right corner of Glacis

• Email — reach us at support@glacis.com

• Related docs — Creating Workflows | Order Fields and Statuses