WeChat Mini Program Service Category Compliance Guide

A WeChat Mini Program service category should reflect the service users actually receive. The entity's name or business-license wording alone does not decide the category, and selecting more categories is not a substitute for holding the required qualifications.

Platform categories, supporting materials, and review practice change. Treat the current category table and submission console in the WeChat Official Accounts Platform as authoritative at the time of filing.

Four facts determine the category

1. The Mini Program entity

Confirm whether the account belongs to an enterprise, government body, media organization, other organization, or individual. Available categories and evidence differ by entity type.

2. What the user can actually do

List real functions—not marketing labels. Browsing information, purchasing goods, booking a service, consulting a professional, posting content, watching live video, storing value, or generating AI content can lead to different categories and controls.

3. Who provides the service

Distinguish a self-operated business from a platform that admits third-party merchants or providers. Marketplace, matching, and platform models often require additional category and governance evidence.

4. Who holds the qualification

The license or filing must belong to an accepted party, cover the actual service and region, and remain valid. A supplier's qualification cannot automatically be borrowed for the Mini Program operator's own regulated activity.

A six-step selection method

1. Build a page-and-function inventory from the current prototype and planned release.
2. Confirm account entity, contracting party, merchant model, service provider, payment recipient, and data controller.
3. Match every function against the current official category descriptions and applicable scope.
4. Create a function-category-evidence matrix with an owner and expiry date for each item.
5. Recheck the matrix against the test build; hidden entry points, copy, payments, and user-generated content still matter.
6. Only then lock the engineering and review schedule, including time for licenses, filings, or product changes.

For example, self-operated food sales, a multi-merchant marketplace, a public posting community, and an AI question-answering feature should be assessed as four different service patterns even when they appear in one Mini Program.

Common classification mistakes

• treating a marketplace as an ordinary self-operated shop;
• classifying paid training, live lessons, or recorded courses as simple corporate information;
• overlooking medical consultation, appointment, drug, or device functions;
• ignoring UGC, comments, communities, live streaming, or public sharing;
• treating AI text, image, face, or personified interaction as a generic utility without reviewing current AI rules;
• confusing industry information with news or current-affairs publishing;
• launching stored-value, prepaid, or membership balance functions without checking the operating model.

Evidence package

Prepare entity registration, administrator authorization, domain and account details, applicable industry licenses, platform or merchant-management documents, product screenshots, test instructions, privacy materials, user agreements, content-governance rules, complaint and takedown paths, and any required AI or data statements.

The exact package depends on the service. Wavesteam can map functions, identify technical controls, align the prototype and build with the declared category, and organize submission evidence. The client must confirm the operating facts, provide authentic qualifications, and obtain legal advice where the classification is uncertain.

Pre-submission check

• every accessible function has a matched category;
• the account entity and service provider are accurately described;
• qualifications are valid, correctly owned, and cover the activity;
• prototype, code, store copy, payments, privacy text, and submission answers agree;
• UGC, complaints, reporting, moderation, and customer-service paths work where needed;
• reviewer accounts and test data remain available;
• later-release functions are disabled in production, not merely omitted from screenshots.

Do not hide an unqualified function for review and reopen it afterward. If no official category clearly matches, reduce the release scope and request platform or professional guidance before development proceeds.