Contact person: Laravel Feature Revamp for Clamsi

Phone:Show

Email:Show

Location: Emrou 1, Cyprus

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Clamsi Laravel Feature Documentation

Customer-Supplier Access Control, Invites, and Analytics

Overview

This feature enables suppliers on the Clamsi platform to manage which customers can view their shops. It includes:

Customer and Supplier identity management

Invite-based customer onboarding

Automatic access control based on mobile number or invite

Logging of shop visits with analytics

Email notifications to suppliers when a customer visits their shop

Customer Management

Each customer record includes:

Full name

Company name

Email and mobile number (unique identifiers)

Country and business category

Verification status (via SMS/OTP)

Account status (active, pending, or suspended)

Customers must register using a verified mobile number. They can gain access to supplier shops through approval, invite, or default visibility settings.

Supplier Management

Each supplier record contains:

Company and contact details

Unique email and mobile number

Country and categories of products offered

Shop visibility setting (public or private)

Verification status

Account status

Suppliers can manage access to their shop through a permission system and send customer invites.

Supplier–Customer Access Control

Each supplier can define who may access their shop:

Public visibility: All customers can view the shop by default

Private visibility: Only customers explicitly approved by the supplier may view the shop

Access records are stored and updated in a dedicated permissions table. Each record includes the customer, the supplier, approval status, approval method, and timestamp.

Approval can be granted manually or automatically through:

Pre-approved mobile numbers submitted by the supplier

Invite links sent via SMS or email

Invite System via SMS/Email

Suppliers can invite potential customers to register via SMS or email. Each invite includes:

Mobile number or email

A unique, secure token embedded in a registration link

Channel of delivery (SMS or Email)

Status tracking: sent, registered, expired

When a customer registers using this link:

Their invite token is verified

Their access to the supplier’s shop is automatically granted

The invite record is marked as used

The system ensures each invite is securely traceable and time-limited.

Auto-Approval via Mobile Number

Suppliers may pre-submit mobile numbers of buyers they intend to allow access. These numbers are stored with the supplier’s ID.

If a buyer later registers using a matching mobile number:

The system automatically creates an approved access record

The match is recorded as an auto-approved entry

The supplier and customer are notified (if enabled)

Shop Visit Logging and Analytics

Whenever a customer views a supplier's shop:

A log entry is created with timestamp, IP address, device details, and customer ID

These logs can be used for auditing, engagement insights, and trend tracking

Each supplier has access to a dashboard that displays:

Total visits per day

Visitor details (buyer name, company, time of visit)

Filters for country, date, or buyer

Real-Time Email Alerts for Shop Visits

Suppliers can opt to receive email notifications when a customer visits their shop.

Each email includes:

Buyer name and company

Time and date of visit

A link to the shop analytics dashboard

This helps suppliers stay informed about customer interest in real time.

Security and Privacy Considerations

All invite links are protected by secure tokens and expire after use or a defined period.

Mobile numbers and email addresses are validated and encrypted at rest.

Customers cannot view or access a supplier’s shop unless explicitly approved or invited.

Unauthorized shop access attempts are blocked and optionally logged for security review.

Admin-Level Capabilities

The admin panel includes:

Full overview of customer-supplier relationships

Visibility toggles and manual overrides

Audit logs of invites, approvals, and shop visits

System-wide analytics on customer engagement per supplier
Update: Onboarding Wizard Data Fix & Seller Table Alignment
Problem

The current Supplier Onboarding Wizard is storing registration data in the suppliers table, which is incorrectly used or structured.
The correct destination should be the sellers table (assuming that sellers is the actual table used to store supplier/vendor data in production logic).

Required Fix
1. Correct Data Storage

All onboarding submissions for new suppliers must be saved in the sellers table, not the suppliers table.

The Laravel SupplierController, registration service, or Livewire component handling onboarding should be updated to insert records into sellers." (client-provided description)