Features / Store isolation

Store isolation, enforced in the database

Every product, order and customer row is scoped to its store by PostgreSQL row-level security. A bug or mistake in one brand cannot surface another brand’s data.

Isolation here is not a filter in the interface that a missing check could bypass — it is enforced in the database. Each request carries its store, and the database returns only that store’s rows.

Who it’s for

  • Operators holding several brands’ data in one system
  • Teams that need a clean audit trail
  • Anyone wary of cross-tenant leaks
01 / HOW IT WORKS

How it works

01

Request carries its store

An x-store-slug header identifies the store.

02

Database scopes the rows

Row-level security returns only that store’s data.

03

Everything is logged

Admin actions land in a per-store audit log.

02 / QUESTIONS

Questions

Is isolation just a WHERE clause?

No — it’s row-level security in Postgres, so it holds even if application code forgets a filter.

Can staff see other stores?

Only the stores they’re assigned to; a keymaster view sees all.

ADD THIS TO YOUR STORE

Every store includes this.

Talk to us

Pricing is on request.