This document covers the five modules that make up the storefront's product catalog: Products, Product Classes (variations/options), Product Stock (inventory), Category, and Category Group. All five follow the generic module architecture described in admin-00-overview.md, and the multi-language text convention and standard JSON response convention apply throughout.

A cross-cutting mechanic worth understanding: the add/edit forms are schema-driven. The form layer reads the underlying table's column list and renders one field per column, in column order, using the database column's comment as the field's label. This means the catalog's admin forms stay in sync automatically with the underlying schema, adding or reordering a column updates the form without a code change.

Cross-module data model

categorygroup (1) ──< category (many) ──< productcategory >── (many) products
                                                                     │
                                                                     ├──< productclass >── classes (option "types", Option Manager module, out of scope)
                                                                     │
                                                                     ├──< productstock  (summed → live stock quantity)
                                                                     │
                                                                     └──< bookingitems  (summed, active orders → reserved quantity)

A product's stock balance is always computed fresh on every read as stock received minus quantity reserved by active orders, there's no separate "quantity on hand" value to keep in sync; it's derived live.

Shared list/grid conventions

Every list view in this document is rendered through the same generic grid pipeline: the list page builds a header/data pair and hands it to a shared client-side grid renderer. The Operation column (edit/clone/delete/sort) is rendered by a shared helper, individually toggleable per module, for example, Product Stock rows suppress the clone and sort icons, since cloning or reordering a dated stock batch wouldn't make sense.

Role gating throughout all five modules follows the same convention: add/edit/delete actions each check the acting user's granted role for that module and action. The super-admin account bypasses these per-module checks everywhere, by design.

1. Products

Purpose

The central catalog record: the sellable item shown on the storefront, its multi-language marketing copy, price, main/gallery images, category assignments, linked variation options, and (via Product Stock and active orders) a live computed stock balance. Every other catalog module exists to attach data to a products row.

Top-level menu item, reached directly from the main admin menu.

Underlying DB table(s) and key columns

products:

Column	Type	Purpose
`ProductID`	int(11) PK, AI	Primary key
`ProductName`	mediumtext	Multi-language name bundle
`ProductHead`	mediumtext	Multi-language short heading/subtitle bundle
`ProductTitle`	mediumtext	Multi-language title bundle (SEO/meta use)
`ProductText`	longtext	Multi-language full description bundle
`ProductTags`	mediumtext	Multi-language tags bundle (searchable)
`ProductCode`	mediumtext	Multi-language SKU/product-code bundle
`ProductQRCode`	mediumtext	Multi-language field also used as the basis for a friendly-URL slug
`ProductPrice`	float, default 0	Base price
`ProductOption`	tinyint(1), default 0	Flag toggled independently; marks a product as having selectable variations
`ProductImage`	mediumtext	Delimited list of image/media paths (main image = first entry)
`LangID`	int(11), default 0	Language scope (0 = all languages)
`ProductStatus`	tinyint(1), default 1	Active/disabled
`ProductSort`	int(11), default 9999	Manual sort order
`ModifiedDate` / `CreatedDate`	datetime	Audit timestamps

Related tables joined into every product read: - productcategory, many-to-many junction to categories; a product can belong to multiple categories. - productclass, see §2; variation/option rows for the product. - productstock, see §3; summed to compute live stock quantity. - bookingitems (order line items, see admin-03-orders-bookings.md), summed for active orders to compute reserved quantity, giving the final stock balance.

Files involved

File	Role
`admin-products/index.php`	One-line stub into the shared router
`forms/products.list.php`	Grid: search bar, category filter, columns No/Name/Option/Image/Language/Status/Operation, plus per-row Item Stock and Item Options buttons opening the Product Stock / Product Classes sub-panels
`forms/products.form.php`	Add/edit form: name/head/title/text fields, tags, code, QR-code, price, variation-flag switch, category checkboxes, media/gallery upload, language, status
`forms/products.drop.php`	Renders a product-picker dropdown, used by other forms (e.g. Product Stock / Product Classes "add" panels)
`datacontrol/products.dc.php`	AJAX endpoint for all product CRUD plus status/sort/option toggles
`selecting/selecting.dc.php`	Read/search query, insert, option toggle, and category-assignment maintenance functions

Available actions (`productsman`)

Action	Behavior
`productsadd`	Inserts new product, then assigns its selected categories
`productsclone`	Duplicates an existing product, including its category assignments
`productsedit`	Full update; replaces the product's category assignments with the submitted set
`productsdis`	Enable/disable toggle
`productssort`	Drag-reorder
`productsoption`	Toggles the variation flag independently
`productsdel`	Removes the product
`productsread`	Returns matching product ID(s)

Notable business rules

Category assignment is a full replace on every edit, the current category set always reflects the most recent save.
Product images are stored as a single delimited list on the product record and managed as a set through the media-upload widget.
The variation flag (ProductOption) is an independent toggle from the main edit action, and marks whether the storefront should present the product's variation selectors.

File upload / media behavior

Uploads go through a shared upload endpoint, with upload buttons (image/video/document) shown per field based on the field's configuration.
Accepted file types are validated by extension and size cap (photos/documents up to 9 MB, video up to 90 MB).
Uploaded files are given a generated filename and stored under a dedicated attachment directory.

2. Product Classes (variations/options)

Purpose

Defines per-product variation instances (e.g. this product's "Red" color option, this product's "Large" size option), the specific value, its own optional image, and how it affects price. This is distinct from the separate Option Manager module, which defines the reusable option types ("Color", "Size", etc.) that Product Class rows point at.

Reached as an AJAX sub-panel from the Item Options button on each Products-grid row, rather than a standalone top-level menu item. Today, this sub-panel is available to the super-admin account; if non-admin staff need to manage product variations directly, the module's menu registration can be extended to open it up to a granted role, the same way every other module in this document is configured.

Underlying DB table(s) and key columns

productclass:

Column	Type	Purpose
`ProdClassID`	int(11) PK, AI	Primary key
`ProductID`	int(11)	FK → `products.ProductID`
`ClassID`	int(11)	FK → `classes.ClassID` (the option type, e.g. "Color")
`ProdClassValue`	text	Multi-language value bundle (e.g. "Red")
`ProdClassPrice`	float	Price delta or override, per `ProdClassPriceOption`
`ProdClassPriceOption`	tinyint(1)	Switch: "Additional Cost" vs "Full Price"
`ProdClassImage`	text	Optional per-variation image
`ProdClassImageOption`	tinyint(1), default 0	Whether the variation's own image should display
`ProdClassStatus`	tinyint(1), default 1	Active/disabled
`ProdClassSort`	int(11), default 9999	Sort order
`ModifiedDate` / `CreatedDate`	datetime	Audit timestamps

Related table classes (option types, part of the separate Option Manager module): ClassID, ClassName, ClassDescription, ClassImage, ClassStatus, LangID, ClassSort, timestamps.

Files involved

File	Role
`admin-productclass/index.php`	One-line stub
`forms/productclass.list.php`	Grid scoped by `ProductID`, columns No/Name/Value/Price/Option/Status/Operation
`forms/productclass.form.php`	Add/edit form: linked product (read-only), option type dropdown, value, price, price-option switch, image upload, status
`datacontrol/productclass.dc.php`	AJAX endpoint
`selecting/selecting.dc.php`	Read/search functions for `productclass` and the parent `classes` table

Available actions (`productclassman`)

productclassadd, productclassclone, productclassedit, productclassdis, productclasssort, productclassdel, productclassread, the same add/edit/delete role-check pattern as Products.

3. Product Stock

Purpose

Inventory ledger for a product: rather than a single "quantity on hand" column, stock is recorded as discrete dated batches, and the live stock quantity is the sum of all batches effective as of today, reduced by quantity reserved on active orders to produce the final stock balance.

Reached via the Item Stock button on each Products-grid row, opening a sub-panel scoped to that product, the same access pattern as Product Classes above.

Underlying DB table(s) and key columns

productstock:

Column	Type	Purpose
`StockID`	int(11) PK, AI	Primary key
`ProductID`	int(11)	FK → `products.ProductID`
`StockQuantity`	float	Quantity added in this batch
`StockDate`	datetime, default now	Effective date, future-dated entries are excluded from the current balance until they arrive
`StockStatus`	tinyint(1), default 1	Active/disabled
`ModifiedDate` / `CreatedDate`	datetime	Audit timestamps

Files involved

File	Role
`admin-productstock/index.php`	One-line stub
`forms/productstock.list.php`	Grid scoped by `ProductID`, columns No/Date/Quantity/Status/Operation
`forms/productstock.form.php`	Add/edit form: linked product (read-only), quantity, effective date, status
`datacontrol/productstock.dc.php`	AJAX endpoint
`selecting/selecting.dc.php`	Read functions, plus live stock-balance and price convenience lookups

Available actions (`productstockman`)

productstockadd, productstockedit, productstockdis, productstockdel, productstockread — the same role-check pattern as the other catalog modules. There's no clone/sort action for this module, since stock batches are chronological, not manually ordered.

Notable business rules

Stock is additive and batch-based; correcting an over-counted figure is done by adding an adjusting entry or editing an existing batch directly.
A live read endpoint exposes the current stock balance and price for a given product, used by the storefront to display up-to-date availability without a full product fetch.

4. Category

Purpose

The classification a product is filed under for storefront browsing/filtering (e.g. "Home Decoration Accessories", "Metal", "Wood"). Categories belong to a parent Category Group (§5) and attach to products many-to-many.

Top-level menu item.

Underlying DB table(s) and key columns

category:

Column	Type	Purpose
`CategoryID`	int(11) PK, AI	Primary key
`GroupID`	int(11), default 0	FK → `categorygroup.GroupID`
`CategoryName`	text	Multi-language name bundle
`CategoryDescription`	text	Multi-language description bundle
`CategoryImage`	text	Category image path
`CategoryStatus`	tinyint(1), default 1	Active/disabled
`LangID`	int(11), default 0	Language scope
`CategorySort`	int(11), default 9999	Sort order
`ModifiedDate` / `CreatedDate`	datetime	Audit timestamps

Files involved

File	Role
`admin-category/index.php`	One-line stub
`forms/category.list.php`	Grid with search bar, columns No/Name/Image/Language/Status/Operation
`forms/category.form.php`	Add/edit form: category group, name, description, image, status, language
`forms/category.drop.php`	Category-picker dropdown, grouped by category group, used across the admin panel
`forms/category.check.php`	Multi-select checkbox variant, used on the Products form to assign multiple categories
`datacontrol/category.dc.php`	AJAX endpoint
`selecting/selecting.dc.php`	Read/search functions, including a live per-category product count

Available actions (`categoryman`)

categoryadd, categoryclone, categoryedit, categorydis, categorysort, categorydel, categoryread, standard role gating on add/edit/delete.

Notable business rules

The category picker appears in two forms across the admin panel, a single-select dropdown (filtering) and a multi-select checkbox list (assignment), both driven from the same underlying data.

5. Category Group

Purpose

The parent grouping for categories, used to organize the category picker UI into labeled sections and to control whether a group allows single or multiple category selection.

Top-level menu item.

Underlying DB table(s) and key columns

categorygroup:

Column	Type	Purpose
`GroupID`	int(11) PK, AI	Primary key
`GroupName`	text	Multi-language name bundle
`GroupDescription`	text	Multi-language description bundle
`GroupNote`	text	Multi-language internal note bundle
`GroupSelection`	tinyint(1), default 1	Selection mode: single or multiple
`GroupImage`	text	Group image path
`LangID`	int(11)	Language scope
`GroupStatus`	int(11), default 1	Active/disabled
`GroupSort`	int(11), default 9999	Sort order
`ModifiedDate` / `CreatedDate`	datetime	Audit timestamps

Files involved

File	Role
`admin-categorygroup/index.php`	One-line stub
`forms/categorygroup.list.php`	Grid with search bar, columns No/Name/Language/Image/Status/Operation
`forms/categorygroup.form.php`	Add/edit form: name, description, note, selection-mode switch, image, language, status
`forms/categorygroup.drop.php`	Group-picker dropdown, used by the Category form's group field
`datacontrol/categorygroup.dc.php`	AJAX endpoint
`selecting/selecting.dc.php`	Read functions, including a live product count per group

Available actions (`categorygroupman`)

categorygroupadd, categorygroupclone, categorygroupedit, categorygroupdis, categorygroupsort, categorygroupdel, categorygroupread, the same role gating as every other module in this document.

ÖTEK StorePlatform Documentation

ÖTEK Store
Platform Documentation