# Customer Type Filtering Solution for Products

## Current Status ✅

Good news! Your database and backend are **already properly configured** to handle products that serve both Business and Wholesale segments.

## Database Structure

### Current Schema
The `product_packages` table has a `customer_type` column with three possible values:

```sql
customer_type ENUM('business', 'wholesale', 'both') DEFAULT 'both'
```

- `business` = Partner/Company customers only
- `wholesale` = Enterprise/Individual customers only  
- `both` = Available to BOTH customer types

### Backend Logic ✅
The ProductController already filters correctly:

```php
if ($request->has('customer_type') && in_array($request->customer_type, ['business', 'wholesale'])) {
    $query->where(function ($q) use ($request) {
        $q->where('customer_type', $request->customer_type)
          ->orWhere('customer_type', 'both');  // ✅ Includes 'both' products
    });
}
```

This means:
- When frontend sends `customer_type=business`, backend returns products with `customer_type='business'` OR `customer_type='both'`
- When frontend sends `customer_type=wholesale`, backend returns products with `customer_type='wholesale'` OR `customer_type='both'`

## Product Mapping from Your Table

Based on your nomenclature table, here's how products should be configured:

| Product Name | In-house Name | Customer Type | Feasibility Test |
|--------------|---------------|---------------|------------------|
| Magellan Metro-VPN | Magellan | `both` | Yes |
| Shared Business Broadband | Shared Broadband | `business` | Yes |
| Dedicated Burst Internet | Dedicated Burst | `business` | Yes |
| Dedicated Internet Access | DIA | `business` | No |
| IP Transit | IP Transit | `both` | No |
| Dark Fibre Lease | Dark Fibre | `wholesale` | No |
| International Private Line Circuit | International Longhaul | `wholesale` | No |
| InterCity-VPN | Longhaul | `both` | No |

## Database Update Required

You need to update existing products in the database to set the correct `customer_type` value:

### SQL Update Script

```sql
-- Products for Business only
UPDATE product_packages 
SET customer_type = 'business' 
WHERE code IN ('SHARED_BROADBAND', 'DEDICATED_BURST', 'DIA');

-- Products for Wholesale only
UPDATE product_packages 
SET customer_type = 'wholesale' 
WHERE code IN ('DARK_FIBRE', 'IPLC');

-- Products for Both Business and Wholesale
UPDATE product_packages 
SET customer_type = 'both' 
WHERE code IN ('MAGELLAN', 'IP_TRANSIT', 'INTERCITY_VPN');

-- Verify the changes
SELECT code, name, customer_type, package_type 
FROM product_packages 
ORDER BY customer_type, code;
```

## Frontend - No Changes Needed! ✅

Your frontend code is already correct:

```javascript
// In products page.js
const customerType = customer?.type === 'company' ? 'business' : 'wholesale';
const { data: productsResponse } = useAvailableProducts(checkId, null, customerType);
```

This works because:
1. Frontend sends either `business` or `wholesale`
2. Backend returns products matching that type OR `both`
3. Products marked as `both` appear for all customers

## Verification Steps

After updating the database, verify the filtering works:

### Test Case 1: Company Customer (Business)
```
Login as: customer.type = 'company'
Expected: See products with customer_type = 'business' OR 'both'
Should see: Shared Broadband, Dedicated Burst, DIA, Magellan, IP Transit, InterCity-VPN
Should NOT see: Dark Fibre, IPLC
```

### Test Case 2: Individual Customer (Wholesale)
```
Login as: customer.type = 'individual'
Expected: See products with customer_type = 'wholesale' OR 'both'
Should see: Dark Fibre, IPLC, Magellan, IP Transit, InterCity-VPN
Should NOT see: Shared Broadband, Dedicated Burst, DIA
```

## Migration File (Optional)

If you want to create a migration to set default values for existing products:

```php
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Support\Facades\DB;

return new class extends Migration
{
    public function up(): void
    {
        // Business only products
        DB::table('product_packages')
            ->whereIn('code', ['SHARED_BROADBAND', 'DEDICATED_BURST', 'DIA'])
            ->update(['customer_type' => 'business']);

        // Wholesale only products
        DB::table('product_packages')
            ->whereIn('code', ['DARK_FIBRE', 'IPLC'])
            ->update(['customer_type' => 'wholesale']);

        // Both business and wholesale
        DB::table('product_packages')
            ->whereIn('code', ['MAGELLAN', 'IP_TRANSIT', 'INTERCITY_VPN'])
            ->update(['customer_type' => 'both']);
    }

    public function down(): void
    {
        // Reset all to 'both' (the default)
        DB::table('product_packages')
            ->update(['customer_type' => 'both']);
    }
};
```

## Summary

✅ **Database schema**: Already supports 'both' value  
✅ **Backend filtering**: Already handles 'both' correctly  
✅ **Frontend code**: Already sends correct customer_type  
⚠️ **Action needed**: Update existing product records with correct customer_type values

The logic for products with both wholesale and business IS accounted for in the filtering - you just need to set the correct `customer_type` value in your product records!