Minecraft Web Panel Market Management Guide

This guide is for you in the PvPServer Minecraft Web Panel admin panel. Market Management It has been prepared to explain the section. Market Management; It is used to manage product categories, products, prices, images, descriptions, stock/status information, RCON delivery commands and order processes to be sold to players on the Minecraft server.

1. What is the use of Market Management?

In Minecraft Web Panel Market Managementis used to organize the products that players can purchase through the website. This section is not just the product adding screen; It also directly affects the economic structure of the server, the delivery flow after payment, the product information to be displayed to the player, and the after-sales support process.

If a market item is configured incorrectly, the player may not see the item, purchase it at the wrong price, the item may not be delivered after payment, or the RCON command may work incorrectly. Therefore, when adding grocery products, it is not enough to just write the title and price. Category, description, image, activity, stock, delivery method, RCON command, player name variable and order control should be considered together.

Market Management is used for the following operations:

• Creating market categories.
• Adding products to sell.
• Determining product prices.
• Editing product images and descriptions.
• Making products active or passive.
• Checking stock or sales status.
• Defining product delivery commands.
• Providing automatic delivery via RCON.
• Tracking orders and delivery statuses.
• To operate the market in harmony with payment, balance, coupon and campaign flow.

2. Main Departments of Market Management

Minecraft Web Panel Market Management generally consists of three basic areas: Categories, Products and Orders. These three areas work together. Without categories, products appear disorganized; Without products, the market remains empty; Payment and delivery issues cannot be resolved without order tracking.

3. Market Categories

Market categoriesAllows products to be grouped regularly. When the player enters the market, he can browse category by category instead of seeing all the products mixed together. This both improves the user experience and can increase the sales rate.

Examples of categories that can be used on Minecraft servers:

• VIP Packages: Temporary or indefinite VIP memberships.
• Vault Keys: Key products connected to the crate/key system.
• Game Money: Money packages provided through the Economy plugin.
• Starter Packages: Items, money or special advantage packages for new players.
• Cosmetic Products: Pet, effect, tag, prefix or visual advantages.
• Special Packages: Server-specific bundle products.
• Event Products: Limited time event or seasonal products.

Category names should be short and understandable. When the player sees the category name, they should be able to guess which products are in it. If very general categories such as “Other”, “Packages”, “Special” are used too much, the market will look cluttered.

4. Things to Consider When Creating a Category

When creating a category, just writing a name is not enough. The category's rank, activity, description and how it appears to the player are also important. Especially in multi-product markets, category order directly affects sales flow.

5. What is Product Management?

Product Managementis the section where you specify the details of each product to be sold in the market. The product's name, price, category, description, image, activity status, stock information and RCON delivery command are managed in this area.

When creating the product, the player must clearly understand what he is purchasing. If the product description is vague, the player has different expectations. If the delivery command is incorrect, the product will not be delivered after payment. If the price is incorrect, the incorrect amount will be charged.

Therefore, the following questions must be answered for each product:

• What does this product give to the player?
• Under which category will the product appear?
• Is the product price correct?
• Is the product image descriptive?
• Is there a delivery condition stated in the product description?
• Will the product be delivered automatically or manually?
• Is the RCON command correct?
• Does the player need to be online?
• Is the product limited or indefinite?
• Is the product active or passive?

6. Product Name

The product name is the most important information the player sees in the market. The product name should be short, clear and explain what the product offers. The player should be able to roughly understand what he will be getting just by looking at the product name.

Good product name examples:

• 30 Day VIP Package
• 10 Diamond Case Keys
• 50,000 Game Coins
• Starter Support Package
• Premium Cosmetic Package
• SkyBlock Private Island Package

Examples of bad product names are vague. Short but incomplete names such as “Package 1”, “Special Product”, “VIP”, “Key” do not give enough information to the player. The product name must match the price and description.

7. Product Description

The product description tells the player exactly what the product gives. A significant portion of market support requests arise from incomplete or unclear product descriptions. The player must know the contents of the product, the method of delivery and the terms of use in advance.

The product description should include the following information:

• What the product gives.
• Product quantity.
• Whether it is temporary or indefinite.
• Whether the player needs to be online or not.
• Whether the delivery is automatic or manual.
• If it is a VIP or authorization product, what advantages it provides.
• If it is the safe key, which safe it will be used in.
• This information is only valid in certain server mode if the product is available.
• Where to check after purchase.

Bu paket 30 gün süreyle VIP yetkisi tanımlar.
Satın alma sonrası VIP yetkiniz RCON sistemi ile otomatik olarak hesabınıza işlenir.
Teslimat için Minecraft kullanıcı adınızın doğru yazılmış olması gerekir.
Sorun yaşarsanız sipariş numaranızla destek talebi oluşturabilirsiniz.

8. Product Price

The item price determines the amount charged to the player. When pricing, not only the value of the product, but also the general economic balance of the server, other product prices, payment commissions, campaigns and coupon system should be considered.

Things to consider when determining the price:

• Is the product in price balance with other products?
• Is the VIP package too cheap or too expensive?
• Are vault keys accessible enough to disrupt the game economy?
• If game currency is sold, will it inflate the server economy?
• Is the price still reasonable after coupons and campaigns?
• Are payment provider commissions taken into account?
• The product is valuable to the player, but is it fair?

9. Product Image

The product image makes the product look more professional and understandable in the market. Players notice products with visuals more easily. However, the image must be compatible with the product and not reduce site performance.

Suggestions for product image:

• An image related to the product must be used.
• Rank/label image can be used for VIP package.
• A key or crate themed image can be used for the safe key.
• Coin/money image can be used for game money.
• Images should not be of very large file size.
• It should not be distorted in mobile view.
• Visual style should be as consistent as possible within the same market.

Products without images can be sold; However, if the entire market is without images, the site will look weak. It is recommended to use high quality images, especially for prominent products.

10. Product Active / Inactive Status

Product activity status determines whether the product will appear to players in the public market. Products that are in preparation, have not been tested, or have been temporarily discontinued should be kept inactive.

Ongoing orders must be checked before the product is deactivated. Delivery problems of old orders are not automatically resolved just because the product has been discontinued. Order history should also be reviewed.

11. Stock Management

Stock logic can be used for some products. For example, a stock limit can be set for a special package, event product or seasonal product that will be sold in limited numbers. If there is a stock system, the number of times the product can be purchased can be controlled.

Inventory management is useful when:

• Making a limited number of VIP campaigns.
• Selling special packages to the first 50 players.
• Publishing special market items such as event rewards.
• Limiting products that may disrupt the server economy.
• Keeping safe key or special package sales under control.

If there is stock, it is useful to display it clearly to the player on the product page. If the product can be purchased even though the stock is out, a serious problem occurs. If the stock system is not used, expressions such as limited sales should not be used in the product description.

12. Delivery Type: Automatic and Manual Delivery

Groceries can be delivered in two basic ways: automatic delivery and manual delivery. In automatic delivery, the RCON command runs. In manual delivery, the manager checks the order and delivers the product himself.

Automatic delivery is fast; but the technical settings must be correct. Manual delivery is more controlled; but requires administrator intervention. Which method to choose should be determined by the product type and server management policy.

13. RCON Delivery Command

The RCON delivery command is the most critical part of automatic delivery. Determines which command will run on the Minecraft server when the product is purchased. If this command is incorrect, the product will not be delivered or will be delivered incorrectly.

The following points should be taken into consideration when preparing the RCON delivery command:

• The command should be executable in the Minecraft console.
• Unnecessary slash should not be used at the beginning of the command; The format expected by the system should be tested.
• The player name variable must be used correctly.
• The product quantity must be written correctly.
• The plugin command must be correct.
• It should be checked whether the command works for the offline player.
• The command should be tried with a test account.

give {player} diamond 10
eco give {player} 50000
crate key give {player} vote 5
lp user {player} parent add vip
say {player} marketten bir ürün satın aldı!

here {player} is an example playername variable. The actual variable name used in your panel may differ. The variable supported by the system must be used when writing the product command.

14. Player Name Variable

The player name variable is very important in grocery delivery. During the order, the panel takes the player's Minecraft username and writes it into the variable in the RCON command. In this way, the same product can be delivered automatically to different players.

Things to consider about the player name variable:

• The variable name must be in the format supported by the panel.
• The Minecraft name on the player's profile must be correct.
• There must be no spaces or special characters in the player name.
• Variables should not be used in the wrong place within the command.
• When testing the command, it should be tried with the real player name.

If the player misspelles the Minecraft name, the RCON command may go to the wrong destination or not work at all. Therefore, it must be ensured that the player name is entered correctly during the membership and market purchase flow.

15. Product and Coupon Relationship

Grocery items can work with coupon codes. A coupon may be valid on all products or may only work on certain category/products. The product price, coupon discount and payment amount must be calculated correctly together.

The following points are important when checking the product coupon relationship:

• Is the coupon valid on this product?
• Is the coupon defined only for a certain category?
• Is the product price correct after the discount?
• Is a minimum basket amount provided?
• Does the product become free with the coupon?
• Is coupon usage recorded in the order record?

While conducting coupon campaigns, grocery product prices should also be reviewed. Selling low-priced products for free or at a loss should be prevented, especially in high-discount coupons.

16. Product and Payment Relationship

The product price must be transferred correctly to the payment system. The player selects a product in the market, purchases it via payment or balance method, the order is placed and the product is delivered. An error at any point in this flow turns into a support request.

Payment related controls:

• Is the product price correct?
• Is the currency correct?
• If there is a coupon, was the discount applied correctly?
• Was the correct amount sent to the payment provider?
• If purchasing with balance, has the correct balance been deducted?
• Is the order status updated when the payment is successful?
• If payment fails, product not delivered?

The product should not be delivered until payment is completed. Otherwise, the player can buy items without paying. Therefore, payment status and order delivery status must be clearly separated.

17. Order Management

Order Managementis used to track players' purchases and delivery status. No matter how well the market system is established, support processes cannot be managed properly without an order tracking screen.

Order records must contain the following information:

• Order number.
• Purchaser member.
• Minecraft username.
• Purchased product.
• Product price.
• Discount information if there is a coupon discount.
• Net amount paid.
• Payment method.
• Payment status.
• Delivery status.
• RCON command result.
• Order date.

When the player says "the product has not arrived", the order number is the most important information. Without the order number it becomes difficult to find the correct order. Therefore, the order history should be clear and understandable in the player panel.

18. Order Statuses

Order status shows what stage the purchasing and delivery process is at. If status information is not used correctly, questions such as whether the player received the product, whether the payment was completed, or whether the delivery failed will be confused.

19. Testing Process Before the Product is Released

After adding a new market product, it is not right to make it available to players immediately. The purchase and delivery process should be tried with a test account first. This testing reduces future payment and delivery support requests.

1. Is the product category correct?
2. Is the product name correct?
3. Is the product description sufficient?
4. Is the product price correct?
5. Is the product image uploaded?
6. Does the product appear correctly in the public market?
7. Is the RCON delivery command correct?
8. Is the player name variable working correctly?
9. Does the command work with the test player?
10. Can a test order be created with payment or balance?
11. Is delivery made when the order is successful?
12. Is there a correct record in the order history?

20. Player Purchasing Flow

The purchasing flow on the player's side should be simple and understandable. The player selects the product, reads the description, logs into his account, selects the payment or balance method, uses a coupon code if available, and completes the order.

A healthy purchasing flow should be like this:

1. The player enters the market page.
2. Selects a product from the category.
3. Checks the product description and price.
4. If he is not logged in, he logs into his account.
5. Makes sure the Minecraft username is correct.
6. If there is a coupon code, apply it.
7. Purchases via payment or balance method.
8. Checks the status from the order history.
9. If the product is delivered automatically, it checks in the game.
10. If there is a problem, it opens a support request with the order number.

If this flow is explained to the player, support requests will decrease. In particular, the warning "Make sure your Minecraft username is correct" should be visible on the market page.

21. Market and Support System Relationship

The market system is directly related to the support system. Players mostly open support regarding payment, balance, product delivery, wrong player name and coupon issues. Therefore, the clearer the grocery products are prepared, the less the support burden will be.

To reduce support requests, the product page should include the following information:

• What does the product give?
• When will the product be delivered?
• Does the player need to be online?
• Why is Minecraft username important?
• Is the product delivered automatically or manually?
• If the product does not arrive, support must be opened with the order number.
• Brief description if there is a return or compensation policy.

If the product description is not clear, the player may misunderstand the product. In this case, he opens a support request and sometimes requests a refund/compensation. Clear disclosure reduces these problems.

22. Market Security

Since the market system works with payment, balance, product delivery and RCON commands, it must be managed carefully in terms of security. Someone accessing the admin panel can change product prices, disrupt RCON commands, or make incorrect deliveries.

Suggestions for market safety:

• Market management should be open only to authorized admins.
• RCON commands should not be issued by unnecessary people.
• Product price changes should be checked.
• Manual deliveries must be recorded.
• Delivery should not be made until payment is completed.
• Coupon and campaign settings should be checked regularly.
• Order history should not be deleted.
• Suspicious orders and unsuccessful payment attempts should be investigated.

23. Common Mistakes

Missing product description

If the player does not know what the product delivers, when it will be delivered, or whether it needs to be online, he opens a support request. The product description should be clear.

Activating the product without testing the RCON command

Incorrect RCON command causes post-payment delivery issue. Every automatic delivery product must be tested.

Misspelling the player name variable

If the panel cannot convert the variable, the command runs incorrectly. The player name variable in the delivery command must be system compatible.

Entering the wrong price

If the product is released at the wrong price, players may purchase the product for the incorrect amount. The public market should be checked after the price change.

Post an empty category

The empty category makes the market look incomplete. If there is no product in the category, it should be kept inactive.

Ordering products manually without checking order history

The order may have already been delivered. Order and RCON logs should be checked before issuing manual products.

Sell very powerful products unlimitedly

Products that may disrupt the game economy or PvP balance should not be sold unlimitedly. Stock, limit or more careful pricing should be used.

24. Checklist Before Opening a Support Request

• Is the product active?
• Is the product under the correct category?
• Is the product price correct?
• Is the product description sufficient?
• Is the product image uploaded?
• Is the product in stock?
• Is the product delivered automatically or manually?
• Is the RCON command correct?
• Is the player name variable correct?
• Is the player's Minecraft username correct?
• Does the player need to be online?
• Is the order payment status successful?
• What is the order delivery status?
• Are there any errors in the RCON command history?
• Has the coupon been applied?
• Has the balance been deducted correctly?
• Has there been a successful response from the payment provider?
• If manual delivery was made, is there a record?

25. Security, Performance and Sales Recommendations

• Separate products into clear categories. The player should easily find the product he is looking for.
• Write detailed product descriptions. Incomplete disclosure increases support requests.
• Test RCON commands. This is mandatory for automatic delivery products.
• Optimize images. Large product images slow down the market page.
• Keep prices in line with the economy. Items that are too powerful can disrupt the game balance.
• Use stock and limit. Reduces abuse of limited products.
• Store order history. Required in case of payment and delivery problems.
• Limit market authorizations. Not every administrator should change the product price or RCON command.
• Check the price after coupon. Campaigns should not make products free.
• Test the public market on mobile. A significant portion of players can shop from their phones.

26. Frequently Asked Questions

I added a product but it does not appear in the market. From where?

The product may be inactive, the category may be inactive, the product may be out of stock or the public market cache may show old data. Product and category activity status should be checked.

The product was purchased but not delivered. What should I look for first?

Order status, payment status, product delivery type, RCON command, player name variable, Minecraft username and RCON command history should be checked first.

Is the RCON command required for every product?

No. The RCON command may not be required for products that will be delivered manually. However, if automatic delivery is desired, the correct RCON command must be defined for the product.

Does the player need to be online?

This depends on the command and plugin used. Some item commands may not work when the player is not online. If there is a requirement to be online in the product description, it must be stated.

I changed the product price, will old orders be affected?

Usually the new price applies to new orders. The recorded price of old orders does not change if they are stored separately. However, old order records should be checked for accounting and support.

Should the coupon work on all products?

It depends on the campaign policy. Working of high discount coupons on all products may result in loss of income. Using a specific category or product requirement is more controlled.

What should be written to the player for products with manual delivery?

In the product description, it should be stated that the delivery is manual, the approximate control time and if there is a problem, support must be opened with the order number.

Conclusion

Minecraft Web Panel Market Management menu is one of the most important management areas of the server used to organize web market products, create categories, set prices, write product descriptions, define RCON delivery commands and track orders. A properly structured market gives players confidence and simplifies the purchasing process.

While preparing market products, the category order, product name, description, price, image, activity, stock, delivery type, RCON command and player name variable should be carefully checked. Automatic delivery products must be tested, delivery must not be made before payment is completed, and order history must be monitored regularly.

When Market Management is used correctly, Minecraft Web Panel is more than just a promotional site; It turns into a professional sales and player services system that works with payment, balance, coupon, order, RCON and support processes. When configured incorrectly, player inconvenience, delivery errors, support congestion and loss of income may occur.

This article is specially prepared for PvPServer.