SanGongXianPEI

The company appears to be a solo developer project named SanGongXianPEI, an internal fresh food distribution platform for unit-based procurement and logistics. The author describes building a system that replaces traditional methods like WeChat groups or Excel spreadsheets with a structured digital workflow involving Android app, web portals, and backend services.

What changed: The project is presented as a technical solution to inefficiencies in traditional food procurement processes — specifically addressing issues around transparency, data consistency, and order tracking. It includes design elements for role-based access control, concurrency handling, and mobile reliability.

Single most important open question: Is there any evidence of real-world usage or adoption by sub-units or administrators? The description contains no mention of customers, revenue, or actual deployment beyond a developer's own testing environment.

This analysis is based entirely on the self-reported project description provided. No external verification, traction data, or third-party sources are available. All claims are attributed to the author’s own account and should be treated as unverified.

The description states that SanGongXianPEI is a collaborative system for application, stocking, distribution, and performance management of unit ingredients. It consists of:

• An Android App built with Kotlin and Jetpack Compose
• A FastAPI server
• Administrator Web background
• Sub-unit Web portal

The system aims to replace traditional tools such as WeChat groups, paper lists, and Excel tables in food procurement.

This is a self-reported product architecture. No evidence of actual customer use or production deployment exists beyond the author’s own development efforts.

The description states that the project was motivated by problems in traditional food procurement processes, including:

• Information dispersion
• Non-transparent order status
• Untimely inventory updates
• Data confusion from multiple units
• Lack of unified records during distribution

It positions itself as a digital replacement for manual methods, aiming to create a complete business closed loop involving:

1. Administrator setup (units, accounts, ingredients)
2. Sub-unit order submission via app
3. Admin processing and delivery photo upload
4. Sub-unit tracking and confirmation of receipt

The author claims this system solves inefficiencies in procurement workflows but does not provide evidence of real-world adoption or validation.

The description identifies two main user types:

1. Sub-units — who apply for ingredients, submit orders, and track status.
2. Administrators — who manage inventory, prices, units, and orders.

It also mentions that the system supports multiple sub-units with data isolation, suggesting a multi-tenant structure where each unit operates independently.

The description does not state whether these are real organizations or hypothetical use cases. No evidence of actual customers or target accounts is provided.

There is no mention in the description of any pricing model, monetization strategy, or revenue streams.

The author focuses on technical implementation and system design rather than commercial aspects such as:

• Who pays for the service
• How many units are expected to use it
• Whether it’s sold as SaaS or deployed internally

Not evidenced. The business model remains unspecified.

Key technical details include:

• Frontend: Android App (Kotlin + Jetpack Compose), Web portals using HTML/CSS/JS templates
• Backend: FastAPI server with SQLite database
• Deployment: Docker Compose + Nginx
• Security features:
  • Role-based access control
  • Data isolation by unit_id
  • Atomic updates to prevent concurrency issues
• Mobile reliability mechanisms:
  • Handling network interruptions
  • Login failure recovery
  • Notification permission handling
• Testing:
  • Stress tests with simulated users
  • No HTTP 5xx errors or database locks during testing

These are self-reported technical features and implementation details. No evidence of production deployment or performance under real load.

The author claims to have completed:

• Stress tests (20–40 users over various durations)
• Database backup/recovery procedures
• Environmental protection mechanisms

However, there is no evidence of:

• Real-world usage
• Customer feedback or adoption
• Live deployment
• Any form of traction beyond personal development and testing

Not evidenced. No signs of product-market fit or real-world traction.

There is no mention in the description of existing competitors or similar platforms. The author does not reference any marketplace, SaaS tool, or other solution addressing internal food distribution for organizations.

Not evidenced. No competitive landscape information provided.

Several potential risks emerge from the self-reported account:

1. Solo developer project: Only one member listed (banple6 Tian), which raises concerns about scalability and long-term maintenance.
2. No real-world usage or feedback: The entire system appears to be built in isolation without customer validation.
3. Limited commercialization strategy: No pricing, monetization, or go-to-market plans are described.
4. Unverified claims: All technical and functional assertions come from the author’s own account — no independent verification.
5. No data on user retention or engagement: The system may not be used beyond initial testing.

These are inferred risks based on the lack of evidence for traction, commercial viability, or multi-user adoption.

1. Has this platform been tested with real sub-units or administrators?
2. What is the expected scale of users and units that will use this system?
3. Are there any plans to monetize or deploy this beyond a prototype?
4. How does the system handle edge cases like large-scale concurrent order submissions?
5. Have you considered integrating with existing ERP or procurement systems?
6. Is there any interest from potential clients or partners in using this platform?

These questions aim to uncover whether the project has moved beyond concept and into real-world application.