Skip to main content

​
Overview

Packages are organizational units that group related shipments and routes together. They enable you to segment operations by client, project, region, or any other logical grouping. Packages also control user access, ensuring team members only see relevant data.

​
Key Features

Logical Grouping

Organize shipments and routes by client, project, or region

Access Control

Restrict user access to specific packages

Route Organization

Assign routes to packages for filtered selection

Status Management

Activate or deactivate packages as needed

​
Viewing Packages

​
For Administrators

Admins see all packages in the system:
  • Complete package list in a sortable table
  • Package names in alphabetical order
  • Active/Inactive status for each package
  • Edit and status toggle controls
Packages List Admin

​
For Standard Users

Users see only their assigned packages:
  • Filtered to packages assigned by admin
  • Read-only view of package information
  • Used for filtering shipments and routes
  • No edit or create capabilities
Standard users are assigned to packages by administrators in the User Management section. Contact your admin to request access to additional packages.

​
Packages Table

ColumnDescription
NamePackage identifier/name
StatusActive/Inactive toggle with label
ActionsEdit button (admin only)

​
Search Functionality

Quickly find packages:
  • Search by package name
  • Real-time filtering as you type
  • Case-insensitive search

​
Adding a New Package (Admin Only)

1

Open the Add Dialog

Click the + Add Package button in the top-right corner.Add Package Button
2

Enter Package Name

Provide a clear, descriptive name for the package:
  • Required field
  • Use meaningful names that describe the grouping
  • Examples: “Client ABC Operations”, “Mumbai Region”, “Q1 2026 Project”
  • Keep names concise but descriptive
Use a consistent naming convention across packages. For example: “[Client Name] - [Region]” or “[Project Code] - [Description]”.
3

Set Initial Status

The package is automatically created as “Active”:
  • Active packages appear in dropdowns
  • Can be assigned to routes and shipments
  • Visible to assigned users
4

Submit the Package

Click Add Package (or similar submit button) to save:
  • Package name is validated
  • Success message appears
  • New package added to the table
  • Immediately available for use

​
Editing Package Details (Admin Only)

1

Locate the Package

Find the package using the search function or by browsing the table.
2

Click Edit Button

Click the pencil icon in the Actions column.Edit Package Icon
3

Modify Package Name

The edit dialog opens with the current name:
  • Update the package name as needed
  • Follow same naming conventions
  • Consider impact on users and routes
4

Save Changes

Click Update Package to save:
  • Changes are validated
  • Success message confirms update
  • Table refreshes immediately
  • All references update automatically
Renaming a package updates the name everywhere it’s referenced (shipments, routes, user assignments). No need to update references manually.

​
Managing Package Status

​
Active vs. Inactive Status

Active Packages:
  • Appear in all dropdown selections
  • Can be assigned to new routes
  • Can be assigned to new shipments
  • Visible to assigned users
  • Used for ongoing operations
Inactive Packages:
  • Hidden from most dropdowns
  • Cannot be assigned to new resources
  • Existing assignments remain unchanged
  • Still visible in Packages table
  • Used for archived/completed projects

​
Toggling Package Status

1

Locate the Status Toggle

Find the switch in the Status column for the package.
2

Click the Toggle Switch

Click to change status:
  • Switch to right + “Active” label = Active
  • Switch to left + “Inactive” label = Inactive
3

Confirm Change

The status updates immediately:
  • Success message appears
  • Dropdown lists update
  • Label changes to reflect new status
Deactivating a package doesn’t affect existing shipments or routes using that package. It only prevents new assignments.

​
Package Use Cases

​
By Client

Organize operations for different clients: 
Package: "ABC Corporation"
- Routes: All routes used for ABC Corp shipments
- Shipments: All ABC Corp deliveries
- Users: Account manager for ABC Corp
Benefits:
  • Client-specific reporting
  • Dedicated account management
  • Clear cost/revenue tracking per client

​
By Region

Group by geographical area: 
Package: "North Region"
- Routes: Delhi, Chandigarh, Amritsar, etc.
- Shipments: All northern deliveries
- Users: North region operations team
Benefits:
  • Regional performance analysis
  • Localized team management
  • Geographic efficiency tracking

​
By Project

Organize time-bound projects: 
Package: "Q1 2026 Infrastructure Project"
- Routes: Project-specific delivery routes
- Shipments: All project deliveries
- Users: Project logistics team
- Status: Active during project, Inactive after
Benefits:
  • Project cost tracking
  • Clear start and end boundaries
  • Historical project records

​
By Material Type

Group by cargo category: 
Package: "Hazardous Materials"
- Routes: Specialized routes with safety compliance
- Shipments: All hazmat shipments
- Users: Certified hazmat handlers
Benefits:
  • Compliance tracking
  • Specialized handling protocols
  • Safety reporting
Choose a package organization strategy that matches your business needs. You can use a combination of strategies (e.g., “[Client] - [Region]”).

​
Integration with Other Modules

​
Routes Integration

Routes can be assigned to packages:
  • Set during route creation or editing
  • Filters route dropdowns in shipment creation
  • “None” assignment = available to all
  • Package-specific routes for organized selection
1

In Routes Module

When adding/editing a route, select the package in the “Assign to Package” field.
2

In Shipments Module

When creating a shipment, select the package first. Only routes assigned to that package (or unassigned routes) will appear.

​
Shipments Integration

Shipments can be assigned to packages:
  • Optional during shipment creation
  • Groups related shipments together
  • Filters shipments for standard users
  • Enables package-level analytics

​
User Management Integration

Users can be assigned to packages:
  • Admin assigns packages to user accounts
  • Users see only shipments in their packages
  • Controls data access and visibility
  • Manages what routes users can select
  1. Navigate to User Management
  2. Edit user profile
  3. Select packages to assign
  4. Save changes
  5. User now has access to those packages
  • User logs in
  • Dashboard shows data from assigned packages only
  • Shipments filtered to assigned packages
  • Routes filtered to assigned packages
  • No visibility into other packages

​
Dashboard Integration

  • Standard users see package-filtered analytics
  • Admins can view all packages or filter by package
  • Revenue/cost calculated per package
  • Shipment counts per package

​
Common Workflows

​
Setting Up a New Client Package

1

Create the Package

Add a new package with the client’s name or project code.
2

Define Routes

Create or assign existing routes to the new package in the Routes module.
3

Assign Users

In User Management, assign relevant team members to the package.
4

Create Shipments

Start creating shipments assigned to this package.
5

Monitor Performance

Track package-specific metrics in the Dashboard.

​
Closing a Completed Project Package

1

Complete All Shipments

Ensure all shipments for the project are delivered and updated.
2

Generate Final Reports

Export or document final analytics and financials.
3

Deactivate Package

Toggle the package status to “Inactive”.
4

Archive Documentation

Save external records and documentation.
5

Unassign Users (Optional)

Remove package assignment from users in User Management.
Keep completed packages in the system as “Inactive” rather than deleting. This preserves historical data and shipment records.

​
Restructuring Package Organization

1

Analyze Current Structure

Review how packages are currently organized and identify issues.
2

Plan New Structure

Design improved package organization (document before implementing).
3

Create New Packages

Add new packages with updated naming scheme.
4

Reassign Routes

Update route assignments to new packages.
5

Update User Assignments

Assign users to new packages in User Management.
6

Migrate Shipments (If Needed)

Edit existing shipments to reassign to new packages if required.
7

Deactivate Old Packages

Toggle old packages to inactive status.

​
Best Practices

  • Use a standardized naming format
  • Avoid abbreviations that aren’t obvious
  • Include enough context to understand the package at a glance
  • Example: “ABC Corp - Mumbai” not “ABCM”
  • More packages = more complexity
  • Start with broad categories
  • Subdivide only when necessary
  • Aim for balance between organization and simplicity
  • Never delete packages with historical data
  • Inactive packages preserve shipment history
  • You can always reactivate if needed
  • Keeps reporting and analytics intact
  • Quarterly review of user assignments
  • Remove access when team members change roles
  • Add access proactively for new responsibilities
  • Audit active packages for relevance
  • Keep external documentation of what each package represents
  • Note start/end dates for project packages
  • Record client agreements or contracts associated
  • Maintain contact information for package owners

​
Mobile Responsiveness

The Packages interface works on all devices:
  • Desktop: Full table with all columns and controls
  • Tablet: Optimized layout with all essential features
  • Mobile: Streamlined view with touch-optimized toggles and buttons

​
Troubleshooting

​
Package Not Appearing in Dropdown?

1

Check Active Status

Ensure the package status toggle is set to “Active” (switched to right).
2

Verify It Was Created

Confirm the package appears in the Packages list.
3

Refresh the Page

Sometimes a browser refresh is needed to update dropdowns.

​
User Can’t See Package?

  • Verify the user has the package assigned in User Management
  • Confirm the package status is “Active”
  • Check that the user has the correct role (not just admin)
  • Ask user to log out and log back in to refresh permissions

​
Routes Not Filtering by Package?

  • Ensure routes are actually assigned to the package in Routes module
  • Verify you’re selecting the package in the shipment form first
  • Check that both package and routes are active
  • Try selecting “None” for package to see all routes

​
Next Steps

Build docs developers (and LLMs) love

Get started for freeTalk to us