Capacity Constraint section showing constraint row with name, unit, and controls
### Step 4: Define Constraint Details
**Constraint Name:**
* Must be unique across your organization
* Use lowercase letters, numbers, and underscores only
* Cannot contain spaces or uppercase letters
* Cannot use reserved keywords: `name`, `address`, `coordinate`, `timeWindow`, `timewindows`, `visitTime`, `visittime`, `tags`, `assignee`, `workingTime`, `workingtime`, `multiday`, `speed`, `fixedCost`, `fixedcost`
**Examples of valid names:**
* `weight`
* `volume`
* `item_count`
* `pallet_quantity`
* `cold_storage_volume`
**Denominator (Unit):**
* Specify the unit of measurement for this constraint
* Can be any string (e.g., `kg`, `m3`, `pcs`, `pallets`, `liters`)
### Step 5: Save the Constraint
The constraint is automatically saved when you complete both fields (name and unit).
## Managing Capacity Constraints
### Activating Constraints for a Hub
Each hub can choose which capacity constraints to use:
1. In the Capacity Constraint section, you'll see a checkbox next to each constraint
2. **Check the box** to activate the constraint for the current hub
3. **Uncheck the box** to deactivate the constraint
**Important Notes:**
* You can have up to 10 active capacity constraints per hub
* Inactive constraints won't be considered during route optimization
* Constraint definitions remain available across all hubs even if not activated
### Editing Constraint Details
To modify an existing constraint:
1. Click on the **name** or **unit** field
2. Update the value
3. Click outside the field to save changes automatically
**Validation Rules:**
* Constraint names must remain unique
* Cannot use reserved keywords
* Cannot use uppercase letters in constraint names
### Deleting Constraints
To remove a capacity constraint:
1. Click the **trash icon** next to the constraint you want to delete
2. Confirm the deletion in the modal dialog
3. The constraint will be removed from your organization
**Important Restrictions:**
* Cannot delete all constraints - at least one must remain active
* Deleting a constraint will remove it from all vehicles and visits that use it
* This action cannot be undone
## Using Capacity Constraints in Optimization
### In Vehicle Configuration
When creating or editing a vehicle:
1. Navigate to **Route Optimization** → **Vehicle**
2. In the vehicle form, you'll see input fields for each active capacity constraint
3. Enter the maximum capacity for each constraint (e.g., weight: 1000)
4. Leave blank if the vehicle has no limit for that constraint
### In Visit/Task Data
When creating visits or tasks:
1. Navigate to **Route Optimization** → **Visit**
2. In the visit form or bulk upload, you'll see fields for each active capacity constraint
3. Enter the demand/requirement for each constraint (e.g., weight: 50)
4. The optimization engine will sum these values per vehicle
### During Optimization
When you run route optimization:
1. The engine calculates the total demand for each constraint per route
2. Ensures no vehicle exceeds its capacity limits
3. May leave some visits unassigned if capacity constraints cannot be satisfied
4. Displays capacity utilization in the optimization results
## Capacity Constraint Limits
You can define **up to 10 capacity constraints** per organization. This is a hard limit enforced at the organization level across all subscription plans.
## Best Practices
### Naming Conventions
**Use Descriptive Names:**
* ✅ `weight_kg` - Clear and specific
* ✅ `volume_m3` - Includes unit in name
* ✅ `pallet_count` - Easy to understand
* ❌ `w` - Too vague
* ❌ `constraint1` - Not descriptive
**Use Consistent Formatting:**
* Use underscores to separate words: `item_count`
* Keep names short but meaningful: `cold_storage` instead of `cold_storage_temperature_controlled_volume`
* Use industry-standard terminology
### Constraint Strategy
**Start Simple:**
Begin with the most critical constraint (usually weight or volume), then add more as needed.
**Combine Related Constraints:**
If you have multiple related dimensions, consider combining them:
* Instead of: `length`, `width`, `height`
* Use: `volume_m3` (calculate volume before creating visit)
**Test Thoroughly:**
After defining constraints, test with a small set of vehicles and visits to ensure:
* Capacity limits are realistic
* Units are consistent between vehicles and visits
* Optimization produces feasible routes
### Common Use Cases
**Delivery Operations:**
```
weight (kg) - Total weight capacity
volume (m3) - Cargo space volume
item_count (pcs) - Number of items
```
**Food Delivery:**
```
hot_food (bags) - Hot food capacity
cold_food (bags) - Cold food capacity
beverage (cups) - Beverage carrier capacity
```
**Pharmaceutical Distribution:**
```
cold_chain (liters) - Refrigerated storage
ambient (boxes) - Room temperature storage
controlled (units) - Controlled substance limit
```
**Furniture Delivery:**
```
weight (kg) - Weight capacity
volume (m3) - Cargo volume
large_items (pcs) - Special handling items
```
## Dynamic Visit Time Integration
Capacity constraints can be integrated with Dynamic Visit Time to automatically adjust service time based on capacity:
1. Navigate to **Dynamic Visit Time** configuration
2. Select a capacity constraint as the basis for time calculation
3. Define the time multiplier (e.g., 2 minutes per unit)
4. The system will automatically calculate visit duration based on constraint values
Read more about Dynamic Visit Time [here](/pages/route-optimization/configuration/dynamic-visit-time).
## Troubleshooting
### Cannot Add New Constraint
**Problem**: The "+" button is disabled or shows an error.
**Possible Causes:**
* You've reached the maximum of 10 constraints
* The last constraint row is incomplete (missing name or unit)
* You don't have "Edit Constraint" permission
**Solution:**
* Complete or delete the last constraint before adding a new one
* Contact your organization administrator for permission access
* Delete unused constraints to make room for new ones
### Constraint Name Rejected
**Problem**: Error message when entering constraint name.
**Common Issues:**
1. **"Constraint name already exists"**
* Each constraint name must be unique
* Check for similar names with different formatting
2. **"Constraint name contains reserved keyword"**
* Cannot use system reserved words
* Choose a different name that doesn't conflict
3. **"Constraint name contains uppercase letters"**
* Use only lowercase letters
* Replace spaces with underscores
4. **"Constraint name must use alphanumeric and underscore only"**
* Remove special characters (-, @, #, etc.)
* Use only: a-z, 0-9, \_ (underscore)
### Optimization Fails with Capacity Constraints
**Problem**: Route optimization fails or produces unexpected results.
**Possible Causes:**
* Vehicle capacities are too small for visit demands
* Constraint values are inconsistent (different units)
* Some visits have missing capacity data
**Solution:**
1. Review vehicle capacity settings - ensure they're realistic
2. Verify all visits have capacity values defined
3. Check that units are consistent (don't mix kg and grams)
4. Try optimization with fewer active constraints to isolate the issue
### Constraint Not Showing in Vehicle/Visit Forms
**Problem**: Newly created constraint doesn't appear in vehicle or visit forms.
**Solution:**
1. Ensure the constraint is activated (checkbox is checked) for the current hub
2. Refresh the page to load the latest constraint configuration
3. Verify you're in the correct hub where the constraint is active
## Related Documentation
* [Route Optimization Configuration Introduction](/pages/route-optimization/configuration/introduction)
* [Dynamic Visit Time](/pages/route-optimization/configuration/dynamic-visit-time)
* [Vehicle Management](/pages/route-optimization/vehicle/introduction)
* [Visit Management](/pages/route-optimization/visit/introduction)
## Frequently Asked Questions
**Q: Can I change a constraint name after creating it?**
A: Yes, you can edit the constraint name at any time. However, if the constraint is already used in vehicles or visits, updating the name won't automatically update historical data. It's recommended to plan constraint names carefully before widespread use.
**Q: What happens to vehicle and visit data if I delete a constraint?**
A: When you delete a constraint, it will be removed from all vehicles and visits that reference it. Historical optimization results may still show the old constraint values, but new optimizations won't consider the deleted constraint.
**Q: Can I have different capacity constraints for different hubs?**
A: Capacity constraints are defined at the organization level, meaning all hubs see the same constraint definitions. However, each hub can independently activate or deactivate which constraints to use. This allows flexibility while maintaining consistency across your organization.
**Q: How does the optimization engine handle vehicles with no capacity limit?**
A: If a vehicle has no value (blank) for a capacity constraint, the optimization engine treats it as unlimited capacity for that specific constraint. The vehicle can carry any amount for that dimension.
**Q: Can capacity constraints be negative?**
A: No, capacity constraints must be positive numbers. Negative values don't make logical sense in the context of capacity limitations.
**Q: What happens if visit demand exceeds all available vehicle capacity?**
A: The optimization engine will flag these visits as "dropped" in the results. You can resolve this by:
* Adding more vehicles with sufficient capacity
* Enabling auto-split configuration to automatically divide large visits
* Adjusting vehicle capacity limits
**Q: Can I use decimal values for capacity constraints?**
A: Yes, you can use decimal values (e.g., 2.5 kg, 1.75 m3) for both vehicle capacity and visit demand. The system supports fractional values for precise capacity management.
**Q: Is there a limit to how many vehicles or visits can use a single constraint?**
A: No, there's no limit. Once a capacity constraint is defined and activated, it can be used by unlimited number of vehicles and visits within that hub.
