OP DAY
1 · WHAT ARE YOU CONFIGURING?
2 · DROP THE DATA
3 · FIELD MAPPING
4 · ASSUMPTIONS & GAPS
5 · COMMIT

NETWORK CONFIGURATION — pick the layer, then the category

These layers describe the operating network. Choose one, drill into its category, then drop the data in any shape — spreadsheet, CSV, pasted table, email. The importer reads it, maps the fields, states its assumptions, asks for what's missing, and commits into the live model. Save the import as a rule and the next file of that shape flows straight through.

LAYER
◂ CONFIG
1 · ZONE HIERARCHY
2 · CREATE ZONES
3 · LANES & RATES
4 · PLANNING PROFILES
5 · RESOLUTION TESTER

GEOGRAPHY IS THE LAW — eight cascading zone layers, most local wins

Every address in the network sits in a stack of zones, from the whole globe down to the single facility. Rates and planning scope attach to zones; when more than one could apply, the most specific wins. Custom zones slot between the integer layers at fractional specificity.

creates editable custom zones straight from the real region/country/state/facility list — safe to click again later, it only tops up what's missing
CUSTOM ZONES IN THE LIBRARY