Appearance
Brand Accounts
Brand accounts represent fabric and component manufacturers — the origin of the supply chain. Examples include Louvolite, Coulisse, and Top Window Covering.
What a Brand Can Do
| Capability | Description |
|---|---|
| Create verified master catalogs | Fabrics, blind types, components with full attribute sets |
| Version control | Publish catalog versions (auto-numbered 1.0, 2.0, 3.0, …) and push updates downstream with opt-in propagation |
| Permission management | Grant or revoke granular catalog access to Suppliers |
| Distribution analytics | Track which Suppliers and Retailers are using your catalog content |
| Blue-tick verification | Products carry your verified status all the way to the end customer |
Tenant Isolation
Each Brand organisation has a dedicated MySQL database named blindstrader_brand_{slug}. Your data is completely isolated from every other Brand on the platform.
Connecting with Suppliers
The relationship between a Brand and a Supplier is mutual and bidirectional:
- Either party can initiate a connection request.
- The other party approves or declines.
- Once connected, the Brand configures which parts of the catalog the Supplier can access.
Connections can be terminated by either party at any time. Terminating a connection does not automatically remove previously imported catalog data from the Supplier's tenant — it only prevents future imports and updates.
Catalog Versioning
Blindstrader tracks your catalog as versioned snapshots. When you publish a new catalog version, an immutable CatalogVersion record and a CatalogVersionSnapshot (frozen JSON of the full catalog state) are created atomically in a single transaction.
- Version numbers are assigned automatically:
1.0,2.0,3.0, … - Each Supplier independently chooses whether to adopt the new version at their own pace.
- Previously adopted versions remain intact — Suppliers are never force-updated.
This opt-in model ensures Suppliers are never surprised by breaking changes in your catalog. See Catalog Management → for full details on the versioning lifecycle and API.