> For the complete documentation index, see [llms.txt](https://features.revver.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.revver.tech/features/2.-pos-features/2.7-shift-management.md).

# 2.7 Shift Management

## Shift Start & End

Shift start and end can be done by users on POS by providing user ID & PIN. This would immediately create active shifts which can then be used to operate the POS.

#### Credentials

Cashier credentials have to be reset the first time being used on the POS. Credentials include a user ID and PIN which can be restet by the cashier's manager if needed.

#### Cash Declarations

Cashier must declare the cash as well as any tracked products while signing on and off the POS shift. This will be used to calculate theorotical balance & used in cash balancing.

Cashier will also have to assign respective cash drawers being used.

#### Shift End Report

revver POS provides a detailed shift end report on completion of a shift which can be used for reconciliation and balancing.

#### Lock & Pause Shift

revver POS provides feature to lock as well as pause a shift if the cashier is on a break or away. This is a very useful function ffor stations with multiple cashiers.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://features.revver.tech/features/2.-pos-features/2.7-shift-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.