تفاصيل المشروع

Qouponi System Development Brief We need to build an internal system for Qouponi to replace our current master data sheet and Looker Studio setup. The goal is to create one centralized platform that manages the full operational workflow across clients, coupons, affiliates, reporting, payments, and media buying, with both manual input and API integrations. 1. Main Objective Build a web-based internal management and reporting system for Qouponi that will: Replace manual Google Sheets / master data sheets Replace fragmented reporting through Looker Studio Centralize all business data in one place Improve visibility, tracking, validation, and payment workflows Connect with external platforms through APIs where possible Support both manual and automated data entry The system should be structured, scalable, easy to use, and suitable for daily operational management. 2. Core Modules Required The system should include the following main sections: A. Client Section This section should manage all client/brand information. Required fields / functions: Client name Client category Country / market Account manager / owner Affiliate platform used Contract start date Contract status Commercial model Currency Payment terms Validation cycle Notes / remarks API connection status Manual reporting status Media buying status Active / inactive status Requirements: Ability to create, edit, archive clients Search and filter clients View client profile with all related activity Link each client to coupons, affiliates, reports, payments, and campaigns B. Coupon Section This section should manage all coupon codes and offers. Required fields / functions: Coupon code Client / brand Market Discount details Start date End date Coupon type General code or exclusive code Assigned affiliate / publisher / influencer Status: active / expired / paused Tracking link Notes Date created Last updated Requirements: Ability to generate / add codes manually Map multiple codes to one client Map codes to specific affiliates or media buying campaigns Filter by market, client, affiliate, or status Alert for expiring codes History log for coupon changes C. Affiliate Section This section should manage all affiliate / publisher / influencer information. Required fields / functions: Affiliate name Affiliate type (publisher / influencer / media partner / sub-network) Country / market Contact details Payment terms Commission model Assigned clients Assigned coupons Status Bank/payment details reference Performance summary Notes Requirements: Ability to assign affiliates to multiple clients Ability to assign specific coupons and tracking links Track performance by affiliate Track pending validation and payment status Separate active and inactive affiliates D. Report Section This is a major module and should be built carefully. The reporting section must support both: API-based data Manual uploaded / manually entered data Data source types: API data from affiliate platforms / client platforms / ad platforms Manual entry Manual file upload (CSV / Excel) Combination of API + manual adjustments Required reporting views: By client By affiliate By coupon By market By date range By media buying source By validation status Metrics to include: Clicks Orders Sales / revenue Commission Conversion rate AOV Cost ROAS Validated sales Rejected sales Pending validation Pre-validation performance Post-validation performance Mandatory split: Pre-validation report This should show raw or initial tracked performance before client validation: sales orders commission affiliate performance coupon performance media buying performance Post-validation report This should show final approved numbers after validation: approved sales approved commission rejected / cancelled sales final payout values final invoicing values Requirements: User can switch between pre-validation and post-validation System should keep record of both versions No overwriting of original data Validation adjustments should be traceable Date filters and export functionality required Dashboard view for high-level KPIs Detailed drill-down tables for operational use E. Payment Section This section should cover both: Payments from clients Payments to affiliates This is very important because Qouponi needs visibility on cash flow, validation stage, and payout timing. 1) Payments from Clients Required fields: Client name Invoice number Invoice amount Currency Invoice date Due date Payment terms Amount received Outstanding amount Payment status Related report / validation period Notes Proof of payment upload Requirements: Track invoiced vs received amounts Show overdue payments Link client payments to validated reports Filter by due date, status, and client 2) Payments to Affiliates This should support two different payment methods: a. Payment in advance Advance payment amount Date paid Period covered Linked affiliate Linked client / campaign Adjustment status Balance to reconcile later b. Payment after validation Final approved amount Date approved Due date Payment status Date paid Method of payment Related report period Requirements: Separate advance payments from after-validation payments Reconciliation view to compare: advance paid final validated amount balance payable / recoverable Payment history by affiliate Export statements for finance Alerts for unpaid affiliate balances Multi-currency support if needed F. Media Buying Section This section should cover paid media campaigns run for Qouponi / client offers. Platforms required: Meta Ads Google Ads Integration: Connect through API where possible Required data / functions: Campaign name Platform Client / brand Market Objective Spend Impressions Clicks CPC Conversions Revenue ROAS Campaign start date Campaign end date Status Related coupon / landing page / affiliate Requirements: Pull media data automatically from Meta and Google Ads APIs Link campaigns to specific clients, offers, or coupons Compare media spend vs generated revenue Show performance by campaign / ad set / market / client Merge media buying performance with affiliate/coupon reporting where applicable Manual entry option in case API is unavailable 3. System Logic / Key Relationships The system must have proper relational logic. Example relationships: One client can have many coupons One client can work with many affiliates One affiliate can promote many clients One coupon can be assigned to one or multiple affiliates depending on logic One reporting period can have: pre-validation data post-validation data One client can have multiple invoices/payments One affiliate can have multiple payout records One media buying campaign should be linked to a client and preferably to an offer/coupon if relevant 4. Data Input Methods The system must support both: Manual Input Create/edit records directly in the system Upload CSV / Excel files Admin override and corrections API Integrations At minimum, the system architecture should be built to support API integrations for: Affiliate platforms / networks Client reporting sources where available Meta Ads Google Ads The developer should build the system with a flexible integration layer so more APIs can be added later. 5. Dashboard & User Experience The system should have a clean admin dashboard with: Dashboard overview: Total active clients Total active affiliates Total active coupons Total pre-validation sales Total post-validation sales Outstanding client payments Pending affiliate payments Media buying spend ROAS summary Filters: Date range Client Market Affiliate Coupon Platform Validation status Payment status Exports: Excel / CSV export PDF export optional 6. User Roles & Access The system should have role-based access. Suggested roles: Super Admin Management Operations Finance Media Buying Team Affiliate Team Read-only viewer Example permissions: Finance can manage payment sections Media team can manage campaign section Ops can manage clients, coupons, affiliates, reports Management can view everything Some users should only have read access 7. Audit Trail / Logs The system should keep a history log for important actions: who created a record who edited a record what changed when it changed validation changes payment status changes This is important for accountability and tracking. 8. Technical Expectations Please build the system with the following in mind: Web-based system Secure login Role-based permissions Scalable database structure API-ready architecture Fast search and filtering Export functionality Data backup and recovery Ability to add more modules later Mobile-friendly admin view is a plus 9. Deliverables Expected from Developer We need the developer to provide: Full proposed system architecture Database structure / schema Recommended tech stack UI/UX wireframe or prototype API integration plan Development timeline by phase Cost estimate Future scalability recommendations 10. Priority for Phase 1 If building in phases, Phase 1 should include: Client section Coupon section Affiliate section Basic reporting section Pre-validation and post-validation logic Payment section Meta and Google Ads API integration Dashboard overview 11. Main Business Outcome This system is meant to give Qouponi a single source of truth for: client management coupon management affiliate management reporting validation collections affiliate payouts media buying performance It should reduce manual work, reduce errors, improve accountability, and give management full visibility across the business.

برمجة منصة affiliate

نقاط الجدية مشروع جاد