Fulfilling multiple items paid through Alipay: parent orders, line snapshots and partial after-sales

Paying for a cart does not prove every item was delivered. Keep one payment parent order with traceable item lines and fulfill each separately. This is a merchant-side design, not a supplied cart, automatic order-splitting, refund or payout API. Confirm actual protocols and after-sales capabilities independently.

Continue by topic

1. Freeze the parent and its item lines before payment

Record merchant, customer, currency, total due and quote version on the parent. Give every line a stable identity with product, quantity, price, allocated discount and entitlement target. A cart URL or the current product price cannot reconstruct a historical purchase.

Define discount, shipping and rounding allocation in advance. In a simulation, A costs 30 and B 20; a discount of 5 is allocated as 3 and 2 under the agreed rule, leaving lines of 27 and 18 and a total of 45. These are illustrative same-unit amounts, not fees. Lines and separate charges must reconcile to the payable total.

2. Verify one payment once

Validate the actual signature and merchant, original parent, amount, currency and success state on the server. Persist the payment evidence. Two lines must not each record the full 45 as separate income, and a browser return must not mark all items delivered.

Reliably establish payment facts and pending fulfillment lines, then execute delivery separately. Use durable idempotency identities for parent, line and fulfillment version. Repeated notifications return the existing result. A changed product, missing stock or invalid target creates a pending line rather than rewriting the paid amount.

3. Retry incomplete work without repeating completed work

If A is delivered and B is out of stock, display paid and partially fulfilled. Do not display complete delivery or ask the customer to pay another 18. Resume B using its original line and operation identity, checking the actual outcome first; do not deliver A again.

A local transaction does not guarantee a remote delivery side effect happens once. Preserve timed-out requests and evidence, using the remote system actual query or idempotency capabilities. Investigate unknown outcomes manually. Payment success, queue acceptance and item fulfillment are different metrics; missing stock is not an Alipay payment failure.

4. Trace after-sales decisions to their lines

If B is approved for cancellation or repayment, reconcile its original net amount of 18, discount rules and agreed terms. Do not silently recalculate at the current 20 or assume a full 45 repayment. Used entitlements, charges and partial handling depend on actual capabilities; this example does not promise a supported refund method.

Keep approvals, actual refund or alternative-resolution evidence and the valid delivery of A. Test duplicate notifications, partial delivery, lost responses, repeated after-sales requests and discount allocation with synthetic orders. Reconcile settlement against verified payment and adjustments, not by settling the same revenue once per item.

Frequently asked questions

Can all lines be marked delivered when the parent payment succeeds?

No. Keep evidence for each actual delivery and derive the aggregate state from the lines. Stock shortages and unknown remote results remain pending.

Can a canceled item be deleted and the paid total edited?

Preserve the paid snapshot. Explain changes through linked cancellation, refund or adjustment records under the confirmed after-sales rules.

References