Skip to main content
Owlery has an inbound mapping foundation for Cin7 Omni sales and purchase orders. It translates freight-relevant order, contact, address, status, and line-item data into Owlery.
Cin7 Omni and Cin7 Core (formerly DEAR Inventory) are separate products with different APIs. Cin7 Core has a broader production connector with date write-back; this guide covers the Cin7 Omni scope. Cin7 Omni is not a self-service connector — Owlery confirms technical availability and scope before enablement.

​
Current integration foundation

Reading data

Review the implemented sales-order and purchase-order mappings, synchronization design, and rate controls.

Scope boundaries

Understand which authentication, item-master, transfer, custom-field, and write-back capabilities require scoping.
Write-back is not part of the current standard scope. Owlery documents any requested outbound workflow separately during solution design.

​
Getting started

1

Confirm product and availability

Confirm your system is Cin7 Omni. Owlery reviews the supported authorization method and current connector availability for your account.
2

Validate API access

Owlery determines the supported authorization method and verifies safe read access.
3

Share representative records

After read access is available, Owlery reviews sample sales or purchases to understand statuses, addresses, contacts, items, and exceptions.
4

Confirm and plan rollout

Your team confirms the proposed mapping, scope, and any additional implementation work before rollout begins.
To review Cin7 Omni availability, email support@owlery.ai.