james
cdfb1b06f2
Sync the group-buying capability plus the order, frontend-mall, and frontend-shop-admin requirements into the main specs, and write the capability Purpose the archive leaves as a placeholder. This closes the last of the five planned marketing changes.
54 lines
2.9 KiB
Markdown
54 lines
2.9 KiB
Markdown
# frontend-shop-admin Specification
|
|
|
|
## Purpose
|
|
The merchant console for managing a shop's products and fulfilling its orders.
|
|
|
|
## Requirements
|
|
|
|
### Requirement: Merchant product management
|
|
Shop users SHALL manage only their own shop's products: create/edit bilingual content, manage SKUs, publish/unpublish with immediate effect on the storefront.
|
|
|
|
#### Scenario: publish visible in mall
|
|
- **WHEN** a merchant publishes a product in shop-admin
|
|
- **THEN** it appears in the mall product list for the matching locale
|
|
|
|
### Requirement: Merchant fulfillment
|
|
Shop users SHALL see incoming orders, create shipments, mark them shipped, and issue requested invoices.
|
|
|
|
#### Scenario: ship an order
|
|
- **WHEN** a merchant creates a shipment for a paid order and marks it shipped
|
|
- **THEN** the shopper sees the shipment with tracking info
|
|
|
|
### Requirement: Merchant coupon management
|
|
Shop users SHALL manage only their shop's coupon templates from shop-admin, including localized title, amount and threshold in minor units, currency, claim stock, active window, and enabled state. Shop-admin SHALL expose a coupons navigation entry beside existing shop operations.
|
|
|
|
#### Scenario: create an active template
|
|
- **WHEN** a shop owner creates a valid coupon template
|
|
- **THEN** the template is available for eligible customers to claim during its active window
|
|
|
|
#### Scenario: coupons appear in shop navigation
|
|
- **WHEN** an authenticated shop user opens shop-admin
|
|
- **THEN** a coupons management entry is reachable without leaving the shop-scoped console
|
|
|
|
### Requirement: Merchant flash-sale management
|
|
Shop users SHALL manage only their flash-sale sessions and items in shop-admin, choosing their own SKU, active window, minor-unit sale price, reserved stock, and per-customer limit. Shop-admin SHALL expose a flash-sale navigation entry beside existing shop operations.
|
|
|
|
#### Scenario: configure item
|
|
- **WHEN** a merchant creates an active valid flash-sale item for its SKU
|
|
- **THEN** it appears to customers through active flash-sale discovery
|
|
|
|
#### Scenario: flash sales appear in shop navigation
|
|
- **WHEN** an authenticated shop user opens shop-admin
|
|
- **THEN** a flash-sale management entry is reachable without leaving the shop-scoped console
|
|
|
|
### Requirement: Merchant group-buying management
|
|
Shop users SHALL manage only their shop's group-buying activities in shop-admin, configuring an owned SKU, localized display content, minor-unit group price, required paid-member count, active window, and group lifetime. Shop-admin SHALL expose a group-buying navigation entry beside existing shop operations.
|
|
|
|
#### Scenario: publish activity
|
|
- **WHEN** a merchant publishes a valid group-buying activity
|
|
- **THEN** shoppers can discover it during its active window
|
|
|
|
#### Scenario: group buying appears in shop navigation
|
|
- **WHEN** an authenticated shop user opens shop-admin
|
|
- **THEN** a group-buying management entry is reachable without leaving the shop-scoped console
|