Changing Zone Setup from Grouped Suburb Zones to Individual Suburb-Based Zones in FreightTracker

Changing Zone Setup from Grouped Suburb Zones to Individual Suburb-Based Zones in FreightTracker

Changing Zone Setup from Grouped Suburb Zones to Individual Suburb-Based Zones

Overview

In FreightTracker, you can choose to structure your delivery zones using either:

  • Grouped Suburb Zones (zones that group multiple suburbs into one pricing/routing area), or

  • Individual Suburb-Based Zones (where each suburb is treated as its own distinct zone)

While both options are supported, it's important to understand the implications of switching zone structures—especially after your system has already gone live.

Option 1: Selecting Individual Suburb Zones During Initial Setup

This is the preferred approach.

If you're still in the setup or go-live implementation phase, we can configure your system to use Individual Suburb-Based Zones from the beginning. This allows us to:

  • Build all rate tables, zones, and routing logic around this structure

  • Avoid disruption or data loss

  • Ensure the system is aligned with your business logic from day one

✅ No issues or risks are associated with this option.

Option 2: Switching to Individual Suburb Zones After Go-Live

It is possible to change your zone setup after your FreightTracker system has already been implemented. However, this is a major change and should be approached with caution.

⚠️ Key Considerations

1. Loss of Current Rate Setups

  • All existing rate setups will be permanently wiped

  • FreightTracker cannot restore or recover your current rate data once the new structure is applied

  • You will need to manually re-enter all rates across all modules

⚠️ FreightTracker does not take responsibility for rate loss or discrepancies during this process.

2. System-Wide Impact

  • This change affects multiple areas of your system:

    • Rate tables

    • Routing rules

    • Zone-based reporting

    • Any automation using zones

  • It may cause unforeseen issues across your setup

  • A full review and testing cycle is strongly recommended

3. Implementation Timeframe

  • Estimated timeframe: 3–4 weeks

  • Dependent on current workload of our development team

  • This is not a quick change — please plan accordingly

4. Implementation Timing

  • We do not recommend making this change after go-live

  • Ideally, this structure should be chosen during the initial system implementation

5. Liability Disclaimer

  • FreightTracker takes no responsibility for:

    • Data loss

    • Rate discrepancies

    • System disruptions caused by this change

  • All rate re-entry and system validation is the responsibility of the customer


    • Related Articles

    • Capacity Management

      Capacity Management is a module that can be activated via the FreightTracker Marketplace. The below setup is required before the module can be utilised The Capacity Management feature requires set up for each of the Allocations Screen Tabs where ...

    • Yard Management Live **PAID FEATURE**. ( Yard Tracker URL )

      Yard Tracker Overview In Freight Tracker, we’ve connected yard movements performed by forklift drivers directly into the Freight Tracker admin system. This allows forklift drivers and allocators to work together using live, real-time data, helping ...

    • POD with invoice

      Overview FreightTracker can automatically send a POD with the invoice for any job in the system. This is setup at a customer level in the Customer screen. The default setting for the POD with Invoice is Yes. Turning on or off the POD with the Invoice ...

    • Customer Notes - Process and email configuration

      Overview This FAQ explains the customer note email notification process. Receiving a note from the portal.... 1. When a customer enters a note into the customer portal, the customer note icon in the job will turn Blue.  2. To send an email to the ...

    • Disable a user from allocating a job without a driver

      New parameter that disables a user from changing the status of a leg unless a driver has been allocated Settings → Parameters → General → Status_Update_Driver_required. When turned on effects all modules minus warehouse.