1. Give each item its own reference and record
Digital products that look similar can have very different conditions. Use an internal reference for each item and record the game, platform, server, contents and limitations. Keep necessary provenance and permission evidence in a private area. Account credentials and recovery information must not appear in public product names, descriptions or promotional images.
If an item can be sold only once, its state must match what is still available for delivery. Check other sales channels too: a sale in chat can make the website's stock inaccurate. Assign responsibility for updating availability and checking pending items. If records disagree, pause the uncertain listing until you have checked it rather than guessing that the item is still available.
2. Distinguish order states from assumptions about success
A created order may be unpaid. An order with submitted evidence may still need verification, and a paid order may still await delivery. Keep these stages distinct in the way you operate the store. You should be able to look at a record and understand the next check. Do not use one success label to mean that a request was received, payment was verified and the customer received the product.
Use the order reference across every support channel. If a customer contacts you repeatedly, check whether the messages concern the same order before doing the work again. Record verification and delivery details needed to investigate issues. Change states through an authorized process that leaves a trace, rather than rewriting history simply to make a report show fewer pending orders.
- Awaiting payment: money has not yet been confirmed
- Awaiting review: information arrived but needs verification
- Ready for delivery: the required checks have passed
- Delivered: the outcome has a reference you can investigate
3. Verify payment through a trustworthy source before delivery
A payment screenshot or a customer message can support a review, but neither is sufficient proof that funds arrived. Verify the recipient, amount, transaction reference and connection to the order through a channel your store is authorized to use. If the system or provider cannot verify the payment, leave the item pending and investigate. Do not mark it paid merely because you assume a delay is a technical problem.
When a result is unclear, separate customer assistance from product delivery. Request only the information needed to resolve the order, never a customer's banking password or verification code. Avoid automatically repeating financial requests to see whether a provider has recovered. Check an existing reference before creating another record so an uncertain result does not lead to duplicate actions.
4. Protect the owner account and customer information
Use a password you do not reuse on other services and enable two-step verification where it is available. Keep recovery codes accessible only to the responsible person. Separate accounts or permissions according to the capabilities your system provides, and review access when staff change. Do not share the main password in a group chat or let everyone use the owner account without a way to identify who performed an action.
Customer information and product access details belong behind access controls. Only people who need them for their work should be able to view them. Redact personal details from screenshots used for support. Sign out when finishing work on a shared device and review access to the owner's email account too, because email is often involved in account recovery and important notifications.
5. Deliver as described and retain only useful evidence
Before selling, define what the customer receives, the delivery channel and the checks they should make. Before revealing sensitive information, verify the recipient and order reference. Do not deliver credentials in public comments. If transfer requires multiple steps, explain them in order and identify when the customer should contact the store rather than continue alone.
Keep evidence that helps verify the work and investigate problems, restrict access, and review information that is no longer needed. Transaction history and private evidence images can have different retention needs. Do not remove financial history just because an item is sold out, and do not reuse a customer's information as a review without their permission.
6. Establish a daily check and prepare for interruptions
At the start of each work session, review orders awaiting verification or delivery and customers awaiting a response. Check inventory at risk of being sold twice and whether the public information still matches your actual process. After changing a price, condition or contact channel, check the public page again. Small, regular checks help reveal issues before they accumulate into a difficult backlog.
Prepare a response when a service is unavailable: pause orders you cannot verify, give customers accurate information, and keep references for follow-up. Check what backups cover and whether restoration has been tested separately from the live store. Do not assume everything can be restored without testing it. Continue reviewing game-provider terms too; maintaining a store system does not change the right to transfer an account.
- Review pending work and assign the next step
- Check unique items and other sales channels
- Review administrator access and public information
- Keep support contacts and investigation references available