> 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/connect-apps.md).

# Connect apps

fulfillmenttools offers multiple apps to help you manage your store operations. Our main app is the [Store Operations app](https://docs.fulfillmenttools.com/documentation/apps/store-operations-app.md).

The fulfillmenttools app portfolio comprises a range of apps tailored to different application areas and operating systems. The following apps are offered:

* [Store Operations Android app](https://play.google.com/store/apps/details?id=com.fulfillmenttools.storeoperations)
* [Store Operations iOS app](https://apps.apple.com/us/app/store-operations/id6768547094)
* [Inventory Android app](https://play.google.com/store/apps/details?id=com.ocfulfillment.inventoryapp\&gl=DE)
* [Returns Android app](https://play.google.com/store/apps/details?id=com.ocfulfillment.multiplatform.app\&gl=DE)
* [Returns iOS app](https://apps.apple.com/us/app/fulfillmenttools-returns/id6477875850)

A fulfillmenttools app can only work if it's connected to a tenant via the Backoffice. An app can only be connected to one tenant at a time.

## Connecting an app to the Backoffice

{% stepper %}
{% step %}
**Download and open the app**

Download the app from the App Store or Google Play Store and open the app.
{% endstep %}

{% step %}
**Grant camera access**

Tap **Allow camera access** to enable your camera for the app. You can only access the app when camera access is active.

This will open the camera in the app.

<div><figure><img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2FTp7B8kew47okz7BLXjuT%2FGrant%20camera%20access.png?alt=media&amp;token=622c9365-0517-416c-a7ec-8a4ac146446e" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2FP1sa86QqO3a1VNqiFXT1%2FCamera%20settings%20for%20using%20the%20app.png?alt=media&amp;token=a377de7e-2bab-48b7-8e5c-f90603a0ea21" alt="" width="188"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Open Backoffice to get the QR code**

Log in to Backoffice, select either view (if you have permissions to choose), and click **Apps and connections** in the page footer. This will show you a QR code that lets you pair your phone app with your tenant.

<figure><img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2FxyjEyDp7QrlsWAz8FdMZ%2FClick%20apps%20and%20connections.png?alt=media&amp;token=066892e4-d0b2-4e67-98f4-0b77ddfdb3b4" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Scan the QR code**

Use the app on your phone to scan the QR code displayed in Backoffice.

<figure><img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2FgxALl6buADT5rShYbm6T%2FScan%20the%20QR%20code.png?alt=media&amp;token=e222ca35-76d4-46a7-aa19-d5bca2051341" alt="" width="188"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Log in**

After scanning the QR code, the app connects to the tenant and redirects you to the login screen. Input your credentials and tap **Log in**.

<figure><img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2FARRde2o8rk7Ue643LJ4A%2FInput%20your%20credentials.png?alt=media&amp;token=d54758c7-c81e-43c7-a616-30a7fab892d9" alt="" width="188"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

Using an outdated app version shows a screen that alerts you to a version mismatch and prompts an update.

## Connect Android devices via MDM

{% hint style="info" %}
This is only possible when using version 38 of the Store Operations app Android.
{% endhint %}

Instead of scanning the tenant's QR code on each device, your MDM can automatically connect Android devices to your tenant. The Store Operations app reads the tenant's QR code from its **managed configuration** (Android Enterprise) when it starts and connects to the tenant before the login screen is shown.

{% hint style="success" %}

### Prerequisites

* The devices are enrolled in your MDM via Android Enterprise (fully managed device or work profile). On devices with a work profile, only the app inside the work profile receives the configuration.
* The Store Operations app (`com.fulfillmenttools.storeoperations`) is deployed via managed Google Play or via your MDM, version **38** or later.
* The text of your tenant's connection QR code, shown in Backoffice under **Settings**, then **Connect apps** (for example, read with any QR code reader). It starts with `fulfillmenttools://marryTenant?`.
  {% endhint %}

### Configuration

| Key            | Title in the MDM | Type   | Value                               |
| -------------- | ---------------- | ------ | ----------------------------------- |
| `tenantQrCode` | Tenant QR code   | String | Full text of the connection QR code |

Leading and trailing whitespace is ignored. A non-string value is treated as an invalid configuration.

### Setup

1. In your MDM, add the Store Operations app.
2. Open the app's **managed configuration** (also called **app configuration** or **app config policy**). With managed Google Play, the **Tenant QR code** field is shown automatically. If the APK is distributed by your MDM, add the key `tenantQrCode` with type `string` manually.
3. Set the value to the full text of the connection QR code.
4. Assign the app and its configuration to your devices.

If your MDM accepts the managed configuration as JSON (for example, the Android Management API):

```json
"managedConfiguration": {
  "tenantQrCode": "fulfillmenttools://marryTenant?..."
}
```

{% hint style="info" %}
The configuration is applied only when the app starts. Changes in your MDM can take a few minutes to reach the device. To apply a new or changed configuration on a device where the app is already running, close the app completely or restart the device.
{% endhint %}

### Behavior

| Situation                                                                           | Result on the next app start                                                                                 |
| ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| The device isn't connected yet, and the configuration is valid                      | The device is connected automatically, and the app opens on the login screen.                                |
| The device isn't connected yet, and the configuration is invalid                    | The QR code scan screen is shown with a message that the configuration is invalid.                           |
| The device is already connected with the same QR code                               | No change. Users stay logged in.                                                                             |
| The device was connected to the same tenant with an app version without MDM support | The connection is taken over by the MDM. Users stay logged in.                                               |
| The device is already connected, and the configuration is invalid                   | No change. Users stay logged in.                                                                             |
| The configuration contains a different QR code or points to a different tenant      | The user is logged out, local app data is reset, and the device connects to the tenant in the configuration. |
| The configuration is removed                                                        | No change. The device stays connected.                                                                       |

### Disconnect devices

To disconnect devices that were connected via MDM, set the **Tenant QR code** value to empty. On the next app start, the user is logged out, local app data is reset, and the QR code scan screen is shown.

To verify the change, open the app on a device and confirm it shows the QR code scan screen.

{% hint style="warning" %}
Removing or unassigning the configuration doesn't disconnect devices. This keeps devices connected when a configuration is removed unintentionally, for example, by changing group or policy assignments in your MDM. Devices that were connected by scanning the QR code aren't disconnected by an empty value either. This also applies to devices that were connected by scanning the same QR code before the configuration was assigned.
{% endhint %}


---

# 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.fulfillmenttools.com/documentation/apps/connect-apps.md?ask=<question>&goal=<user_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.
