Salveowell

The hard part of this system was never any single screen. It is that commerce, membership tiers and compensation are one connected machine, and five different clients all have to reflect its state correctly while the commercial rules keep changing underneath them.

1. One platform, five front doors. A retail shopper, a distributor, a trainee and a director all read from the same Laravel backend but must see entirely different prices, entitlements and data. Any surface that computed its own view of that would eventually contradict the others.
2. Price depends on who is asking. Retail pricing, member pricing by package tier, and four regional catalogues with different products and currencies all coexist. No price can be hardcoded or naively cached on a client.
3. Every member is also a shopfront. Distributors sell from their own subdomain, with member-specific pricing, referral attribution and package visibility — using the same interface as the public site.
4. Purchases have downstream consequences. Membership package purchases feed a binary and unilevel genealogy that drives commissions, bonus credits and payroll. A client must hand that off cleanly and never predict the outcome itself.
5. The audience is on low-end hardware. A large share of users are on mid-to-low-end Android devices and metered, intermittent mobile data. An app that only works on a good connection does not work.
6. Sensitive data on the smallest screen. The admin surface exposes revenue, margin and commission liability across 15+ distinct user role types, so access control could never be an afterthought.
7. Store review changes the cost of a mistake. With App Store and Play Store review in the loop, a broken checkout is not a hotfix — it is a week of lost sales across two stores.