Customer Management

Purpose and Scope

This document provides an overview of the customer management system in GP247/Shop. It covers the customer data model, authentication mechanisms, and administrative interfaces for managing customer accounts and addresses.

For detailed information about customer authentication and frontend registration flows, see Customer Authentication. For administrative CRUD operations and address management, see Customer Administration. For information about customer-specific API endpoints, see Customer API.

---

Customer Data Model

The ShopCustomer model represents customer accounts in the system. It extends Laravel's Authenticatable class to support authentication and uses several traits for enhanced functionality.

Core Model Structure

Sources: src/Models/ShopCustomer.php1-195

Key Model Attributes and Methods

Attribute/Method	Type	Description
$table	string	shop_customer
$guarded	array	Empty (all fields mass assignable)
$hidden	array	password, remember_token
$appends	array	name (computed attribute)
orders()	Relationship	HasMany relationship to ShopOrder
addresses()	Relationship	HasMany relationship to ShopCustomerAddress
getNameAttribute()	Accessor	Concatenates first_name and last_name
getAddressDefault()	Method	Returns the customer's default address
isVerified()	Method	Checks if email_verified_at is not null
hasVerifiedEmail()	Method	Returns true if verification required but not completed
sendEmailVerify()	Method	Sends verification email if required

Sources: src/Models/ShopCustomer.php25-194

UUID Generation and Lifecycle Hooks

The model uses the UuidTrait to automatically generate customer IDs with the prefix "CUS":

Sources: src/Models/ShopCustomer.php71-93

Customer Creation and Updates

The model provides static methods for creating and updating customers:

Sources: src/Models/ShopCustomer.php96-142

---

Email Verification System

The customer model integrates with Laravel's email verification system and provides configuration-driven verification requirements.

Verification Flow

Sources: src/Models/ShopCustomer.php164-194 src/Middleware/EmailIsVerifiedMiddleware.php1-39

Email Verification Middleware

The EmailIsVerifiedMiddleware enforces email verification based on the customer_verify configuration:

Route Name	Behavior
customer.verify	Allowed for unverified users
customer.verify_resend	Allowed for unverified users
customer.verify_process	Allowed for unverified users
customer.logout	Allowed for unverified users
All other routes	Blocked if unverified, redirected to customer.verify

Sources: src/Middleware/EmailIsVerifiedMiddleware.php17-38

---

Configuration-Driven Field Visibility

Customer fields are highly configurable through the gp247_config_admin() function, allowing different stores to require different customer information.

Field Configuration Map

Sources: src/Views/admin/screen/customer_edit.blade.php24-332

Example Configuration Checks

The admin customer edit view uses configuration checks throughout to conditionally render fields:

Configuration Key	Controls	View Lines
customer_lastname	First/Last name split vs single name field	24-80
customer_name_kana	Japanese phonetic name fields	82-119
customer_phone	Phone number field	121-140
customer_postcode	Postal code field	142-162
customer_address2	Secondary address line	203-221
customer_address3	Tertiary address line	223-241
customer_country	Country selection dropdown	244-266
customer_sex	Gender selection	268-288
customer_birthday	Date of birth field	290-310
customer_group	Customer group number	312-332

Sources: src/Views/admin/screen/customer_edit.blade.php24-332

---

Customer Address Management

Customers can have multiple addresses, with one designated as the default address stored in ShopCustomer.address_id.

Address Relationships

Sources: src/Models/ShopCustomer.php40-48 src/Models/ShopCustomer.php145-154

Address Operations

The admin interface provides address management functionality:

Operation	Route	Description
View addresses	customer_edit view	Displays all addresses for a customer
Edit address	admin_customer.update_address	Updates an existing address
Delete address	admin_customer.delete_address	Deletes an address (AJAX)
Default indicator	Visual badge	Shows which address is the default

Sources: src/Views/admin/screen/customer_edit.blade.php399-490

Address Deletion Flow

Sources: src/Views/admin/screen/customer_edit.blade.php467-487

---

Password Reset and Recovery

The ShopCustomer model overrides Laravel's default password reset notification to use the GP247 email system.

Password Reset Flow

Sources: src/Models/ShopCustomer.php50-59

---

Social Login Integration

The ShopCustomer model uses the SocialAccountTrait to support social login providers when the LoginSocial plugin is active.

Social Login Configuration

Sources: src/Models/ShopCustomer.php16 src/Views/front/auth/login.blade.php45-51

---

Multi-Store Customer Isolation

Customers are isolated by store_id in multi-store environments:

Field	Purpose
store_id	Links customer to specific store/vendor
Query filtering	Automatically applied in multi-store mode
Root store access	Can view all customers across stores

For more information on multi-store architecture, see Multi-Store and Multi-Vendor Architecture.

Sources: src/Models/ShopCustomer.php25-27

---

Admin Dashboard Customer Display

The admin dashboard includes a component that displays recently registered customers:

Top Customer Component

The component conditionally displays the provider column only if the SocialAccount class exists, indicating the LoginSocial plugin is installed.

Sources: src/Views/admin/component/new_customer.blade.php1-53

---

Custom Field Integration

Customers support custom fields through the GP247 Core custom field system:

Custom Field Lifecycle

Sources: src/Models/ShopCustomer.php71-86 src/Models/ShopCustomer.php104-114 src/Models/ShopCustomer.php125-136 src/Views/admin/screen/customer_edit.blade.php368

The admin customer edit form includes a custom field rendering section at line 368 using the gp247-core::component.render_form_custom_field partial.