Skip to main content
If your warehouse system doesn’t have a direct Owlery integration, you can still keep Owlery in sync by sending order data as a flat file. Your system drops a CSV on Owlery’s SFTP server, and Owlery picks it up and loads the orders so appointments line up with what’s coming and going.

How It Works

  1. Your system exports inbound and outbound orders to a CSV that follows the Owlery template.
  2. The file is uploaded to the inbound/ folder on Owlery’s SFTP server, ideally on an automated schedule.
  3. Owlery picks up each new file and creates or updates the matching inbound and outbound orders so your dock team can schedule against them.
  4. If an order can’t be loaded, Owlery emails your IT contact with what’s wrong so you can correct and resend it.
There is nothing to install and no API to build. Most WMS and ERP platforms can already export a scheduled CSV and push it over SFTP.
The template is built for facilities that handle their own goods, so every order stays in your facility’s Owlery account. If you’re a 3PL and need orders routed to the clients who own the goods, contact Owlery Support.

Who Does What

Owlery loads what’s in the file as sent. If an order has the wrong date, quantity, or trading partner, the fix belongs in your source system, followed by a corrected file.

Quick Start

Fill in every column in the template that your system can export. Only a few are strictly required, but those are a floor, not a target.
We strongly recommend sending the full order data. Trading partners and line items tell your warehouse and dock team who’s coming, what’s on the truck, and how much of it. That context makes it much easier to plan labor, stage freight, and catch problems before the truck arrives. The required columns get orders loading, but the full order is what makes them useful on the dock.

Download the blank template

Every column header, ready to fill in. Leave a column out only if your system can’t provide it.
1

Fill in every column you can

Use the full template and fill in as many columns as your system can export. At a minimum, every order needs these:A file with only these columns still loads:
2

Save it as a CSV

Use a .csv extension and a unique filename for every upload, such as orders-20261103-0800.csv.
3

Upload it to the inbound folder

Put the file in the inbound/ folder on Owlery’s SFTP server. Owlery picks it up from there.
Files left at the SFTP root, in other folders, or without a .csv extension are not processed, and no notification is sent.

Template Reference

Every column is listed below. Only the order columns marked Yes are required, but we strongly recommend filling in the trading partner, location, and line item columns as well. Headers aren’t case-sensitive, and each column also accepts the alternate names listed. If your system already exports one of those names, you can keep it.

Order Columns

The trading partner is who’s on the other side of the order: the vendor on an inbound order, the customer on an outbound order, or the other warehouse on a transfer. It shows in the Trading Partner column on the Orders table. The Ship From and Ship To columns are locations, not the partner. They’re often the same, but not always. For example, a vendor might ship from a third-party warehouse. Use Ship From on inbound orders and Ship To on outbound orders. If Ship From Name or Ship To Name is blank, it defaults to the Trading Partner Name. Most files only need the partner name plus the address. Also accepted:
  • Inbound: Shipper or Origin in place of Ship From, such as Shipper Name or Origin City.
  • Outbound: Consignee or Destination in place of Ship To, such as Consignee Name or Destination City.
  • Zipcode: Ship From Postal Code and Ship To Postal Code also work.
Line items show your dock team what’s on each order. Use one row per line, and repeat the order columns on each row.

Example File

A file using every column, with one inbound and one outbound order of two lines each. Inbound rows leave the Ship To columns blank, and outbound rows leave the Ship From columns blank. The inbound order leaves Ship From Name blank, so it defaults to the trading partner, Sunrise Packaging. The outbound order ships to one of Acme Foods’ stores, so Ship To Name is filled in.
A file can also contain only inbound or only outbound orders. Leave out the columns you don’t use.

How Owlery Handles Your File

  • UTF-8, comma-delimited, with standard CSV quoting (RFC 4180). Wrap any value that contains a comma in double quotes.
  • A header row is required. Headers aren’t case-sensitive, and the alternate names listed in each table are accepted.
  • Columns Owlery doesn’t recognize are ignored.
  • Owlery moves processed files out of inbound/.
Each file is a complete picture of the orders it contains. Resending an order replaces it, including its line items. Resending an order with no line rows clears its earlier lines.
Problems are handled one order at a time, so one bad order doesn’t block the rest of the file. Your facility’s IT contact receives a rejection email for each order that couldn’t be loaded.
  • If an order appears on several rows, the first row’s Notes value is used.
  • If you include any line item column, then Line Number, SKU, and Quantity are all required. An order with no line item columns at all is valid.
  • A duplicate Line Number within an order replaces the earlier line.
  • Unit of Measure accepts common names and abbreviations (each/ea, case/cs, pallet, pack, tray, and so on). Unrecognized units default to each with a warning.
  • On an inbound order, the trading partner is stored as the order’s supplier. On an outbound order, it’s stored as the customer.
  • Ship From columns are ignored on outbound orders, and Ship To columns are ignored on inbound orders.
  • A blank Ship From Name or Ship To Name defaults to the Trading Partner Name.
  • If you include any address field, city and state are required.
  • Include Trading Partner Code, Ship From Code, and Ship To Code so each partner and location maps to one stable record instead of creating duplicates.

Getting SFTP Credentials

To get a login for Owlery’s SFTP server, email Owlery Support at support@owlery.ai. We’ll send your credentials and connection instructions, and confirm your first file loads correctly.

FAQ

How Often Can We Send Files?

As often as you like. Owlery picks up every new file in inbound/, so you can send on a schedule, whenever orders change, or both.

Can We Send a Different CSV Format?

If your system can’t produce the template, let Owlery Support know what you can export and we’ll see what we can do to work with you.