Cancellation requests
Review how buyers and sellers would request a cancellation before pickup, shipment, or auction closeout turns into a dispute.
Buyer Requests
- Buyers should see whether an order can still be cancelled before pickup release, carrier handoff, or seller packing confirmation.
- The request needs a reason, order snapshot, item status, seller response window, and expected refund or credit outcome.
- Repeated cancellation patterns should stay visible to support when they affect seller protection or auction integrity.
Seller Requests
- Sellers should be able to request cancellation for inventory errors, item damage, hub rejection, duplicate sale, or restricted-item review.
- Seller-initiated cancellations need buyer notice, score impact, refund visibility, and relist limits.
- High-volume sellers need cancellation history close to standards, payouts, support cases, and account health.
Auction Orders
- Auction cancellations should show bid count, reserve state, winning bidder, payment readiness, retraction history, and seller closeout duties.
- Late cancellations after a winning bid should require support review instead of a one-click outcome.
- Cancelled auction orders should create a clear path to relist, offer to the next bidder, or refund review.
Pickup Windows
- Pickup cancellations should explain hub custody, QR release status, appointment window, no-show history, and item return-to-seller timing.
- Buyers should be able to reschedule before requesting cancellation when the hub can still hold the item.
- Hub teams need a visible state for held, released, expired, returned, and support-review pickup cancellations.
Shipment Status
- Cancellation eligibility should change when a label is created, carrier scan is present, insurance is active, or delivery is completed.
- Seller packing proof and carrier events should determine whether a request becomes cancellation, return, missing item, or damage review.
- International and insured shipments need stricter support review before refund routing changes.
Refund Impact
- Cancellation review should show item price, shipping, tax estimate, credits, seller fee impact, payout hold, and invoice update.
- Buyer-facing language should separate immediate credits from refund timing that depends on payment providers.
- Seller balances should show whether fees are reversed, held, or reviewed because of repeated cancellations.
Support Review
- Support should review late auction cancellations, shipped orders, hub release exceptions, repeated buyer requests, and seller inventory failures.
- Each review needs order evidence, messages, hub notes, shipment events, policy version, and customer notice status.
- Staff decisions should leave a clear timeline so buyer, seller, finance, and hub teams see the same outcome.
Owner Approval
- Owners should approve cancellation windows, seller score impact, fee reversal rules, auction exceptions, and support escalation limits.
- The launch review should confirm that cancellation language is visible from checkout, order status, seller tools, and help routes.
- Rollback controls should pause self-service cancellation if notices, refund routing, or seller protection becomes unreliable.
Seller Orders
Buyer requests, seller requests, auction order rules, pickup windows, shipment state, and payout impact.
Checkout Review
Cart items, handoff choices, fee visibility, review limits, and cancellation notice placement.
Order Status
Pickup, shipment, review, report timeline, and cancellation window context.
Auction Operations
Proxy bids, reserves, closeout, handoff rules, seller cancellations, and support review.
Bid Integrity
Bidder eligibility, retractions, reserve changes, closeout holds, and seller cancellations.
Payment Readiness
Authorization, credits, seller releases, refund review, and tax readiness.
Seller Protection
Buyer abuse, return swaps, payout holds, evidence packets, pickup disputes, and review disputes.
Returns Center
Eligibility, evidence, seller response, refund holds, and support review.
Support Operations
Staff ownership, evidence review, response targets, refund authority, and appeals.
Current demo state
Cancellation requests are represented as guided order review.
The demo shows buyer requests, seller requests, auction orders, pickup windows, shipment status, refund impact, support review, and owner approval as static decision screens. It does not cancel live orders, reverse money, notify real sellers, or change inventory.
Future platform state
Live cancellation requests need account, order, payment, and support ownership.
A launched marketplace needs account-linked requests, order state checks, seller notices, hub and carrier events, refund routing, fee reversal rules, audit history, support escalation, customer notices, and rollback controls.