Understanding our data model for physical places

Two things are worth noting about locations. One, they are needed absolutely
everywhere in logistics-related systems. Two, they are inherently quite complex.
This page aims to explain how Skrym represents a physical location.
The data model
Below, you can explore the data model.


Locations

Understanding how Skrym handles your locations

Skrym tags physical locations with an organization in order to better handler locations of our users' stores, warehouses, terminals, pickup points, etc.
Each location has a type, and currently Skrym supports the following location types:
STORE, WAREHOUSE, OFFICE, HEADQUARTERS, TERMINAL, UNMAPPED, LOCKER, DELIVERY_HUB, PICKUP_POINT
Configuring Organization Locations
One of the possible configurations for organization locations is to set the maximum distance between two of Your location types. This is understood as the largest possible distance between the two location types, which skrym uses to better estimate routing of packages.
This is accessible to retrieve from the following authenticated REST API endpoint:

One can also insert new or update existing configuration via:

It is also possible to delete your configuration through and API endpoint:

However, it may be preferable and more user friendly to do this via Scope.