17 lines
1.2 KiB
Markdown
17 lines
1.2 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Platform aftersale monitoring and arbitration
|
|
The platform admin console SHALL provide a read-only cross-shop aftersale list and detail view with customer, shop, order-item, amount, evidence, status, message history, and refund-total context. A platform administrator SHALL be able to resolve an escalated dispute with a terminal refund or rejection through the guarded service path, without directly editing balances or bypassing shop ownership checks.
|
|
|
|
#### Scenario: admin inspects a cross-shop application
|
|
- **WHEN** a platform administrator opens the aftersale workspace
|
|
- **THEN** applications from all shops are listed with filters and authoritative status and refund amounts
|
|
|
|
#### Scenario: admin grants terminal refund
|
|
- **WHEN** a platform administrator resolves an eligible dispute in favor of the customer
|
|
- **THEN** the aftersale reaches refunded, the customer ledger is credited once, and the order refund total refreshes from the API
|
|
|
|
#### Scenario: admin rejects terminal dispute
|
|
- **WHEN** a platform administrator rejects an escalated dispute
|
|
- **THEN** the aftersale reaches rejected and the console shows that only the permitted one-time customer reopen can resume it
|