Commerce · Component · aftersales-refunds-replacements
Aftersales approvals, refunds and replacement orders
What it does
Register aftersales requests, approve them, create linked refund or replacement orders, evaluate completion readiness and close the case with a traceable lifecycle.
Core pattern
Exception intake + human-approved refund or replacement
- Input
- Return/refund/replacement request and operator decisions
- Output
- Aftersales case, linked financial or replacement records and readiness/completion state
Key parameters
| Name | Type | Default | Values |
|---|---|---|---|
| source_order | — | — | — |
| customer | — | — | — |
| request_type | — | — | — |
| items_quantity | array | — | — |
| reason | — | — | — |
Maturity and limits
Implemented stateful aftersales service and FastAPI routes, including readiness checks and linked order creation. Static source inspection only; no runtime, provider, deployment or test-pass claim.
No root reuse license found; config with credentials present. Tenant isolation and operational correctness require deployment validation. Refund records do not imply a live payment provider; returns require accurate physical inspection and inventory handling.
Used in pipelines
Industry tags
- Retail & ecommerceSource-supported industry
For work involving products, customers and fulfillment, use exception intake followed by human-approved refund or replacement.
- Manufacturing & industryTransferable use
For stock, delivery and returns for spare-part orders, use exception intake followed by human-approved refund or replacement.
- Logistics & supply chainTransferable use
Support “Reconcile receipts and damage” with exception intake followed by human-approved refund or replacement.
- Lifestyle & consumer appsTransferable use
Support “Support approves refunds or corrections” with exception intake followed by human-approved refund or replacement.
Skills pack
Contract scaffold and deterministic mock
Download · 10KBSHA-256 26ecc114bd8c1ac413950d7513d34e7559f65d555c747b3780296d415a8ec197
Related components
-
Cruise booking and passenger workflow
Selections and participant records + state and amount history
Working 1 pipeline -
Customer-specific catalogs, pricing, promotions and credit
Segment-aware quotes + promotion budgets and credit checks
Working 1 pipeline -
Cruise inquiries and request tracking
Preference-based inquiry records + numbered tracking and handling
Working 1 pipeline -
Distribution customer, SKU and warehouse master data
Unified customer, material and address records + units and storage locations
Working 1 pipeline