12 parts · 22 checkpoints · Take away: 7 records · 1 note
Show all 12 parts
- 01What will the license support?
- 02Choose the role before deciding what the license covers
- 03Test the entity against the next action, has a checkpoint, has a work product
- 04Compare entity forms and real capital obligations
- 05Prepare registration for the real business, then check payments separately
- 06After the license, put responsibilities on the calendar, has a checkpoint
- 07Records should explain the business impact and be easy to retrieve, has a checkpoint
- 08Use three layers of facts to explain identity and responsibility, has a checkpoint, has a work product
- 09Turn the facts into a usable handover pack
- 10Protect open orders, money and duties before changing entities, has a checkpoint, has a work product
- 11Find the first evidence behind an operating conflict, has a checkpoint
- 12Keep a record someone can review and use, has a checkpoint, has a work product
What will the license support?
A China business license identifies a registered business. You still need to explain who contracts with suppliers, who sells to customers, which account receives the money, and who handles refunds and support. This lesson compares a China individual business with a China limited liability company and builds a record you can revisit. You can start with no entity or check an existing business; no earlier lesson is required.
The operating entity is the business or person responsible for a particular activity. A company is a legal person; its legal representative is a human acting for it. They are different roles. “Limited liability company” and “individual business” here refer to Mainland China forms, not US LLC or sole-proprietor formation rules.
Classroom case: a Zhejiang supplier and a US target market
- Travel tumbler capacity (oz)
- 20
- Planned first batch (units)
- 300
Suppose you plan to buy 300 stainless-steel 20oz travel tumblers from a Zhejiang supplier, sell to US customers through Shopify, and use Meta and Google ads. The supplier wants a formal contract, the payment provider needs merchant records, and the store needs clear support and refund responsibilities. This is a teaching plan, not an observed sale or approval. The target market alone does not choose the entity’s jurisdiction.
There are three separate checks: registration and the license establish the business record; particular products or activities may require permits or approval; banks and payment providers review the merchant, people, business, account and beneficiary. Tax and ongoing filings have their own requirements. Progress on one check tells you about that check only.
A payout is a transfer of settled funds from a payment provider to the receiving account. The beneficiary is the named account holder. Record customer receipts, bank receipts and supplier payments separately so each part of the money flow has an accountable owner.
Choose the role before deciding what the license covers
One entity can serve several roles. Start with the activity that currently needs it. The main-operator example is shown first for reading; it is not a recommendation for your business. For each role, compare its use, the remaining conditions and the next check.
What role does this domestic entity have?
- Role
- You plan to use this entity for purchasing, contracts, banking, tax filing schedule, and team operations.
- Supports
- China-side supply contracts, business banking, contract records and clear team finance roles.
- Still to verify
- Does not automatically solve overseas payouts, payment-gateway support, or target-market compliance.
- Next check
- Check payment eligibility, then determine whether another jurisdiction’s entity or account is needed.
- Role
- You use it for supplier, warehouse and service contracts, invoices and business-account payments.
- Supports
- Purchase contracts, invoice title, reimbursement, and cost records.
- Still to verify
- Payout eligibility and customer-facing responsibilities still need their own evidence.
- Next check
- Check purchasing, payout, and storefront disclosure as three separate evidence chains.
- Role
- You use it as one proof item for platform, payment, bank, or partner review.
- Supports
- Business proof, address proof, responsible-person records, contracts, and invoice archive.
- Still to verify
- A provider still reviews the documents against its own requirements; evidence alone does not guarantee approval.
- Next check
- Check the entity type required by payment, ads, platforms, and banks one by one.
- Role
- You are running early tests and using a domestic entity for local operations, with later arrangements determined by the actual payment requirements.
- Supports
- Early purchasing, service contracts and basic finance records.
- Still to verify
- Check the target payment path and its entity requirements.
- Next check
- Set a review date to decide whether the entity or payment setup needs to change.
Split the case into purchasing, payments, team finance and public storefront information. The contracting company, payment merchant, bank beneficiary and customer-facing seller can have different roles, but each relationship needs evidence and must fit the applicable rules. If a brand or return warehouse differs from the registered name or address, explain the role rather than entering false information to make the text match.
Four operating boundaries
- What the domestic entity supports
- Supplier contracts, invoices, business settlement, and cost records.
- What remains open
- Overseas payouts, target-market tax, and overseas buyer trust.
- Check first
- Whether contract, invoice path, and business account can match.
- What the domestic entity supports
- Provides business proof, address, and responsible-person records.
- What remains open
- Whether the target gateway accepts a domestic entity cannot be guessed.
- Check first
- Check target gateway, ad account, and platform document requirements one by one.
- What the domestic entity supports
- Separate business funds, reimbursements, team roles and a named finance owner.
- What remains open
- Responsibility for cross-border receipts and payments, another entity’s duties and applicable overseas tax.
- Check first
- Whether someone is responsible for business banking, invoices, contracts, and tax filing schedule.
- What the domestic entity supports
- Company name, address, support email and policies can identify the same operator and its responsibilities.
- What remains open
- Local buyer trust, return address, and market compliance still need separate review.
- Check first
- Whether policies, payout entity, return language, and support records conflict.
Continues from
Carry the identity decision into store setup
Continue with General settings for merchant names, contacts and addresses, and Payments and payouts for the gateway and beneficiary. Establish responsibility here before filling the actual English admin fields.
Test the entity against the next action
“Can I open a store with this license?” is too broad. Supplier contracts, ad verification, policy pages and customer payments require different evidence. Choose the next action, then read what the entity covers, what it leaves open and which evidence comes first.
A SKU identifies a particular product or variant; PDP means product detail page. Meta Business Portfolio manages business assets and permissions. Pixel/CAPI carry website or server events. A license can support business verification, while control of these assets requires its own evidence.
The earliest action you need to take
- Current action
- Use it for contracts covering samples, the first batch, photography props, warehousing or inspection services.
- Can cover
- Can cover purchasing responsibility, invoice title, business payment, cost archive, and supplier communication records.
- Does not establish
- Cannot prove overseas refund responsibility, target-market tax position, payment entity, or support promise.
- First evidence
- Purchase contract, quote, invoice title, business payment record, SKU list, and supplier contact.
- Next route
- If purchasing is blocked, fix domestic records first. Before live checkout, verify the gateway and determine whether an overseas entity is needed.
- Current action
- Use it to document the operator and records owner for ad platforms, SaaS vendors, partners or service providers.
- Can cover
- Can provide company name, address, responsible person, business scope, contracts, and basic diligence records.
- Does not establish
- Cannot replace Business Portfolio control, ad billing path, domain verification, Pixel/CAPI asset control, or recovery access.
- First evidence
- Business license, address proof, ad account business info, domain-verification screenshot, and asset admin list.
- Next route
- If the issue is ad asset control, move to Meta/Google asset lessons; do not use the license to hide permission problems.
- Current action
- Use it to explain merchant identity and duties across Contact, Privacy, Refund, Terms and order emails.
- Can cover
- Can explain who operates, who supports, who handles returns, who keeps records, and what the China-side contact path is.
- Does not establish
- The return address, billing descriptor, warehouse, privacy contact and entity still need clearly related roles.
- First evidence
- Policy screenshots, support-email test, return-address note, billing descriptor, and privacy-contact record.
- Next route
- If public records are not explainable, go back to policy and compliance pages before launch QA.
- Current action
- Use it as one piece of evidence for China-side sourcing and operations.
- Can cover
- Can add review documents, purchasing proof, address records, and domestic account boundaries.
- Does not establish
- Cannot directly replace the local company, local bank, actual-operations proof, or overseas tax boundary required by the target payment path.
- First evidence
- Supported country list, merchant-entity requirement, bank beneficiary, payout terms, and storefront merchant identity.
- Next route
- Before cross-border checkout, verify the chosen provider’s merchant, account and verification requirements. Then decide whether another entity is needed.
Tumbler case: four jobs for the same license
Supply chain
- Use
- Sign China-side purchase contracts, issue invoices, pay through a business account, and keep sample or first-batch records.
- Limit
- It does not prove refund responsibility, overseas tax position, or payment entity for US buyers.
- Next action
- Put supplier contract, invoice title, SKU list, and business scope into one evidence sheet.
Payment review
- Use
- Act as one proof that you have a real China-side sourcing and operating base.
- Limit
- If the gateway requires a US, UK, Hong Kong, or other local company or bank account, the China license does not replace it.
- Next action
- Check supported regions, merchant entity type, bank beneficiary, and policy-page identity before checkout.
Storefront disclosure
- Use
- Support Contact, Refund, and Privacy pages that explain the China-side operator, support email, and record responsibility.
- Limit
- A return address, support email and payment descriptor need to trace to an explainable merchant and set of duties.
- Next action
- Write a merchant identity map: operator, support team, return handler, and refund responsibility.
Capital and scope
- Use
- Cover realistic ecommerce, trading, technical service, or import/export activities where relevant.
- Limit
- High registered capital is not credibility, and vague scope does not cover high-risk claims.
- Next action
- Use the next 1-3 years of real operations to set capital and use core SKUs to test scope.
In the case, the purchasing owner checks the contract, invoice title, payer and SKU. The payments owner keeps the provider requirements and merchant-to-bank relationship. The storefront owner establishes who provides support and refunds. Each person should be able to locate the relevant record and name its owner.
Each group has its own manual save, restore and clear controls. A button applies to that group only. Copy and download use the current inputs; each JSON backup contains that group’s fields and readable text. For a handover, keep the relevant group backups and the combined note at the end. If copying fails, select the visible note and copy it manually. Record status, roles and controlled file locations, not identity numbers, full home addresses, bank numbers, passwords or customer data.
Record the immediate action
Start with item 1.
China-side purchasing, payment review, policy pages, tax and banking, or overseas entity setup.
License type, business scope, responsible-person/address records, supplier contract, bank/tax status, payment requirements, and policy screenshots.
Choose entity type, check target gateway, repair scope or record consistency, or move into overseas entity/payment setup.
Not saved yet.
Kept in this browser only. Switching device or clearing browser data removes it; download a copy.
Compare entity forms and real capital obligations
Compare the contracts, people, money and responsibilities you expect to manage. An individual business may fit small solo tests. A company provides a structure for shareholders, staff and company finances. Actual formation and maintenance work depends on the activity, location and arrangements; the form alone guarantees neither lower costs nor payment approval.
Compare the entity forms
- Possible uses
- Solo validation, small-scale tests, and lightweight operations.
- Potential benefit
- Compare local filing, accounting and upkeep requirements to see whether a solo test needs a more complex structure; actual costs depend on the business.
- Responsibility and cost
- Civil Code Article 56 distinguishes personal and family property liability according to how the business is operated. Assess cooperation, branding, staffing and financing separately.
- Decision rule
- If you are still validating, do not complicate the entity just to look formal.
- Possible uses
- Long-term operation, team collaboration, business banking, and brand building.
- Potential benefit
- Clearer structure for contracts, finance, team roles, and regulated operations.
- Responsibility and cost
- Plan for formation procedures, tax, ongoing administration and capital-contribution duties.
- Decision rule
- If staffing, financing or formal cooperation is likely in the next 6–12 months, include company governance, finance and ongoing duties in the comparison before deciding.
Under PRC Civil Code Article 56, an individual business’s debts are borne by personal property for personal operations, by family property for family operations, and by family property where the two cannot be distinguished. A limited liability company bears debts with company property, and shareholders generally have liability up to their subscribed contributions. Statutory exceptions, including abuse of the company’s separate status or failure to separate property, can create further liability. Keep company funds and personal spending distinct in practice.
Registered capital is a contribution obligation. Company Law Article 47 generally requires shareholders of a newly formed limited liability company to pay subscribed contributions in full within five years of formation, subject to applicable statutory exceptions. This does not make every business viable without working funds. A larger figure is not a platform-trust score. Use a realistic one-to-three-year operating plan, contribution capacity and risk assessment, then confirm the applicable position with a qualified adviser.
Before filing, founders should record each person's subscribed contribution, planned payment dates and continuing responsibilities. Resolve disagreements about the contributions or articles of association before submitting the registration, using the applicable rules and qualified advice where needed.
Older companies have transition rules. Under the provisions published on 1 July 2024, an LLC registered before 30 June 2024 whose remaining contribution term exceeds five years from 1 July 2027 generally needs to adjust that term to within five years by 30 June 2027; any exception must be confirmed under the rules. Clearly abnormal terms or amounts can also require adjustment. Check an existing company’s formation date, articles and remaining term rather than applying a new company’s starting date.
Prepare registration for the real business, then check payments separately
Check the proposed name against the brand, domain and trademarks, including readability for international customers. A name search does not grant trademark rights. The registered scope should explain actual products, services, purchases, sales and invoices. Add import/export, warehousing or restricted categories only where they reflect the business and meet the applicable rules. Distinguish general activities from licensed activities; extra wording does not obtain a permit.
Choose entity type and business scope first
Choose an individual business or company, then establish whether the real activity includes ecommerce, technical services, consulting, import/export or other work.
Keep as evidence
Keep the link between the entity form, actual SKUs and scope.Prepare address and identity records
Check address use, lease or property evidence and identity records together, including the right to use the premises.
Keep as evidence
Confirm address use, acceptable evidence and the custodian of identity records.Submit registration online
Submit through the applicable local business-registration or government service and check each document against its current list.
Keep as evidence
Find the applicable local service through the national registration entry point and use its forms.Receive electronic or paper license
After receiving the license, hand over banking, tax, contracts and storefront records so the business can operate and maintain them.
Keep as evidence
Check the registration particulars and retain the current version and verification entry point.Continue tax, banking, and records
Put tax filings, business banking, contracts, invoices, policies and archives on the task list.
Keep as evidence
Assign banking, tax, contracts, invoices, policies and archives to named owners.
The SAMR registration service links to formation, changes, cancellation, name and business-scope searches, and guidance for obtaining, presenting and verifying an electronic license. Confirm the local service, address evidence and how to obtain and retain the electronic license before proceeding. Confirm documents for the location and entity type. Applicants are responsible for their truthfulness, legality and validity. Electronic and paper business licenses have equal legal effect. Check the name, domicile, people, scope and version, and handle required changes or permits. The lesson’s five-to-ten-day estimate is a study and preparation window, not a government, bank or provider turnaround promise.
Check the payment provider’s current page for the actual region. On 17 October 2026, Shopify Payments for Mainland China was in invitation-only early access. The regional requirements address eligible Mainland-registered businesses making cross-border sales, with WorldFirst and verification requirements. A license does not automatically qualify the merchant. This path does not support sales to customers within Mainland China. Availability, account eligibility and settlement details depend on the invitation, setup and review.
Read both the Mainland China overview and requirements. Hong Kong SAR has a separate requirements page, covering physical operations, identity records, Hong Kong HKD banking and matching beneficiary records. A Hong Kong registration certificate alone does not establish eligibility. Check the Mainland or other applicable path before concluding that an overseas entity is necessary.
After the license, put responsibilities on the calendar
Use a thirty-day planning board after licensing: task, owner, evidence and next reminder. Thirty days is a classroom planning window, not permission to defer a legal or provider deadline. No revenue does not by itself eliminate tax, annual-report or change-reporting duties. Check the actual status and keep the professional confirmation.
The worked example marks banking and tax, giving 2/6: those two have retrievable records and the other four still need work. Your checklist below starts empty. Tick only items you can support with evidence; the sample does not count as your completed work.
Hold
Evidence still to collect
Six items reported checked; prepare the review
For banking, record account purpose, permissions and the division between finance and operations. For tax, record taxpayer status, filing periods and the owner. Schedule annual reporting and changes to registration particulars. Connect contract and invoice templates to purchasing reconciliation. Keep policies, support and supplier records on the current version and archive the old versions.
Records should explain the business impact and be easy to retrieve
A name difference can affect money, asset handover or a customer’s claim. Identify the affected activity, then choose the repair and supporting evidence.
When names differ, identify the affected activity
Payment and payout
- Difference
- Policy pages show the domestic company, the payment account uses a personal name, and the bank beneficiary is another company.
- Business impact
- Reviewers may question who is responsible for transactions and refunds; payout, refund, and chargeback explanations become harder.
- Repair
- Write a payment role sheet first: storefront merchant, payment account, bank beneficiary, and refund lead.
Ad account proof
- Difference
- The license, Business Portfolio, ad billing, domain, and Pixel/CAPI assets belong to different people or entities.
- Business impact
- Account recovery, risk review, and asset handover can stall; even paid traffic may not prove who controls the assets.
- Repair
- Put ad asset control, billing method, domain verification, and license screenshots into one asset sheet.
Invoices and tax
- Difference
- The supplier contract, invoice title, payer, registered scope and actual SKUs point to different entities or activities.
- Business impact
- Cost recording, reimbursement, filings and supplier checks become harder to reconcile, obscuring the business’s actual profit.
- Repair
- Line up core SKUs, contract entity, invoice title, payment account, and business scope in one record-chain table.
Refunds and disputes
- Difference
- Contact email, return address, billing descriptor, payment entity, and public merchant identity do not show who is responsible.
- Business impact
- Buyer trust drops and support cost rises; platforms may also reject explanations during refunds, chargebacks, or privacy requests.
- Repair
- Align merchant identity and responsibility across Contact, Refund, Privacy, order emails, and support templates.
Prepare the following six evidence categories. They answer different questions about registration, addresses, money, tax, customer responsibility and purchasing. A license screenshot alone cannot do all six jobs. Try a five-minute retrieval exercise: ask another owner to locate the current version, explain its purpose and find the next review date. Five minutes is a classroom retrieval goal, not an official review deadline.
Six record categories and where to keep them
License and verification
- Fields to check
- Legal name, unified social credit code, representative or operator, domicile, scope, formation date, version and check date.
- Question it answers
- Identify the operator and the current registration record.
- Storage and handover
- Registration folder, with a verification entry point and controlled file location.
Addresses and premises
- Fields to check
- Registered, operating, warehouse and return addresses; lease or use evidence, contacts and the role of each address.
- Question it answers
- Explain different addresses and which review or return task each can support.
- Storage and handover
- Separate folders by address purpose; a warehouse is not automatically the registered address.
Banking and payments
- Fields to check
- Account status, name, bank, currency and beneficiary; distinguish ad charges, supplier payments, customer payments and payouts.
- Question it answers
- Separate company funds, purchasing payments and store receipts; connect them to the account roles in cash planning.
- Storage and handover
- Controlled finance records; put only roles and status in learning notes.
Tax and invoices
- Fields to check
- Taxpayer status, filing period, invoice title, owner and first reminder date.
- Question it answers
- Put applicable duties, open questions and actual documents on the calendar.
- Storage and handover
- Finance calendar and invoice archive, including the accountant’s confirmation.
Policies and contacts
- Fields to check
- Contact, Refund, Privacy and Terms URLs; merchant, support and return roles, version, date and owner.
- Question it answers
- Let customers find who handles service, refunds and privacy requests.
- Storage and handover
- Policy version archive, synchronized with order emails and support templates.
Supplier contracts and SKUs
- Fields to check
- Supplier, contracting entity, SKU and category, invoice title, payment, delivery, compensation and inventory responsibility.
- Question it answers
- Connect the purchase, registered scope and cost record to the same transaction.
- Storage and handover
- Contract and SKU purchasing archive, including handover and reconciliation records.
A second worked example ticks only the name item, giving 1/6. It has a name record but still needs account, settlement, scope, storefront and refund-responsibility checks. Your checklist starts empty and counts only your own ticks.
Hold
Evidence still to collect
Six record categories reported checked
Use three layers of facts to explain identity and responsibility
For each topic, keep three layers of facts: the value in registration or review requirements, the actual or planned value on the store or account, and evidence explaining their relationship. Then select same, explainable difference or unclear. “Same” records your judgment and still needs a version check. Blank means unreviewed.
First set aside differences in case and whitespace, then decide whether the records refer to the same registered fact. “River Desk Ltd” and “river desk ltd” may differ only in formatting. “Example A Trading Co.” and “Example B Trading Co.” require checking whether they are different entities. The prompt below flags a writing difference for review; it does not establish an identity conflict. Follow the provider’s exact spelling and punctuation requirements when filling its forms.
Legal name and brand/store name
A brand name can differ, but applicable footer, Contact, policy, or payment records must let buyers and reviewers trace the legal merchant. Do not substitute a marketing name where a payment form requires the legal name.
Pause for review when the website, payment account, and bank records look like three unrelated merchants with no role explanation or proof.
Legal name and brand/store name
Start with item 1.
Not saved yet.
Kept in this browser only. Switching device or clearing browser data removes it; download a copy.
Writing differs: review the relationship
Same legal record
Different but explainable
Not yet explainable
Note
Not reviewed yet
Registered address and operating/return address
Registration, warehouse, and return addresses can differ when each address has an explainable purpose, contact path, and evidence. Do not present an unverified address as the office, return, or bank-record address.
Pause for review when support, privacy, returns, and payment records use conflicting addresses and the team cannot explain which entity is responsible.
Registered address and operating/return address
Start with item 1.
Not saved yet.
Kept in this browser only. Switching device or clearing browser data removes it; download a copy.
Writing differs: review the relationship
Same legal record
Different but explainable
Not yet explainable
Note
Not reviewed yet
Payout beneficiary and payment account
Account representative, legal merchant, and beneficiary can differ only when the target payment path explicitly allows it and records prove the relationship. Do not enter account numbers, identity numbers, or passwords in this kit.
Pause for review when the payment account or bank beneficiary uses another entity or personal name with no provider rule, authorization relationship, or responsibility explanation.
Payout beneficiary and payment account
Start with item 1.
Not saved yet.
Kept in this browser only. Switching device or clearing browser data removes it; download a copy.
Writing differs: review the relationship
Same legal record
Different but explainable
Not yet explainable
Note
Not reviewed yet
Website information and responsibility chain
Support email, overseas warehouse, and return handler can differ from the registered entity, but public pages must explain the responsibility boundary and align with payment, refund, and privacy records.
Pause for review when buyers cannot tell from the website and order email who handles refunds, privacy, or disputes, or the billing descriptor cannot trace back to the same merchant.
Website information and responsibility chain
Start with item 1.
Not saved yet.
Kept in this browser only. Switching device or clearing browser data removes it; download a copy.
Writing differs: review the relationship
Same legal record
Different but explainable
Not yet explainable
Note
Not reviewed yet
Turn the facts into a usable handover pack
The purpose determines the evidence pack. Choose purchasing, payment review or public responsibility to compare a strong pack with a weak one. The purchasing pack is simply the first reading example. This selection, the migration checklist and its quiz share one separately saved group; the four fact records keep their own saves.
Which evidence pack do you need?
- Reviewable pack
- Business license and scope, core SKU/category note, supplier contract, invoice title, business payment or explainable payment record, and the archive location.
- Weak pack
- Only a license screenshot is supplied while contract, invoice, payer, and actual goods point to different entities or categories.
- Interpretation
- This pack lets suppliers, finance, and later review understand purchasing responsibility, cost records, and the real product category.
- Reviewable pack
- Current target-path entity requirements, legal merchant name, account-representative record, bank beneficiary name, storefront merchant explanation, and the role plus evidence behind every difference.
- Weak pack
- A brand or personal name substitutes for the legal record the path requires, and screenshots are assembled only after more documents are requested.
- Interpretation
- Shopify and third-party paths review against their own requirements. A domestic license can be one operating proof, not a promise of payment eligibility, banking, or payouts.
- Reviewable pack
- Footer and Contact merchant information, Privacy/Refund/Return pages, support-email test, return-address explanation, order-email version, and responsible lead plus review date.
- Weak pack
- The site shows a brand, the refund page has no entity, the return address and support email have no role explanation, and the billing descriptor cannot be connected.
- Interpretation
- A brand can use a different name, but buyers, payment review, and dispute handling still need to trace who operates, refunds, and handles privacy.
Protect open orders, money and duties before changing entities
Moving from an individual business to a company, changing a payment account or changing the public merchant description can affect existing orders. Map current and proposed roles and an effective date. List dependencies across domains, ad assets, Pixel/CAPI, payments, banking, policies, support and suppliers. Reconcile open orders, refunds, chargebacks, payouts, inventory and supplier payables, with a named owner for the cutover record.
Hold
Evidence still to collect
Five items reported checked; send them for owner review
Plan controlled tests, notifications and support handover under the provider’s requirements. Keep the old versions, rollback conditions and a pause window. If accounts, outstanding balances or customer duties remain unexplained, pause the affected live checkout, public change or scaling action. This planning exercise does not authorize changes to real accounts, messages, orders, payments or refunds.
Self-check not answered
Changing public identity first disconnects it from old-order duties. Start with the order, refund, payout and record-dependency map.
Protect customer duties, money and explainable records first; then update public pages and growth activity.
A new account alone leaves duties unresolved. Payment records, public identity, refunds and open orders need one cutover record.
Note
Not answered yet
Save the pack, five checks and migration answer
Start with item 1; your choices in the exercises above are carried over.
Not saved yet.
Kept in this browser only. Switching device or clearing browser data removes it; download a copy.
Find the first evidence behind an operating conflict
Matching names are only a starting point. Suppose a Hangzhou company’s license is mixed with a personal PayPal account, a friend’s Meta Business Portfolio, a free Gmail support address and a footer with no merchant identity. Pause live checkout and ad scaling while mapping asset control, seller, beneficiary and refund owner. A free email address is not itself evidence of illegality; the issue is control and explainable responsibility. Check the bank beneficiary, domain verification, contact-email test and policy versions before choosing the repair.
Four common record conflicts
Storefront policies
- Observed difference
- The license is a Hangzhou company, Contact uses a personal Gmail, the return address is an overseas warehouse, and Privacy has no company name.
- Impact
- Users, payment review, and dispute handling see three identities: domestic entity, personal inbox, and overseas return point. This combination can work only if it is explainable.
- Repair
- Align policies to one merchant identity: company name, support email, return handler, refund responsibility, and privacy contact each need a clear role.
- Evidence
- Keep the license, Contact / Return / Privacy screenshots, support-email test, and return-address explanation.
Payment account
- Observed difference
- The website shows a domestic company, PayPal or Stripe uses a personal name, and the payout bank belongs to another entity or person.
- Impact
- Payment paths care about transaction responsibility, refund responsibility, and control of funds. Inconsistent entities make the records look stitched together.
- Repair
- Confirm which entity type the target payment path accepts, then define how domestic entity, overseas entity, bank account, and storefront disclosure split roles.
- Evidence
- Keep payment entity requirements, account screenshots, bank records, and storefront-policy entity explanation.
Payment, ads, and support mismatch together
- Observed difference
- The license is Hangzhou Company A, PayPal uses the founder’s personal name, Meta Business Portfolio belongs to a friend’s company, support still uses a free Gmail, and the footer has no company name.
- Impact
- This mismatch affects payment KYC, ad account review, buyer refund questions, and chargeback evidence at the same time. The unresolved issue is responsibility for the store, money, ad assets and support, beyond the wording of the names.
- Repair
- Pause live checkout and ad scaling first. Build one entity role table: storefront identity, payment account, ad assets, support, and refund responsibility. Keep evidence for explainable differences and align or split the path where it cannot be explained.
- Evidence
- Keep the license, PayPal/payment profile, Meta Business Portfolio screenshot, domain verification, support email test, Contact / Refund / Privacy / Terms versions, and bank beneficiary name.
Domestic purchasing chain
- Observed difference
- Supplier contract, invoice title, business payment, and actual store category do not match, and business scope does not cover the core activity.
- Impact
- This affects cost records, reimbursement, tax explanation, and partner review. A license proves the entity exists, but not that the operating chain is clear.
- Repair
- Put supplier contract, invoice, business payment, SKU category, and business scope in one sheet, then identify mismatched fields.
- Evidence
- Keep contract template, invoice title, reconciliation sheet, business-scope screenshot, and category note.
A Hangzhou registration, overseas return warehouse and separate support email may each have a valid role. Document address purposes, contact routes and the responsible operator in Privacy, then check the payment requirements. Where contracts, invoices, payer or SKU scope differ, reconcile the same purchase across category, money and responsibility. A license does not automatically resolve ad-asset ownership, billing, domain control, Pixel/CAPI or account recovery.
Which evidence folder needs attention first?
- Keep
- License screenshot, unified social credit code, business scope, registration date, address, and status.
- Used for
- Used for supplier contracts, invoice title, platform business proof, and dispute explanation.
- Weak signal
- Business scope cannot explain the real SKU, product claim, or ad promise.
- Next action
- Put core SKU, PDP claims, and business scope into one table; pause unclear categories first.
- Keep
- Responsible-person name, identity record, address proof, support email, phone, and policy-page presentation.
- Used for
- Used for payment review, ad account records, support disputes, privacy contact, and return responsibility.
- Weak signal
- Contact, Privacy, Refund, order email, and payment profile look like different operators.
- Next action
- Map merchant identity first: operator, support, refund lead, and privacy contact, then sync pages.
- Keep
- Business-bank status, tax filing schedule, invoice title, contract template, payment records, and archive folder.
- Used for
- Used for business payments, cost records, finance review, supplier diligence, and team responsibility.
- Weak signal
- License exists, but bank, tax, contracts, and invoices have no responsible person.
- Next action
- Assign owners for banking, tax, contracts, invoices and archives. Put their actual due dates on the thirty-day classroom planning board.
- Keep
- Payment-path entity requirements, account screenshots, bank beneficiary, Shopify store profile, policy pages, and billing descriptor.
- Used for
- Use it to assess the provider’s requirements and whether another entity or payment path needs further review.
- Weak signal
- Storefront entity, payout entity, bank beneficiary, and refund responsibility cannot form one record chain.
- Next action
- Pause live checkout or ad scaling first, then repair payment path and policy-page entity explanation.
When a problem appears, read the signal and unsafe move before choosing the first evidence, repair target and pause condition. The five situations below require different responses; renaming fields or resubmitting repeatedly does not replace a review.
Should this issue proceed or pause?
- Signal
- The policy pages show a domestic company, but PayPal, Stripe, a third-party processor, or payout bank uses a personal name, another company, or another jurisdiction.
- Unsafe move
- Finish the store first and explain the entity only after payment review or payout gets blocked.
- Proceed or pause
- Pause live payment setup; first write how merchant identity, payment account, refund responsibility, and payout bank split roles.
- First evidence
- Target payment entity requirements, account screenshots, bank beneficiary name, and Contact / Privacy / Refund / Terms pages.
- Repair target
- Payment profile, payout account, policy pages, support email, and refund-responsibility language.
- Pause condition
- Do not open live checkout or scale ads until payment entity, storefront entity, and refund responsibility are explainable.
- Signal
- The license scope is mostly consulting or technical services, while the store plans to sell strong-claim, restricted, high-return-risk, or permit-sensitive products.
- Unsafe move
- Assume broad words cover every category and launch first to see whether platforms notice.
- Proceed or pause
- Pause high-risk categories or strong claims; check business scope, SKU list, supplier contract, and target-market restrictions.
- First evidence
- License business scope, core SKU list, product claims, supplier contract, and any permit or restricted-goods list.
- Repair target
- Business scope, product catalog, product-page claims, purchasing contract, and platform product category.
- Pause condition
- If scope and category cannot be explained, do not launch high-risk SKUs or write claims stronger than the evidence.
- Signal
- License address, Contact email, return address, privacy contact, and billing descriptor look like five different operators.
- Unsafe move
- Assume buyers will not check these details and hide or scatter them across pages.
- Proceed or pause
- Create a merchant identity map first: who operates, who supports, who handles returns, and who is responsible for privacy and refunds.
- First evidence
- License, address proof, Contact / Return / Privacy pages, support email test, and return-address explanation.
- Repair target
- Footer, Contact, Privacy, Refund, Return, order email, and support templates.
- Pause condition
- Do not enter launch QA until the public merchant identity has one consistent explanation.
- Signal
- The license is issued, but business banking, tax filing schedule, contracts, invoices, and archive have no responsible person or due date.
- Unsafe move
- Treating "license done" as proof that every post-license requirement is ready, then starting purchasing, ads, or large contracts.
- Proceed or pause
- Create a 30-day post-license board: banking, tax, contracts, invoices, archive, and policy sync each need a responsible person.
- First evidence
- License issue date, bank-account status, tax status, contract template, invoice title, and archive path.
- Repair target
- Business bank account, tax calendar, contract and invoice templates, archive folder, and review schedule.
- Pause condition
- Do not sign large purchases, scale ad spend, or treat entity readiness as complete until post-license duties have responsible people.
- Signal
- The target payment path or platform asks for overseas entity, local bank, or operating proof, but the team treats a domestic license as the answer.
- Unsafe move
- Keep building and advertising, hoping to explain it during review.
- Proceed or pause
- Split domestic purchasing entity from overseas payout entity; move into the overseas entity or payment-gateway lesson when needed.
- First evidence
- Gateway region requirements, supported-country list, bank-account requirements, storefront entity, and refund-responsibility language.
- Repair target
- Entity boundary sheet, overseas entity plan, payment path, policy pages, and next-route domestic entity boundary record.
- Pause condition
- Do not mark payment ready for launch until domestic and overseas roles are separated.
Self-check not answered
Payment is an early setup condition. Leaving it until the end pushes the entity risk into later work.
The domestic entity supports domestic operations. Verify overseas payouts and the target gateway separately.
Registered capital carries real contribution obligations; setting it high for appearances can create future responsibility.
Choose for your purchasing, payments, team and target market, rather than copying another seller’s entity.
Note
Not answered yet
Keep a record someone can review and use
Use short entries for this week’s action, the live activity to pause, official or professional questions and the review date. Each text field allows up to 2,000 characters. Keep longer documents in controlled storage and note their location and version. The old page had unbounded inputs, so restoring a short record does not demonstrate lossless import of an arbitrarily long draft. Back up any longer original separately.
Record the pause and review
Start with item 1.
Do not use a China license as the overseas compliance answer; do not submit payment review while entity and payout records conflict; do not inflate registered capital.
Review banking, tax, contracts, invoices and policies within the thirty-day classroom plan, checking actual deadlines separately; review entity roles before live checkout.
Payment gateway setup, overseas company registration, policy and compliance pages, or personal cash readiness.
Not saved yet.
Kept in this browser only. Switching device or clearing browser data removes it; download a copy.
The combined note includes current selections and advice, review status, original values and evidence notes, migration ticks and quiz feedback, plus the six written entries. Use it for a handover, alongside official documents. Group JSON files provide local field backups. After saving, restoring or clearing, recheck the displayed values and dates; clearing one group does not clear the others.
Domestic entity boundary record
Purpose: hand over the current assessment and evidence locations; check registration, permits, tax and provider review for the actual business.
- Entity role: Main operating entity — (to fill in)
- Operating boundary: Domestic purchasing and contracts — (to fill in)
- Early action: Supplier contract and first purchase — (to fill in)
- Entity form: Individual business — (to fill in)
- Evidence folder: License and business scope — (to fill in)
- Pause condition: Storefront entity and payout entity do not match — (to fill in)
- Payment answer: Not answered yet
- Legal name and brand/store name: (to fill in) | (to fill in) | (to fill in) | (to fill in)
- Registered address and operating/return address: (to fill in) | (to fill in) | (to fill in) | (to fill in)
- Payout beneficiary and payment account: (to fill in) | (to fill in) | (to fill in) | (to fill in)
- Website information and responsibility chain: (to fill in) | (to fill in) | (to fill in) | (to fill in)
- Evidence pack: Pack 1: China-side purchasing and invoices — (to fill in)
- Migration checks: 0 — (to fill in)
- Migration answer: Not answered yet
- Next route: Domestic role clear; another entity is confirmed necessary — (to fill in)
- Current pressure: (to fill in)
- First evidence: (to fill in)
- This-week action: (to fill in)
- Stop action: (to fill in)
- Review window: (to fill in)
- Next route: (to fill in)
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
Your work
- Record · Test the entity against the next actionNot saved
- Record · Use three layers of facts to explain identity and responsibilityNot saved
- Record · Use three layers of facts to explain identity and responsibilityNot saved
- Record · Use three layers of facts to explain identity and responsibilityNot saved
- Record · Use three layers of facts to explain identity and responsibilityNot saved
- Record · Protect open orders, money and duties before changing entitiesNot saved
- Record · Keep a record someone can review and useNot saved
- Note · Keep a record someone can review and useNot copied
Kept in this browser only. Switching device or clearing browser data removes it; download a copy.
Common questions
- Can a China domestic business license directly solve Shopify Payments?
- A domestic license supports business evidence, purchasing, invoices and records, but does not establish payment eligibility. Mainland China Shopify Payments currently has invitation-only early access, with requirements covering Mainland-registered cross-border businesses, WorldFirst and verification. Other regions, providers and banks have separate conditions. Verify the actual path before deciding whether an overseas entity is needed.
- How should a beginner choose between a sole proprietor and a limited company?
- Compare purchasing, contracts, people, banking, finance and liability. An individual business can be a candidate for solo validation; a company provides a structure for shareholders, staff and company finances. Compare local filing, ongoing duties, property liability and the next six-to-twelve-month plan rather than choosing by filing speed or promises of easier approval.
- Should the business scope mention ecommerce or import/export?
- Confirm it against the real business and local registration rules. The scope should explain purchasing, selling, services, invoices, and supplier contracts. If import/export, warehousing, restricted products, or licensing are involved, ask the local registration office, accountant, or lawyer first.
- Can I launch when the store entity, payment entity, and bank beneficiary do not match?
- Do not release it by default. Use the entity mismatch pause check to write who owns the merchant identity, payment account, bank beneficiary, ad assets, policy pages, refund responsibility, and support email. If the mismatch affects payout, refunds, ad review, or buyer trust, collect first evidence before launch.
- What documents should I prepare after registering a business license for a Shopify store?
- Keep the license, verification screenshot, business scope, registered and operating address notes, payment or bank boundary, supplier contracts, invoice title, tax and annual-report duties, Contact / Refund / Privacy merchant identity, and next review date.
- What should the entity record consistency check verify?
- Check the company name, address, responsible person, scope, payment and FX accounts, ad verification, invoice title, supplier payments, Shopify store, policies and support email together. The records should explain who is responsible for each activity. If license, PayPal, Meta Business Portfolio, support email, and footer identity point to different operators, pause live checkout and ad scaling first.
- When is a domestic entity only supporting proof, and when should I consider an overseas entity?
- The domestic entity can support China-side purchasing, supplier contracts, invoices, costs and business evidence. Compare another jurisdiction’s route when the actual provider or business requires its entity, banking, tax or customer-service arrangements. Shopify Payments is not a blanket reason to register overseas; first check current Mainland and target-region requirements.
- What should I save in the entity evidence folder?
- Save the license, registration or verification screenshot, business scope, registered address, tax and annual-report schedule, bank or payout path, supplier contracts, invoice samples, ad account business proof, policy-page merchant identity, and domestic entity boundary record.
Choose the next lesson for the earliest blocker
Choose for the evidence missing now. If the domestic role is clear and the verified requirements call for another entity, compare overseas routes. Revisit cash planning for uncertain costs, payment gateways for uncertain eligibility, or domain and email work for unclear public identity.
Next route
- Why this route
- Continue to overseas entity choice and check whether payout, tax, platform records, and storefront disclosure can be explained together.
- Why this route
- Return to the 90-day cash runway. Entity maintenance, tax, banking, and payment paths all consume cash and time.
- Why this route
- Do not assume the domestic entity works. Check gateway, entity requirement, payout account, and refund path together.
- Why this route
- Align company name, address, email, policies, and account records before domain, email, and store setup.
You can also revisit overseas entity choice, cash readiness, or the Basics course. At the next review, start with the first evidence and its owner before advancing the affected activity.