Network Engine / Structure

Every tier of your network, in one hierarchy.

Onboard manufacturers, regional distributors, sub-dealers and retailers into a single structure - so a product's entire path is one connected record, not a stack of disconnected order books.

Hierarchy, top to bottomlive
Manufacturer
12,400
dispatch origin
Regional Distributor4
11,800
first-tier nodes
Sub-Dealer28
9,600
second-tier nodes
Retailer140+
8,600
point of sale

Guided onboarding

Bring tiers in from your existing records and place each node where it belongs in the chain.

Connected hierarchy

Every node knows its parent and children, so stock movement is traceable end to end.

Zones and territories

Group nodes into zones for reporting, allocation rules and bottleneck detection.

Set the structure once - every other capability builds on it.

Because tracking, allocation, credit and analytics all read from the same hierarchy, the shape of your network only has to be defined a single time.

  • Onboard each tier with its own roles and access scope
  • Assign sub-dealers to their parent distributor and zone
  • Attach product lines and price structures to nodes
  • Reassign or restructure nodes without losing order history
Worked example

One product's full path, end to end.

Follow a single SKU from the manufacturer down to a specific retailer. Every hand-off is a record on the same chain, so a backup at any tier is visible against the tier above and below it.

SKU 7S-4402 / path trace
Manufacturer dispatch12,400 u
Distributor - North3,100 u
Sub-dealer - Zone 2820 u
Retailer - Store 11864 u
Path integritytraced

Illustrative trace. Real product paths are built from your own dispatch and receipt records during onboarding.

Map your real network structure with us.

Share how your tiers are organised today and we will show the hierarchy modelled inside 7SANDZ.