Synchronized records
Order mapping can include IDs, order numbers, statuses, timestamps, customers or suppliers, facilities, dates, references, notes, variants, quantities, units, prices, and totals.
Account-specific interpretation
- Sales destinations use the order shipping address; origins use Katana locations.
- Country and state values are normalized when possible.
- E-commerce context can identify a sales order as parcel.
- Product and material units can map to quantity, weight, length, or volume units.
- Katana permits duplicate SKUs, so Owlery preserves the variant ID as the stable item identity.
- Inventory can include in-stock, committed, reorder-point, and missing-or-excess quantities by location.
Current inventory synchronization does not import Katana batch stock, lot codes, or expiration dates.
Synchronization and reliability
- Rate pacing keeps requests within the configured Katana allowance.
- Pagination retrieves up to 250 records per page with a page safety limit.
- Incremental windows use update timestamps and overlap the prior successful sync.
- Reference caching avoids repeatedly fetching the same customer, supplier, facility, or variant.
- Stable identities use Katana record IDs for orders, facilities, and variants.
- Targeted refresh reloads one order directly from its source record.
- Exact lookup finds an order by Katana order or transfer number.