Custom E-Commerce Platform with Sales Partner & Commission System
Budget / Salary₹75,000–150,000
TypeFreelance project
LocationRemote
Posted1 hour ago
We are looking for an experienced full-stack developer or development team to build a production-ready e-commerce platform with a unique Sales Partner system.
This is NOT a standard e-commerce website.
The initial products will be physical products such as watches, but the system must be configurable so products, categories, prices, stock and commission structures can be changed easily from the admin panel.
The platform will have separate interfaces and permissions for Customers, Sales Partners, Admin, Finance Staff, IT Staff, Stock Keepers and Delivery Staff.
We are open to technology recommendations. Please propose the most suitable, secure and maintainable architecture for this project.
1. E-COMMERCE
* Homepage, categories and product listing
* Product search/filter
* Product details, images, price and stock
* Configurable tax
* Cart and checkout
* Customer registration/login
* Delivery address/details before payment
* Order history/status
* Return/replacement/refund requests
* Mobile-responsive design
Admin must be able to manage products, categories, images, prices, tax, stock and product display priority.
2. PAYMENT GATEWAY
We are considering Razorpay or another suitable Indian payment gateway.
Required flow:
Customer selects product → enters delivery details → payment gateway → secure server-side payment verification → order confirmed → stock updated → relevant Sales Partner commission process triggered.
Proper server-side verification and payment webhooks are required. The system must not rely only on browser redirection after payment.
Please explain your recommended payment architecture and relevant experience.
3. SALES PARTNER SYSTEM
A customer completing a qualifying purchase can become eligible to create a Sales Partner account.
The account initially enters an Account Verification Period based on the applicable return/refund period of the qualifying purchase.
After the verification period is successfully completed, the account becomes Active.
The verification period must be configurable by Admin.
4. SALES PARTNER REGISTRATION
May include:
* Full name
* Mobile number
* Alternative/WhatsApp number
* Email
* Bank account number and confirmation
* IFSC
* Permitted ID/KYC information
* Username/password
Sensitive information must be securely handled.
5. SALES PARTNER DASHBOARD
Should show:
* Account and verification status
* Direct customers introduced
* Sales history
* Commission earned
* Pending commission
* Approved/available commission
* Withdrawn amount
* Points/balance
* Withdrawal history
Initially 1 point = ₹1, but this must be configurable.
6. DIRECT REFERRAL STRUCTURE
Only direct customers introduced by a Sales Partner should be visible to that Sales Partner.
Example:
A introduces B and C → A sees B and C.
B introduces D and E → B sees D and E.
A must NOT see D and E.
There is no multi-level commission. Commission is generated only for qualifying direct sales attributable to the relevant Sales Partner.
7. COMMISSION SYSTEM
Commission percentage or fixed amount must be configurable by Admin, including potentially different commission settings by product.
Example:
₹5,000 product with 50% commission = ₹2,500.
Commission initially becomes Pending and is released only after the applicable return/refund period for that specific order expires.
If an order is cancelled/refunded, the related commission must be reversed or held according to configurable rules.
Commission must be tracked per order.
8. SELF-REFERRAL AND FRAUD CONTROL
Sales Partners must not earn commission from their own purchase or artificial/self-referral transactions.
The system should flag suspicious cases using configurable indicators such as duplicate mobile number, email, bank details or KYC information.
Preferably flag for staff review rather than automatically blocking every possible family/shared-address situation.
9. WITHDRAWAL SYSTEM
Sales Partners can request withdrawal of approved balance.
Minimum withdrawal rules must be configurable.
Example:
First withdrawal: minimum 5,000 points
Later withdrawals: minimum 2,500 points
Workflow:
Withdrawal request → Finance Staff review → Approve/Reject/Issue → Manual bank payment → Staff records payment/reference → Sales Partner sees updated status.
Maintain complete financial and audit history.
10. FINANCE STAFF PANEL
Separate secure staff login.
Finance staff can:
* View withdrawal requests
* Check relevant Sales Partner and transaction details
* Check available balance
* Approve/reject
* Move requests to Issues
* Add notes
* Record manual payment/reference details
Important financial approvals should require an additional approval credential/password.
Each staff member must have individual login and role permissions.
11. IT AND ISSUE TICKETS
Authorized Finance or Delivery staff can move problematic requests/orders to an Issues section.
The system automatically generates a unique ticket number and emails the designated IT support address.
IT staff can:
* Investigate
* Add notes
* Resolve
* Reject fraudulent/wrong requests where authorized
* Suspend/block accounts where authorized
* Return issues to relevant staff with an explanation
Ticket status should be visible to relevant users.
12. STOCK KEEPER
Admin can create multiple Stock Keeper accounts.
Stock Keepers can:
* View stock
* Update quantities
* Record stock changes
* View relevant product information
Access must be role-restricted.
13. DELIVERY PANEL
Paid orders should automatically appear in the Delivery Staff panel.
Delivery staff can:
* View orders ready for dispatch
* Select multiple orders
* Export selected orders to Excel
* Print order details
* Manually verify orders
* Enter courier/post tracking number
* Update dispatch/process status
* Record delivery information
* Send delivery issues to the ticket system
14. RETURNS, REPLACEMENT AND REFUND
System must support configurable return, replacement and refund workflows.
Customer request → staff review → approve/reject → replacement/refund → order status update → related commission handled automatically.
Genuine defective, damaged or wrong-product cases should be distinguishable from normal cancellation/refund where appropriate.
Final legal/business policy will be provided separately.
15. NOTIFICATIONS
Automatic email notifications for important events such as:
* Registration and account verification
* Order/payment confirmation
* Return/refund updates
* Commission updates
* Withdrawal request/status
* Issue/ticket creation/resolution
* Dispatch/delivery updates
SMS/WhatsApp automation is not essential for Version 1 unless separately proposed.
16. ADMIN PANEL
Admin should manage:
* Products and categories
* Prices, tax and stock
* Orders and customers
* Sales Partners
* Commission settings
* Withdrawal rules
* Staff accounts and permissions
* Returns/refunds
* Delivery
* Reports
* System settings
* Audit records
17. SECURITY
Security is a major requirement because the system handles customer, financial and KYC-related information.
Required:
* Secure authentication
* Password hashing
* Role-based access control
* Server-side authorization
* Secure payment verification and webhooks
* Protection against common web vulnerabilities
* Audit logs
* Database backups
* HTTPS/SSL
* Secure session management
* Secure handling of sensitive information
Users must only access information permitted by their role.
18. HOSTING AND DEPLOYMENT
We expect a proper cloud/VPS/server environment rather than basic shared hosting.
Please recommend:
* Server type and specifications
* Operating system
* Database
* Required services
* Backup strategy
* Security configuration
* Estimated infrastructure cost
* Deployment process
Domain, hosting, payment gateway and major service accounts will remain under client ownership.
19. SOURCE CODE AND OWNERSHIP
Complete source code and database must be handed over to the client.
Client should own the project code and database after completion.
All third-party plugins, libraries, licenses and external services must be disclosed.
No critical functionality should depend on an undisclosed service controlled by the freelancer.
20. TESTING
Before final delivery, test:
* Registration and login
* Product, cart and checkout
* Payment success/failure/webhooks
* Orders and stock
* Sales Partner creation and verification
* Direct referral attribution
* Commission calculation, holding and release
* Refund and commission reversal
* Withdrawals and finance approval
* Tickets and issues
* Stock and delivery workflows
* User permissions
* Mobile responsiveness
* Security and common errors
TARGET
Version 1 target development period: approximately 10–12 weeks.
We prefer a properly tested and secure system rather than a rushed delivery.
PROPOSAL REQUIREMENTS
Please provide:
1. Recommended technology/architecture and why
2. Realistic development timeline
3. Fixed project quotation
4. Proposed milestones
5. Included and excluded features
6. Payment gateway experience
7. Experience with custom commission/referral systems
8. Experience with financial/admin workflows
9. Security approach
10. Hosting/server recommendation
11. Post-launch bug-fix period
12. Maintenance cost
13. Relevant previous work or demos
Please identify any requirement that needs clarification or a different technical approach.
We will shortlist based on technical understanding, relevant experience, security, architecture, communication and overall value, not simply the lowest quotation.
This is Version 1. Future features and major changes will be handled separately.
This is NOT a standard e-commerce website.
The initial products will be physical products such as watches, but the system must be configurable so products, categories, prices, stock and commission structures can be changed easily from the admin panel.
The platform will have separate interfaces and permissions for Customers, Sales Partners, Admin, Finance Staff, IT Staff, Stock Keepers and Delivery Staff.
We are open to technology recommendations. Please propose the most suitable, secure and maintainable architecture for this project.
1. E-COMMERCE
* Homepage, categories and product listing
* Product search/filter
* Product details, images, price and stock
* Configurable tax
* Cart and checkout
* Customer registration/login
* Delivery address/details before payment
* Order history/status
* Return/replacement/refund requests
* Mobile-responsive design
Admin must be able to manage products, categories, images, prices, tax, stock and product display priority.
2. PAYMENT GATEWAY
We are considering Razorpay or another suitable Indian payment gateway.
Required flow:
Customer selects product → enters delivery details → payment gateway → secure server-side payment verification → order confirmed → stock updated → relevant Sales Partner commission process triggered.
Proper server-side verification and payment webhooks are required. The system must not rely only on browser redirection after payment.
Please explain your recommended payment architecture and relevant experience.
3. SALES PARTNER SYSTEM
A customer completing a qualifying purchase can become eligible to create a Sales Partner account.
The account initially enters an Account Verification Period based on the applicable return/refund period of the qualifying purchase.
After the verification period is successfully completed, the account becomes Active.
The verification period must be configurable by Admin.
4. SALES PARTNER REGISTRATION
May include:
* Full name
* Mobile number
* Alternative/WhatsApp number
* Bank account number and confirmation
* IFSC
* Permitted ID/KYC information
* Username/password
Sensitive information must be securely handled.
5. SALES PARTNER DASHBOARD
Should show:
* Account and verification status
* Direct customers introduced
* Sales history
* Commission earned
* Pending commission
* Approved/available commission
* Withdrawn amount
* Points/balance
* Withdrawal history
Initially 1 point = ₹1, but this must be configurable.
6. DIRECT REFERRAL STRUCTURE
Only direct customers introduced by a Sales Partner should be visible to that Sales Partner.
Example:
A introduces B and C → A sees B and C.
B introduces D and E → B sees D and E.
A must NOT see D and E.
There is no multi-level commission. Commission is generated only for qualifying direct sales attributable to the relevant Sales Partner.
7. COMMISSION SYSTEM
Commission percentage or fixed amount must be configurable by Admin, including potentially different commission settings by product.
Example:
₹5,000 product with 50% commission = ₹2,500.
Commission initially becomes Pending and is released only after the applicable return/refund period for that specific order expires.
If an order is cancelled/refunded, the related commission must be reversed or held according to configurable rules.
Commission must be tracked per order.
8. SELF-REFERRAL AND FRAUD CONTROL
Sales Partners must not earn commission from their own purchase or artificial/self-referral transactions.
The system should flag suspicious cases using configurable indicators such as duplicate mobile number, email, bank details or KYC information.
Preferably flag for staff review rather than automatically blocking every possible family/shared-address situation.
9. WITHDRAWAL SYSTEM
Sales Partners can request withdrawal of approved balance.
Minimum withdrawal rules must be configurable.
Example:
First withdrawal: minimum 5,000 points
Later withdrawals: minimum 2,500 points
Workflow:
Withdrawal request → Finance Staff review → Approve/Reject/Issue → Manual bank payment → Staff records payment/reference → Sales Partner sees updated status.
Maintain complete financial and audit history.
10. FINANCE STAFF PANEL
Separate secure staff login.
Finance staff can:
* View withdrawal requests
* Check relevant Sales Partner and transaction details
* Check available balance
* Approve/reject
* Move requests to Issues
* Add notes
* Record manual payment/reference details
Important financial approvals should require an additional approval credential/password.
Each staff member must have individual login and role permissions.
11. IT AND ISSUE TICKETS
Authorized Finance or Delivery staff can move problematic requests/orders to an Issues section.
The system automatically generates a unique ticket number and emails the designated IT support address.
IT staff can:
* Investigate
* Add notes
* Resolve
* Reject fraudulent/wrong requests where authorized
* Suspend/block accounts where authorized
* Return issues to relevant staff with an explanation
Ticket status should be visible to relevant users.
12. STOCK KEEPER
Admin can create multiple Stock Keeper accounts.
Stock Keepers can:
* View stock
* Update quantities
* Record stock changes
* View relevant product information
Access must be role-restricted.
13. DELIVERY PANEL
Paid orders should automatically appear in the Delivery Staff panel.
Delivery staff can:
* View orders ready for dispatch
* Select multiple orders
* Export selected orders to Excel
* Print order details
* Manually verify orders
* Enter courier/post tracking number
* Update dispatch/process status
* Record delivery information
* Send delivery issues to the ticket system
14. RETURNS, REPLACEMENT AND REFUND
System must support configurable return, replacement and refund workflows.
Customer request → staff review → approve/reject → replacement/refund → order status update → related commission handled automatically.
Genuine defective, damaged or wrong-product cases should be distinguishable from normal cancellation/refund where appropriate.
Final legal/business policy will be provided separately.
15. NOTIFICATIONS
Automatic email notifications for important events such as:
* Registration and account verification
* Order/payment confirmation
* Return/refund updates
* Commission updates
* Withdrawal request/status
* Issue/ticket creation/resolution
* Dispatch/delivery updates
SMS/WhatsApp automation is not essential for Version 1 unless separately proposed.
16. ADMIN PANEL
Admin should manage:
* Products and categories
* Prices, tax and stock
* Orders and customers
* Sales Partners
* Commission settings
* Withdrawal rules
* Staff accounts and permissions
* Returns/refunds
* Delivery
* Reports
* System settings
* Audit records
17. SECURITY
Security is a major requirement because the system handles customer, financial and KYC-related information.
Required:
* Secure authentication
* Password hashing
* Role-based access control
* Server-side authorization
* Secure payment verification and webhooks
* Protection against common web vulnerabilities
* Audit logs
* Database backups
* HTTPS/SSL
* Secure session management
* Secure handling of sensitive information
Users must only access information permitted by their role.
18. HOSTING AND DEPLOYMENT
We expect a proper cloud/VPS/server environment rather than basic shared hosting.
Please recommend:
* Server type and specifications
* Operating system
* Database
* Required services
* Backup strategy
* Security configuration
* Estimated infrastructure cost
* Deployment process
Domain, hosting, payment gateway and major service accounts will remain under client ownership.
19. SOURCE CODE AND OWNERSHIP
Complete source code and database must be handed over to the client.
Client should own the project code and database after completion.
All third-party plugins, libraries, licenses and external services must be disclosed.
No critical functionality should depend on an undisclosed service controlled by the freelancer.
20. TESTING
Before final delivery, test:
* Registration and login
* Product, cart and checkout
* Payment success/failure/webhooks
* Orders and stock
* Sales Partner creation and verification
* Direct referral attribution
* Commission calculation, holding and release
* Refund and commission reversal
* Withdrawals and finance approval
* Tickets and issues
* Stock and delivery workflows
* User permissions
* Mobile responsiveness
* Security and common errors
TARGET
Version 1 target development period: approximately 10–12 weeks.
We prefer a properly tested and secure system rather than a rushed delivery.
PROPOSAL REQUIREMENTS
Please provide:
1. Recommended technology/architecture and why
2. Realistic development timeline
3. Fixed project quotation
4. Proposed milestones
5. Included and excluded features
6. Payment gateway experience
7. Experience with custom commission/referral systems
8. Experience with financial/admin workflows
9. Security approach
10. Hosting/server recommendation
11. Post-launch bug-fix period
12. Maintenance cost
13. Relevant previous work or demos
Please identify any requirement that needs clarification or a different technical approach.
We will shortlist based on technical understanding, relevant experience, security, architecture, communication and overall value, not simply the lowest quotation.
This is Version 1. Future features and major changes will be handled separately.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.