Skip to content

Selling in-app content packs

Your Outpost shop sells in-app content as well as files. Publish a world you built, a scene you painted, a token pack, a card template, an asset pack, or a Collection that bundles everything in one purchase. Buyers don’t download a zip — the content lands directly in their library, ready to use.

Different kinds deliver differently:

  • World / Scene / Board — on purchase, the buyer gets their own deep clone in their library. They can edit, fork, and play freely. Your original is untouched.
  • Token / Card template / Asset pack — buyers gain entitled access to your originals. They appear in the buyer’s library as “purchased” items. If you later refund, access is revoked.
  • Collection bundle — sells everything in a Collection in one purchase. Cloned members get cloned; entitlement members get entitled access. Mix and match.
  • A Collector subscription on your Outpost (the monetisation tier).
  • Stripe Connect set up and ready — see Connecting Stripe.
  • Monetisation enabled on your Outpost.

The content products you sell must already exist in your own library. You publish from a resource you own — there’s no “create-as-you-sell” flow.

  1. Open your Outpost → click the Shop tab.
  2. Click Add product.
  3. In the Type dropdown, scroll to the Content group and pick the kind that matches your resource (World, Scene, Board, Token pack, Card template, Asset pack).
  4. A Source from your library picker appears. Pick the resource you want to sell.
  5. Fill in Name, Description, Cover image URL, Price, and Currency as usual.
  6. Set the License URL and License name — content products can’t be published without a license link.
  7. Click Create draft. You’ll land on the product’s edit page.
  8. Click Publish when you’re ready.

If you’ve already organised content into a Collection, you can sell the whole thing in one go.

  1. Open your Collection at /app/collections/....
  2. Click the menu in the header → Publish as bundle.
  3. Pick the Outpost you want to publish from (must be your own with monetisation enabled).
  4. Click Continue. You’ll land on the new-product page with the bundle kind + source already filled in.
  5. Set Name, Price, License URL, and any other details.
  6. Click Create draft, then Publish.

The Collection’s detail page will show “Manage as bundle” in the menu from then on, instead of “Publish as bundle”.

Every content product needs a License URL — a link to the terms buyers agree to when they purchase. Pick something appropriate:

  • Creative Commons for art / lore you’re happy to be reused.
  • Your own ToS page for everything-rights-reserved sales.

The license appears under the price on the product detail page; buyers can click through to read the terms before purchasing.

You can also set Credit name + Credit link for art / attribution, which shows beneath the license block.

  • Price is in your selected currency, including decimals (e.g. 12.99 USD). Zero-decimal currencies like JPY can use whole numbers.
  • PostRoll’s platform fee applies to every sale (same as file products) — see Selling products for the details.

On a content product page, buyers see a kind-aware preview before purchase:

  • World: cover + counts of scenes / wiki pages / entities.
  • Scene: map thumbnail + dimensions.
  • Board: image preview + board type + node count.
  • Token pack: sprite preview + size.
  • Card template: front + back artwork.
  • Asset pack: cover + total asset count.
  • Collection bundle: cover + per-type item counts.

After purchase, buyers see You own this + an Open in library button that deep-links to their cloned resource (for cloned kinds) or to the seller’s resource via entitled access (for entitlement kinds).

For entitlement kinds (tokens / card templates / asset packs) refunds work exactly like file products: hit Refund on the Sales page and the buyer’s access is revoked the moment the webhook lands.

For cloned kinds (worlds / scenes / boards / collection bundles containing clones), refunds are blocked by default once the buyer has claimed their clone. The buyer has an editable copy in their library — refunding without revocation would leave them with both the content and their money back. The Refund button surfaces a second confirmation in that case, asking whether you really want to go through; if you accept, the refund runs but the clone stays with the buyer.