Customers often abandon their cart if the site doesn't offer a convenient delivery method. PickPoint — a network of 4,000+ parcel lockers in 500 cities across Russia — solves this problem: the customer picks up their order at any time without queues.
As web developers, we integrate this service into your online store so that everything works without failures. We guarantee a stable integration and a 15–20% reduction in delivery costs.
How we integrate PickPoint: step by step
Integration begins with an audit of your site's current architecture. If you have a Laravel monolith or a React application with Next.js — we will select the optimal connection method.
We usually use the PickPoint REST API (documentation is available after registering in the partner dashboard). For simple tasks, SOAP is sufficient, 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 applications, mobile clients |
We recommend REST: JSON parses faster, and the request structure is intuitive. We connect to the sandbox environment for testing, and after debugging — to production.
Why is it important to cache the list of parcel lockers?
Each request to /api/postamatlist returns the full list — more than 4000 locations. If it is called on every page load, the server will receive excessive load, and the user — a long map loading time. We cache the list in Redis or MySQL with a refresh once a day. This reduces TTFB by 30–50%.
// Example of caching in Laravel
$postamats = Cache::remember('pickpoint_postamats', 86400, function () {
return Http::get('https://e-solution.pickpoint.ru/api/postamatlist')->json();
});
Typical integration errors and their solutions
- Incorrect authorization header: Make sure the requests include the header Authorization: Bearer {token}. Otherwise the API returns 401.
- Ignoring request limits: PickPoint limits the number of requests per minute. Set up a request queue with a delay.
- Lack of error handling: Always check response.status and display a clear message to the user.
PickPoint integration: stages and timelines
| Stage | Duration |
|---|---|
| Architecture audit | 1 day |
| API connection | 1–2 days |
| Implementation of parcel locker selection and tracking | 2–3 days |
| Testing on sandbox | 1 day |
| Deployment and support | 2 weeks |
- Audit — we analyze the current architecture and integration points.
- API connection — we configure access to PickPoint and validate the data.
- Caching — we implement caching of the parcel locker list for fast loading.
- Frontend — we display the map with parcel lockers and filter by dimensions.
- Webhooks — we configure the receipt of shipment statuses.
- Testing — we check in the sandbox environment and fix errors.
- Deployment — we move to production and train managers.
Common mistakes when integrating PickPoint
Errors in cost calculation. If the parcel dimensions are passed incorrectly, PickPoint may return an incorrect price or refuse to accept the shipment. We validate the data before sending and suggest acceptable dimensions to the user.
Tracking issues. Shipment statuses arrive via webhooks. If the webhook URL is unavailable, statuses are lost. We set up a retry queue and alerts for the administrator.
Incorrect locker selection. The customer may select a locker that is not suitable for the order dimensions. We calculate compatibility on the fly and hide unsuitable points from the list.
How to choose a parcel locker for the client?
On the frontend side, we display a map with parcel lockers retrieved from the cache. The client clicks on a point — its parameters are loaded: address, opening hours, available cells. We check whether the order fits (by MaxWidth/MaxHeight/MaxDepth from the API). If it does not, we warn the user and suggest another parcel locker.
// Example of filtering 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 and response examples.
- Module code for your CMS or framework (Laravel, WordPress, 1C-Bitrix, React).
- Testing in the PickPoint sandbox environment.
- Training for your managers: how to manage shipments, print labels.
- Setting up PickPoint label printing.
- Support for 2 weeks after launch.
Over the course of our practice, we have integrated PickPoint into 20+ projects — from clothing online stores to food delivery services. Not a single order was lost due to an integration failure. Contact us for a consultation — an engineer will analyze your project and propose a solution.
How long does the integration take?
Basic setup (selecting a parcel locker on the map, creating a shipment, tracking) — 3–4 business days. If integration with an accounting system (1C, CRM) or custom logic is required — from 7 to 10 days. The cost is calculated individually after analyzing your project. Time savings compared to in-house development — up to 40%.
For an accurate estimate, send us the technical specification or a link to your website — we will analyze it and propose a solution within a day. Order PickPoint integration today — and your customers will forget about delivery issues.
