> 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/september-2026/postgresql-support.md).

# PostgreSQL Support

The data layer now works natively with PostgreSQL, removing per-query text conversions. Searching, filtering and importing are faster, and text matching is consistent across the platform.

OE Commerce now runs on PostgreSQL as well as the database it has always used, and new stores are created on it by default.

**This includes:**

* PostgreSQL supported alongside the existing database, chosen per store, so the two run side by side across the platform
* New stores provisioned on PostgreSQL automatically, in every environment
* Existing stores left on the database they are already using, with nothing to migrate and nothing to switch off
* Text matching handled by the database itself rather than converted on every query
* Consistent case-insensitive matching across searching, filtering, imports, menus, category addresses and sitemaps
* Faster queries, most noticeably on large catalogues

**How it benefits the Merchant**

This is the largest piece of platform work OE Commerce has done, and most of it is deliberately invisible. The data layer was rewritten to speak PostgreSQL natively rather than translating on every request, which removes a significant amount of work from each query and takes a ceiling off how large a catalogue can get before search and filtering start to feel slow.

It also makes matching consistent. Searching for a brand, importing a product or following a category address now behaves the same regardless of how text is capitalised, which removes a class of problems where a product could not be found or an import created a duplicate because of a difference in case.

For merchants already running on OE Commerce, nothing changes and nothing needs doing. Your store continues on the database it has always used, and the work that makes PostgreSQL possible has improved how queries are written for every store regardless of which database is behind it.

For new stores, PostgreSQL is now the default, which gives them more headroom as the catalogue grows and a clearer path as the platform continues to build on it.

**Potential FAQs**

Q: Do I need to do anything?

A: No. If your store already exists it stays exactly where it is, and there is no migration to plan or downtime to schedule.

Q: Which database is my store on?

A: Stores created before this change are on the original database. Stores created from now on are on PostgreSQL. Your OE Commerce representative can confirm which applies to you.

Q: Will my searches return different results now?

A: They should return better ones. Matching that previously failed because of capitalisation now succeeds, so a search or an import that quietly missed a product is more likely to find it.

Q: Will an existing store be moved to PostgreSQL later?

A: Possibly, but not without being planned with you first. There is no automatic migration, and nothing happens to a running store as part of this release.

Q: Does this change anything I can see in the back office?

A: No. This is behind-the-scenes work. The only difference you should notice is that searching, filtering and bulk imports are quicker, particularly on a large catalogue.