> 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.md).

# February 2026 Enhancements

11th February 2026, **More Reliable Sitemaps and URL Handling (Fewer 404s)**

When sitemap URLs had a trailing slash (for example `/category/` instead of `/category`), this could cause **404 errors** for some pages.

[View More](/release-notes/enhancements/2026-enhancements/february-2026-enhancements/more-reliable-sitemaps-and-url-handling-fewer-404s.md)

11th February 2026, **Safer Redirects – Preventing Redirect Loops**

Previously, it was possible to create **problematic redirects** such as only adding or removing a trailing slash (for example `/branda` → `/branda/`). These types of redirects can cause **redirect loops** and break navigation.

[Viw More](/release-notes/enhancements/2026-enhancements/february-2026-enhancements/safer-redirects-preventing-redirect-loops.md)

11th February 2026, **Better Performance by Removing Extra Database Operations**

A part of the system was using **Dapper** alongside **EF Core**, which caused **extra database operations** to spin up unnecessarily. This could harm performance and add complexity.

[View More](/release-notes/enhancements/2026-enhancements/february-2026-enhancements/better-performance-by-removing-extra-database-operations.md)

11th February 2026, **Updated Footer Branding to “Order Eazi”**

he footer previously displayed **“OE Commerce”** branding. This has been updated across the site to show **“Order Eazi”** instead.

13th February 2026, **Updated Integration Header for the New Platform Name**

The platform has been rebranded, but some technical integrations were still using the old header name `X-Storefront-Application-Key`.

[View More](/release-notes/enhancements/2026-enhancements/february-2026-enhancements/updated-integration-header-for-the-new-platform-name.md)

17th February 2026, **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.

[View More](/release-notes/enhancements/2026-enhancements/february-2026-enhancements/capture-and-store-client-id-on-customer-accounts-for-oe-integration.md)

17th February 2026, **Branch‑Aware Cart View for Multi‑Warehouse Setups**

For setups with **multiple branches and warehouses**, the cart page previously showed **every line item together**, regardless of which warehouse they were linked to. This made it hard for customers to understand which items ship from where and how delivery might be affected.

[View More](/release-notes/enhancements/2026-enhancements/february-2026-enhancements/branch-aware-cart-view-for-multi-warehouse-setups.md)

17th February 2026, **Warehouse Code Field Added to Inventory Locations**

Warehouse records previously did not have a dedicated **“Code”** field, which made it harder to uniquely identify or reference warehouses (especially in integrations or internal processes).

[View More](/release-notes/enhancements/2026-enhancements/february-2026-enhancements/warehouse-code-field-added-to-inventory-locations.md)

17th February 2026, **Improved Branch Selector (Slide‑In) for Shoppers**

The **branch selector slide‑in** (used when customers choose their preferred branch) has been upgraded to provide a smoother, more helpful experience.

[View More](/release-notes/enhancements/2026-enhancements/february-2026-enhancements/improved-branch-selector-slide-in-for-shoppers.md)


---

# 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.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.