---
title: "What to do with the notification: 'The barcode already exists for a product which is not available at your location.'?"
slug: "what-to-do-with-the-notification-the-barcode-already-exists-for-a-product-which-is-not-available-at-your-location"
updated: 2026-03-13T13:34:49Z
published: 2026-03-13T13:34:49Z
canonical: "docs.retailvista.net/what-to-do-with-the-notification-the-barcode-already-exists-for-a-product-which-is-not-available-at-your-location"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.retailvista.net/llms.txt
> Use this file to discover all available pages before exploring further.

# What to do with the notification: 'The barcode already exists for a product which is not available at your location.'?

When the following message appears while creating a product, this means that the product/barcode already exists in the system but is not available for the current branch type.

This message will therefore only occur for companies linked to an organisation.

- The barcode already exists for an product that is not available for your branch. Search for the product without specifying a branch or branch type (via the Advanced tab) and either mutate the entry or add availability for your branch.

![](https://cdn.document360.io/9cfe1b80-9c32-4b2a-9328-1df667cdd950/Images/Documentation/image-1763380952512.png?sv=2026-02-06&spr=https&st=2026-10-26T11%3A59%3A19Z&se=2026-10-26T12%3A59%3A19Z&sr=c&sp=r&sig=h9HNW%2FAvOaCWS3SAdFfpZW5E2IP%2FwE6i0ycdXTPKYNE%3D)

*Image 1*

To resolve this, you can search in the product database for this barcode, but leave the **branch** and **branch type** fields empty in the Advanced tab (Images 1 & 2). Make both fields “empty”. When you now search, the product will appear. Apply a mutation to the product (e.g., adjust the description) so that the product is derived. After this, the product can be used and searched for in the normal way.

![](https://cdn.document360.io/9cfe1b80-9c32-4b2a-9328-1df667cdd950/Images/Documentation/image-1773408764399.png?sv=2026-02-06&spr=https&st=2026-10-26T11%3A59%3A19Z&se=2026-10-26T12%3A59%3A19Z&sr=c&sp=r&sig=h9HNW%2FAvOaCWS3SAdFfpZW5E2IP%2FwE6i0ycdXTPKYNE%3D)

*Image 2* ![](https://cdn.document360.io/9cfe1b80-9c32-4b2a-9328-1df667cdd950/Images/Documentation/image-1773408870480.png?sv=2026-02-06&spr=https&st=2026-10-26T11%3A59%3A19Z&se=2026-10-26T12%3A59%3A19Z&sr=c&sp=r&sig=h9HNW%2FAvOaCWS3SAdFfpZW5E2IP%2FwE6i0ycdXTPKYNE%3D)

*Image 3*

## What to do if the 'branch' field cannot be cleared?

If the branch field cannot be cleared, a branch has been assigned to the currently logged-in user.

One option is for a user within the organisation to log in who is not restricted to a specific branch. If this is not possible, it is also possible to temporarily remove the restriction from the user.

Go to *Extra* > *Users*, open the desired user, and clear the field “*Restrict access to branch*”.

**NOTE:** Restricting a user to a branch only makes sense if there are multiple branches. If there is only one branch, the restriction can be omitted.