Game listings

A game listing is the page players browse, share, and book from. On a GM Storefront it’s the only thing you fill in — the Stripe SKU that actually charges players is created and kept in sync for you. Set the format, the price, the room, and you’re ready to publish.

Note

Game listings are the marketplace skeleton. The public browse surface (/games) ships in a follow-up release; this page describes what you can do today from your Outpost admin.

Prerequisites

• An Outpost that can host listings: a GM Storefront, Publisher, Community, Guild, or Creator Studio. Game Tables can’t host listings directly — they’re the table / show community page.
• For paid listings: Collector on the owner, Stripe Connect set up, and monetisation enabled on the Outpost. Stripe charges + payouts must both be live before you can publish a paid listing. For free RSVP listings, none of this is required.
• A VTT room you GM (own or are listed as gm on). The room’s Seat capacity is what caps sales.

Create a listing

1. Open Outpost → Admin → Listings (the dice icon).

2. Click New listing. A modal opens.

3. Type a title.

4. Choose Paid (default) or toggle on Free RSVP if no money changes hands.

5. Paid path — pick the Format:

   • One-shot — single session.
   • Mini-series — 2-5 sessions sold as one purchase.
   • Campaign — 6+ sessions sold as one purchase.
   • Weekly seat — monthly subscription, ongoing.

   Then set Price per seat + Currency, and pick the Play room from your room list.

6. Free RSVP path — set Maximum seats.

7. Click Create draft. The matching Stripe SKU is created automatically; the editor opens for the rest of the details (pitch, system, refund policy, etc.).

Tip

You only fill in price + room once, on the listing. PostRoll keeps the Stripe product in sync as you edit. You don’t need to touch the Products tab unless you’re selling something that isn’t a game (files, packs, modules).

In the editor

The editor’s Format & booking section lets you change the format, booking mode, and refund policy after creation. Price & room is where you adjust pricing or relink to a different room.

• Pitch (markdown) — 2-4 paragraphs setting the scene.
• System — dnd-5e, pf2e, mothership, homebrew, etc.
• Format → Arc sessions (for Mini-series / Campaign) — an inline schedule editor. Add a row per session with optional title, date, and duration. At least one session is required to publish.
• Format → Session date (for One-shot) — optional datetime + duration. Leave blank for “Date TBC”.
• Refund policy — Flexible, Moderate, Strict, No refunds, or Custom (free-text markdown).

Publish

Click Publish in the editor. PostRoll runs the publish gate:

• Title, system, refund policy must be set.
• For paid listings: a play room with a price, valid Stripe Connect, and (for campaigns) at least one arc session.
• For free RSVP: a maximum-seats value.

If everything checks out, the listing and the matching Stripe SKU go live in one click. The product gets its stripe_product_id and stripe_price_id provisioned on your Connect account at the same moment — no separate “publish product” step.

Pause vs Close

• Pause hides the listing from the marketplace. Existing bookings + sessions continue. Re-publish anytime.
• Close stops new bookings. Remaining scheduled sessions still run. Refunds still possible.
• Delete (trash icon) soft-removes the listing. The synced product keeps its ID and Stripe state — in-flight purchases are unaffected.

Why not just create a product?

You can — for digital downloads, bundles, tier perks, content packs (world / scene / token / card / asset / collection bundle), and events. On non-storefront outposts, the legacy “New product → Game seat” flow is also still available for one-off cases.

On a GM Storefront, though, the legacy flow hides the seat kinds and points you back here. Why:

• The listing has everything the buyer cares about (title, pitch, system, format, policy). Splitting “what is it” from “how much” across two forms is friction.
• One save = one Stripe SKU. No mismatch between marketing copy and product copy.
• Format → kind mapping is automatic. No “which kind do I pick?” decision.

Free vs paid: same listing shape

The schema doesn’t distinguish free and paid games — both write the same listing row. The difference is whether the listing has a synced product underneath. Once the marketplace ships, a free recurring drop-in and a paid campaign have the same discoverability, same review aggregates, same SEO.

Related

• GM storefront — the new pro-GM outpost subtype that hosts your listings.
• Selling paid game seats — the underlying seat-product mechanics. Mostly relevant on non-storefront outposts (publisher / community / guild).
• Selling content packs — for selling worlds, scenes, tokens (not games).