## ADDED Requirements

### Requirement: Products table
The `products` table SHALL store product templates with a unique sku, a name, an optional default item type, and timestamps.

#### Scenario: Unique sku
- **WHEN** a second product row is inserted with an existing sku
- **THEN** the insert is rejected

### Requirement: Orders table
The `orders` table SHALL record sales with an account reference and a status lifecycle (`pending`, `paid`, `lapsed`, `cancelled`).

#### Scenario: Order lifecycle
- **WHEN** an order is created as `pending` and later marked `paid`
- **THEN** the status reflects each state

### Requirement: Tag to product and order linkage
Each `tags` row SHALL optionally reference a `product_id` and an `order_id`, linking a tag to what it is and which sale it belongs to.

#### Scenario: Linked tag
- **WHEN** an admin links a tag to a product and an order
- **THEN** the tag row carries both foreign keys

#### Scenario: Unlinked tag
- **WHEN** a tag has no product/order assigned yet
- **THEN** both columns are NULL and the tag still functions (registry-only binding unchanged)
