Published price book
Not published yetPricing & trust
Explain the pricing engine before asking for confidence
This marketplace uses snapshot-based pricing, not live quote roulette. Operators import market data, normalize it against internal SKU identity, generate a draft price book, and publish one stable book per cycle window.
Live line count
0Average confidence
n/aSource snapshots tracked
0How prices are formed
Cycle price books, liquidity classes, policy adjustments, and seller payout ratios now surface as explicit operator-visible layers instead of opaque totals.
Why the hub exists
The hub is a lightweight audit and consolidation point. It is there to reduce downstream friction, not to turn the business into a warehouse.
Typical timing
The UX should teach the cadence: Fill Request, matching, seller round, final offer, inbound shipment, hub consolidation, buyer delivery, payout release.
Dispute discipline
We will present disputes as rules-driven and evidence-backed, with clear liability outcomes instead of vague moderation language.
Trust promises
What this product should communicate clearly from day one
Buyer commitment pointOnly at final offer confirmation
Pricing stanceStable snapshot price book per cycle
Seller payout timingDeferred, reserve-aware, quiet-period based
Current published bookNo published book yet
UX intention
CardTrader-level seriousness without copying CardTrader visually
Dense data, strong hierarchy, clear trust language, and surfaces that make buying and operating feel understandable. That is the direction now encoded in the execution plan.
Live published price book
The marketplace should be able to show the current public-facing pricing posture without revealing the whole operations console.
No published price book lines are visible yet.
Source governance
Pricing trust is built by making the snapshot pipeline understandable, not by pretending the market is simpler than it is.
Policy layers
These are the product promises behind price formation, bundle behavior, and seller payouts.
| Policy layer | What it means |
|---|---|
| Snapshot-based pricing | Matching uses a published book, not live external calls during bundle generation. |
| Liquidity classes | Core, standard, attach-only, and disabled state shape visibility and seller activation behavior. |
| Auditability | Sources, snapshots, mapped rows, and publish timestamps remain inspectable from admin pricing ops. |