FAQ

A corporate site usually takes 4–8 weeks; commerce, community and platform projects range from 8 weeks to several months depending on modules.

Yes. Every site ships with a content admin, documentation and a training session.

Yes, and we usually recommend it. The architecture leaves room to grow.

No. It is an optional monitoring service from DaleGEO.

Typically 6–12 weeks, depending on the number of templates, how quickly content is ready and your approval cycle.

Yes. News, products, projects, careers, copy and images are all managed in the CMS. New page types or layout changes need a developer.

Once the project is accepted and paid, the full source code and design files are handed over to you. Open-source components remain under their own licenses.

Templates suit simple sites on tight budgets. A custom build follows your content model, gives you control of the code and allows deeper SEO, performance and AI-readability work.

If your rules are standard, a hosted builder is quicker and cheaper. Custom makes sense when B2B pricing, complex promotions or deep ERP sync become bottlenecks.

A business license, corporate bank account and merchant accounts on both platforms, plus an ICP-filed domain. We handle certificates, callbacks and testing.

Most ERPs expose APIs. We review the documentation and agree on sync direction and frequency; without an API we can use a staging database or file exchange.

The code is handed over on acceptance and payment. Order and customer data is always yours and lives on your own cloud servers.

At minimum an ICP filing; interactive UGC services may also require a security assessment, and commercial operations may need an ICP license. We flag these during planning.

We do not recommend it. Automated screening blocks obvious violations and flags suspicious content; people make the final call using a review console.

We provide invite codes, content import and bulk posting tools, but cold start is mainly an operations effort: seed users, prepared content and clear rules.

Code is handed over on acceptance and payment. All user and content data lives on your own cloud servers and belongs to you.

Shopify is hosted and has polished checkout — good for fast B2C starts, with monthly and some transaction fees. WooCommerce is self-hosted and flexible, suited to content-heavy, inquiry-led sites, but you manage hosting, security and updates.

Not if the site is hosted outside mainland China, which is typical for sites serving overseas buyers. Mainland hosting always requires filing.

No one should. We get the technical foundations right; rankings also depend on content, links and competition, and usually take months of sustained work.

There is always some risk. We map every old URL to a 301 redirect, preserve titles and structured data, and monitor indexing in Search Console after launch.

Usually the category does not match the features, a permit is missing or privacy disclosures are inaccurate. We check these upfront and address review feedback point by point.

uni-app or Taro gives substantial reuse, but login, payments and messaging differ per platform and each needs its own testing and review.

Mini-programs need no download and spread well through WeChat. Apps suit background, offline or heavy interaction needs. Many companies start with a mini-program.

The mini-program is registered under your business and belongs to you. Source code is handed over on acceptance and payment.

Yes. We recommend a paid discovery and design phase that produces workflows, prototypes and phase-one scope before committing to a build plan.

Yes. Deployments are containerized and can run in your Alibaba Cloud or Tencent Cloud account or data center, with scripts and runbooks provided.

Volatile parts such as approvals, fields and reports are configurable; anything beyond that is estimated and built in iterations.

On acceptance and payment, the custom source code and documentation are yours to maintain, extend or register. Open-source components keep their own licenses.

Managed cloud platforms save ops effort for smaller fleets; self-hosted EMQX gives more control over data and long-term cost at scale. We compare both for your numbers.

Usually yes, via an edge gateway that translates Modbus, serial or proprietary protocols, provided the protocol is documented.

Yes. Source, deployment docs and thing-model definitions are part of the handover.

Collecting centrally and paying out yourself can be treated as unlicensed payment clearing. Official splits send funds directly to each party through a licensed provider.

Standard leader and fulfilment models are faster on a mature system; unusual commission or delivery rules often justify a custom build.

Yes, with separate warehouses, pickup points and catalogues per region; this adds inventory and transfer logic.

For users in mainland China, data residency, stability and compliance matter; DeepSeek, Doubao and Qwen cover most support and office tasks. Providers stay swappable.

Grounded answers with sources, forced handoff on pricing and commitments, output checks, and regression testing. Handoff and audit logs remain essential.

We start read-only, then allow low-risk writes with logging and require human approval for high-risk ones.

We advise against it: conflicting sources produce conflicting answers and erode trust. Clean-up can be done department by department.

Documents stay in your database and only relevant snippets are sent per query, using APIs that exclude training; private deployment is an option.

Against a test set of real questions: correctness, correct citations and honest 'not found' answers.

Shopify suits retail checkout with minimal ops; WordPress suits lead generation, content and flexible data models. Both can rank well.

We do not promise rankings or timelines. New sites typically take months, depending on competition, content and technical foundations.

Yes. Entity, product category and policy pages are reviewed, and some categories are restricted; we check this before building.

Crawlability, structured data and quality content matter for both; GEO stresses citable facts and entity consistency, and measures mentions in AI answers rather than search rankings.

No. Each model decides its own answers and they change over time. We improve the foundations and measure what happens.

Dale Network handles site engineering and content; DaleGEO provides ongoing AI answer monitoring and the free checker at tools.dalegeo.com.

Usually category, series and model, with specs as structured fields rather than images, imported in bulk from ERP or spreadsheets.

Pilot one high-volume model with frequent service issues, prove alerts and remote viewing, then expand.

Marketplaces win new buyers; a mini-program serves repeat purchase, membership and store tie-ins, if you have those audiences.

It can be, if funds go through official profit-sharing and tiers stay within legal limits.

Yes, with a WeChat Pay merchant account; local escrow rules may shape the payment flow.

We recommend leaving fees, discounts and refunds to human advisers.

No efficacy promises. Objective descriptions of services, equipment and procedures are fine, ideally reviewed by legal or compliance.

Only licensed institutions can; most should limit mini-programs to booking and non-clinical services.

Platforms bring new customers; your own mini-program serves repeat visits, stored value and booking.

Usually a mini-program or WeCom is enough; native apps only for background location or offline needs.

Not necessarily; migrating to SSR or static generation can keep your design and components.

Start with the free checker at tools.dalegeo.com, then use DaleGEO monitoring for ongoing tracking.