Commerce integration
Review the commerce contracts a marketplace owner would need before live services connect: identity scopes, listing actions, bids, offers, order events, hub handoff, support events, and launch controls.
Route Contracts
- Storefront, search, listing detail, category, seller, hub, checkout review, order, support, and operator routes should each map to a stable data contract.
- Every contract needs owner, required fields, allowed states, customer-visible copy, private fields, and fallback behavior.
- Route coverage should stay tied to the demo map so broken pages cannot silently fall back to the homepage.
Identity Scopes
- Buyers, sellers, hub staff, support staff, finance owners, and marketplace owners should have different access boundaries.
- Private data should stay limited to the action being performed: bid, offer, pickup release, report review, proceeds review, or support case.
- Every elevated action needs audit history, owner role, and rollback path.
Listing Actions
- Listing search, item detail, save, compare, offer, trade, bundle, question, report, and cart review all need consistent item state.
- Seller listing creation should carry title, category, condition, media, item specifics, format, reserve, quantity, handoff, and returns.
- Weak item proof should route to catalog repair, hub check, seller coaching, or hold before promotion.
Bid and Offer Events
- Auction events should cover bid placed, top bid changed, reserve met, instant buy used, auction closed, won, lost, and payment review.
- Offer events should cover offer sent, seller countered, buyer accepted, offer expired, proof requested, and support escalation.
- Customer alerts should always point back to the listing, offer, auction, order, or support case.
Order Events
- Order contracts should cover cart review, buyer acknowledgement, seller release, shipment, hub pickup, local pickup, delivery, review gate, and report window.
- Refund, credit, seller hold, tax record, settlement, and insurance states should match finance-owner readiness pages.
- Reviews should only open from completed purchases or won auctions.
Hub Handoff Events
- Hub events should cover seller intake, item check, custody change, packing proof, pickup window, QR release, no-show, and issue report.
- Retail hub activation adds location setup, staff roles, pickup desk, packing bench, event desk, and launch gate requirements.
- Support should reuse the same item snapshot, release proof, and condition notes shown to buyers and sellers.
Support Events
- Support contracts should cover missing item, damage, item not as described, pickup issue, seller appeal, restricted item, and suspicious activity.
- Each case needs required documents, owner, customer notice, seller response window, evidence packet, decision, and appeal status.
- Support events should update account activity, order timeline, staff queue, risk review, and owner reporting.
Launch Controls
- Before live use, owners should approve access scopes, rate limits, event names, retries, private data rules, support ownership, and rollback steps.
- Provider activation should remain separate for payments, payout releases, identity, notifications, media, carriers, and support tools.
- Go-live rehearsal should prove route checks, event review, service health, support drill, and rollback before any public launch.
Migration Readiness
Seller migration, inventory migration, policy mapping, customer notices, records, redirects, and cutover gates.
Integration Evidence
Customer routes, operator console, data views, package boundary, noindex controls, and audit checks.
Service Activation
Checkout, identity, notifications, media evidence, carriers, support, and launch guardrails.
API Access
App registry, sandbox keys, scoped permissions, event delivery, rate limits, audit logs, and launch gates.
Event Delivery
Event names, delivery status, retry review, replay controls, owner alerts, and privacy limits.
Access & Audit
Role permissions, staff actions, approval history, privacy boundaries, and launch review.
Communications
Buyer alerts, seller messages, support notices, preferences, templates, and delivery review.
Auction Operations
Proxy bids, reserves, bid increments, bidder checks, closeout, handoff, and support holds.
Retail Hub Activation
Counter setup, staff roles, custody trail, pickup desk, packing bench, event desk, and launch gate.
Current demo state
Commerce integration is represented as an owner review surface.
The demo shows contracts, event names, access boundaries, route links, and launch controls without exposing credentials, collecting payment details, or enabling live service calls.
Future platform state
Live integration needs credentials, monitoring, and signed ownership.
Launch needs approved service credentials, rate limits, retry rules, event delivery, provider monitoring, staff permissions, privacy review, incident contacts, and owner approval for each connected service.