Transfer Orders import field reference and situation how-tos
What this covers
This article explains which columns to include in a Transfer Orders import for common tasks, which fields are required, and what every Transfer Orders import field does. It applies to both the [Basic Importer] and the [Admin importer].
Field names below are the Zenventory defaults. If your company renamed fields in the Lexicon, your screens and sample file show your names instead.
Required for a basic transfer order
- Deliver From
- Deliver To
- Required By
- SKU
- Quantity
All other fields are optional. The Situation how-tos above cover the fields needed for other tasks, like drafts, several orders in one file, and one-step transfers.
Mapping reference table
This table lists every field on the Transfer Orders import mapping screen, in the same order and under the same section headings (Transfer Order and Item). Use it to decide which of your file's columns to map to each field, and to check that your data is in the right format.
For each field, the table shows:
- What to map this to for Transfer Orders: what the field does on the transfer order or its items.
- When is this field required?: whether the field is always needed or optional.
- Format: the type of value the field accepts, such as text, number, date, or Y/N, and its character limit.
Complete Automatically only shows on the mapping screen when one-step warehouse transfers are turned on for your company.
Field names are the Zenventory defaults. If your company renamed fields in the Lexicon, your mapping screen shows your names instead.
| Mapping Field | What to map this to for Transfer Orders | When is this field required? | Format |
|---|---|---|---|
| Transfer Order | |||
| Import ID | Groups rows into the same transfer order during the import. It isn't saved. Only needed when the file holds more than one transfer order. Rows with the same Import ID become one order, and the order details are taken from its first row. If every Import ID is blank, the whole file becomes one order. | Optional | Text, not saved (no limit) |
| Deliver From | The warehouse the stock is transferred from. Must match an active warehouse. Capitalization doesn't matter, but spelling and spaces do. A name that isn't found fails the order. | Required | Text, 50 characters |
| Deliver To | The warehouse the stock is transferred to. Must match an active warehouse and can't be the same as Deliver From. A name that isn't found fails the order. | Required | Text, 50 characters |
| Required By | The date the transfer is needed by. Only YYYY-MM-DD saves correctly. MM/DD/YYYY does not. | Required | Date, YYYY-MM-DD only |
| Draft | Set to Y to save the order as a draft. Drafts aren't allocated. Leave blank to create the order and allocate stock during the import. | Optional | Y, Yes or 1 |
| Ship Via | The shipping method for the transfer. Must match a service code or carrier code. Names aren't matched. A value that doesn't match fails the order. | Optional | Service code or carrier code, 30 characters |
| Note | Internal notes about this transfer order. | Optional | Text, 412 characters |
| Complete Automatically | Set to Y to complete the transfer during the import. Only shown when one-step warehouse transfers are turned on. Only works on orders that aren't drafts. Turned off if any line is serialized. | Optional | Y, Yes or 1 |
| Item | |||
| SKU | The SKU of the item being transferred. It must already exist within the selected client. The import doesn't create items. Kit, Non-Inventory, and Drop-Ship items can't be transferred. A SKU like that, or one that doesn't exist, fails the whole order. | Required | Text, must match an existing SKU, 100 characters |
| Quantity | The quantity of this item to transfer. Any value above 0 is accepted, including decimals. A quantity of 0 or less fails the order. | Required | Number above 0 (decimals allowed) |
Situation how-tos
| Situation | Columns to include | What to know |
|---|---|---|
| Import one transfer order | • Deliver From • Deliver To • Required By • SKU • Quantity • Leave Import ID blank |
Use one row per item. If every Import ID is blank, the whole file becomes one order. The order details are taken from the first row. |
| Import several transfer orders in one file | • Import ID (the same on each row of an order) • Deliver From • Deliver To • Required By • SKU • Quantity |
Give each order its own Import ID. Rows with the same Import ID become one order, and the order details are taken from its first row. Import ID isn't saved. |
| Save transfer orders as drafts | • Draft = Y | Drafts aren't allocated. Finish them in Zenventory when you're ready. |
| Allocate stock during the import | • Leave Draft blank | Orders that aren't drafts are created and allocated during the import. There's no separate allocation step. |
| Transfer and complete in one step | • Complete Automatically = Y • Leave Draft blank |
Only available when one-step warehouse transfers are turned on. The setting is ignored for drafts, and it's turned off if any line on the order is serialized. |
| Import transfers for a client (3PL) | • Select the client in the import window (there's no client column) | Only one client can be imported at a time. For several clients, run a separate import for each. SKUs are looked up within the selected client. |
| Set the shipping method | • Ship Via | Enter a service code or carrier code. Names aren't matched. A value that doesn't match fails the order. |
| Transfer kits, non-inventory, or drop-ship items | • Not possible by import | These items can't be transferred. If any line has one, or a SKU that doesn't exist, the whole order is rejected and nothing is saved for it. |
| Avoid duplicate transfer orders | • Not possible by import | The import always creates a new transfer order and never checks whether one already exists. Reimporting a file you've already successfully imported creates duplicate orders rather than failing or updating the originals. |
How the import handles transfer orders
How does Zenventory know which rows belong to the same transfer order?
Each row is one item on a transfer order.
- One order in the file: leave Import ID blank. The whole file becomes one order.
- Several orders in the file: give each order its own Import ID, and use it on every row of that order.
- The order details (Deliver From, Deliver To, Required By, Draft, Ship Via, and Note) are taken from the order's first row.
- Import ID is only used during the import. It isn't saved on the order.
Does the import allocate stock?
Yes, unless the order is a draft. Orders that aren't drafts are created and allocated during the import.
- Set Draft to Y to save an order without allocating it.
- If one-step warehouse transfers are turned on, set Complete Automatically to Y to finish the transfer during the import.
Can I update a transfer order that's already in Zenventory?
No. The import only creates new transfer orders. Edit existing orders in Zenventory.
What items can be transferred?
Items must already exist within the selected client. The import doesn't create items.
- Kit, Non-Inventory, and Drop-Ship items can't be transferred.
- If any line has one of these items, or a SKU that doesn't exist, the whole order is rejected and nothing is saved for it.
Can I import transfers for more than one client?
Not in one file. Select the client in the import window. For several clients, run a separate import for each one.