Jordan-Hall / Jordan-Hall/browser
[P4][SHOP-05] Receipts, orders, returns and recurring purchases
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Programme: #1
Epic: #27
## Objective
Extend commerce beyond checkout into provider-truth order tracking, receipts, returns/refunds/disputes and explicitly bounded recurring purchase workflows.
## Scope
- Normalize order, shipment/delivery, receipt/invoice and return/refund/dispute state without losing provider IDs.
- Refresh order status from provider truth and preserve observation times.
- Receipt/invoice artifact storage and export.
- Return/refund/cancellation preparation as new TX actions with current policy/eligibility checks.
- Evidence bundle for disputes (order, listing/source snapshots, communications, receipts where permitted).
- Recurring purchase rules with product/seller/price/quantity/frequency/expiry ceilings.
- Renewal/recurring action notifications, reservations and revocation.
## Correctness rules
- Compensation is explicit and may fail; UI never promises refund/cancellation before provider verification.
- Recurring authority is narrow, expiring and inspectable.
- Order status comes from provider observations rather than local inference.
## Acceptance criteria
- [ ] Order/delivery/refund state reflects provider truth with freshness metadata.
- [ ] Returns/refunds/cancellations create new proposals and receipts.
- [ ] Recurring rule cannot exceed configured product/amount/quantity/frequency/time boundaries.
- [ ] Revocation prevents new recurring commits while preserving existing order history.
- [ ] Dispute evidence links source/order/receipt records with access controls intact.
- [ ] Ambiguous compensation remains NeedsReconciliation instead of being called successful.
## Dependencies
- SHOP-03
- TX-02
- AUTO-01
**First phase:** P4
**Maturity target:** P6
**Owner:** connectors-domains
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Read dependencies SHOP-03, TX-02, and AUTO-01 first, then identify the existing order, transaction, and provider-connector boundaries before defining a phase-sized change. Done means meeting the listed provider-truth, recurring-authority, compensation, and dispute-evidence acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100