Seller compliance
Give sellers a clear view of eligibility, category access, tax-readiness status, record exports, holds, and appeal paths before high-value commerce goes live.
Seller Eligibility
- Seller standing should show profile completeness, response history, report status, return settings, and unresolved account tasks.
- New sellers can start with lower limits while trusted sellers unlock higher-value auctions, timed drops, and hub-assisted listings.
- Every limit needs a plain reason and a visible next step.
Category Permissions
- High-trust categories such as graded cards, creator electronics, sneakers, and local pickup can require stronger proof before publishing.
- Category access should connect listing quality, item proof, report history, hub acceptance, and seller response speed.
- Restricted or rejected inventory should explain whether the issue is item type, proof quality, condition, or seller standing.
Tax Readiness
- Seller finance should show whether tax-readiness status is not started, needs review, ready, or blocked by missing seller action.
- This demo does not collect bank, tax, payment, address, or identity details.
- Live seller setup needs permissioned review, clear record retention, and seller-visible status changes.
Records and Exports
- Sellers need sales records, fee lines, refund impact, report outcomes, hub service lines, and settlement history in export-ready form.
- Record views should separate gross sales, fees, credits, holds, refunds, and estimated release amounts.
- Support notes and private buyer details should stay outside seller exports unless policy allows them.
Holds and Reviews
- Account, listing, order, seller-release, and category holds should show reason, owner, age, affected actions, and appeal path.
- Open reports, missing proof, delayed response, restricted items, or hub rejection can pause selected seller actions.
- Operators need a review reason before changing seller status or releasing a hold.
Appeal Paths
- Sellers should be able to respond with corrected listing details, proof photos, shipping evidence, category documentation, or support notes.
- Appeal status should show submitted, under review, action needed, approved, denied, or limited approval.
- Buyer safety, seller fairness, and hub proof need to stay visible together when a decision is reviewed.
Identity Checks
Buyer trust, seller limits, business review, proceeds readiness, privacy boundaries, and appeals.
Seller Finance
Fees, earnings, proceeds readiness, refund reserves, and tax-readiness status.
Payment Readiness
Seller releases, refund holds, chargeback review, tax readiness, and audit controls.
Tax & Records
Seller status, order records, exemptions, statements, retention, and owner approval.
Compliance Readiness
Seller verification, tax records, payment posture, consumer protection, and audit trails.
Policy Pack
Seller standards, buyer protection, returns, restricted items, privacy, and approval ownership.
Verification Center
Buyer trust, seller status, hub release rules, finance readiness, and privacy boundaries.
Restricted Items
Rejected inventory, category limits, seller education, and staff review paths.
Staff Queue
Support, trust, seller limits, hub issues, report aging, and review notes.
Business Seller
Business account roles, approval flow, seller limits, service standards, and owner review.
Seller Standards
Listing accuracy, fulfillment, communication, dispute response, visibility limits, and appeals.
Seller Protection
Buyer abuse, return swaps, seller release holds, pickup disputes, evidence packets, and owner approval.
Current demo state
Seller compliance is represented as guided readiness states.
The demo shows eligibility, category permissions, tax-readiness status, record exports, holds, and appeal paths without collecting sensitive seller details.
Future platform state
Live seller compliance needs permissioned review.
Launch needs verified seller records, tax setup, account limits, hold history, appeal ownership, staff permissions, export controls, and documented policy decisions.
