# China Store Knowledge Context

> Source knowledge base: `/Users/ninebot/Documents/project/ChinaStore`
> Last reviewed for this project: 2026-05-20

This note keeps the China Store business context close to the current merchant intake tool. It is a distilled working reference, not a full mirror of the knowledge base.

## What The Store Is

九号官方商城（`ninebot.com`）是九号公司官方线上销售与服务平台，核心模式是 **B2C + O2O**:

1. 用户在线浏览商品并下单付款。
2. 商城生成订单并绑定或分配提车门店。
3. 用户到门店提车。
4. 门店确认交付并完成核销。
5. 核销触发分账。
6. 门店提现到绑定银行卡。

The current project is narrower than the full mall: it focuses on the **merchant onboarding / card-binding data collection** needed before a store can receive settlement.

## Core Roles

| Role | Responsibility |
| --- | --- |
| 用户 | 在线下单、支付、到店提车、发起售前/售后咨询 |
| 商城/九号平台 | 流量入口、订单管理、支付入口、运营规则、资金托管和分账 |
| 门店 | 线下体验、实物交付、核销确认、售后履约、本地服务 |
| 中信银行 | 账户、对账、资金托管相关服务 |
| 银联 | 收单与清算链路 |
| 微信/支付宝 | 用户支付入口 |
| 菜鸟物流 | 邮寄商品或配件物流链路 |

## Store And Settlement Flow

The business flow most relevant to this form is:

```text
门店入驻/商户进件
    -> 门店账户与银行卡绑定
    -> 用户在线支付订单
    -> 订单进入担保/托管状态
    -> 用户到店提车
    -> 门店核销
    -> 平台按订单分账
    -> 门店发起提现
    -> 资金到绑定银行卡
```

The payment and settlement chain from the knowledge base is:

```text
用户付款（微信/支付宝/银联）
    -> 银联收单/中间账户
    -> 每日清算
    -> 九号担保账户
    -> 按核销订单分账
    -> 门店账户
    -> 门店银行卡到账
```

Important timing assumptions:

| Step | Timing |
| --- | --- |
| 用户付款 | T+0 |
| 银联日切清算 | T+0 around 23:00 |
| 对账/分账/提现发起 | T+1 |
| 门店银行卡实际到账 | T+2 |

The knowledge base notes that a T+0 settlement direction is a future exploration topic, not the current confirmed process.

## Why Merchant Intake Matters

For this project, merchant intake and card binding are prerequisites for O2O settlement:

- The store must have a valid merchant identity before receiving distributed funds.
- The merchant name, legal representative, license information, and bank account holder need to stay consistent enough for onboarding, review, and settlement.
- Card binding updates are operationally sensitive because the bound card is the final withdrawal destination for store funds.
- For individual/sole-proprietor flows, the bank account may be personal; for enterprise flows, the account can be a corporate account.

## Current Tool Scope

This repository currently implements a static merchant intake form that generates two request bodies:

| Output | Purpose |
| --- | --- |
| `merchantCreate` | Create/register a CITIC merchant user. |
| `updateCardStatus` | Bind or unbind the merchant's settlement bank card. |

This maps to the knowledge base as follows:

| Form Section | Business Meaning |
| --- | --- |
| 门店与联系人 | Store-facing merchant identity and operational contact. |
| 法人信息 | Legal representative or operator identity for compliance review. |
| 营业执照信息 | Business registration proof for enterprise or sole-proprietor merchants. |
| 中信绑卡/解绑卡 | Settlement destination used after O2O verification and split settlement. |
| OCR uploads | Data-entry aid for license, ID card, and bank card information. |

## Product And Operations Context

The broader mall supports:

- Product display for electric two-wheelers, scooters, balance vehicles, robots, and accessories.
- Full-payment online ordering.
- Store selection or allocation for pickup.
- Store-side verification and delivery confirmation.
- Platform-driven coupons, N-coin promotions, and verification-triggered lottery campaigns.
- Online customer service and 400 phone support.

Known store network facts from the knowledge base:

- More than 9,700 stores as of 2025-09.
- 2026 target is about 13,000 stores.
- Stores handle display, trial experience, delivery, verification, maintenance, and local promotion.

## Design Implications For This Project

Future changes to the form should preserve these constraints:

- Keep merchant identity and bank-card identity visibly connected; users should notice mismatches before submitting.
- Treat card binding/unbinding as a distinct operation from merchant creation.
- Keep `subjectType`, account type, legal person/operator fields, and business license fields aligned.
- Prefer explicit status text for review, binding, and settlement readiness instead of vague "done" language.
- Avoid presenting T+0 settlement as available until the process is confirmed.
- If O2O order or store-management features are added later, model核销 as the settlement trigger.

## Open Questions To Confirm

The knowledge base leaves these items unresolved:

- Exact核销 method: QR code, manual code input, app confirmation, or multiple methods.
- Pickup timeout and overdue handling rules.
- Whether a store can initiate card changes independently or only through platform/finance review.
- Exact CITIC merchant review statuses and failure reasons.
- Whether future store-owned coupons require separate settlement records.
- Whether T+0 settlement will be supported and under what account structure.

## Source Files Reviewed

Primary sources:

- `Ninebot China Store/00-知识库说明.md`
- `Ninebot China Store/商城运营/商城概述.md`
- `Ninebot China Store/商城运营/系统架构.md`
- `Ninebot China Store/商城运营/系统模块详情.md`
- `Ninebot China Store/商城运营/O2O核销流程.md`
- `Ninebot China Store/支付与分账/支付体系.md`
- `Ninebot China Store/支付与分账/分账方案.md`
- `Ninebot China Store/业务模式/O2O商业模式.md`
- `Ninebot China Store/门店管理/门店网络.md`
- `Ninebot China Store/会员与营销/会员体系.md`
- `Ninebot China Store/会员与营销/营销活动.md`
- `Ninebot China Store/客服与售后/售后服务.md`

Secondary/rough sources:

- `China Store/前端页面/首页.md`
- `China Store/前端页面/产品详情页.md`
- `China Store/后台功能/产品.md`