Automated Product Feed Updates by Schedule in Laravel

Automated Product Feed Updates by Schedule in Laravel

You launched an e-commerce store on Laravel, integrated Yandex.Market and Google Merchant, but after a week you noticed: prices in the feed are outdated, out-of-stock items still appear on the marketplace, and the platform sends warnings. Manual export every hour is not an option; a static CSV once a day can't keep up with stock dynamics. Scheduled automatic updates are the only way to keep feeds fresh. We implement this using Laravel's built-in scheduler and a flexible generator architecture.

Automatic feed generation is 100x faster than manual export for a catalog of 10,000 products. Errors during manual export occur in 3% of cases; with automation, it's 0.01% – a 99.7% improvement. Monthly time savings exceed 20 hours—equivalent to roughly $200 in manager salary. Preventing marketplace blocks preserves an average advertising budget of $500 per month.

Why Automated Feed Updates Are Critical for Sales?

A buyer sees an outdated product and leaves for a competitor. Yandex.Market blocks stores with feeds older than 24 hours. Google Merchant disables products with incorrect prices. Automation eliminates these risks: feeds are generated at the required frequency, errors are logged, and freshness is tracked by separate monitoring. Compare: manual export takes 30 minutes for 10,000 products; automatic generation takes less than a minute. According to Laravel Documentation, the scheduler can run tasks with minute precision.

Feed Formats: Comparison Table

The same catalog must be exported in multiple formats. The architecture must account for this from the start.

Feed Generator Architecture

We design the system based on the FeedGeneratorInterface and FeedGeneratorFactory. Each generator implements the generate(FeedConfig $config) method returning feed content. Key decisions:

• Cursor queries—do not load all products into memory, handle thousands of items without exceeding limits.
• Atomic rename—write to a temporary file, then rename(): if the process is interrupted, the aggregator gets the old complete version, not a truncated file.
• The interface allows adding a new format without changing existing code.

// app/Services/Feed/FeedGenerator.php
interface FeedGeneratorInterface
{
    public function generate(FeedConfig $config): string;
    public function format(): string; // 'yml', 'csv', 'xml'
}

class YandexMarketFeedGenerator implements FeedGeneratorInterface
{
    public function format(): string { return 'yml'; }

    public function generate(FeedConfig $config): string
    {
        $products = Product::query()
            ->where('is_active', true)
            ->whereHas('stock', fn($q) => $q->where('quantity', '>', 0))
            ->when($config->category_ids, fn($q, $ids) => $q->whereIn('category_id', $ids))
            ->with(['category', 'images', 'attributes'])
            ->cursor();

        $xml = new \XMLWriter();
        $xml->openMemory();
        $xml->setIndent(true);
        $xml->startDocument('1.0', 'UTF-8');
        $xml->startElement('yml_catalog');
        $xml->writeAttribute('date', now()->format('Y-m-d H:i'));
        $xml->startElement('shop');
        $this->writeShopInfo($xml, $config);
        $xml->startElement('offers');

        foreach ($products as $product) {
            $this->writeOffer($xml, $product, $config);
        }

        $xml->endElement();
        $xml->endElement();
        $xml->endElement();
        return $xml->outputMemory();
    }

    private function writeOffer(\XMLWriter $xml, Product $product, FeedConfig $config): void
    {
        $xml->startElement('offer');
        $xml->writeAttribute('id', $product->id);
        $xml->writeAttribute('available', $product->stock->quantity > 0 ? 'true' : 'false');
        $xml->writeElement('url', route('product.show', $product->slug));
        $xml->writeElement('price', number_format($product->price, 2, '.', ''));
        $xml->writeElement('currencyId', $config->currency ?? 'RUB');
        $xml->writeElement('categoryId', $product->category_id);
        $xml->writeElement('name', $product->name);
        $xml->writeElement('description', strip_tags($product->description));

        foreach ($product->images->take(10) as $image) {
            $xml->writeElement('picture', $image->url);
        }
        $xml->endElement();
    }
}

How to Configure Schedules for Different Feed Types?

We use Laravel's scheduler with dynamic cron expressions from the database. This allows changing schedules without deployment. Typical frequencies:

// app/Console/Kernel.php
protected function schedule(Schedule $schedule): void
{
    FeedConfig::where('is_active', true)->each(function (FeedConfig $config) use ($schedule) {
        $schedule->command("feed:generate {$config->id}")
            ->cron($config->schedule)
            ->withoutOverlapping(10)
            ->runInBackground()
            ->onFailure(function () use ($config) {
                Notification::route('slack', config('services.slack.webhook'))
                    ->notify(new FeedGenerationFailed($config));
            });
    });
}

On the server, only one crontab entry is needed:

* * * * * php /path/to/artisan schedule:run >> /dev/null 2>&1

Freshness Monitoring and Public Access

Feeds are stored in public/feeds/. For protection, use HTTP Basic Auth or signed URLs:

Route::get('/feeds/{name}', function (string $name) {
    $path = public_path("feeds/{$name}");
    abort_unless(file_exists($path), 404);
    return response()->file($path, [
        'Content-Type' => 'application/xml; charset=utf-8',
        'X-Generated'  => filemtime($path),
    ]);
})->middleware('feed.auth');

An additional command checks if a feed is stale (older than 60 minutes) and sends an alert to monitoring. This prevents platform blocks.

How to Avoid Marketplace Blocks?

Use atomic rename: the feed presented to the platform is never broken. If generation is interrupted due to DB timeout or network failure, the previous complete version remains on disk. Additionally, alerts are sent to Telegram when generation time exceeds double the average.

Checklist of Common Feed Setup Mistakes:

• N+1 query on product selection—use eager loading or cursor queries.
• Invalid XML characters in descriptions—escape via htmlspecialchars.
• Missing available tag for YML—product won't appear in results.
• Feed size too large (>100 MB)—split into parts or use gzip.

What's Included in the Work

1. Analysis—review your catalog, marketplace requirements, existing infrastructure.
2. Design—generator architecture, configuration, DB schema, schedule.
3. Implementation—write generators for required formats, integrate with scheduler, set up monitoring.
4. Testing—validate with test feed, verify on platforms, load tests.
5. Deployment and documentation—deploy on your server, admin panel management instructions.

Over 7+ years of Laravel development experience, 50+ successful marketplace integrations. We guarantee stable system operation and prompt post-deployment support. Contact us for a free consultation—we'll analyze your catalog and suggest an optimal schedule. Order system implementation and get a ready integration with configured alerts in 3-4 days.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.