Owlery discovers your locations, products, fulfillment patterns, and exceptions from the connected account. Your team confirms the recommended mapping rather than preparing a field specification.
Orders
Owlery can synchronize source IDs, order numbers, statuses, notes, references, customer or supplier contacts, facilities, requested and actual dates, SKUs, quantities, prices, units, weights, dimensions, and packaging.
Service sales and service purchases are excluded because they do not represent inventory freight movements.
Products and facilities
Owlery synchronizes products, including deprecated products referenced by historical orders. Product mapping can include SKU, description, unit, weight, and dimensions. Unsupported units safely default toeach for review.
Facilities can come from:
- Cin7 Core locations
- Child locations that inherit a parent address
- Customer and supplier address books
- The shipping address on an order
Multi-location sales
When splitting is enabled, Owlery reads pick lines from the latest fulfillment and groups quantities by location ID. One SKU can be divided across multiple pickup locations. Owlery creates one linked freight order per location. Unallocated quantities remain visible for review. Later syncs reconcile changed assignments, preserve stable child identities where possible, and retire obsolete splits.Synchronization and reliability
- Incremental synchronization uses update timestamps for sales and purchases.
- Pagination retrieves large lists in API-sized pages and processes details in smaller batches.
- Targeted retries retry temporarily unavailable detail records without discarding the rest of the page.
- Independent workflows allow one order family to continue if another API request fails.
- Exact-reference lookup supports a specific
SO,PO, or transfer outside the background cycle. - Stable reconciliation handles changing fulfillment locations and quantities across later syncs.