How Copilot Automations Work
Co-Pilot is Packiyo's rules engine — it lets you set up automated rules that react to things happening in your account (mostly around orders, plus purchase orders) so you're not manually touching every order yourself.
Every automation is built from three pieces, checked in this order:
- Event — the trigger ("when this happens...")
- Conditions — optional filters ("...but only if this is true...")
- Actions — what to actually do ("...then do this")
If an automation has no conditions, its actions run every time the event fires. If it does have conditions, those get combined with AND/OR logic before Packiyo decides whether to run it.
1. Events (the "when")
These are the triggers a rule can react to:
| Event | Packiyo meaning |
|---|---|
| Order is created | A new order comes into Packiyo |
| Order has any change / Order updated | Something on an existing order changed |
| Order deallocated | Inventory previously reserved for an order got un-reserved |
| Order marked pending | Order moved to a "pending" state |
| Order marked ready to ship | Order became ready to ship |
| Order shipped | An order shipped out |
| Order tags updated | Tags were added/removed from an order |
| Order warehouse updated | The assigned warehouse changed |
| Order turns X [time unit] old ("aged") | A timed check — e.g. "order has been pending 2 days" |
| Purchase Order created / updated / received / closed | Same idea, but for purchase orders (POs) |
| Return received / closed | A return came in or was closed out |
💡 A few other events exist behind the scenes — these are internal/system triggers, not ones you'd typically set up yourself. Looking for more advanced events to trigger? Reach out to support@packiyo.com
2. Conditions (the "only if")
These are the filters you can layer onto a rule:
- Order details — order number, text field match/pattern, numeric field comparison, weight, subtotal/total amount
- Line items — quantity of a specific SKU, number of distinct SKUs, line-item count, line-item property matches
- Tags/flags — order tags, order-item tags, a custom flag being set
- Order type/source — manual vs. system-created, wholesale vs. not, which sales/order channel it came from, raw channel payload data matching
- Allocation status — allocated / not allocated
- Shipping/destination — ship-to country, state, postal code, customer name, shipping option/method chosen
- Customer type — whether the triggering user is a certain type (e.g., staff vs. customer)
Each condition works like: compare this field to this value using this operator — equals, contains, starts with, greater/less than, is one of, and so on.
3. Actions (the "then do this")
These are the things a rule can actually do to the order:
- Line items — add a specific line item, add one per SKU, add one per tag
- Notes — add a gift note, add a packing note
- Tags — add tags to the order
- Status changes — cancel order, archive order, mark as fulfilled
- Holds — set/remove address hold, allocation hold, fraud hold, operator hold, payment hold
- Priority — set or remove priority
- Shipping setup — set shipping box (directly or "by history"), set shipping method, set shipping profile, set sender address, set delivery confirmation, set signature requirement
- Warehouse routing — set warehouse directly, by nearest zip, by nearest zone, or by first available
- Billing/customs — charge an ad-hoc rate or shipping-box rate, set third-party billing, set incoterms, mark contains-alcohol
- Packing slip/labels — set packing dimensions, packing slip template, show/hide product barcodes on slip
- Misc field — set a date field, set a text field, allow partial shipments
- Flow control — "run first matching of group" lets you group several possible actions and only run the first one whose conditions match, like an if/elseif chain
Putting It Together
An automation always follows the same logic: an Event fires, Packiyo checks any Conditions you've set, and if they pass, it runs the Actions you've defined. No conditions means the actions run every time the event happens.