Last indexed: 13 December 2025 (dd8fb9)

Order Processing and Email Notifications

This page documents the order creation process, post-order processing, email notification system, and dynamic validation logic that occurs after a customer completes checkout. For the checkout flow leading up to order creation, see page 4.2 (Checkout Process).

Overview

After checkout confirmation, the system executes three primary operations:

Order Creation: Converts cart session data into persistent order records in shop_order, shop_order_detail, and shop_order_total tables
Email Notifications: Sends order confirmation emails to customers and administrators based on configuration
Payment Processing: Delegates to payment plugins for transaction processing

The entry point is ShopCartController::addOrder(), which orchestrates these operations.

Sources:

Order Creation Process

The ShopCartController::addOrder() method handles order creation in Step 06 of the checkout flow. It retrieves data from session storage and constructs database records.

Order Creation Workflow

Diagram: Order Creation Sequence

Sources:

Session Data Requirements

The addOrder method expects the following session keys to be populated during checkout:

Session Key	Description	Set During Step
`dataCheckout`	Cart items for the current store	Step 03 (checkout screen)
`dataTotal`	Total calculations from plugins	Step 05 (checkout confirm)
`shippingAddress`	Customer shipping information	Step 04 (process checkout)
`paymentMethod`	Selected payment method key	Step 04 (process checkout)
`shippingMethod`	Selected shipping method key	Step 04 (process checkout)
`storeCheckout`	Store ID being checked out	Step 02 (prepare checkout)

Sources:

Order Data Structure

Diagram: Order Database Schema

Sources:

Initial Order Status Values

Orders are created with default status constants defined in ShopCartController:

ORDER_STATUS_NEW = 1 // New order, awaiting processing
PAYMENT_UNPAID = 1 // Payment not received
SHIPPING_NOTSEND = 1 // Products not shipped

These constants are used in lines src/Controllers/ShopCartController.php567-569 when constructing the $dataOrder array.

Sources:

Product Detail Processing

For each cart item, the system retrieves current product data and builds order detail records:

This loop constructs the $arrCartDetail array that is passed to ShopOrder::createOrder().

Sources:

src/Controllers/ShopCartController.php617-631

Post-Order Processing

After order creation, the system executes post-processing operations through gp247_order_process_after_success() and delegates to payment plugins if configured.

Post-Order Success Hook

The helper function gp247_order_process_after_success() is called immediately after ShopOrder::createOrder() returns successfully. It handles:

Email notification dispatch
Configuration-based conditional execution
Downloadable product link generation

Diagram: Post-Order Processing Flow

Sources:

Payment Plugin Integration

After email processing, the system checks for a configured payment plugin. If a payment method requires additional processing, control transfers to the plugin's processOrder() method:

Sources:

src/Controllers/ShopCartController.php669-676

Complete Order Method

The completeOrder() method is the final step when no payment plugin processing is required (e.g., cash on delivery). It:

Retrieves the order ID from session
Clears cart for the checked-out store
Clears session checkout data
Redirects to order success page

Diagram: Complete Order Flow

Sources:

src/Controllers/ShopCartController.php998-1033

Email Notifications

The gp247_order_process_after_success() function sends order confirmation emails based on two configuration flags: order_success_to_admin and order_success_to_customer.

Email Configuration Gates

Both email types require email_action_mode to be enabled. If disabled, no emails are sent.

if ((gp247_config('order_success_to_admin') || gp247_config('order_success_to_customer')) 
 && gp247_config('email_action_mode')) {
 // Email processing
}

Sources:

src/Library/Helpers/order.php10

Email Data Preparation

The function loads the complete order with relationships and constructs an $orderDetail array:

Diagram: Email Data Construction

For each order item, the system:

Retrieves the product using ShopProduct::getDetail($detail['product_id'])
Checks if the product has tag == GP247_TAG_DOWNLOAD
If downloadable, adds $product->downloadPath->path to the email data
Formats price using gp247_currency_render()

Sources:

src/Library/Helpers/order.php11-29

Email Template Variables

Both email templates receive identical data structures:

Variable	Type	Description
`$orderID`	string	Order identifier
`$toname`	string	Customer full name (`first_name` + `last_name`)
`$address`	string	Concatenated address fields
`$phone`	string	Customer phone number
`$comment`	string	Order comment/notes
`$currency`	string	Currency code (e.g., "USD")
`$orderDetail`	array	Array of product items with sku, name, price, qty, total, linkDownload
`$subtotal`	string	Rendered subtotal amount
`$shipping`	string	Rendered shipping cost
`$discount`	string	Rendered discount amount
`$otherFee`	string	Rendered other fees
`$total`	string	Rendered total amount

Sources:

Admin Notification Email

Sent to gp247_store_info('email') with subject from language file key email.order.email_subject_to_admin.

The template renders order information and a product table. The gp247_mail_send() function is called with:

Sources:

Customer Notification Email

Sent to the customer's email address ($data['email']) with subject from email.order.email_subject_customer.

Configuration includes a replyTo field set to the store email:

Sources:

Email Template Structure

Both templates extend a base layout and render in a responsive HTML structure:

Sources:

Dynamic Validation

The gp247_order_mapping_validate() helper function generates Laravel validation rules dynamically based on configuration settings. This allows stores to require different customer fields without code changes.

Validation Rule Generation

Diagram: Dynamic Validation Logic

Sources:

src/Library/Helpers/order.php89-210

Configuration-Based Field Validation

The function checks pairs of configuration keys for each optional field:

Field visibility: gp247_config('customer_fieldname') - Controls if field is shown
Field requirement: gp247_config('customer_fieldname_required') - Controls if field is required

Example for last name field:

This pattern repeats for: address1, address2, address3, phone, country, postcode, company, first_name_kana, last_name_kana.

Sources:

src/Library/Helpers/order.php105-175

Validation Rules Table

Field	Conditional Config	Validation Rule (if required)	Validation Rule (if optional)
`first_name`	Always required	`required\|string\|max:100`	N/A
`email`	Always required	`required\|string\|email\|max:255`	N/A
`shippingMethod`	`use_shipping`	`required`	Not added
`paymentMethod`	`use_payment`	`required`	Not added
`last_name`	`customer_lastname`	`required\|string\|max:100`	`nullable\|string\|max:100`
`address1`	`customer_address1`	`required\|string\|max:100`	`nullable\|string\|max:100`
`address2`	`customer_address2`	`required\|string\|max:100`	`nullable\|string\|max:100`
`address3`	`customer_address3`	`required\|string\|max:100`	`nullable\|string\|max:100`
`phone`	`customer_phone`	`required\|regex:/^0[^0][0-9\-]{6,12}$/`	`nullable\|regex:/^0[^0][0-9\-]{6,12}$/`
`country`	`customer_country`	`required\|string\|min:2\|in:{codes}`	`nullable\|string\|min:2\|in:{codes}`
`postcode`	`customer_postcode`	`required\|min:5`	`nullable\|min:5`
`company`	`customer_company`	`required\|string\|max:100`	`nullable\|string\|max:100`
`first_name_kana`	`customer_name_kana`	`required\|string\|max:100`	`nullable\|string\|max:100`
`last_name_kana`	`customer_name_kana`	`required\|string\|max:100`	`nullable\|string\|max:100`

Sources:

src/Library/Helpers/order.php92-175

Usage in Checkout Process

The validation rules are applied during Step 04 (Process Checkout) in ShopCartController::processCheckout():

Sources:

src/Controllers/ShopCartController.php329-348

Custom Validation Messages

The function generates localized validation messages for all fields:

Sources:

src/Library/Helpers/order.php177-204

Payment Integration

The order processing system integrates with payment methods through a plugin architecture. After order creation, if a payment method is configured, the system hands off to the payment plugin's processing method.

Sources:

src/Controllers/ShopCartController.php669-676

Integration Points

The Order Processing system integrates with several other components:

Cart System: Orders are created from cart data
Product System: Order items reference products
Customer System: Orders are associated with customer accounts
Email System: Notifications are sent via the email system
Payment Plugins: Payment processing is delegated to payment method plugins
Shipping Plugins: Shipping methods are used from shipping plugins

Sources:

Conclusion

The Order Processing system forms a critical part of the GP247/Shop e-commerce platform, handling the conversion of shopping carts to orders and managing the entire order lifecycle. Its modular design allows for flexible integration with payment and shipping methods while providing robust administrative tools for order management.

Refresh this wiki

URL: https://deepwiki.com/gp247net/shop/4.3-order-processing-and-email-notifications