Lavarel Clamsi, customer access and Bug Fixing -- 2
Budget: $250 – $750 USD
In Clamsi, customer access is strictly permission-based: buyers can only view a supplier’s store if they’ve been explicitly invited or approved by that supplier
To Be Developed
1. Customer access development so that Seller provide acess to the store for customers. Currently the template is set so that customers can view all sellers stores.
2. Seller invitation via SMS/email development
3. Auto-approval by mobile number if customer is inside supplier customer list with email or mobile phone
4. Supplier Customer List , Mobile phones or emails
5. Seller Shop Customer visit logging & analytics
6. Send Real Time Notifications or email alerts when customer logins on Seller Shop
Problem
Onboarding wizard saves data into the wrong table (suppliers).
Required Fix
Save to sellers table instead.
Stop new writes to suppliers.
Integrate catalogue checks into onboarding for auto-approval.
Fix 2
• Re-enable OTP feature
• Stop enforcing GeoIP on phone input
To Be Developed
1. Customer access development so that Seller provide acess to the store for customers. Currently the template is set so that customers can view all sellers stores.
2. Seller invitation via SMS/email development
3. Auto-approval by mobile number if customer is inside supplier customer list with email or mobile phone
4. Supplier Customer List , Mobile phones or emails
5. Seller Shop Customer visit logging & analytics
6. Send Real Time Notifications or email alerts when customer logins on Seller Shop
Problem
Onboarding wizard saves data into the wrong table (suppliers).
Required Fix
Save to sellers table instead.
Stop new writes to suppliers.
Integrate catalogue checks into onboarding for auto-approval.
Fix 2
• Re-enable OTP feature
• Stop enforcing GeoIP on phone input
Related categories:
PHP
Mobile App Development
Android
Software Architecture
Data Analytics
Backend Development
Twilio
API Development