Reading Data from SOS Inventory

Once SOS Inventory is authorized, Owlery retrieves each order family and the item master in pages, then resolves the supporting records needed for freight planning.

​

Orders

Mapped data can include source IDs, order numbers, open or closed status, dates, customers or vendors, facilities, expected ship or delivery dates, customer references, items, descriptions, quantities, line numbers, prices, totals, units, and transfer notes.

​

Item master

Owlery can synchronize:

• SOS item ID and type
• SKU, name, and description
• Barcode and notes
• Source synchronization timestamp when available
• Base and alternate units of measure
• Packaging conversion relationships

When SOS provides a base unit and an alternate case unit with a conversion, Owlery preserves that relationship for shipment planning.

​

Supporting records

Owlery batches and caches item, location, customer, and vendor lookups during synchronization. This converts SOS Inventory IDs into usable facilities, partners, item details, and packaging without repeatedly calling the same supporting endpoint.

​

Synchronization and reliability

• Request pacing respects the SOS Inventory API throttle with an operational buffer.
• Pagination uses the supported page size and follows reported totals.
• Incremental overlap includes one minute before the prior successful boundary.
• Parallel family reads request sales, purchases, and transfers while a shared limiter controls pacing.
• Batched lookups group supporting IDs into bounded requests.
• Local caching avoids duplicate lookups during one sync.
• Refresh locking prevents concurrent OAuth token rotation.
• Exact refresh reloads one source order by ID.