shopcall/MISSING_FEATURES.md

ShopCall.ai - Missing Features & Incomplete Implementation Report

Generated: 2025-10-22 Project: ShopCall.ai (AI-powered calling system for e-commerce) Repositories:

• Frontend: shopcall.ai-main (React/Vite/TypeScript)
• Backend: shopcall.ai-backend-main (Express.js/Node.js)

---

🔴 CRITICAL MISSING FEATURES

1. Onboarding Flow - Not Connected to Backend

Location: shopcall.ai-main/src/components/OnboardingContent.tsx

Status: UI complete, backend integration missing

Issues:

• ❌ No API integration for submitting onboarding data
• ❌ Shopify connection flow exists in UI but doesn't save to backend
• ❌ Phone number selection doesn't persist
• ❌ Package selection doesn't create subscription
• ❌ handleFinish() function only redirects to homepage (line 100-108)

Missing Backend Endpoints:

POST /api/onboarding/complete
  Body: {
    shopifyUrl: string,
    selectedPhone: string,
    selectedPackage: string
  }

Impact: Users can complete onboarding but nothing is saved. On next login, they'll need to onboard again.

Effort: Medium (2-3 days)

---

2. Shopify OAuth Integration Incomplete

Location: shopcall.ai-backend-main/api/index.js:532-597

Status: OAuth flow works, but tokens not persisted

Issues:

• ✅ OAuth authorization flow implemented
• ✅ Token exchange working
• ❌ TODO Comment (line 586): "Save tokenJson.access_token securely" - tokens not being stored
• ❌ No store record created in stores table after successful OAuth
• ❌ Redirect goes to homepage (https://shopcall.ai/) instead of dashboard
• ❌ User-to-store relationship not established

Current Code:

// Line 586
// TODO: Save tokenJson.access_token securely
console.log(`Successfully authenticated shop: ${normalizedShop}`);

res.redirect(`https://shopcall.ai/`);

Required Fix:

// Save to database
const { data: storeData, error: storeError } = await supabase
  .from('stores')
  .insert({
    user_id: nonceData.userId, // from nonce
    platform_name: 'shopify',
    store_name: normalizedShop.split('.')[0],
    store_url: `https://${normalizedShop}`,
    access_token: tokenJson.access_token,
    scopes: tokenJson.scope.split(','),
    connected_at: new Date().toISOString()
  });

res.redirect(`https://shopcall.ai/dashboard?connected=true`);

Impact: Shopify stores cannot be properly connected. OAuth succeeds but connection is lost immediately.

Effort: Small (1 day)

---

3. Phone Number Management - UI Only

Location: shopcall.ai-main/src/components/PhoneNumbersContent.tsx

Status: Complete UI mockup with static data

Issues:

• ❌ All data is hardcoded in connectedShops, availableCountries, carriers arrays
• ❌ No backend API for phone number operations
• ❌ "Get Number" button (line 278) - no handler
• ❌ "Assign" button (line 196-199) - no handler
• ❌ "Connect" carrier buttons (line 231-234) - no handler
• ❌ Cannot actually purchase or assign phone numbers

Missing Backend Endpoints:

GET    /api/phone-numbers              # List phone numbers for user
POST   /api/phone-numbers              # Purchase new phone number
PUT    /api/phone-numbers/:id/assign   # Assign number to store
DELETE /api/phone-numbers/:id          # Release phone number

POST   /api/carriers/connect            # Connect external carrier (Twilio, etc.)
GET    /api/carriers                    # List connected carriers

Missing Database Tables:

CREATE TABLE phone_numbers (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID REFERENCES profiles(id),
  store_id UUID REFERENCES stores(id),
  number VARCHAR(20) NOT NULL,
  country VARCHAR(2) NOT NULL,
  type VARCHAR(20), -- 'local', 'toll-free'
  carrier VARCHAR(50), -- 'internal', 'twilio', 'telnyx', etc.
  status VARCHAR(20), -- 'active', 'pending_kyc', 'inactive'
  monthly_cost DECIMAL(10,2),
  carrier_config JSONB, -- carrier-specific data
  created_at TIMESTAMP DEFAULT NOW(),
  assigned_at TIMESTAMP
);

CREATE TABLE carrier_integrations (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID REFERENCES profiles(id),
  carrier_name VARCHAR(50), -- 'twilio', 'telnyx', 'vonage', 'zadarma'
  credentials JSONB, -- encrypted API keys
  is_active BOOLEAN DEFAULT true,
  created_at TIMESTAMP DEFAULT NOW()
);

Impact: Core feature completely non-functional. Users cannot set up phone numbers which are essential for the service to work.

Effort: Large (5-7 days including carrier API integrations)

---

4. AI Configuration - UI Only

Location: shopcall.ai-main/src/components/AIConfigContent.tsx

Status: Complete UI for AI settings, no backend persistence

Issues:

• ❌ All settings stored only in component state
• ❌ "Save Configuration" button (line 55) - no handler
• ❌ "Sync Store Data" button (line 247) - no handler
• ❌ "Test Configuration" button (line 253) - no handler
• ❌ "Copy from Another Shop" button (line 52) - no handler
• ❌ Voice settings, greeting messages, escalation policy, knowledge base - none saved

Missing Backend Endpoints:

GET  /api/ai-config/:storeId           # Get AI config for store
POST /api/ai-config/:storeId           # Create/update AI config
POST /api/ai-config/:storeId/test      # Test AI configuration
POST /api/ai-config/:storeId/sync      # Sync store data (products, policies)
POST /api/ai-config/:storeId/copy      # Copy config from another store

Missing Database Table:

CREATE TABLE ai_configurations (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  store_id UUID REFERENCES stores(id) UNIQUE,

  -- Voice settings
  voice_type VARCHAR(50) DEFAULT 'sarah',
  speaking_speed VARCHAR(20) DEFAULT 'normal',
  accent VARCHAR(50) DEFAULT 'us-english',

  -- Conversation behavior
  greeting_message TEXT,
  business_hours_mode BOOLEAN DEFAULT true,
  local_currency_support BOOLEAN DEFAULT true,
  escalation_policy VARCHAR(20) DEFAULT 'medium',

  -- Knowledge base
  product_catalog_synced BOOLEAN DEFAULT false,
  product_catalog_last_sync TIMESTAMP,
  store_policies TEXT,
  faq_database JSONB,
  custom_knowledge JSONB,

  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

Impact: AI cannot be customized per webshop. All stores would use default settings, making the service less valuable.

Effort: Medium-Large (4-5 days)

---

🟡 HIGH PRIORITY MISSING FEATURES

5. Analytics Data - All Mocked

Location: shopcall.ai-main/src/components/AnalyticsContent.tsx

Status: Complete UI with charts, all using static data

Issues:

• ❌ weeklyData, resolutionData, callDurationData, topIntentsData, etc. - all hardcoded (lines 6-58)
• ❌ Charts display fake data
• ❌ No real metrics calculation
• ❌ Peak hours heatmap generated randomly (line 130)

Missing Backend Endpoints:

GET /api/analytics/overview?timeRange=week       # KPIs and overview charts
GET /api/analytics/trends?timeRange=month        # Trend analysis
GET /api/analytics/performance?timeRange=week    # Performance metrics
GET /api/analytics/call-volume?groupBy=day       # Call volume data
GET /api/analytics/intents?limit=10              # Top call intents

Required Aggregation Logic:

• Call volume by day/hour/week
• Resolution rate calculation
• Average call duration by intent
• Peak hours analysis
• Sentiment distribution
• Cost analysis

Impact: Dashboard shows misleading fake data. Users cannot make data-driven decisions.

Effort: Medium (3-4 days for proper aggregation queries)

---

6. Dashboard KPIs - Hardcoded

Location:

• shopcall.ai-main/src/components/KPICards.tsx
• shopcall.ai-main/src/components/ChartsSection.tsx
• shopcall.ai-main/src/components/RecentCallsTable.tsx

Status: Complete UI, static mock data

Issues:

• ❌ All KPI values hardcoded
• ❌ Charts show static data
• ❌ Recent calls table shows hardcoded 5 calls (lines 8-64 in RecentCallsTable.tsx)
• ❌ No refresh functionality

Missing Backend Endpoint:

GET /api/dashboard/summary?timeRange=24h
  Response: {
    totalCalls: number,
    resolvedCalls: number,
    activeConversations: number,
    avgResponseTime: number,
    resolutionRate: number,
    avgCallDuration: number,
    totalCost: number,
    chartData: {
      callVolume: [...],
      resolutionRate: [...]
    },
    recentCalls: [...]
  }

Impact: Dashboard is just a demo, not showing real data.

Effort: Small-Medium (2-3 days, reuses analytics logic)

---

7. Webshop Integration Management - Partially Implemented

Location: shopcall.ai-main/src/components/IntegrationsContent.tsx

Status: Backend APIs exist, frontend not connected

Issues:

• ✅ Backend has GET /api/stores (line 800)
• ✅ Backend has PUT /api/stores/:id (line 855)
• ✅ Backend has DELETE /api/stores/:id (line 893)
• ❌ Frontend shows hardcoded connectedShops array (lines 10-86)
• ❌ "Connect Webshop" button (line 96-99) doesn't trigger OAuth
• ❌ Settings buttons (line 202) don't open edit modal
• ❌ No fetch call to /api/stores

Required Frontend Changes:

const [stores, setStores] = useState([]);

useEffect(() => {
  const fetchStores = async () => {
    const response = await fetch('https://shopcall-ai-backend.vercel.app/api/stores', {
      headers: { 'Authorization': `Bearer ${token}` }
    });
    const data = await response.json();
    setStores(data.stores);
  };
  fetchStores();
}, []);

Impact: Users see fake store list instead of their actual connected stores.

Effort: Small (1 day to connect frontend to existing backend)

---

8. Call Recording Playback

Location: shopcall.ai-main/src/components/CallDetailsModal.tsx

Status: UI exists, no audio implementation

Issues:

• ❌ Play button exists (line 145-152) but no audio player
• ❌ recording_url field in call_logs table not used
• ❌ No audio streaming functionality
• ❌ No waveform visualization
• ❌ Progress bar not functional (line 159-161)

Required Implementation:

const [audio] = useState(new Audio());
const [isPlaying, setIsPlaying] = useState(false);
const [currentTime, setCurrentTime] = useState(0);
const [duration, setDuration] = useState(0);

useEffect(() => {
  if (call.recording_url) {
    audio.src = call.recording_url;
    audio.addEventListener('loadedmetadata', () => {
      setDuration(audio.duration);
    });
    audio.addEventListener('timeupdate', () => {
      setCurrentTime(audio.currentTime);
    });
  }
}, [call.recording_url]);

const handlePlayPause = () => {
  if (isPlaying) {
    audio.pause();
  } else {
    audio.play();
  }
  setIsPlaying(!isPlaying);
};

Impact: Cannot review call recordings, limiting quality assurance capabilities.

Effort: Small (1-2 days)

---

9. WooCommerce Integration - Incomplete

Location: shopcall.ai-backend-main/api/index.js:463-529

Status: OAuth callback implemented, token storage works

Issues:

• ✅ OAuth initiation works (line 463)
• ✅ Callback saves credentials (line 481)
• ❌ No frontend UI to trigger WooCommerce connection
• ❌ No WooCommerce-specific configuration options
• ❌ Product sync not implemented
• ❌ No webhook setup for order updates

Missing Features:

• WooCommerce product catalog sync
• Order status webhooks
• Customer data integration
• Store policy import

Impact: WooCommerce support advertised but not fully functional.

Effort: Medium (3-4 days for full WooCommerce integration)

---

🟢 MEDIUM PRIORITY MISSING FEATURES

10. Search & Filtering

Location: Multiple components

Issues:

• ❌ Call logs search input exists but no filter logic (CallLogsContent.tsx:118-124)
• ❌ "Filters" button exists but no filter panel (CallLogsContent.tsx:126-129)
• ❌ Date range picker button non-functional (CallLogsContent.tsx:107-111)
• ❌ No backend support for query parameters

Required Backend Changes:

GET /api/call-logs?search=xxx&status=completed&outcome=resolved&dateFrom=...&dateTo=...

Required Frontend Changes:

• Search debouncing
• Filter panel UI
• Date range picker integration
• Query string management

Impact: Users must manually scroll through all calls, poor UX for high-volume users.

Effort: Small-Medium (2-3 days)

---

11. Export Functionality

Location: shopcall.ai-main/src/components/CallLogsContent.tsx:102-105

Status: Button exists, no implementation

Issues:

• ❌ Export button present but no click handler
• ❌ No backend endpoint for data export
• ❌ No file format options (CSV, PDF, Excel)

Missing Backend Endpoint:

GET /api/call-logs/export?format=csv&dateFrom=...&dateTo=...
  Response: CSV/PDF file download

Required Features:

• CSV export (for Excel)
• PDF export (formatted report)
• Email export option
• Export scheduling (weekly/monthly reports)

Impact: Users cannot extract data for external analysis or reporting.

Effort: Small (1-2 days)

---

12. Real-time Updates

Status: Not implemented

Issues:

• ❌ No WebSocket connection for live updates
• ❌ Dashboard requires manual refresh
• ❌ No notification system for new calls
• ❌ Active call status not real-time

Required Implementation:

• WebSocket server (Socket.io or native WebSockets)
• Real-time call status updates
• Live dashboard KPI updates
• Browser notifications

Missing Infrastructure:

// Backend
const io = require('socket.io')(server);

io.on('connection', (socket) => {
  socket.on('authenticate', async (token) => {
    // Validate token and join user room
    socket.join(`user_${userId}`);
  });
});

// Emit on new call
io.to(`user_${userId}`).emit('new_call', callData);

Impact: Users miss real-time updates, dashboard feels outdated.

Effort: Medium (3-4 days for WebSocket implementation)

---

13. User Profile Management

Status: Not implemented

Issues:

• ❌ No profile page/route
• ❌ Cannot edit profile information (name, company, email)
• ❌ No password change functionality
• ❌ No account deletion option
• ❌ profiles table exists but no edit endpoint

Missing Endpoints:

GET    /api/profile                    # Get current user profile
PUT    /api/profile                    # Update profile
POST   /api/profile/change-password    # Change password
DELETE /api/profile                    # Delete account

Missing Frontend Pages:

• /settings/profile - Profile edit page
• /settings/security - Password change
• /settings/account - Account management

Impact: Users stuck with initial registration data. Cannot fix typos or update information.

Effort: Small-Medium (2-3 days)

---

14. Payment Integration

Location: OnboardingContent.tsx:31-80 - Package selection UI

Status: Package selection UI only

Issues:

• ❌ No payment gateway integration (Stripe, PayPal, etc.)
• ❌ Package selection doesn't create subscription
• ❌ No billing page
• ❌ No invoice generation
• ❌ No payment history
• ❌ Free trial not tracked

Missing Implementation:

• Stripe/PayPal SDK integration
• Subscription management
• Webhook handling for payment events
• Billing portal

Missing Endpoints:

POST   /api/subscriptions/create        # Create subscription
GET    /api/subscriptions/current       # Get current subscription
POST   /api/subscriptions/cancel        # Cancel subscription
POST   /api/subscriptions/upgrade       # Upgrade plan
GET    /api/invoices                    # List invoices

Missing Database Table:

CREATE TABLE subscriptions (
  id UUID PRIMARY KEY,
  user_id UUID REFERENCES profiles(id),
  plan_id VARCHAR(50), -- 'free-trial', 'starter', 'professional'
  status VARCHAR(20), -- 'active', 'cancelled', 'past_due'
  stripe_subscription_id VARCHAR(100),
  current_period_start TIMESTAMP,
  current_period_end TIMESTAMP,
  cancel_at_period_end BOOLEAN,
  created_at TIMESTAMP DEFAULT NOW()
);

Impact: Cannot monetize the service. All users have unlimited access.

Effort: Large (5-7 days for full payment integration)

---

15. Email Notifications

Status: Only OTP emails implemented

Issues:

• ✅ OTP email works (sendOTPEmail function exists)
• ❌ No call summary emails
• ❌ No alerts for failed calls
• ❌ No weekly/monthly reports
• ❌ No password reset emails
• ❌ No subscription notifications

Missing Email Templates:

• Call completed summary
• Failed call alert
• Weekly activity report
• Monthly invoice
• Password reset
• Subscription renewal reminder

Required Implementation:

• Email template system (Handlebars, Pug, etc.)
• Email queue (Bull, BullMQ)
• Background job processing
• Email service (SendGrid, Mailgun, or continue with Nodemailer)

Impact: Users not notified of important events. Must check dashboard constantly.

Effort: Medium (3-4 days)

---

🔵 LOW PRIORITY / NICE TO HAVE

16. Advanced Call Features

Missing Features:

• ❌ Call forwarding to human agents (escalation)
• ❌ Voicemail functionality
• ❌ Call scheduling (schedule calls for later)
• ❌ SMS fallback (if call fails, send SMS)
• ❌ Call recording consent management (GDPR)
• ❌ IVR (Interactive Voice Response) menu
• ❌ Call queuing
• ❌ After-hours handling

Impact: Basic AI calling only. Limited flexibility.

Effort: Large (ongoing feature development)

---

17. Team Collaboration

Status: Not implemented (single-user only)

Missing Features:

• ❌ Multi-user accounts (team members)
• ❌ Roles & permissions (admin, agent, viewer)
• ❌ Team member invitation
• ❌ Shared call notes/comments
• ❌ Call assignment to team members
• ❌ Activity logs

Required Database Tables:

CREATE TABLE team_members (
  id UUID PRIMARY KEY,
  organization_id UUID,
  user_id UUID REFERENCES profiles(id),
  role VARCHAR(20), -- 'owner', 'admin', 'agent', 'viewer'
  permissions JSONB,
  invited_by UUID,
  invited_at TIMESTAMP,
  joined_at TIMESTAMP
);

CREATE TABLE organizations (
  id UUID PRIMARY KEY,
  name VARCHAR(255),
  owner_id UUID REFERENCES profiles(id),
  created_at TIMESTAMP
);

Impact: Only suitable for solo users. Cannot scale to businesses with teams.

Effort: Large (7-10 days)

---

18. API Documentation

Status: Not implemented

Missing:

• ❌ No public API documentation
• ❌ No API keys for developers
• ❌ No webhooks for third-party integrations
• ❌ No SDK/client libraries
• ❌ No API rate limiting
• ❌ No API versioning

Required:

• OpenAPI/Swagger documentation
• API key generation endpoint
• Webhook configuration UI
• Developer portal

Impact: Cannot integrate with external tools. Limited extensibility.

Effort: Medium (3-5 days for basic API docs + key management)

---

19. Testing Coverage

Status: No tests exist

Missing:

• ❌ No unit tests (frontend or backend)
• ❌ No integration tests
• ❌ No E2E tests
• ❌ No test coverage reports

Required:

• Jest + React Testing Library (frontend)
• Jest + Supertest (backend)
• Playwright/Cypress (E2E)
• CI/CD pipeline with test gates

Impact: High risk of bugs, difficult to refactor safely.

Effort: Ongoing (20-30% of development time)

---

20. Additional E-commerce Platforms

Status: Shopify & WooCommerce partially implemented

Missing Platforms:

• ❌ BigCommerce
• ❌ Magento
• ❌ Squarespace
• ❌ Wix
• ❌ PrestaShop
• ❌ Custom/Generic REST API integration

Required:

• OAuth flows for each platform
• Product sync adapters
• Order webhook handlers
• Platform-specific configuration

Impact: Limited market reach. Many e-commerce users excluded.

Effort: Large per platform (4-5 days each)

---

📝 TODO COMMENTS IN CODE

Backend (shopcall.ai-backend-main/api/index.js)

1. Line 586: // TODO: Save tokenJson.access_token securely

   • Context: Shopify OAuth callback
   • Issue: Access tokens not being stored in database
   • Priority: 🔴 Critical

2. Line 604: // TODO: Retrieve access token from database

   • Context: Product API endpoint
   • Issue: Incomplete API endpoint implementation
   • Priority: 🟡 High

3. Line 677: // TODO: Implement your business logic here

   • Context: GDPR webhook processing
   • Issue: Webhook processing empty
   • Priority: 🟡 High (GDPR compliance issue)

Frontend

• No TODO comments found in source code

---

🎯 SUMMARY BY PRIORITY

Priority	Category	Count	Estimated Effort
🔴 Critical	Core functionality blockers	4	12-15 days
🟡 High	Major features incomplete	5	15-20 days
🟢 Medium	UX and data issues	6	15-20 days
🔵 Low	Enhancement features	5	40-50 days
TOTAL		20	82-105 days

---

💡 RECOMMENDED DEVELOPMENT ORDER

Phase 1: Critical Fixes (2-3 weeks)

1. Complete Shopify OAuth - Save tokens, create store records
2. Connect Integrations UI to backend - Use existing /api/stores endpoints
3. Implement Phone Number Management APIs - Critical for service to work
4. Implement AI Configuration APIs - Required for customization

Phase 2: Data & Analytics (2-3 weeks)

1. Connect Analytics to real data - Replace mock data with real queries
2. Connect Dashboard KPIs - Real-time metrics
3. Onboarding flow backend integration - Save user selections
4. Call recording playback - Audio player implementation

Phase 3: User Experience (2-3 weeks)

1. Add search & filtering - Improve call log navigation
2. Export functionality - CSV/PDF export
3. User profile management - Edit profile, change password
4. Email notifications - Call summaries, alerts

Phase 4: Monetization & Growth (3-4 weeks)

1. Implement payment system - Stripe integration
2. Real-time updates - WebSocket implementation
3. Complete WooCommerce integration - Product sync, webhooks
4. Team collaboration features - Multi-user support

Phase 5: Enhancement & Scale (Ongoing)

1. Advanced call features - Forwarding, voicemail, scheduling
2. API documentation - Public API + webhooks
3. Additional e-commerce platforms - BigCommerce, Magento
4. Testing coverage - Unit, integration, E2E tests

---

🔍 TECHNICAL DEBT ITEMS

1. In-memory state stores (pendingSignups, nonceStore Maps in api/index.js)

   • ⚠️ Will reset on serverless function cold starts
   • Should use Redis or database

2. Hardcoded URLs in frontend

   • Backend URL: https://shopcall-ai-backend.vercel.app (should be env variable)
   • Frontend URL: https://shopcall.ai (should be env variable)

3. No database migrations system

   • Using Supabase migrations manually
   • Should have automated migration tool

4. No error tracking

   • No Sentry or error monitoring
   • Console.log only

5. No API versioning

   • Breaking changes will break all clients
   • Should implement /api/v1/...

6. No rate limiting

   • API endpoints not protected
   • Vulnerable to abuse

---

📊 FEATURE COMPLETENESS MATRIX

Feature Category	UI Complete	Backend Complete	Integration Complete	Overall
Authentication	✅ 100%	✅ 100%	✅ 100%	✅ 100%
Onboarding	✅ 100%	❌ 0%	❌ 0%	⚠️ 33%
Dashboard	✅ 100%	⚠️ 50%	❌ 30%	⚠️ 60%
Call Logs	✅ 100%	✅ 90%	✅ 90%	✅ 93%
Analytics	✅ 100%	❌ 0%	❌ 0%	⚠️ 33%
Integrations	✅ 100%	✅ 80%	❌ 20%	⚠️ 67%
Phone Numbers	✅ 100%	❌ 0%	❌ 0%	⚠️ 33%
AI Config	✅ 100%	❌ 0%	❌ 0%	⚠️ 33%
User Profile	❌ 0%	⚠️ 50%	❌ 0%	❌ 17%
Payments	⚠️ 50%	❌ 0%	❌ 0%	❌ 17%
OVERALL				⚠️ 48%

---

🚨 SECURITY & COMPLIANCE CONCERNS

1. GDPR Webhooks Not Implemented (line 677)

   • Shopify GDPR webhooks receive data but don't process it
   • Legal compliance issue

2. No API Key Encryption

   • Store API keys/tokens stored in plain text
   • Should use encryption at rest

3. No Session Management

   • Tokens in localStorage never expire on frontend
   • No refresh token mechanism

4. No CORS Configuration Per Environment

   • CORS enabled globally with app.use(cors())
   • Should restrict origins

5. Email Credentials in Code

   • Default Gmail credentials in code (lines 36-38)
   • Should be env-only

---

📋 NEXT STEPS

1. Prioritize Phase 1 (Critical fixes)
2. Set up project tracking (GitHub Projects, Jira, etc.)
3. Create detailed tickets for each feature
4. Establish CI/CD pipeline with test gates
5. Set up error monitoring (Sentry)
6. Document API as features are completed
7. Create staging environment for testing

---

Report End - For questions or clarifications, refer to source code locations provided in each section.