PickPoint Integration: Lockers, API, Tracking

Cart abandonment often stems from inconvenient delivery options. PickPoint's network of 4000+ pickup lockers across 500 Russian cities offers a solution: clients pick up orders anytime, skipping queues. As web developers, we integrate this service into your online store for seamless operation. We guarantee stable integration and aim to reduce delivery costs by 15–20%, leading to substantial annual savings.

How We Integrate PickPoint Step by Step

Integration begins with an audit of your site's current architecture. Whether you have a Laravel monolith or a React app with Next.js, we choose the optimal connection method. We typically use PickPoint REST API (documentation available after registration in the partner cabinet). For simple tasks SOAP suffices, but REST is more flexible and easier to cache.

We recommend REST: JSON parses faster and the request structure is intuitive. We connect to the sandbox environment for testing, then switch to production after debugging.

Why Is Caching the List of Lockers Important?

Each /api/postamatlist request returns the full list – over 4000 points. Calling it on every page load overloads the server and delays map rendering. We cache the list in Redis or MySQL with a daily refresh, reducing TTFB by 30–50%.

// Example caching in Laravel
$postamats = Cache::remember('pickpoint_postamats', 86400, function () {
    return Http::get('https://e-solution.pickpoint.ru/api/postamatlist')->json();
});

PickPoint Integration: Stages and Timelines

1. Audit — analyze current architecture and integration points.
2. API connection — set up PickPoint access, validate data.
3. Caching — implement locker list cache for fast loading.
4. Frontend — display map with lockers, filter by dimensions.
5. Webhooks — configure status updates for shipments.
6. Testing — test in sandbox, fix errors.
7. Deployment — go live, train managers.

Common Integration Mistakes

Errors in cost calculation. If parcel dimensions are passed incorrectly, PickPoint may return an incorrect price or reject the shipment. We validate data before sending and hint at allowed sizes to the user.

Tracking issues. Shipment statuses come via webhooks. If the webhook URL is unreachable, statuses are lost. We set up a retry queue and admin alerts.

Wrong locker selection. A client might select a locker that cannot accommodate the order dimensions. We calculate compatibility on the fly and hide unsuitable points from the list.

How to Let Clients Choose a Locker?

On the frontend, we display a map with lockers pulled from cache. When the client clicks a point, its details load: address, working hours, available cells. We check if the order fits (based on MaxWidth/MaxHeight/MaxDepth from the API). If not, we warn the user and suggest another locker.

// Example filter by dimensions
const suitable = postamats.filter(p => 
  order.width <= p.MaxWidth && 
  order.depth <= p.MaxDepth && 
  order.height <= p.MaxHeight
);

What Is Included in the Work?

• Integration documentation: description of all API methods, request/response examples.
• Module code for your CMS or framework (Laravel, WordPress, 1C-Bitrix, React).
• Testing on PickPoint sandbox environment.
• Manager training: how to manage shipments, print labels.
• Setup of PickPoint label printing.
• Two weeks post-launch support.

In our practice, we have integrated PickPoint into over 20 projects – from clothing stores to food delivery services. No order has been lost due to integration failure. Contact us for a consultation – our engineer will analyze your project and propose a solution.

How Long Does Integration Take?

Basic setup (locker selection on map, shipment creation, tracking) takes 3–4 working days. If integration with an accounting system (1C, CRM) or custom logic is needed, it takes 7–10 days. The cost is calculated individually after analyzing your project. Time savings compared to self-development are up to 40%.

For an accurate estimate, send your technical specification or site URL – we will analyze and propose a solution within a day. Order PickPoint integration today and your clients will forget about delivery issues.

How does shipping service integration affect conversion?

Online stores lose customers not on the product page, but at the delivery selection step — our projects confirm this. Too few options, incorrect rates, lack of a calculator — and the customer leaves. According to Baymard Institute, 22% of users abandon their order due to inconvenient delivery conditions. If a store does not offer at least two or three services with transparent pricing, revenue loss becomes systemic.

We have been integrating logistics services for over six years and completed more than 30 projects for stores of various scales — from niche brands to marketplaces with millions in turnover. Integration is not just about 'displaying a list of pickup points.' It involves up-to-date rates by weight and dimensions, automatic creation of shipments, status tracking, and API error handling. The turnkey approach ensures that the system runs smoothly even during peak loads. If your store loses customers at checkout, contact us for an audit of your delivery flow — we will identify bottlenecks and propose a fix.

What problems does delivery setup solve?

Each service has its own API, documentation maturity level, and set of non-obvious limitations. Let's break down the three most common difficulties.

CDEK API v2 is the most mature among Russian carriers. OAuth 2.0 authorization (token lives 24 hours, refresh logic needed), REST JSON. Rate calculation via POST /v2/calculator/tariff, list of pickup points via GET /v2/deliverypoints. Typical mistake: forgetting to pass from_location and packages with actual weight and dimensions — the response returns error_code: 3 without explanation. Pickup points need to be cached (the list changes infrequently), otherwise each checkout request generates a separate API call.

Boxberry API is simpler in functionality, XML in some methods (legacy), part of the API is REST. Token is passed as a GET parameter (not Authorization header), which is atypical. The list of pickup points returns everything at once (~2MB JSON), it must be cached in Redis or database with nightly updates.

Russian Post API is the most complex among Russian carriers. SOAP + REST hybrid, requires a contract and setup in the personal account. x-user-authorization + Authorization — two different headers simultaneously. Standard shipments, EMS, 1st class — different rate groups. Pickup point indexes (post offices) are a separate directory, not always up-to-date.

DHL Express API is for international shipping. XML-based API (DHL XML Services), though there is a newer MyDHL+ API. Requires a registered account number. Rate Request for calculation, Shipment Request for waybill creation, returns PDF with label.

Why is caching pickup points and rates mandatory?

Caching is not an option but a necessity. CDEK API has a limit of 1000 requests per minute, Boxberry — 300. Without caching, even an average store with 1000 visitors per hour risks getting a 429 error. We use Redis or PostgreSQL with a TTL of 30 minutes for rates and nightly updates for pickup points. This reduces API load by 70–80% and speeds up page display. Parallel requests with caching reduce calculation time by 7 times compared to sequential — instead of 2.8 seconds, the customer gets rates in 380 ms. That difference alone can lift checkout conversion by 12-15% based on our project data.

What deliverables can you expect?

Each integration project includes:

• Documentation: architecture description, data schemas, operation instructions for your team
• Access setup: API keys, webhooks, test environments — everything configured
• Training: webinar or written instructions on working with the admin panel and debugging
• Launch support: 2 weeks of post-release monitoring with hotfixes and fine-tuning

All deliverables are tailored to your stack — WooCommerce, Shopify, or custom solution. Schedule a free consultation to get a detailed scope for your store.

How we build integration

Abstraction over providers

No store uses one delivery service forever. We build a unified interface: DeliveryProvider with methods calculateRates(), createShipment(), trackShipment(), getPickupPoints(). Each service is a separate implementation. Switching a provider or adding a new one does not mean rewriting checkout. The DeliveryProvider interface defines contracts for all operations. Each carrier has its own class, e.g., CdekProvider implements DeliveryProvider. The constructor receives configs (keys, URLs, cache settings). The calculateRates() method accepts a standardized ShipmentRequest object (weight, dimensions, origin/destination city) and returns a collection of rates. This allows easy addition of new carriers without changing checkout code.

Caching pickup points

Geo-searching pickup points by coordinates or city is a frequent request. Pulling from the API every time is impossible (limits, latency). Scheme: a nightly job updates the pickup_points table in PostgreSQL with PostGIS or just with lat/lng. Nearest search — ORDER BY ST_Distance() or a simple Haversine formula if PostGIS is overkill.

Frontend widget

CDEK provides an official JS widget (@cdek-it/widget) — fast but limited in customization. For non-standard designs, a custom widget: map (Yandex.Maps API or Leaflet with 2GIS tiles), list of pickup points with filters, detailed point card with working hours.

Status tracking

Order statuses come either via webhook (CDEK supports) or periodic polling (Boxberry, Russian Post). For polling, a job queue (Laravel Queue, Bull for Node.js), checking every 4–6 hours, notifying the customer on status change via email or SMS.

Case: multi-carrier for WooCommerce

A sports nutrition store: CDEK + Boxberry + pickup from 3 physical stores. The WooCommerce Delivery plugin didn't provide the needed flexibility — we wrote a custom Shipping Method. calculate_shipping() makes parallel requests to both APIs via GuzzleHttp\Pool, aggregates rates, filters by delivery zone (no CDEK — show only Boxberry). Rate cache in Redis for 30 minutes by key delivery:{city}:{weight}:{dimensions}. Calculation time: was 2.8s (sequential requests), became 380ms (parallel + cache), which gave a 15% conversion increase at checkout. Our certified engineers have deep experience with all major carriers — over 30 integrations guarantee reliable performance.

Process and timelines

Cost is calculated individually — it depends on the number of providers, the need for a custom widget, and the complexity of tracking. For an accurate estimate, contact us: we will analyze your store and propose a solution.

Typical mistakes when setting up independently

• Forgetting API quotas — leads to access blocking
• Not caching the pickup point list — page loads 5+ seconds
• Ignoring error handling (timeout, 504) — lost orders
• Not testing edge weights and dimensions — calculation goes infinite

Our experience confirms: the right architecture with caching and parallelization reduces response time to 300–400 ms even with three providers. Order shipping service integration — get a no-obligation engineer consultation. Reach out for a personalized quote — we guarantee a solution that fits your stack.