Custom PostNL API integration development
Appfront builds custom integrations with the PostNL API, so your webshop or business software can create shipping labels automatically, track shipments in real time and handle returns. From the first barcode to proof of delivery, your shipping process runs without manual work via the official PostNL Shipping API.
What is a PostNL API integration?
PostNL is the national postal service of the Netherlands and the largest parcel carrier in the Benelux. Through the PostNL Developer Portal, the company makes a range of REST APIs available that let external systems control the entire shipping process programmatically — from label creation to delivery.
A PostNL API integration connects your webshop, order management system or fulfilment software directly to those APIs. Orders are automatically turned into shipping labels with the correct barcode, customers receive real-time tracking updates, addresses are validated before shipping, and return labels are included or generated on request. Creating shipments manually via MijnPostNL disappears from your workflow.
Appfront builds these integrations to order. We tailor the integration to your specific shipping logic — shipping methods, weight classes, international destinations, pick-up points — and make sure it runs reliably, with proper error handling and monitoring.
Automatic shipping labels
A shipping label with barcode is created via the Shipment API for every new order. The label is ready to print as soon as the order comes in — no more manual entry.
Real-time track & trace
Every status change — from the sorting centre to delivery at the customer's door — is retrieved via the Track & Trace API and passed on to your system or directly to the recipient.
Address validation before shipping
Before a shipment leaves the building, the Addresses API checks whether the delivery address is valid and complete. This prevents returns caused by incorrect postcodes or house numbers.
Our development process for PostNL integrations
We work in a structured way from analysis to go-live, so your shipping integration runs stably from day one. Every step is aimed at an integration your team understands and that grows with your shipping volume.
We map out your shipping process: which product types, weight classes, destinations and shipping methods (standard, evening, pick-up point) do you offer? Which systems need to be integrated?
We design the integration layer, select the PostNL APIs you need and build a working prototype in the PostNL sandbox environment. You see how labels and tracking work early on.
Implementation with automated tests, retry logic for API errors and monitoring. We test with real shipping scenarios in the sandbox and validate every label and every status update.
A controlled transition to the PostNL production environment. We monitor the first shipping volume, catch edge cases and provide ongoing maintenance for API updates or new shipping methods.
What a PostNL API integration delivers in practice
Every integration is set up specifically for your shipping process. Below are the features we build most often for organisations that want to automate PostNL.
Generating shipping labels
The Shipment API v4 creates a complete shipping label for each order, with barcode, delivery address and shipping method. Labels are delivered as PDF or ZPL, ready for your label printer. Bulk shipping of dozens of labels at once is supported.
Track & trace integration
Real-time status updates via the Track & Trace API are processed automatically in your system. Customers receive proactive notifications at every step, from collection at the sorting centre to delivery at the door or at a PostNL point.
Address validation
The Addresses API checks postcodes and house numbers for validity up front. Incomplete or incorrect addresses are caught before a label is created, which saves on returns, costs and customer queries.
Pick-up points in checkout
Via the Location Services API, you show all PostNL points near the customer directly in your checkout. The customer chooses a pick-up point, and that location is automatically applied to the shipping label, including opening hours and directions.
Returns handling
The Return API generates return labels that you include with the original shipment or that the customer requests afterwards. The returns process is linked to your order management so that returns are registered automatically and stock is updated.
Rate calculation
Based on weight, dimensions and destination, shipping costs are calculated automatically and shown in the checkout or factored into your margin calculation. For contractual PostNL rates, we implement your specific rate structure.
Typical use cases in practice
A PostNL API integration works out very differently for each type of organisation. Below are the four scenarios we encounter most often, and for which we have developed proven integration patterns.
Webshops
A web shop that processes dozens to hundreds of orders a day cannot run on manual label creation. We connect your Shopify, WooCommerce, Magento or Lightspeed environment to PostNL so that a shipping label is created automatically for every paid order, the customer receives a tracking link and stock is updated. We show delivery options and pick-up points directly in the checkout. More about our approach: e-commerce development.
Fulfilment companies
Fulfilment partners that ship on behalf of multiple clients need a central shipping layer that applies the right PostNL configuration (sender, rates, return address) for each client. We build a multi-tenant integration that receives orders from different source systems and generates the right label for each client. See also our middleware solutions.
Marketplaces & platforms
Marketplaces and platform providers that want to offer sellers an integrated shipping experience connect PostNL at platform level. Sellers do not need to configure a PostNL account themselves: the platform handles label creation, tracking and return labels centrally via the API. We build this layer as part of your platform architecture.
B2B distribution
Wholesalers and distributors that ship multiple pallets or parcels via PostNL every day benefit from an integration that generates bulk labels, groups parcels by route and automatically applies the right service code (standard, extra large, letterbox parcel). Tracking for each shipment is fed back to your ERP or WMS.
Technology we use
We build PostNL integrations with modern, maintainable technology stacks. The exact choice depends on your existing infrastructure and the expected shipping volume, so that your team can manage or extend the integration itself after delivery.
Why choose Appfront for your PostNL integration?
Appfront has extensive experience building shipping integrations for Dutch webshops and e-commerce organisations. We know the PostNL APIs, we know where the edge cases are (international shipments, letterbox parcels, signature on delivery) and we build integrations that stay stable even at peak volumes.
Every integration is delivered with clear documentation, structured logging and monitoring. Your team, or a future supplier, can understand, maintain and extend the integration without depending on Appfront.
Do you need other carriers besides PostNL? We regularly build multi-carrier solutions in which PostNL, DHL, DPD and other carriers are managed from the same shipping layer. Also compare our integrations with MyParcel and Sendcloud.
Also take a look at our broader services around API integrations and e-commerce development.
- Experience with the full PostNL API suite (Shipment, Track & Trace, Addresses, Delivery Options, Returns)
- Multi-carrier architecture if PostNL is not your only carrier
- Tested at peak volumes: Black Friday, holidays, flash sales
- Retry logic and dead-letter queues for failed API calls
- Extensive logging and alerting from day one
- Clear documentation that your team can read and maintain
- A single point of contact, no passing you between account managers
- Ongoing maintenance for PostNL API updates and version migrations
Security and privacy in PostNL integrations
Shipping data contains personal data: names, addresses, phone numbers and sometimes recipients' email addresses. Appfront treats every PostNL integration with that in mind. We only store the data needed for the shipping process, encrypt sensitive information in transit and at rest, and document the data flows for your record of processing activities.
The PostNL API key is stored encrypted and is never included in source code, log files or error messages. Access to shipping data is role-based, so that only authorised employees and systems can access personal data.
More about our approach: information security policy and coordinated vulnerability disclosure policy.
- GDPR-compliant processing of recipient data
- Encryption in transit (TLS 1.2+) and at rest
- API key management via environment variables or a secrets manager
- Role-based access to shipping and personal data
- No unnecessary storage of delivery addresses after processing
- Audit logs with traceable data flows
- Monitoring and alerting for unusual patterns
- Documentation for your record of processing activities
Frequently asked questions about PostNL API integrations
Answers to the questions we get asked most often about custom integrations with the PostNL API.
A PostNL API integration is a technical integration that lets your webshop or business software communicate directly with PostNL's systems. Through PostNL's official REST APIs, shipping labels are generated automatically, shipments are tracked, addresses are validated and return labels are created, without having to log in to MijnPostNL manually.
PostNL offers several APIs that can be used separately or combined: the Shipment API (v4) for creating shipments and labels, the Track & Trace API for real-time status updates, the Addresses API for address validation, the Delivery Options API for delivery options at checkout, the Barcode Service for unique shipping barcodes, and the Location Services API for pickup points. Which combination you need depends on your shipping process.
A standard integration that generates labels and offers tracking can go live within two to four weeks. More complex integrations, with address validation, delivery options at checkout, returns handling and multi-carrier logic, typically take four to eight weeks. After a short intake, we can give you a realistic timeline.
Yes. We regularly build integrations as part of a multi-carrier architecture, where PostNL is managed alongside other carriers (DHL, DPD, UPS, GLS) from the same shipping layer. Through a middleware layer, your system automatically selects the right carrier based on destination, weight, speed or rate.
Yes. Via the PostNL Delivery Options API, your checkout retrieves the available delivery options in real time: standard delivery, evening delivery, Saturday, pickup at a PostNL point or delivery to the neighbours. The customer chooses during checkout, and that choice is automatically applied to the shipping label.
The cost depends on the number of APIs being integrated, the complexity of your shipping logic (multiple shipping methods, international shipments, returns handling), and whether the integration is part of a broader multi-carrier system. Monitoring, error handling and ongoing maintenance are also factors. We always provide a clear quote after a no-obligation consultation.
PostNL uses an API key that you create via the MijnPostNL portal. This key is sent as a header with every API request. We store the key encrypted and use environment variables or a secrets manager so the key never ends up in source code or log files.
Yes. After going live, we monitor the integration for errors, timeouts and deviations in PostNL's API responses. When PostNL releases API version updates (such as the move from v2 to v4), we adapt the integration in good time. We also offer ongoing support for extensions, new shipping methods or changes to your order process.
Ready to automate your PostNL shipping process?
Tell us which systems you want to connect to PostNL and what your shipping process looks like now. We'll help think through the architecture and deliver an integration that grows with your volume. A no-obligation consultation gives you a clear picture of the possibilities within half an hour.
Current context (May 2026)
REST architecture has become the de facto standard for web APIs, based on stateless HTTP requests and resource-oriented URLs — a pattern that Roy Fielding defined in his dissertation in 2000.
Source: MDN Web Docs — REST (developer.mozilla.org)