TABLE OF CONTENTS
Areas are a good way of physically separating locations. Areas have been used to designate locations that exist in separate physical buildings or to simply segment physical locations for separate purposes.
An Inventory Allocation routine can ensure that an order is only allocated into its matching area. This helps ensure that an order is only fulfilled out of the locations designated for that purpose. But having this allocation routine turned on is not required to see a benefit with areas.
Even if not allocating by Area, adding Areas to a site has deeper implications on permissions and batching and those should be understood before adding Areas.
Implications of Areas
If Locations are assigned an Area, a User must be assigned to the same Area in order to perform any inventory transaction against those locations.
If an Area has been assigned to a User, only batches with matching Areas will be allowed to be downloaded and picked
When Batches are created, all of the orders within the batch must be in the same area. The batch adopts that area and the batch is assigned to the same area as the orders.
If orders don't have Areas, the batches won't have an Area assigned. Users won't be able to pick those batches because it doesn't fall under the permissions assigned by Area
These are the steps to adding Areas to a site