> 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/close-lane.md). # Close Lane Ends the current self-checkout session and marks the lane as unavailable for new customers. This function is typically used by staff when the station needs maintenance, restocking, or temporary shutdown. {% hint style="info" %} Close Lane requires Verifone Commander 57.00.00 and higher release version. {% endhint %}

Field/Button	Description
Message	Text displayed to customers on the self-checkout screen, typically used for instructions or alerts.
Lane Closed	It indicates that the self-checkout station is unavailable for use and is not accepting new customers.
Message Color	Sets the color of the on-screen text to ensure visibility and match store branding.
Background Color	Defines the color behind the message, helping important notices stand out.
Store Logo	The store’s brand image shown on the self-checkout interface for consistent customer experience.

--- # 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/close-lane.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.