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

# ASNs & Invoices to Retailers

> When Owlery sends retailers PO acknowledgments, ASNs, and invoices, and where each one's data comes from.

This page is for **Shippers**: teams that quote, tender, and pay for freight in Owlery. If the person you're helping isn't a shipper, this page doesn't apply to them.

Owlery sends your retailers three kinds of documents. Each one shows as a row in **Retail Status**, with the retailer's [receipt status](/shippers/orders.md#receipt-status).

| Document | Code | When it's sent |
| - | - | - |
| PO acknowledgment | 855 | Right after a new PO creates an order, if it's turned on for that retailer. |
| ASN | 856 | When your warehouse confirms the shipment. |
| Invoice | 810, or 880 for grocery | After the order closes. |

## PO Acknowledgments

A PO acknowledgment tells the retailer you've accepted their order. Owlery sends one per PO, when the PO first creates an order. Cancellations aren't acknowledged automatically.

PO acknowledgments are optional and set per retailer. See [Retailer Settings](/shippers/retail-wholesale/configuration.md).

## ASNs

An ASN tells the retailer exactly what's on the truck and when it left.

### When It's Sent

* **Automatically**: when your pickup warehouse confirms what it shipped. This is the normal path.
* **When you click the button**: click **Send ASN** (or **Update ASN**) on the retailer's drop-off stop. Use it after you fix a problem. See [Resend an ASN](/shippers/troubleshoot-retail-orders.md#resend-an-asn).

### Where the Data Comes From

| ASN content | Comes from |
| - | - |
| PO number and the retailer's line references | The retailer's purchase order |
| Items and quantities shipped, lots, and pallet labels | Your warehouse's shipment confirmation |
| Ship date, carrier, BOL, PRO and seal numbers, and weights | The load and its tender |

Because the ASN pulls from the load, missing carrier or BOL details on the load show up as missing details on the ASN. Fix the load first, then resend.

### Resends

Owlery skips an automatic resend when nothing changed, so retailers don't get duplicates. A manual resend, or a shipment that changed, goes out as a change to the original ASN, for retailers that accept ASN changes.

> [!WARNING]
>
> A missing or late ASN can turn into a retailer chargeback. If an ASN can't be created, Owlery emails your [Retail ASN Issue Contact](/shippers/contacts.md#retail-asn-issue-contact).

## Invoices

Owlery sends a retail invoice only after the order closes. That normally means your warehouse has confirmed the shipment.

**1. Owlery Writes the Order to Your Accounting System**

The order goes to your connected accounting system.

**2. The Invoice Is Created There**

Prices and terms come from your books, so the invoice matches your records.

**3. Owlery Sends It to the Retailer**

Owlery reads that invoice, converts it to the retailer's format, and sends it.

Owlery sends one invoice per order. If one already went out, another attempt is skipped.

Invoices go out automatically after the order syncs, if invoicing automation is on for you. Where it's turned on, you can also click **Send Invoice** in the order drawer.

> [!NOTE]
>
> Retail invoicing needs a supported accounting integration. See [Integrations Overview](/shippers/integrations-overview.md).

## If a Document Didn't Go Out

See [Your ASN or Invoice Didn't Reach the Retailer](/shippers/troubleshoot-retail-orders.md#your-asn-or-invoice-didnt-reach-the-retailer).

> **[Next: Retailer Settings](/shippers/retail-wholesale/configuration.md)**
>
> See the settings Owlery keeps for each retailer.


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