Digital Products Shop

Server structure

Overview

For someone selling presets, templates, brushes, fonts or similar: small products, many customers, and support questions that repeat forever. #what-your-licence-allows is read-only and is the most important channel here, stating in plain language what a buyer may and may not do — personal use, client work, resale, redistribution — because almost every awkward conversation in this business comes from a buyer who genuinely did not know. #before-you-buy answers the pre-purchase questions publicly so they are not asked twenty times privately. Products is one channel per product line, each carrying its own support, so a question about the brush pack is not buried under the template questions. #installation-help covers the single largest support category, and #compatibility states which versions each product works with, which is where refund requests actually originate. Customers is verified and small: #customer-chat, #show-what-you-made, which is both a pleasure and the best marketing the shop has, and #feature-requests. Updates is read-only: #product-updates with what changed, and #changelog. #known-issues is published rather than hidden, because a buyer who finds an undocumented bug asks for a refund while one who reads it in a channel usually waits for the fix. A hidden shop area holds the refund log and support notes.

When to use it

Selling digital products generates the same support questions endlessly, and the ones that turn into refunds are almost always licence confusion or a version incompatibility nobody stated. This layout publishes the licence in plain language, gives each product line its own support channel, states compatibility up front, and publishes known issues rather than letting buyers discover them and ask for money back.

What makes it different

• The licence is stated in plain language, which prevents almost every awkward conversation.
• Compatibility is published up front, since that is where refund requests actually originate.
• Known issues are public, because a buyer who reads one waits and a buyer who finds one refunds.
• One support channel per product line, so questions are not buried under other products.

Recommended Vetox setup

• Tickets

  Point Tickets at #order-problem so a purchase or refund question is private rather than a public complaint.

• Auto Roles

  Assign the Visitor role on arrival so the customer floor stays behind verification without manual work.

• Embed Messages

  Use Embed Messages for #what-your-licence-allows so the terms are edited in place and never ambiguous.

• Starboard

  Point Starboard at #show-what-you-made so customer work becomes the shop's best marketing.