Operating CBSP from the administration area.

Business setup

Maintain products, designations, payment types and bank information before processing day-to-day transactions. Keep setup values consistent because they are reused throughout the original CBSP business.

Administrative users

Create administrators only for authorized personnel. Assign the correct role, name, email/login and password, then use Roles and Permissions to limit access according to responsibility. New administrator accounts can receive a configurable account-created email.

Members & teams

Use Employee Profiles and Teams to maintain the original CBSP member information and referral hierarchy. Product Owner programs maintain their own program memberships and sponsor relationships separately.

Scratch card generation

Generate scratch-card batches against the correct existing CBSP product. The product price is used automatically and newly generated codes begin as unused. Review the inventory counters before and after generation.

Sales

Record and review sales carefully because they are the commercial basis for commission. New Admin-created CBSP sales are processed through the active CBSP-CORE plan so a sale cannot be stored silently without the configured commission policy.

Commission & member payouts

Commission remains generated into the established T_Commission ledger. Use Member Payouts for settlement: verify member bank details, configure the minimum payout and deductions, prepare a numbered payout batch, submit and approve it under maker/checker control, export the bank CSV, record one or more bank transfers with references/proof, handle failed or reversed payments, and complete the payout only when the full net amount is received. Each payout statement keeps the included commission records, bank snapshot, adjustments and payment history traceable.

Product Owner Program

Create the Product Owner and secure Product Owner login. The Product Owner can then create programs and products, create/version a Commission Plan, define the maximum depth and individual level rules, preview the payout, activate the approved plan, enroll the first/root member, generate Product Access Codes and record program sales.

Website Content

Use Website Content in Back Office to maintain the public website without editing code. The Site Profile controls About Us, owner/founder, founded year, vision, mission, contact details and social links. The Product Content area manages descriptions, benefits, ingredients, usage instructions, featured status, images, videos and media galleries for both existing CBSP products and Product Owner products. The Articles area creates, edits, publishes and links knowledge-centre articles to products.

Contact & Complaint Centre

Public Contact requests and Complaints are stored in Back Office with generated reference numbers. Contact requests can be opened and replied to by email. Complaints operate as tracked tickets with category, priority, status, assignment, public conversation history and customer replies. Every public ticket action should be entered through the ticket screen so the customer communication and history remain complete.

Email & Notifications

Use Email & Notifications to configure the sender pool, SMTP host/port, encrypted mailbox passwords, individual sender accounts, templates, enable/disable settings, test messages and delivery logs. Migration 05 creates ten noreply sender records automatically; apply the shared mailbox password once through Back Office so it is encrypted rather than stored in source code.

Password recovery

The Login page includes Forgot Password. Administrators and Product Owners can request reset by email; members can request reset using username or registered email. Reset links are one-time, time-limited and stored as hashes. A successful reset also sends a password-changed confirmation email.

Recommended operating checks

• Confirm CBSP-CORE has the expected active plan before processing existing CBSP sales.
• Generate and test scratch cards against the intended CBSP product.
• Confirm a Product Owner can see only its own programs, products, plans, codes and sales.
• Preview every new Product Owner plan before activation.
• Enroll the correct first/root member before using Product Access Codes for new referrals.
• Reconcile sample commission transactions level by level before production rollout.
• Use a new plan/version when commercial policy changes; do not rewrite historical commission evidence.
• Confirm unpaid qualified commission appears in Member Payouts, verify member bank details before batching, and reconcile the exported bank batch against recorded payment references before closing the payout.
• Review About Us, product media and article publishing before making content public.
• Send test emails from the Email & Notifications screen after SMTP changes.
• Review failed email log entries and disabled senders before assuming a customer received a message.
• Keep complaint status, assignment and public replies inside the ticketing screen so email and audit history remain synchronized.