Order exceptions

An Order Exception is what TruSync creates when it can’t post an order automatically — usually because something about it isn’t mapped yet.

Common causes

• The order’s payment method isn’t mapped to a QuickBooks payment method.
• The order’s tax jurisdiction isn’t mapped to a QuickBooks tax rate.
• A product on the order isn’t mapped to a QuickBooks item.

TruSync deliberately doesn’t guess at a mapping to keep the order moving — an incorrectly auto-mapped order just creates rework later when you have to find and fix it in QuickBooks. Instead, the order waits as an exception until you resolve the underlying mapping.

Getting notified

You’ll receive an email when a new order exception is created, so you don’t have to check the dashboard proactively.

Resolving an exception

1. Open Order Exceptions from your TruSync dashboard.
2. Open the exception to see what’s unmapped.
3. Add the missing mapping (payment method, tax jurisdiction, or product) from Settings.
4. TruSync syncs the order once the mapping is in place.

FAQ

Do I need to resolve exceptions in order? No, resolve them in whatever order makes sense — mapping one payment method or product often clears several exceptions at once.

Will future orders with the same issue also become exceptions? Not once you’ve added the mapping — only orders that arrived before the mapping existed need manual resolution.

Can I dismiss an exception without resolving it? Exceptions represent orders that haven’t posted to QuickBooks yet — dismissing without mapping leaves that order unsynced.