{"id":8511,"date":"2019-03-25T12:17:40","date_gmt":"2019-03-25T12:17:40","guid":{"rendered":"https:\/\/support.loginextsolutions.com\/?p=8511"},"modified":"2026-02-24T05:02:11","modified_gmt":"2026-02-24T05:02:11","slug":"eta-properties","status":"publish","type":"post","link":"https:\/\/support.loginextsolutions.com\/index.php\/2019\/03\/25\/eta-properties\/","title":{"rendered":"ETA Profile"},"content":{"rendered":"\n\n\n\t<div class=\"dkpdf-button-container\" style=\" text-align:left \">\n\n\t\t<a class=\"dkpdf-button\" href=\"\/index.php\/wp-json\/wp\/v2\/posts\/8511?pdf=8511\" target=\"_blank\"><span class=\"dkpdf-button-icon\"><i class=\"fa fa-file-pdf-o\"><\/i><\/span> Download PDF<\/a>\n\n\t<\/div>\n\n\n\n\n\n\n<p>ETA Profile lets you configure the various aspects of order ETA calculations and revisions. It includes <strong>ETA Components<\/strong>, which define the factors used to calculate ETAs, and the <strong>ETA Revision Agent<\/strong>, which manages how and when ETAs are recalculated based on real-time updates.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><b>ETA Components&nbsp;<\/b><\/h4>\n\n\n\n<p>ETAs are calculated when an order is assigned to a delivery associate. ETA calculation considers loading time at the branch, transit time (including the impact of traffic, road closures, and weather) from the branch to the order location, as well as the service time required to fulfill the order.<\/p>\n\n\n\n<p>To define the parameters to calculate ETAs as per your requirements, follow the steps below:<\/p>\n\n\n\n<ol>\n<li>Click the Settings icon.<\/li>\n\n\n\n<li>From the drop-down menu, select ETA Profile.<br><img decoding=\"async\" style=\"width: 300px;\" src=\"https:\/\/lh7-rt.googleusercontent.com\/docsz\/AD_4nXd0PwDlFXpkJg7wQfft909SuFisTYGqdnRk4HLjO72PqZwABdzl_tB6DXVqyIJdEbfShqFqPoLqKJppZi70I0snfN1tsW-A4gLPXYKKkIUrJDYJlV6yJvPExIBWJW-W-nvWdfhzFA?key=wuiRk-u64D_GG3l90AVdmg\"><\/li>\n\n\n\n<li>The ETA Components page will open. Here, define the following parameters to calculate ETAs as per your requirements:<br><img loading=\"lazy\" decoding=\"async\" width=\"2879\" height=\"1509\" class=\"wp-image-32107\" style=\"width: 850px;\" src=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.25\u202fPM.png\" alt=\"\" srcset=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.25\u202fPM.png 2879w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.25\u202fPM-300x157.png 300w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.25\u202fPM-1024x537.png 1024w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.25\u202fPM-768x403.png 768w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.25\u202fPM-1536x805.png 1536w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.25\u202fPM-2048x1073.png 2048w\" sizes=\"(max-width: 2879px) 100vw, 2879px\" \/>\n<ul>\n<li><b>Loading Time per Order (in seconds)<\/b>: Use this to define the average time taken (in seconds)&nbsp;to load each order in the vehicle\/bag at the branch.<br><\/li>\n\n\n\n<li><strong style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">Default Service Time per Order (in minutes)<\/strong><span style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">: Use this to define the default time (in minutes) spent at a customer&#8217;s location to fulfill each order. For example, if this is set to 5 and there are 5 orders to be delivered at a customer\u2019s location, 25 minutes will be considered. This default value will be used to calculate ETAs if the Order Service Time is not defined for orders at the time of creation.<\/span> <br><\/li>\n\n\n\n<li><b>Default Service Time at Customer&#8217;s Location (in minutes)<\/b>: Use this to define the default time (in minutes) spent at a customer&#8217;s location (regardless of the number of orders to be fulfilled). This represents aspects like parking time, security check time, etc. that are one-time activities to be done at a customer&#8217;s location, regardless of how many orders are being fulfilled there. For example, if this is set to 5 and there are 5 orders to be delivered at a customer&#8217;s location, 5 minutes will be considered. This default value will be used to calculate ETAs if the Address Service Time is not defined for a customer&#8217;s location.<br><strong>Example:<\/strong><br>Let&#8217;s consider that 2 orders are to be delivered at a customer&#8217;s location. Order Service Time (service time per order) and Address Service Time (service time at customer&#8217;s location) are not provided. Default Service Time per Order is 3 min and Default Service Time at Customer&#8217;s Location is 5 min. The total service time then comes to be 11 minutes.<br><strong>Note:<\/strong> The ETA calculation algorithm uses Service Time per Order only after the defined Start Time for an order, whereas it can use Service Time at Customer&#8217;s Location before the defined Start Time for an order as well. Let us understand it with the help of an example. If a delivery associate (who has to deliver one order) were to reach the customer&#8217;s location 15 min prior (4:45 PM) to Start Time (5:00 PM); Service Time per Order is 3 min and Service Time at Customer&#8217;s Location is 5 min. Then, the ETA calculation algorithm would calculate ETA as 5:03 PM.<br><\/li>\n\n\n\n<li><b>ETA Notification Window:&nbsp;<\/b>This will impact the ETA windows communicated to your customers through alerts, e.g., an order with the ETA of 2:38 PM will be shown as arriving between 2:00 PM and 3:00 PM if a 1-hour window is selected. The available values for this are 1, 2, 4 and 8 hours.<br><strong>ETA Window Calculation Logic:<\/strong><br>-If 1-hour window is selected:<br>Subtract 30 minutes from the order ETA and round off to the nearest half-hour window. This will be the start time.<br>Add 30 minutes to the order ETA and round off to the nearest half-hour window. This will be the end time.<br>-If 2-hour window is selected:<br>Subtract 60 minutes from the order ETA and round off to the nearest half-hour window. This will be the start time.<br>Add 60 minutes to the order ETA and round off to the nearest half-hour window. This will be the end time.<br>-If 4-hour window is selected:<br>Subtract 120 minutes from the order ETA and round off to the nearest half-hour window. This will be the start time.<br>Add 120 minutes to the order ETA and round off to the nearest half-hour window. This will be the end time.<br>-If 8-hour window is selected:<br>Subtract 240 minutes from the order ETA and round off to the nearest half-hour window. This will be the start time.<br>Add 240 minutes to the order ETA and round off to the nearest half-hour window. This will be the end time.<br><strong>Rounding Off Logic:<\/strong><br>Round down if the calculated time is less than or equal to the 15-minute mark in a half-hour window and round up if it is greater than the 15-minute mark.<br><strong>Example:<\/strong><br>Let&#8217;s say an ETA of 2:45 PM is to be communicated and 1-hour window is selected. Upon subtracting 30 minutes, we get 2:15 PM, which is at the 15-minute mark, hence the Start Time will be rounded down to 2:00 PM. Similarly, upon adding 30 minutes, we get 3:15 PM, which will be rounded down to 3:00 PM. Hence, the ETA window will be 2:00-3:00 PM.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Once you are satisfied with the required changes, click Save.<\/li>\n<\/ol>\n\n\n\n<h4 class=\"wp-block-heading\"><b>ETA Revision<\/b> Agent<\/h4>\n\n\n\n<p><span style=\"font-weight: 400;\">You can configure the events for the ETA Revision Agent<\/span><span style=\"font-weight: 400;\"> to dynamically revise the planned order ETAs to keep your customers and teams informed of on-ground variations in real-time.<\/span><\/p>\n\n\n\n<p>To select the events for ETA revision, follow the steps below:<\/p>\n\n\n\n<ol>\n<li>Click the Settings icon.<\/li>\n\n\n\n<li>From the drop-down menu, select ETA Profile.<br><img decoding=\"async\" style=\"width: 300px;\" src=\"https:\/\/lh7-rt.googleusercontent.com\/docsz\/AD_4nXd0PwDlFXpkJg7wQfft909SuFisTYGqdnRk4HLjO72PqZwABdzl_tB6DXVqyIJdEbfShqFqPoLqKJppZi70I0snfN1tsW-A4gLPXYKKkIUrJDYJlV6yJvPExIBWJW-W-nvWdfhzFA?key=wuiRk-u64D_GG3l90AVdmg\"><\/li>\n\n\n\n<li>In the left navigation panel, select ETA Revision Agent under the ETA profile module.<\/li>\n\n\n\n<li>In the ETA Revision section, you can specify the required events:<br><img loading=\"lazy\" decoding=\"async\" width=\"2880\" height=\"1516\" class=\"wp-image-32109\" style=\"width: 850px;\" src=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.18\u202fPM.png\" alt=\"\" srcset=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.18\u202fPM.png 2880w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.18\u202fPM-300x158.png 300w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.18\u202fPM-1024x539.png 1024w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.18\u202fPM-768x404.png 768w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.18\u202fPM-1536x809.png 1536w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-3.16.18\u202fPM-2048x1078.png 2048w\" sizes=\"(max-width: 2880px) 100vw, 2880px\" \/>\n<ul>\n<li><strong style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">Order Manually Assigned to the Trip:&nbsp;<\/strong><span style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">ETAs for the subsequent orders in a trip will be revised when a new order is manually assigned to the trip.<\/span><\/li>\n\n\n\n<li><b style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">Trip Start:&nbsp;<\/b><span style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">ETAs for all orders in a trip will be revised on trip start.<\/span> <\/li>\n\n\n\n<li><b>Order Checkout:&nbsp;&nbsp;<\/b>ETAs for the subsequent orders in a trip will be revised after each order fulfillment.<\/li>\n\n\n\n<li><b>Delivery Associate Resuming Duty After Break: <\/b>ETAs for the subsequent orders in a trip will be revised when the delivery associate resumes their duty after their break.<\/li>\n\n\n\n<li><strong style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">Duration-based ETA Revision:&nbsp;<\/strong><span style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">ETAs for the subsequent orders in an ongoing trip will be revised periodically on the basis of the frequency defined here. Use this preference if you have long trips that span hours or days. In the next field, ETA Revision Duration (in minutes), you can specify how often the ETAs should be revised, for example, every 10 minutes.<\/span> <\/li>\n\n\n\n<li><strong style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\">Order Cancelation:<\/strong><span style=\"color: initial; font-family: -apple-system, BlinkMacSystemFont, &quot;Segoe UI&quot;, Roboto, Oxygen-Sans, Ubuntu, Cantarell, &quot;Helvetica Neue&quot;, sans-serif;\"> ETAs for the subsequent orders in a trip will be revised when an order of the trip is canceled.<\/span> <br><strong>Note:<\/strong>\n<ul>\n<li><span style=\"font-weight: 400;\">You can also revise ETAs in accordance with your delivery associates\u2019 break time and hours of service regulations. If Hours of Service Regulations property is enabled in the Planning Profile, the ETA calculation algorithm also considers it in calculations. Similarly, if break timings are defined for delivery associates, the same will be considered in ETA calculations.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">For an End-to-End account, the following points are applicable:<\/span><br><span style=\"font-weight: 400;\">a) For an End-to-End order (an order with multiple milestones), these events will only revise the time windows for individual milestones. The ETA of an End-to-End order will only be affected by these events when the order is in its last mile. <\/span><br><span style=\"font-weight: 400;\">b) For First Mile and Last Mile order types, since there is only one milestone, the events configured here will revise the order ETA.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">To revise the ETA of an End-to-End order and time windows for all the middle milestones, you must configure the events in the \u2018ETA Revision of Orders\u2019 section.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">The ETA Revision of Orders section<\/span> <span style=\"font-weight: 400;\">lets you configure the events to dynamically revise the ETAs for End-to-End orders and the time windows for all subsequent milestones. These events are only applicable to End-to-End orders with multiple middle milestones. The ETA of an End-to-End order will be updated at each selected event, thereby enabling you to provide accurately updated ETAs to customers, enhancing transparency and trust in your delivery processes.<\/span> This section is only available in<span style=\"font-weight: 400;\"> an End-to-End account.<\/span><br><b>Note:<\/b><span style=\"font-weight: 400;\"> When fulfilling an End-to-End order, the order ETA will be updated at each specified event in the \u2018ETA Revision of Orders\u2019 section; however, once the order reaches its last mile, the ETA will be revised according to the events specified in the \u2018ETA Revision\u2019 section.<\/span><br><span style=\"font-weight: 400;\">Here, you can specify the required events from the following:<\/span><br><img loading=\"lazy\" decoding=\"async\" width=\"2210\" height=\"1382\" class=\"wp-image-32172\" style=\"width: 850px;\" src=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-24-at-10.27.55\u202fAM.png\" alt=\"\" srcset=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-24-at-10.27.55\u202fAM.png 2210w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-24-at-10.27.55\u202fAM-300x188.png 300w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-24-at-10.27.55\u202fAM-1024x640.png 1024w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-24-at-10.27.55\u202fAM-768x480.png 768w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-24-at-10.27.55\u202fAM-1536x961.png 1536w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-24-at-10.27.55\u202fAM-2048x1281.png 2048w\" sizes=\"(max-width: 2210px) 100vw, 2210px\" \/>\n<ul>\n<li><b>Trip Start: <\/b><span style=\"font-weight: 400;\">ETAs for all orders and the time windows for subsequent milestones in a trip will be revised on trip start.<\/span><br><\/li>\n\n\n\n<li><b>Milestone Checkout: <\/b><span style=\"font-weight: 400;\">ETAs for all orders and the time windows for subsequent milestones in a trip will be revised after each milestone fulfillment.<\/span><br><\/li>\n\n\n\n<li><b>Duration-based ETA Revision: <\/b><span style=\"font-weight: 400;\">ETAs for all orders and the time windows for subsequent milestones in an ongoing trip will be revised periodically on the basis of the frequency defined here. In the next field, ETA Revision Duration (in hours), you can specify how often the ETAs should be revised, for example, every 3 hours.<\/span><br><span style=\"font-weight: 400;\">Note that the ETA Revision Duration must be greater than or equal to 2 hrs.<\/span><br><\/li>\n\n\n\n<li><b>Milestone Attempted: <\/b><span style=\"font-weight: 400;\">ETAs for all orders and the time windows for subsequent milestones in a trip will be revised if a milestone of the trip is attempted.<\/span><br><span style=\"font-weight: 400;\">Note that for ETA calculation, if the milestone is marked as attempted, it is considered that the milestone will resume from the next serviceable day, taking the <a href=\"https:\/\/support.loginextsolutions.com\/#\/2020\/08\/04\/holiday-calendar\/\">Holiday Calendar<\/a> and serviceable days into account.<\/span><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Once you are satisfied with the required changes, click Save.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Download PDF ETA Profile lets you configure the various aspects of order ETA calculations and revisions. It includes ETA Components, which define the factors used to calculate ETAs, and the ETA Revision Agent, which manages how and when ETAs are &hellip; <a href=\"https:\/\/support.loginextsolutions.com\/index.php\/2019\/03\/25\/eta-properties\/\">Continued<\/a><\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[],"tags":[351,1460,1590,1591,1592,1593,1594,1595,1932,3010,3011,3014,3017,3018,3019,3020],"_links":{"self":[{"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/posts\/8511"}],"collection":[{"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/comments?post=8511"}],"version-history":[{"count":48,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/posts\/8511\/revisions"}],"predecessor-version":[{"id":32173,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/posts\/8511\/revisions\/32173"}],"wp:attachment":[{"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/media?parent=8511"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/categories?post=8511"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/tags?post=8511"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}