Skip to main content
SOS Inventory has a focused configuration surface. Owlery inspects your item records and recommends an override only when the standard mapping does not match your operating model.

​
SKU mapping

Owlery uses sku by default. Some accounts use another item field, such as name, as the operational SKU. Owlery can select that field without rewriting existing item records. When name becomes the SKU, Owlery chooses a separate display name from the first populated full name, description, purchase description, or original name. The selected source field must be available on the SOS item response.

​
Authentication details

An authorized user grants Owlery access through SOS Inventory OAuth 2.0. The account needs read permission for Items, units, sales orders, purchase orders, transfers, locations, customers, and vendors. Owlery coordinates token refresh so concurrent requests do not replace the same refresh token.

​
Read-only boundary

The current connector does not write back to SOS Inventory. If outbound updates are required, Owlery documents the event, target record, fields, and API behavior before proposing an extension.