> For the complete documentation index, see [llms.txt](https://support.storefront.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.storefront.co.za/release-notes/enhancements/2026-enhancements/february-2026-enhancements/capture-and-store-client-id-on-customer-accounts-for-oe-integration.md).

# Capture and Store Client ID on Customer Accounts (for OE Integration)

Some Order Eazi (OE) setups require a **specific client ID** to be linked to a customer before their orders can be pushed through correctly. Previously, there was **no place in the backoffice account screen** to capture and store this client ID.

This release adds:

* A **new Client ID field** on the **backoffice account** screen.
* Support for both **person** and **corporate** accounts.
* A **database update** so the client ID is stored on the account record and can be used by OE.

**Benefits for you**

* You can now **store the required OE client ID** per customer directly in the backoffice.
* Orders that depend on this client ID are **less likely to fail** or be blocked.
* Easier onboarding and management of OE‑linked customers, with fewer manual workarounds.


---

# 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.storefront.co.za/release-notes/enhancements/2026-enhancements/february-2026-enhancements/capture-and-store-client-id-on-customer-accounts-for-oe-integration.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.