Card preorders delayed: coordinating refunds when stock arrives
When stock arrives during a delayed preorder refund request, two workers must not both act on an old undelivered state. For owned or authorized digital goods, coordinate fulfillment and after-sales decisions through the original item. This is a merchant design, not a 稳付pay feature promise.
Continue by topic
1. Preserve the preorder commitment
Record product version, quantity, estimated delivery, delay notices and cancellation terms before payment. Explain changes and available options without silently replacing the original date or inventing guarantees.
Preserve payment facts and stable item identities. Refund requested, approved, executing and actually successful are distinct states. Stock arrival permits allocation; it does not automatically authorize delivery.
2. Coordinate both decisions on the same item
Maintain a version and current processing claim for each item. Delivery workers and refund approval must recheck state within local transactions; only the process that obtains the applicable claim proceeds. An earlier query is not a lock.
Fictional PRE-A buys one owned license. If after-sales first places it on delivery hold pending refund review, stock allocation skips it. If delivery has already entered an external system, a locally incomplete flag alone cannot justify a refund.
3. Keep unknown external outcomes unresolved
A local database cannot roll back external email, licensing or refund execution. After a delivery timeout inspect the original operation and evidence; pause the competing final action. Do not both issue another card and submit a refund.
After a refund failure confirm whether failure is definitive before resuming delivery or review. A revealed key does not return to saleable stock simply because its order was canceled; verify real revocation and redemption capabilities.
4. Retain separate completion evidence
Trace each original item to delivery or an actual refund, approved amount and responsible operator. Approved with unknown external result remains pending review. Customer notices describe verified progress without fixed refund arrival promises.
Simulate refund-first, delivery-first, concurrent approval, external timeout and worker restart using owned records. Require an explainable terminal state or an unresolved exception. Confirm actual refund arrangements separately; this is not automatic refund or payout API documentation.
Frequently asked questions
May stock arrival override an existing refund request?
No. Check claims, original terms and the agreed resolution. New stock does not erase accepted after-sales work.
Can a local transaction guarantee no double loss?
It coordinates local state only. External idempotency, queries or manual evidence are still needed; unknown results stay unresolved.