Seller GuidesListing a Product

Listing a Product

Learn how to become a seller on Web3.Market and submit your first product listing. This guide covers the full process from applying for a seller account to getting your product approved and live on the marketplace.

Becoming a Seller

Before you can list products, you need to apply for a seller account. All seller applications are reviewed by the Web3.Market team to maintain marketplace quality.

Create an Account

If you haven’t already, sign up at web3.market by connecting your wallet. You’ll need a valid wallet address for receiving payouts.

Submit a Seller Application

Navigate to your dashboard and select Apply to Sell. You’ll need to provide the following information:

FieldDescriptionRequired
First NameYour legal first nameYes
Last NameYour legal last nameYes
EmailContact email addressYes
CountryCountry of residenceYes
Tax IDTax identification number for your countryYes
GitHub UsernameYour GitHub handle (helps verify credibility)No
Telegram UsernameFor direct communicationNo
Discord UsernameFor community supportNo
Payout AddressWallet address for receiving earningsYes
Payout BlockchainBlockchain network for payouts (e.g., Solana, Ethereum)Yes

Wait for Approval

Your application will be reviewed by the Web3.Market team. You’ll receive a notification when your application is approved or rejected. If rejected, a reason will be provided and you can reapply after addressing the feedback.

The review process typically takes 1-3 business days. Make sure your payout address is correct — this is where your earnings will be sent.


Submitting a Product

Once approved as a seller, you can submit products from your seller dashboard.

Product Information

Fill out the product submission form with the following details:

Title A clear, descriptive name for your product. This appears in search results and on the product page. Keep it concise and specific (e.g., “DeFi Yield Aggregator Dashboard” rather than “My Cool Project”).

Tagline A short one-line summary that appears below the title in listings. Maximum impact in minimum words.

Description A detailed description of what your product does, its features, and how buyers can use it. Supports Markdown formatting. Include:

  • What the product does
  • Key features and capabilities
  • Technology stack and dependencies
  • Installation or deployment instructions
  • Any requirements or prerequisites

Category and Subcategory Select the most relevant category and subcategory for your product. Accurate categorization helps buyers find your product through browsing and filtering.

Blockchains Select all blockchain networks your product supports (e.g., Ethereum, Solana, Polygon, BSC). You can select multiple blockchains.

Tags Add relevant tags to improve discoverability. Tags are used in search and filtering. Examples: defi, nft, dao, smart-contract, react, nextjs.

File Uploads

Upload your product as a ZIP file. This is the deliverable that buyers receive after purchase. Include all source code, assets, documentation, and any necessary configuration files.

Best practices:

  • Include a README.md with setup instructions
  • Remove any .env files with sensitive data
  • Include a license file if applicable
  • Test the ZIP by extracting and following your own setup steps

GitHub Integration

If your product is open-source or you want to showcase its development health, link your GitHub repository.

https://github.com/your-username/your-repository

When you provide a GitHub URL, Web3.Market automatically fetches and displays:

  • Stars, forks, and watchers — social proof of community interest
  • Contributors — team size and community involvement
  • Commit activity — how actively the project is maintained
  • Issue tracking — open/closed issue ratio
  • Releases — versioning and release cadence
  • Documentation quality — presence of README, CONTRIBUTING guide, wiki, and license

These metrics are combined into a GitHub Health Score displayed as a radar chart on your product page, covering five dimensions: Activity, Popularity, Maintenance, Community, and Documentation. Each is scored 0-100, with a weighted overall score.

GitHub metrics are refreshed periodically. A strong health score builds buyer confidence and can significantly increase sales.

Demo URL and Documentation URL

Demo URL — Link to a live demo or preview of your product. Buyers can try before they buy, which improves conversion rates.

Documentation URL — Link to external documentation, a GitBook, or a docs site. Helpful for products with complex setup or integration steps.


Enabling Domain-Locked Licensing

If your product is a web application or dApp that runs on a domain, you can enable domain-locked licensing to protect it from unauthorized use.

How It Works

When licensing is enabled, buyers receive a license key tied to their purchase. They must activate the key on specific domains. Your product can call the Web3.Market License Verification API to confirm the license is valid for the domain it’s running on.

Enabling Licensing on Your Product

Toggle the license_enabled option to On in the product submission form. This is opt-in — licensing is disabled by default.

Once enabled, a license key is automatically generated for each buyer upon purchase. Each license allows activation on one domain at a time. Buyers can deactivate their current domain and activate a new one whenever they need to, directly from their dashboard — no support ticket required.

⚠️

For full details on integrating the license verification API into your product, see the License System documentation.


Product Approval Workflow

All new product submissions go through a review process before appearing on the marketplace.

Submit for Review

After completing the submission form and uploading all files, submit your product. Its status will be set to Pending.

Admin Review

A Web3.Market administrator reviews your product for quality, accuracy, and policy compliance. They check:

  • Product description accuracy and completeness
  • File quality and contents
  • Appropriate categorization
  • Compliance with marketplace guidelines

Approval or Rejection

  • Approved — Your product goes live on the marketplace immediately. A published_at timestamp is set and the product becomes visible in search results and category listings.
  • Rejected — You receive a notification with the rejection reason. You can edit the product and resubmit.

Editing Products After Approval

You can update your product details at any time after approval. However, file changes (product ZIP, thumbnail, and screenshots) follow a special workflow to maintain quality control.

Text and Metadata Changes

You can freely update the following without re-review:

  • Title, tagline, and description
  • Category and subcategory
  • Blockchains and tags
  • Price and discount settings
  • Demo URL and documentation URL
  • GitHub URL
  • License settings

File Changes (Pending File Workflow)

When you upload a new product file, thumbnail, or screenshots for an already-approved product:

  1. The new files are stored as pending (pending_product_file_url, pending_thumbnail_url, pending_screenshot_urls)
  2. A has_pending_file_changes flag is set on the product
  3. The existing live files continue to be served to buyers
  4. An administrator reviews the pending files
  5. Upon approval, the pending files replace the live files and the pending fields are cleared

This workflow ensures buyers always receive reviewed, approved files while allowing sellers to submit updates at any time. Your product remains live and available for purchase during the review period.