Understanding Time in Transit (TNT) Retry Policy [Information]

Time in Transit (TNT) determines the best fulfillment route for an order by checking carrier transit times. To do so, all configured fulfillment channels must respond successfully; otherwise, the order fails.

RETRY TRIGGER CONDITIONS

techOMS uses a retry policy triggered by the following error conditions:

• Can't get data from techSHIP

• techSHIP timeout

• Connect Timeout expired, all pooled connections are in use

SCOPE

The retry policy applies only to enabled and active fulfillment channels for the order.

A retry attempt is considered successful if each location receives data from at least one available carrier.

NOTE: Disabled fulfillment channels are skipped. If some carriers return valid data and others return an error unrelated to connection issues (e.g., an invalid zip code error), techOMS will use the successful carrier/service data for each location. 

RETRY POLICY

Once triggered, the retry policy works as follows:

• Retry Attempts: techOMS attempts to retrieve TNT data up to 4 more times.

• Retry Scope: Each retry attempt includes all configured fulfillment channels for the order.

  
  

  NOTE: techOMS does not retry individual failed locations; instead, it reattempts the full TNT request.  

  
  

• Retry Interval: Retry attempts occur at increasing intervals: 5 seconds, 30 seconds, 60 seconds (1 minute), 180 seconds (3 minutes).

• Failure Condition: If, after 5 attempts (including the initial one), techOMS still cannot retrieve TNT data, the entire order is marked as failed.

• Error Logging: If the failure condition is reached, an exception is raised, and the order requires manual intervention. You can review execution and retry details in the sales order log.

If a retry attempt is successful, order processing continues as normal.