> For the complete documentation index, see [llms.txt](https://support.barnetpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.barnetpos.com/liquor-store-portal/vendors/vendor-maintenance-best-practice.md).

# Vendor Maintenance - Best Practice

**VENDOR MAINTENANCE – COMMON ISSUE & BEST PRACTICES**

If a Vendor ID is too long, the vendor may appear to disappear or not display correctly in the system. This most commonly happens when vendors are created or edited in the Portal with an ID that exceeds system limits.

**Vendor ID Requirement**

* Maximum length: 20 characters
* Vendor IDs longer than 20 characters are not supported and can cause visibility or syncing issues.

**How to Fix the Issue**

1. Open the vendor record.
2. Shorten the **Vendor ID** to **20 characters or fewer**.
3. Save the changes.
4. Refresh the vendor list to confirm the vendor is visible.

**Preventing Duplicate Vendors (Very Important)**

**Use One System to Create Vendors**

To avoid duplication and syncing issues:

* Create vendors **only in one place**:
  * **POS Manager** *or*
  * **Portal**
* Do **not** alternate between systems when creating vendors.

Creating vendors in both systems can result in:

* Duplicate vendors
* Inconsistent Vendor IDs
* Ordering and reporting issues

**Head Office (HO) Mode – Best Practice**

If you operate in Head Office mode:

* Vendor creation and maintenance should be centralized
* Create and manage vendors only at Head Office
* Avoid creating vendors at individual store levels

Centralized vendor management ensures consistency across all locations and prevents duplicates.

**Additional Cleanup Recommendation**

* Review and delete **duplicate vendors**
* Removing duplicates helps prevent inventory, ordering, and reporting issues

Refer to the **Vendor Cleanup** document for step-by-step instructions.


---

# 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://support.barnetpos.com/liquor-store-portal/vendors/vendor-maintenance-best-practice.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.