Current build posture
The UX layer is now explicitly in execution, not deferred.
Runtimeprisma
Latest cycledrafting
Notification outbox0
Public area
A trading-card marketplace built like an operational control system
Scheduled Fill Exchange is being shaped around the same trust-heavy clarity a serious marketplace needs: strong pricing narrative, visible logistics, readable risk, and buyer/seller journeys that stay understandable even when the flow is complex.
Buyer workspace
0Requests in motionSeller console
n/aPending offersHub visibility
0Inbound shipmentsRequests are not orders
The public message has to make this obvious: buyers express intent first, then receive a final bundle offer with hard constraints checked before payment.
Pricing must feel earned
We are designing a trust page that explains price formation, hub handling, timing expectations, and dispute discipline in plain language.
Seller tooling must feel professional
Inventory, offers, packing, and payouts need dense, fast surfaces closer to an operator console than a generic SaaS dashboard.
Hub and admin need clarity under pressure
Inbound exceptions, dispute load, and cycle state should be visible immediately, without navigation friction or buried status changes.
Requests, offers, and orders in one flow
The buyer workspace will connect live Fill Requests, Final Bundle Offers, and confirmed orders. Until runtime data is available, the UX skeleton stays aligned with the product spec.
- Waiting for live runtime dataMemory mode fallback
Operational console for offers, inventory, and packing
Seller screens are designed around dense, trust-heavy operational data: reserve rate, offers awaiting response, inventory discipline, and packing readiness.
- No seller runtime data yetMemory mode fallback
Operational pulse
Latest outbox and dispute-sensitive activity
- No operational events yetOutbox will populate as live flows run.
Why this UX direction
Marketplace-grade clarity is a product requirement, not polish.
Target feelSpecialist marketplace, not CRUD admin
Desktop biasHigh-density operational layouts
Mobile stanceUsable, trimmed, still coherent
Trust priorityPricing, timing, and status legibility