Custom Order Tracking Development for E-commerce Stores

A customer lands on the order page and sees only 'Processing' — day after day. The result: a flood of support calls asking about order status. With 5+ years on the market and over 50 successful tracking projects, our team of 10 engineers solves this: we implement an order tracking system that automatically updates statuses, sends notifications, and provides a transparent delivery picture. Our experience shows tracking reduces support load by 60% compared to manual updates — a 3x improvement in inquiry reduction. One client cut inquiries from 200 to 80 per day after implementation, saving $10,000 annually in support costs. Other clients save $8,000–$15,000 per year. Another boosted NPS by 20 points. Many stores limit themselves to simple statuses, manually updating them in the admin panel. This leads to delays and errors. Our solution fully automates this process, integrating with your system and carrier APIs. Backed by 5+ years of experience and 50+ projects, we deliver robust solutions.

Order state machine mechanics

Our order tracking system leverages an order state machine, carrier API integration, and a public tracking page to ensure transparent package tracking. The order passes through several strict states: from awaiting payment to completion. Each transition is controlled by an order state machine based on Spatie Model States for Laravel. This ensures no invalid transition occurs. The order state machine approach is 3x more reliable than manual status updates.

class Order extends Model
{
    use HasStates;

    protected function registerStates(): void
    {
        $this->addState('status', OrderStatus::class)
            ->allowTransition(Pending::class, Confirmed::class)
            ->allowTransition(Confirmed::class, [Processing::class, Cancelled::class])
            ->allowTransition(Processing::class, [Shipped::class, Cancelled::class])
            ->allowTransition(Shipped::class, [Delivered::class, Failed::class])
            ->allowTransition(Delivered::class, Completed::class);
    }
}

At each transition, the system records an entry in order_status_history, updates the timestamp, and sends a notification to the buyer. Below are typical statuses and their descriptions:

Status history: the backbone of tracking

All changes are stored in a table:

CREATE TABLE order_status_history (
    id BIGSERIAL PRIMARY KEY,
    order_id BIGINT REFERENCES orders(id) ON DELETE CASCADE,
    status VARCHAR(30) NOT NULL,
    comment TEXT,
    changed_by BIGINT REFERENCES users(id),
    created_at TIMESTAMP DEFAULT NOW()
);

From this table, a timeline is built on the public page — the buyer sees when and which status was assigned. Without history, delays or errors cannot be traced. Over 10,000 orders have been tracked with this system, achieving 99.9% status accuracy and uptime.

Carrier tracking integration benefits

After shipment, the order gets a tracking number. The system queries the carrier via API every 2 hours. Automated carrier tracking is 5x faster than manual checks. Example for CDEK:

$cdek = new \CdekSDK2\Client($clientId, $clientSecret);
$info = $cdek->orders()->get($order->cdek_uuid);
$cdekStatus = $info->getStatuses()[0]->getName();

Our solution integrates with 6+ carriers: CDEK, Russian Post, Boxberry, DPD, Dostavista, Yandex Go. We use custom adapters for each carrier, handling authentication, rate limits, and error logging. For last-mile delivery, we integrate real-time courier location on a map. Comparison of approaches:

When the carrier status changes, the system automatically updates the order status and sends a notification. This is more convenient than manual checking — it saves your managers' time, reducing manual effort by 80%.

How does public tracking page work?

The page is accessible without login via a token link — for guest orders and from emails. Example React component:

const OrderTrackingPage = ({ order }: { order: OrderTrackingData }) => (
  <div className="max-w-2xl mx-auto py-8 space-y-6">
    <OrderSummaryCard order={order} />
    <div>
      <h2 className="font-semibold mb-3">Status History</h2>
      <StatusTimeline steps={order.status_history} currentStatus={order.status} />
    </div>
    {order.tracking_number && (
      <div>
        <h2 className="font-semibold mb-3">Delivery</h2>
        <ShippingTracker carrier={order.carrier} trackingNumber={order.tracking_number} events={order.carrier_events} />
        <a href={order.carrier_tracking_url} target="_blank" className="text-blue-600 text-sm mt-2 inline-block">
          Track on {order.carrier} site →
        </a>
      </div>
    )}
  </div>
);

Visually, the timeline is a progress bar with steps: 'Accepted', 'Confirmed', 'Processing', 'Shipped', 'Delivered'. The current status is highlighted. The page loads in under 2 seconds.

Notifications: email and SMS

On each status change, the buyer receives an email with current state and a link to tracking. For key events (shipment, delivery) we additionally send SMS. We use Laravel Notification channels — easily extensible. Templates are customizable to your brand. Over 95% of buyers find the notifications helpful.

What's included in the work

• Development of the order state machine with transition history
• Integration with 2–3 carriers (list agreed upon)
• Public tracking page with responsive design and token access
• Notification system (email + SMS/messengers optional)
• API documentation and status schema
• Training your team on the system
• 6-month code warranty, post-launch support

Our process

1. Analysis — we study your current order logic, carrier list, and notification requirements.
2. Design — we describe the order state machine, database schema, and integrations.
3. Implementation — we write code on Laravel (backend) + React (frontend).
4. Testing — we check all status transitions, notification delivery, and real tracking numbers.
5. Deployment — we deploy on your server, configure cron tasks.

Timelines and pricing

Base implementation takes 4–6 working days. Typical investment ranges from $2,000 to $5,000, depending on complexity. Contact us — we'll estimate your project in 1 day. Our team has experience in e-commerce development and over 50 successful tracking implementations.

Results you will get

Beyond reducing support load by 60%, you gain increased loyalty: buyers see real-time status and ask fewer questions. Additionally, we help set up CRM and analytics integration. Get a free consultation right now — we'll tell you how to improve your service.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.