Once Cin7 Core is connected, Owlery pulls your records automatically and turns them into the stops, partners, items, dates, quantities, prices, and statuses your freight workflow uses.
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 to each 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
Owlery can resolve a missing location ID by name and prefers a supplier’s default shipping address for purchase pickups.
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 pick up changed assignments, keep existing split orders where possible, and remove splits that no longer apply.
Reliability
Each sync pulls only what changed since the last one. If Cin7 Core is briefly unavailable, Owlery retries the affected records without holding up the rest, so a problem with one order type doesn’t stop the others. You can also import a specific sale, purchase, or transfer by its number at any time. 
