> For the complete documentation index, see [llms.txt](https://docs.fulfillmenttools.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fulfillmenttools.com/documentation/apps/store-operations-app.md).
# Store Operations app
The Store Operations app supports operational processes necessary for order fulfillment, including picking, packing, printing shipping labels, and handover to the shipping provider. It's available as a web-based application and for Android devices.
To set up the app on your device, follow the steps in the [Connect apps article](/documentation/apps/connect-apps.md).
More information on the hardware requirements can be found in the [technical requirements article](/documentation/apps/technical-requirements.md).
## L**og in**
The login screen displays the available authentication options for the tenant. If SSO providers are configured, they appear alongside the username option. Selecting an SSO option redirects to the provider's login page, where any authentication errors are handled. If SSO isn't configured, only the username and password fields are shown. Incorrect credentials trigger an inline error message.
After a successful login, the facility selection screen is displayed. Available facilities can be searched and filtered. After a facility is selected and confirmed, the app requests permission to send notifications. Once this step is completed, the app opens the home screen.
{% hint style="danger" %}
#### Important: The application must not be re-signed
Re-signing changes the application's certificate fingerprint (SHA-1/SHA-256), which is used for SSO authentication. As a result, SSO login may fail with errors such as `INVALID_CERT_HASH`.
Always deploy the original APK signed with the approved certificate.
If the app is re-signed by an MDM, wrapping solution, or deployment process, SSO functionality can't be guaranteed.
{% endhint %}
## Home
The home screen is the first screen displayed after logging in or reopening the app. It provides a central overview of operational progress within a facility. It gives you an immediate picture of what needs attention and how work is progressing, both at the personal and facility levels. The screen is accessible at any time via the **Home** tab in the bottom navigation.
### **Urgent and overdue tasks**
If tasks are approaching their deadline, an urgent tasks banner is displayed at the top of the screen. If tasks have already passed their deadline, an overdue tasks banner is shown. Both can appear simultaneously. Selecting a banner navigates directly to the relevant tasks.
### **Facility tasks**
The facility tasks section shows the total number of open tasks across the facility, broken down by type: Picking, Packing, and Handover. This gives managers and team leads a quick overview of where workload is concentrated.
### **Task versus order view**
The home screen can be configured to display either task-based or order-based metrics. This is controlled via the remote configuration `HOME_COMPLETED_AS_TASKS` (see the [Remote configuration article](/documentation/by-pillar/store-operations/remote-configuration.md)).
Task-based metrics are suited for facilities where employees work on a single step, such as picking only. In this case, tracking individual tasks provides meaningful feedback. Order-based metrics are suited for employees who process orders end-to-end, from picking through to handover. Counting completed orders reflects their work more accurately than counting individual tasks.
### **Your tasks (orders)**
This section shows the completed tasks or orders of the logged-in user over the last 5 days. A bar chart displays the daily completion trend.
### **Completed facility tasks (orders)**
When anonymization is configured by the tenant, individual user performance is not tracked. In this case, the **Your tasks** section is replaced by a facility-wide view showing the total number of completed tasks or orders over the last 5 days.
Order-based home view
Task-based home view
Overdue task home view
## Settings
Settings are accessible via the user avatar in the top right corner of the home screen. The screen displays the user's name and currently selected facility.
### **Notifications**
{% columns %}
{% column %}
Push notifications for new tasks can be enabled or disabled using the toggle.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### **Language**
{% columns %}
{% column %}
The currently active language is shown next to the menu item. Selecting it opens a list of available languages. The change takes effect immediately after saving.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### **Change facility**
{% columns %}
{% column %}
Select the **Change facility** option to switch to a different facility, then select the desired facility. This option is displayed only if more than one facility is available to the user.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### **Change password**
{% columns %}
{% column %}
Users logged in with a username can update their password here. The current password is required, and the new password must be at least 6 characters long. This option is not available for users authenticated via SSO.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### **About the app**
{% columns %}
{% column %}
Technical information about the app, including the app version, project, build, device ID, and username. Any of these values can be copied to the clipboard by long-pressing on the value. Links to the Imprint and Privacy Policy are also available.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### **Log out**
{% columns %}
{% column %}
Selecting **Log out** ends the current session and returns to the login screen.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
## Bottom bar
Use the bottom bar to navigate through the different areas of the app.
---
# 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://docs.fulfillmenttools.com/documentation/apps/store-operations-app.md?ask=&goal=
```
`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.