You can now configure ETA rules per destination area within the same carrier service or product.

Previously, operational rules such as pickup schedules, transport days, and delivery days were defined once per service and applied to all destinations. This update allows you to define different rules depending on where the shipment is going, making ETA calculations more accurate and aligned with real carrier operations.
 

How it works

ETA-related rules can now be defined at multiple levels. When multiple rules exist, the system applies them in the following order of priority:

Destination (To) → Origin (From) → Product → TransitTime (default)

This means that destination-specific rules will override more general configurations.
 

What you can configure

You can now define the following per destination area:

• Pickup schedules (including cutoff times)
• Transport days
• Delivery days
• Initiation days

If no destination-specific rule is provided, the system will fall back to the default configuration.
 

Example

Below is a simplified example showing how different delivery rules can be applied depending on destination:

<TransitTime name="CarrierX" trigger="submit"
            transportdays="1,2,3,4,5" deliverydays="1,2,3,4,5">

  <Products>
    <Product id="CARRIERX_STD" name="CarrierX Standard"/>
  </Products>

  <TimeTable>
    <From area="ORIGIN">

      <!-- Metro: allows Saturday delivery -->
      <To area="METRO" days="2" deliverydays="1,2,3,4,5,6"/>

      <!-- Rural: weekday delivery only -->
      <To area="RURAL" days="3" deliverydays="1,2,3,4,5"/>

    </From>
  </TimeTable>
</TransitTime>

In this example:

• Shipments to METRO areas can be delivered Monday–Saturday
• Shipments to RURAL areas are delivered Monday–Friday only

Notes

• Avoid overlapping or conflicting area definitions to ensure predictable results
• Destination rules take precedence over origin and product-level rules
• This update removes the need to duplicate services or products for different destination behaviors