Rules and restrictions

Reference list of the rules that limit, lock or validate Locations, Location Groups, bulk uploads, sharing and data policies.

Rule	Applies to	Behavior
Every Location belongs to one Trade Partner	Locations	The Trade Partner must exist before the Location is added.
Required names	Location drawer	The Location Name cannot be saved empty: an error appears and Wholechain restores the name. The Location Identifier can be saved empty.
Identifier numbers are validated	GLN, DUNS, PGLN	An invalid number is rejected.
Address requirements	Locations	Address line 1, Country and Postal code are required for an address. Without an address, both Latitude and Longitude are required. When an address is provided, Wholechain attempts to find the coordinates; if none can be found, the Location is saved with 0, 0.
Network Status	Locations	Self for your own company's Locations; External for others.
Owner is fixed	Location details	The Owner cannot be edited.
Connected or shared records	Location details	A Location that is shared with you, or that belongs to another Wholechain account, cannot be edited because the details belong to another account.
Locations with active inventory	Archive	Cannot be archived.
Archiving a Trade Partner	Locations	The partner's Locations are archived too.
Group deletion	Location Groups	Cannot be undone; member Locations are kept.
Linking to a group	Bulk uploads	A Location Group must exist before Locations are linked to it; a group is not created by an upload.
Sharing tab	Locations	Shown only for Locations that belong to your own company.
Only your own Locations can be shared in an invitation	Invitations	Select your locations you would like to share lists only Locations that belong to your own company. See Invitations.
Connected partners only	Sharing	The Share Locations drawer lists only Wholechain-connected Trade Partners; the list is empty when none is connected. The Share button stays greyed out until a Trade Partner is chosen.
Shared Locations in events	Locations shared with you	Can be used only in Ship and Receive events: as a destination on Ship events and as an origin on Receive events. Viewer access cannot edit custom data (KDEs); Editor access can.
Template rows must stay	Bulk uploads	Do not remove or rename the heading row or the field-code row.
File types	Bulk uploads	.xlsx and .xls.
Rows are processed individually	Bulk uploads	Rows without errors can be added even when an error banner appears; there is no preview and no count of created rows.
Updating records by upload	Bulk uploads	A row that matches an existing record updates it. Records are matched by identifier, so include the Trade Partner Number/ID and Location Number/ID in every file if you use identifiers. A row with a blank identifier for a record that has one creates a new record. A name can be changed through an upload only when the row carries the identifier.
Re-uploading a corrected file	Bulk uploads	Upload only the rows that were not added, to avoid duplicates.
Location type codes	Locations bulk upload	Use the codes, not the labels (for example WarehouseDC, not Warehouse / Distribution Center).
Coordinates not found	Bulk uploads	When no coordinates are given and none can be found for the address, the Location is saved with 0, 0.
Locations created from the Trade Partners template	Locations	Get the type Warehouse / Distribution Center.
Vessels switch	Settings	Adding vessels as Locations is off by default. Turning on the Vessels switch activates a special form of Location with additional fields specific to vessels, for GDST compliance.
Account-wide settings	Settings pages	Changes apply to the whole account.
Data Policy must be switched on	Data policies	An Admin switches Data Policy on for the whole account in Organization Settings > Account, in the Compliance section. See Account Settings.
Universal data policy	Locations	A data policy set in Master Data Settings > Location is universal, for all Locations.
Data policy for Location Groups	Location Groups	A group policy is a sub-group of the universal policy. It is managed on the Location Groups sub-tab of Master Data Settings > Location, and also in the Data Policy tab of the group drawer.
Data policy for one Location	Location	Set only on that Location's details drawer (gear icon, or View Settings in the row menu).
Only Required blocks	Data policies	Only the enforcement level Required prevents an event from being logged when the value is missing. Optional, Recommended and Expected do not block.
Values are entered on the record	Data policies	A data policy defines which KDEs apply and how strictly; the values themselves are always entered on the individual Location.
Escape key	Drawers	Closes the drawer and discards entries that are not saved.

Was this page helpful?