> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/store-operations/blue-laws.md).
# Blue Laws
Blue Laws prohibit the sale of certain items during specific days and times. Blue Laws are dependent upon local government laws/regulations. Up to two blue laws can be configured.
### **Adding a Blue Law**
{% stepper %}
{% step %}
**Select Blue Law**
Select the Blue law from the drop-down list in the top left corner.
{% endstep %}
{% step %}
**Select Days**
Select the days of the week the blue law applies.
{% endstep %}
{% step %}
**Start and End Times**
Enter in the start and end times for the blue law. Times are entered based on military time. There are two start and end times that can be used in the event the blue law starts at midnight and ends in the morning, but then starts again in the afternoon. \
Values can be copied to different days of the week by selecting the three dots to the right of the End 2 time. The change applies to the selected day of the week immediately upon selection.
{% endstep %}
{% step %}
**Assigned**
Blue Laws can be assigned to Departments and PLUs after they are created.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/store-operations/blue-laws.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
