Fulfillment

• What happens after payment

  • Delivery note or license key is sent to the buyer (DM if possible; otherwise in-channel as configured).

  • Product role is granted; if an expiration is set, it’s scheduled for removal later.

  • Stock updates automatically when keys are consumed.

• Delivery

  • Delivery note: Set via /product-set-delivery; view via /product-delivery. Sent to buyers on purchase.

  • License keys: Upload via /product-add-keys (one per line). Keys are auto-assigned on purchase and stock decrements.

  • DMs can fail if the buyer has DMs closed; sellers should clearly instruct buyers to enable DMs or provide an in-channel fallback.

  • [IMAGE: delivery note/keys setup]

  • [IMAGE: delivery received by buyer]

• Roles

  • Attach a role and optional expiration when configuring the product.

  • The bot needs Manage Roles, and its highest role must sit above the roles it grants.

  • Expirations: set durations (e.g., 60m, 2d) to auto-remove access later.

  • [IMAGE: role + expiration settings]

  • [IMAGE: role applied to buyer]

• Notifications

  • Sales channel: purchase alert with buyer mention.

  • Alerts channel: bot announcements/updates for your team.

  • [IMAGE: sales alert example]

• Common issues & fixes

  • Role not granted: check bot permissions and role order (bot role above target role).

  • Role not removed after expiration: confirm the bot still has Manage Roles and correct role order.

  • Keys exhausted: add more via /product-add-keys or set stock appropriately.

  • Buyer didn’t get DM: DMs may be closed—sellers must remind buyers to open DMs or provide an in-channel fallback.

  • Embeds/alerts not posting: ensure the bot can send messages and embed links in Sales/Alerts channels.