Openfront Collectibles

Openfront Collectibles is a self-hosted shop for Pokémon trading cards. It sells singles stocked per card, printing, language, and condition; graded slabs as single serialized items; and sealed product, including pre-orders with an allocation and a per-customer limit. It also runs a buylist for buying cards from customers, takes items in on consignment, stores market price readings, and applies repricing rules. Collectors get a binder and a want list in their account.

What the codebase contains

The application uses Next.js 16 (App Router, React 19), Keystone 6 with a GraphQL API at /api/graphql, Prisma, and PostgreSQL. Source is laid out as:

Schema overview

The schema extends the shared Openfront E-commerce commerce lists (products, variants, carts, orders, payments, fulfillment, returns, regions, discounts, gift cards, users, roles) with collectibles lists:

• Catalog: CollectibleSet (a Pokémon set with series, release date, release status, TCGplayer group id), CatalogItem (one card printing or one sealed product), Specimen, SpecimenIdentifier, CollectibleMedia, MarketPrice, and PricingRule.
• Stock and selling: card fields on ProductVariant (stockKind, cardCondition, cardFinish, cardLanguage, pricingMode, pre-order fields), plus InventoryUnit, InventoryMovement, Reservation, and Listing for serialized items such as slabs.
• Buying and consignment: Buylist, BuylistEntry, TradeInSubmission, TradeInItem, ConsignmentIntake, ConsignmentItem, ConsignmentAgreement, and ConsignmentSettlement.
• Evidence and operations: condition, grade, provenance, custody, and valuation observations; FulfillmentRequirement, ShipmentEvidence, DisputeCase, SellerProfile, and CollectorProfile.
• Collector records: Binder, BinderCard, WishlistItem (the want list), and SavedSearch.

See Architecture and workflows for relationships and lifecycles.

Operator surfaces

Operators work in /dashboard. The product-specific pages cover Cards & Sets, Graded Slabs, Sealed & Pre-orders, Market & Repricing, Buylist, Trade-ins, Consignments, Receive Items, condition and grading evidence, disputes, high-value fulfillment, sellers, and the inherited commerce pages (orders, products, regions, discounts, gift cards, payment and shipping providers). The full route list is on External dashboards.

Storefront

The customer storefront is country-scoped under /[countryCode]. It shows each set as its full checklist with stock and the latest market reading, card and product pages, search, a "Sell to us" buylist page at /trade-in, cart and checkout, and an account area with orders, binder, want list, saved searches, and trade-in history. See External storefronts.

Onboarding

The dashboard onboarding dialog offers three templates: Complete card shop (19 sets imported as checklists with market readings, singles, graded slabs with labelled sample certificates, sealed product including pre-orders, pricing rules, and a buylist), Starter shop (two modern sets, a few singles and sealed boxes, one region, bank transfer), and Custom setup (the starter data as editable JSON per section). The seed shop, "Eighth Street Cards", is fictional.

Ownership and tenancy

A deployment is one shop. Collectibles commands such as catalog import, repricing, and trade-in submission look up the single Store record and refuse to run until exactly one exists. There is no multi-store or multi-tenant separation inside one database.

Staff access is controlled by role permissions such as canManageCatalog, canManageProducts, canManageInventory, canManageConsignments, canManageEvidence, and canReadCollectibles. Customer records are owner-scoped: binders, binder cards, want-list items, and saved searches are created against the signed-in user and filtered to that user on read, update, and delete. Inventory units, movements, reservations, and listings cannot be created or edited through generic GraphQL CRUD; they change only through named commands.