> ## Documentation Index
> Fetch the complete documentation index at: https://help.owlery.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reading Data from Katana

> How Owlery synchronizes Katana orders, locations, variants, and inventory.

Once Katana is authorized, Owlery retrieves changed transactions and the linked master data needed to build complete freight orders.

## Synchronized records

| Katana record  | How Owlery uses it                                               |
| -------------- | ---------------------------------------------------------------- |
| Sales Order    | Customer shipment from a Katana location to the shipping address |
| Purchase Order | Supplier shipment arriving at a Katana location                  |
| Stock Transfer | Internal inventory movement between Katana locations             |
| Location       | Facility with a stable Katana source ID                          |
| Variant        | Item-master record for a product or material                     |
| Inventory      | Location-specific stock quantities for a variant                 |

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.

<Note>
  Current inventory synchronization does not import Katana batch stock, lot codes, or expiration dates.
</Note>

## 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.