Scenario A
Guest vs logged-in price and stock policy must be explicit.
B2B mini programs win by shortening inquiry paths and capturing leads, not by being a mobile brochure. Permissions, price visibility, and follow-up loops decide outcomes.
Guest vs logged-in price and stock policy must be explicit.
Inquiry forms must hit CRM or sales queues, not email alone.
SKUs, specs, and downloads must be searchable or a PDF wins.
| Decision lens | Common trap or cost | Safer cut |
|---|---|---|
| Core loop | Inquiry to sales queue | Measurable |
| Permissions | Price/stock visibility | Stop leaks |
| Phase one | Catalog+inquiry+status | Configurator later |
A mini program is a lead pipe, not a mobile brochure Put scenarios into the contract annex—better for acceptance than module names alone.
Start with top SKUs and spec templates; restage the long tail.
B2B often starts with terms or offline settlement; payments later.
Mini program for WeChat traffic and repeat; website for SEO and brand.
Combine login gates, rate limits, watermarks, and contracts.
Goals, constraints, and legacy systems change the phased boundary. Send your current systems and target; engineering will return an executable plan and acceptance list.