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

# Katana Configuration Reference

> Order scope, synchronization, mapping, and supported tracking controls.

Owlery reviews your Katana account and recommends the relevant controls. Your team confirms the result; Owlery maintains the configuration.

| Area | Available controls |
| - | - |
| Overall synchronization | Enable or disable Katana background synchronization |
| Order scope | Enable or disable sales, purchase, and transfer orders independently |
| Initial history | Run a full synchronization when historical records are needed |
| Ongoing changes | Retrieve records changed since the prior successful sync with boundary overlap |
| Exact lookup | Find an order by its Katana order or transfer number |
| Status interpretation | Map transaction statuses to Owlery order states |
| Facility mapping | Build origins and destinations from Katana locations and shipping addresses |
| Facility contact sync | Fill facility contacts, such as the BOL contact, from Katana; off by default so contacts entered in Owlery aren't overwritten. Most helpful when you ship mostly to residential addresses |
| Item identity | Preserve variant IDs while interpreting SKU, name, and unit data |
| Tracking write-back | Enable the currently supported carrier-specific fulfillment workflow |

## Authentication details

Katana uses OAuth 2.0. Owlery stores account-specific access and refresh tokens and can refresh expired access. A connection-level lock prevents concurrent workers from rotating the same refresh token.

Read access can include orders, fulfillments, locations, customers, suppliers, variants, products, materials, and inventory. Write access to sales-order fulfillments is needed only when supported tracking write-back is enabled.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.