Skip to main content
Where to find it: Settings → Integrations. On the integration’s card, click Settings, then open the Import Rules tab. Every order-source connection has an Import Rules tab. Use it to decide which orders Owlery imports. You don’t need to change anything in your ERP. Changes save automatically and take effect on the next sync.

​
Pause or Resume Sync

Turn off Sync Enabled to stop Owlery from importing new orders or updates from this connection. Orders already in Owlery stay where they are. Turn it back on to resume. The next sync catches up on the changes made while sync was paused.
QuickBooks only looks back 30 days. If a QuickBooks connection is paused for longer, it needs a full sync to catch up.
Sync Enabled appears on ERP connections only. Warehouse and retail connections don’t have it.

​
Choose Order Types

Pick the order types to import, such as sales orders, purchase orders, or transfer orders. Owlery skips any type you leave unchecked. The types listed depend on what your system supports. Order types appear on ERP connections only.

​
Exclude Orders with a Rule

A rule tells Owlery to skip orders that match it. Add a rule for each kind of order you don’t want in Owlery.
1

Add a Rule

On the Import Rules tab, click Add rule.
2

Choose How Conditions Combine

In the Match dropdown, pick All conditions to skip orders that match every condition, or Any condition to skip orders that match at least one.
3

Add Conditions

Click + to add a condition. Pick a field, a match type, and one or more values. A rule can have up to 20 conditions.
4

Pick a Direction

On warehouse connections, choose whether the rule applies to Inbound orders, Outbound orders, or both. Leave it empty to apply the rule to both.
5

Choose Whether to Clean Up Existing Orders

Turn on archiving if the rule should also archive matching orders that are already in Owlery. See Archive Orders Already in Owlery.

​
Fields You Can Match On

  • Order number
  • Status
  • Shipping mode
  • Customer
  • Supplier
  • Notes
  • Reference number
  • Pickup location
  • Dropoff location

​
Match Types

Each match type also has a “does not” version, such as Does not contain. Rules always skip the orders they match, so a “does not” condition works as an include list. For example, a rule that skips orders whose customer does not equal your managed customers imports only those customers.

​
How Matching Works

  • A condition with several values matches when any one of the values matches.
  • A “does not” condition matches only when none of the values match.
  • Matching ignores capitalization. will call matches WILL CALL.
  • A blank field never matches anything, including “does not” conditions. So an order is never skipped because a field is empty. For example, if a rule skips orders whose carrier does not equal UPSN, orders with no carrier still come in.

​
Archive Orders Already in Owlery

A new rule only affects orders on the next sync. To also remove matching orders that Owlery already imported, turn on archiving for the rule. Owlery archives every order already in Owlery that matches the rule.
Check the rule’s conditions before you turn on archiving. A rule that’s too broad archives orders your team is still working on.

​
Undo Archiving

1

Fix the Rule First

Change or delete the rule so it no longer matches the order. If the rule still matches, the next sync archives the order again. Deleting a rule doesn’t bring archived orders back on its own.
2

Unarchive the Order

Find the order on the All tab of the Orders page. Click Unarchive in the order drawer or in the order’s row menu.

​
Common Rules

​
System-Specific Filters

Some systems add filters to the Import Rules tab: