> 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/technical-requirements/zebra-hardware-scanner-configuration.md).
# Zebra hardware scanner configuration
{% hint style="success" %}
#### Prerequisites
* Zebra hardware scanner
* Android device meeting the [Technical requirements](/documentation/apps/technical-requirements.md)
* DataWedge app installed on the Android device
**Note**: If the Android device uses multiple user profiles, the configuration steps in this guide must be performed using the same profile where the target application is installed.
{% endhint %}
## Activate the hardware scanner
Zebra devices with built-in hardware scanners are managed by the DataWedge application. This application connects the scanner to the fulfillmenttools apps.
{% hint style="info" %}
A separate DataWedge profile must be configured for each fulfillmenttools app. For example, you'll need to create one profile for the Store Operations App and one profile for the Inventory App.
{% endhint %}
You'll need to ensure the DataWedge application is installed on your device. Then follow the steps below.
{% stepper %}
{% step %}
**Open DataWedge**
{% endstep %}
{% step %}
**Create a new profile**
Tap the more icon (three dots), select **New profile**, enter a name, for example, StoreOperationsApp, then tap **OK**.
  
{% endstep %}
{% step %}
**Associate the relevant app**
Tap **Associated apps**, then tap the more icon (three dots), and select **New app/activity**.
Select the appropriate package:
* Store Operations app: `com.fulfillmenttools.storeoperations`
* Returns app: `com.ocfulfillment.multiplatform.app`
* Inventory app: `com.ocfulfillment.inventoryapp`
Then, select **\*.** to access all activities within the package, and tap **OK**.
   
{% endstep %}
{% step %}
**Update the Intent output settings**
Select **Intent output**, then tap the **Enabled** checkbox.
Tap **Intent action**, then enter the appropriate action for the app used:
* Store Operations app: `com.fulfillmenttools.storeoperations.ACTION`
* Returns app: `com.ocfulfillment.multiplatform.app.ACTION`
* Inventory app: `com.ocfulfillment.inventoryapp.ACTION`
Tap **Intent delivery**, then select **Broadcast intent.**
{% endstep %}
{% endstepper %}
## Supported barcodes
* GS1 DataBar (DataBar-14)
* GS1 DataBar Stacked
* GS1 DataBar Stacked Omnidirectional
* GS1 DataBar Limited
* GS1 DataBar Expanded
* GS1 DataBar Expanded Stacked
* GS1 128 Composite Symbologie
* GS1 Databar Composite Symbologie
* GS1 Databar Stacked Composite Symbologie
* GS1 Databar Stacked Omni Composite Symbologie
* GS1 Databar Limited Composite Symbologie
* GS1 Databar Expanded Composite Symbologie
* GS1 Databar Expanded Stacked Composite Symbologie
* EAN-8 Composite Symbologie
* EAN-13 Composite Symbologie
* QR-Code
* Data Matrix
* Code-128
* UPC-A
* UPC-E
* 2 of 5 Interleaved
---
# 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/technical-requirements/zebra-hardware-scanner-configuration.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.