Skip to main content
QuickBooks Online does not expose a native sales-order record like many ERPs. Owlery’s supported workflow represents the accounting-side customer order as a QuickBooks Estimate linked to an originating Owlery order.

​
Estimate synchronization

Owlery reads the Estimate ID, synchronization token, status, Item identities, SKU or description, quantity, unit price, and amount. The linked Owlery order retains its originating facilities, customer, and operational context. Estimate lines are currently interpreted as cases. Owlery confirms whether this matches your item model during discovery.
Owlery does not import every unrelated QuickBooks Estimate as a new freight order. The workflow synchronizes Estimates that match an originating Owlery order.

​
Change tracking and reliability

  • Incremental Change Data Capture reads changed Estimates and Items.
  • Cursor overlap includes one minute around the prior successful sync.
  • Lookback control stays within QuickBooks’ 30-day Change Data Capture limit.
  • Intentional full refresh uses a paginated Estimate query instead of the limited change window.
  • Deletion reconciliation marks deleted Estimates and invalidates deleted Items.
  • Connection-scoped caching isolates Item data between QuickBooks companies.
  • Request pacing spaces QuickBooks API calls.
  • Change-volume monitoring warns as a response approaches QuickBooks’ object limit.

​
Authentication

A QuickBooks administrator authorizes Owlery through Intuit OAuth 2.0 and selects the company to connect. Owlery stores the company ID and account-specific access and refresh tokens. Token refresh is serialized per connection to prevent concurrent rotation.