Organize your inventory facilities by defining parent-child relationships between
locations. By defining a location hierarchy, you can group sub-locations such as aisles,
shelves, or rooms under a single parent warehouse or service center. This structure allows
inventory managers to create comprehensive inventory count plans for an entire facility at once,
reducing the administrative effort of managing hundreds of individual sub-locations.
Required Editions
Available in: Lightning Experience
Available in: Automotive Cloud, Communications Cloud, Energy and Utilities Cloud,
Manufacturing Cloud, Service Cloud, and Media Cloud. View edition
availability.
User Permissions
Needed
To create and edit locations:
System Administrator permission set
To build a hierarchy, you must assign a parent to your sub-locations.
From the App Launcher, find and select Locations.
Create the Parent Location:
Click New. Enter a name (e.g., Innsbruck Warehouse).
Select a Location Type (e.g., Warehouse).
Select the Inventory Location checkbox. Only locations with this option enabled can
be included in inventory count plans.
Save your changes.
Define Child Locations:
Select an existing sub-location or click New to create one
(e.g., Loading Dock).
In the Parent Location field, search for and select the parent record you created
in Step 2 (e.g., Innsbruck Warehouse).
Save your changes.
Repeat Step 3 for all aisles or rooms that belong to the parent facility.
You can add product items to only active plans.
Once location hierarchy is created, these relationships are automatically recognized when
creating an Inventory Count Plan.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.