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.
| API | Protocol | Format | When to Use |
|---|---|---|---|
| SOAP | XML | Heavy | Legacy systems, 1C |
| REST | JSON | Light | Modern web apps, mobile clients |
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(); }); Common Integration Mistakes and Their Solutions
- Incorrect authorization header: Ensure every request includes the header
Authorization: Bearer {token}. Otherwise the API returns 401. - Ignoring rate limits: PickPoint limits requests per minute. Set up a queue with delays.
- Missing error handling: Always check
response.statusand display a clear message to the user.
PickPoint Integration: Stages and Timelines
| Stage | Duration |
|---|---|
| Architecture audit | 1 day |
| API connection | 1–2 days |
| Locker selection & tracking implementation | 2–3 days |
| Sandbox testing | 1 day |
| Deployment and support | 2 weeks |
- Audit — analyze current architecture and integration points.
- API connection — set up PickPoint access, validate data.
- Caching — implement locker list cache for fast loading.
- Frontend — display map with lockers, filter by dimensions.
- Webhooks — configure status updates for shipments.
- Testing — test in sandbox, fix errors.
- 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.