Reuse Complex Query Logic Cleanly in Laravel Using clone()

In Laravel, you often build a base query like this:

$baseQuery = Order::query()
    ->where('status', 'paid')
    ->whereDate('created_at', now()->today());

Then later:

$totalOrders = $baseQuery->count();
$totalRevenue = $baseQuery
    ->sum('amount');

👉 Looks fine… but query builders are mutable.

Changes affect the same instance.

The Safer Solution: clone

Use PHP’s clone keyword when reusing queries.

Correct Usage

$baseQuery = Order::query()
    ->where('status', 'paid');
$totalOrders = (clone $baseQuery)->count();
$totalRevenue = (clone $baseQuery)->sum('amount');

Why This Matters

Without cloning:

$baseQuery->where('amount', '>', 1000);

👉 The original query also changes unexpectedly.

With cloning:

• Each query becomes isolated
• No side effects
• Cleaner logic

Real Project Example

Dashboard statistics:

$baseQuery = Order::query()
    ->whereMonth('created_at', now()->month);
$totalOrders = (clone $baseQuery)->count();
$completedOrders = (clone $baseQuery)
    ->where('status', 'completed')
    ->count();
$totalRevenue = (clone $baseQuery)->sum('amount');