Enhanced interface

Field descriptions: Warehouses

The following table describes each field on the Warehouse information page.

General

Field	Description
Warehouse ID	A short identifier for the warehouse. This ID will appear in any applicable selection lists in the system. You cannot change the warehouse ID after you save the warehouse. Using 0 by itself is not a valid value. Best practice for warehouse IDs Use a generic ID (like W001) instead of embedding semantics in an ID (like W-Boston) because you cannot change the warehouse ID. If the Boston warehouse moves to Philadelphia, you won't have to worry about the warehouse ID not matching. You can change the warehouse name, so that W001 could be named "Boston warehouse".
Name	A description of the warehouse. You can change the warehouse name as desired.
Location	Use the dropdown list to select a geographical location for the warehouse. If your company is multi-entity, multi-currency, the system applies the base currency of this location (or the selected location's parent location, if applicable) to inventoried items for consolidations.
Manager ID	Use the dropdown list to select an employee who will be responsible for the warehouse.
Parent warehouse	If this warehouse is part of a hierarchy, use the dropdown list to select the parent warehouse for this warehouse. Leave this field blank if the warehouse is the top parent in a hierarchy.
Contact	Use the dropdown list to select the warehouse contact. If your company is using the Avalara AvaTax integration, Avalara uses this contact's address as the Ship From address when calculating sales tax for inventory items.
Ship- to contact	Use the dropdown list to select a ship-to contact for the warehouse. If your company is using the Avalara AvaTax integration, Avalara might use this ship-contact to calculate purchasing transaction line-level tax if there's no deliver-to contact at the line level on the purchasing transaction. If Enable deliver-to contact at the line level is set to true in the Configure Purchasing page, Avalara uses the following hierarchy to calculate purchasing line level tax rates: Warehouse ship-to contact (if the item is an Inventory, Kit, or Stockable kit item) Location ship- to contact Purchasing transaction header deliver-to contact
Status	Select Active or Inactive. If you select Active, the warehouse will be available for use. If you select Inactive, the warehouse will not be available for use. You can change the warehouse's status as desired.
Enable replenishment for this warehouse	Items in this warehouse will be included in the replenishment process, which identifies which items need to be reordered and enable purchase transactions to be automatically created. This checkbox appears only if Replenishment is selected in the Configure Inventory Control page.
Allow negative inventory for this warehouse	This checkbox appears only if Do not allow negative inventory globally is selected in the Configure Inventory Control or Configure Order Entry page. It does not appear for Supplies Inventory Use this checkbox to specify whether you can save Order Entry or Inventory Control transactions that create negative inventory for the items in this warehouse. Leave the option deselected to prevent saving transactions that would cause the quantity on hand to become negative. This is the default. Select this option to allow saving transactions that would cause the quantity on hand to become negative. For example, if you use a drop-ship workflow, you might want to use a separate drop-ship warehouse where negative inventory is allowed. With a separate warehouse, you can convert the drop-ship sales orders to sales invoices without having to worry about having the purchasing receipts recorded first. COGS for negative quantities The COGS for negative quantities is calculated using the last purchase cost previously recorded for average, FIFO, and LIFO items and the standard cost in effect for standard cost items. In the rare situation where the very first transaction for an inventory item is a sale and not a purchase, a last purchase cost does not exist and the COGS would be zero. However, when Inventory Control was implemented, an inventory adjustment that affects quantity and value was most likely used to set up a beginning balance for the item, which then acts as the last cost. If Sage Intacctcannot find a last cost, it creates a zero-value journal entry for COGS.

Tracking

This section appears only if the warehouse does not allow negative inventory, and Enable tracking by: Bin is selected in the Configure Inventory Control page. Learn more about bin tracking, including best practices for naming conventions.

Field	Description
Bins table	Use the table to add, edit, and delete bins from the warehouse. Any changes you make (such as to the bin attributes like zone, aisle, or row) are reflected back in the Bins Information page. Using the table, you can: Sort on any of the columns by selecting the column heading Add a bin Rename a bin Change any of the bin attributes in each row (you can select Add at the top of a dropdown list to add a new zone, aisle, row, bin face, or bin size). Delete a bin by selecting the trash can icon at the end of a row Add more lines by selecting the + sign at the end of a row For a description of the bin attributes, see the bin field descriptions.

Field

Description

Bins table

Use the table to add, edit, and delete bins from the warehouse. Any changes you make (such as to the bin attributes like zone, aisle, or row) are reflected back in the Bins Information page.

Using the table, you can:

Sort on any of the columns by selecting the column heading
Add a bin
Rename a bin
Change any of the bin attributes in each row (you can select Add at the top of a dropdown list to add a new zone, aisle, row, bin face, or bin size).
Delete a bin by selecting the trash can icon at the end of a row
Add more lines by selecting the + sign at the end of a row

For a description of the bin attributes, see the bin field descriptions.