# Opening/closing Hours 1 to 10 ### Opening/closing Hours These constraints let you specify the time window during which a visit can take place.\ **Opening time 1** indicates the earliest time the visit can start, and **Closing time 1** indicates the latest time it can begin. This time window applies to all days unless **Opening days 1** is defined; in that case, the time window applies only to those specified days. If no time window is defined for a visit, it can be performed at any time on the allowed Opening days and within the resource’s working hours. You can configure up to four different time windows (each with their own associated days) for a single visit. **Format:** HH:MM:SS **Example 1:**\ Opening time 1 = 07:30:00 and Closing time 1 = 11:30:00 create a four-hour time window during which the customer can be visited. **Example 2:**\ For a customer requiring delivery between 11:00 p.m. and 03:00 a.m., the times must be shifted so they fall within the same day. This allows the visit order to be correctly determined.\ For example:\ Opening time 1 = 19:00:00 and Closing time 1 = 23:00:00 define a four-hour window.\ After optimization, the planned visit times must be shifted back to the original time range.\ If TourSolver schedules the visit at 09:00 p.m., the actual visit will occur at 01:00 a.m. (= 23:00:00 + 2 hours). Time windows that extend across multiple days are not supported. For example, a time window from 23:00:00 to 03:00:00 cannot be used without adjusting the times. A visit cannot begin before the Opening time. By default, a visit that starts within the time window may continue past the Closing time. If you want the visit to end before the Closing time, enable the **End visit before closing time** option. ### Opening/closing Hours 2 to 10 **Opening and Closing Hours 2** These constraints allow you to define a second time window that applies to the visit days specified in **Possible visit days 2**.\ **Opening time 2** indicates the earliest time a visit can begin, while **Closing time 2** specifies the latest time it can start. **Format:** HH:MM:SS **Example 1:**\ A customer is available for delivery during two separate periods: * Morning: 09:00 a.m. to 12:00 p.m. * Afternoon: 02:00 p.m. to 05:00 p.m. **To configure this, set**: * Opening time 1 = 09:00:00 * Closing time 1 = 12:00:00 * Opening time 2 = 14:00:00 * Closing time 2 = 17:00:00 **Example 2:**\ A customer can be visited on: * Monday from 07:00 a.m. to 05:00 p.m. * Wednesday from 09:00 a.m. to 06:00 p.m. **The configuration would be:** * Opening time 1 = 07:00:00 * Closing time 1 = 17:00:00 * Opening days 1 = 1 (Monday) * Opening time 2 = 09:00:00 * Closing time 2 = 18:00:00 * Opening days 2 = 3 (Wednesday) **Opening and Closing Hours 3** These constraints allow you to set a third time window that applies to the visit days specified in **Possible visit days 3**.\ **Opening time 3** indicates when the visit can begin, and **Closing time 3** indicates the latest time the visit can start. **Format:** HH:MM:SS **Opening and Closing Hours 4** These constraints allow you to define a second time slot that will apply to visit days defined under \ Possible visit days 4. Opening time 4 corresponds to the time from which the visit can be performed. \ Closing time 4 corresponds to the time beyond which the visit can no longer be performed. \ **Format**: HH:MM:SS --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nomadia-docs.gitbook.io/products/solver-constraints/my-deliveries/availability/opening-closing-hours-1-to-10.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.