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

# Writing Back to Katana

> The supported carrier-specific sales-order fulfillment tracking workflow.

Katana write-back currently supports fulfillment tracking for a specific carrier workflow. Owlery confirms whether this workflow applies before enabling it.

<Info>
  This is not a general fulfillment or receipt write-back feature for every carrier. Owlery documents any additional outbound workflow separately.
</Info>

## Supported behavior

When the supported tender workflow returns a tracking number, Owlery can:

* Read the current Katana sales-order rows and quantities
* Create a `PACKED` fulfillment when none exists
* Add the carrier tracking number, tracking URL, and carrier name
* Update only the tracking fields on one existing fulfillment
* Treat already-matching tracking data as a successful no-op
* Record a separate success or failure for every Katana order in a consolidated shipment

## Safe writes by design

Owlery does not overwrite a different tracking number or guess when Katana returns multiple fulfillments.

If a create request fails after Katana may have accepted it, Owlery queries the fulfillment again before returning an error. This recovery check reduces duplicate records after a timeout.

* Fulfillment creates include the source sales-order rows and quantities.
* Existing records receive tracking-only updates.
* Per-order audits preserve actionable results.
* Matching tracking values do not generate unnecessary updates.

<Tip>
  Validate inbound Katana sales orders first. Enable tracking only after Owlery confirms that the supported carrier workflow and fulfillment structure match your account.
</Tip>