Custom PostNL API integration development
Appfront builds custom PostNL API integrations that let your webshop or business software create shipping labels automatically, track consignments 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 provides a range of REST APIs 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 converted into shipping labels with the correct barcode, customers receive real-time tracking updates, addresses are validated before dispatch, and return labels are included or generated on request. Creating consignments manually via MijnPostNL disappears from your workflow.
Appfront builds these integrations to measure. We align the integration with your specific shipping logic (shipping methods, weight bands, international destinations, pick-up points) and make sure it runs reliably, with proper error handling and monitoring.
Automatic shipping labels
With every new order, a shipping label with barcode is created immediately via the Shipment API. The label is ready to print as soon as the order arrives, with no manual entry required.
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 forwarded to your system or directly to the recipient.
Address validation before shipping
Before a consignment leaves, the Addresses API checks that 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 focused on an integration your team understands and that grows with your shipping volume.
We map out your shipping process: which product types, weight bands, destinations and shipping methods (standard, evening, pick-up point) do you offer? Which systems need to be connected?
We design the integration layer, select the required PostNL APIs and build a working prototype in the PostNL sandbox environment. You see early on how labels and tracking work.
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 notification.
Controlled transition to the PostNL production environment. We monitor the first shipping volumes, catch edge cases and provide ongoing management 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 most often build for organisations that want to automate PostNL.
Generating shipping labels
The Shipment API v4 creates a complete shipping label for each order, including 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 in advance. Incomplete or incorrect addresses are intercepted before a label is created, saving on returns, costs and customer queries.
Pickup points in checkout
Via the Location Services API, you display all PostNL points near the customer, directly in your checkout. The customer chooses a pickup point, and that location is automatically included on the shipping label, including opening hours and directions.
Returns handling
The Return API generates return labels that you include with the original consignment 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 included in your margin calculation. For contractual PostNL rates, your specific tariff structure is implemented.
Typical use cases in practice
A PostNL API integration works very differently depending on the type of organisation. Below are the four scenarios we encounter most often, and for which we have developed proven integration patterns.
Online shops
A webshop processing 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. Delivery options and pick-up points are shown directly at 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 correct 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 correct label per 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 set up 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 send multiple pallets or parcels via PostNL every day benefit from an integration that generates bulk labels, groups parcels by route and automatically applies the correct service code (standard, extra large, letterbox parcel). Tracking per consignment 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 expected shipping volume, so that your team can manage or further develop the integration after handover.
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 lie (international consignments, letterbox parcels, signature on delivery), and we build integrations that remain stable 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 carriers other than PostNL as well? We regularly build multi-carrier solutions in which PostNL, DHL, DPD and other carriers are driven from the same shipping layer. You can also compare our integrations with MyParcel and Sendcloud.
See also 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, public holidays, flash sales
- Retry logic and dead-letter queues for failed API calls
- Comprehensive logging and alerting from day one
- Clear documentation your team can read and manage
- A fixed point of contact, no account managers passed around
- Ongoing management for PostNL API updates and version migrations
Security and privacy for PostNL integrations
Shipping data contains personal information: names, addresses, phone numbers and sometimes email addresses of recipients. Appfront treats every PostNL integration with that in mind. We store only the data required for the shipping process, encrypt sensitive information both 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 only authorised staff and systems can access personal data.
More about our approach: information security policy and 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 link that allows your webshop or business software to communicate directly with PostNL's systems. Through PostNL's official REST APIs, shipping labels are generated automatically, consignments are tracked, addresses are validated and return labels are created, without anyone having to log in to MijnPostNL manually.
PostNL offers several APIs that can be used individually or in combination: 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. The combination you need depends on your shipping process.
A standard integration that generates labels and provides tracking can be live within two to four weeks. More complex integrations, with address validation, delivery options in the checkout, return handling and multi-carrier logic, usually 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, in which PostNL is driven 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. Using the PostNL Delivery Options API, your checkout retrieves the available delivery options in real time: standard delivery, evening delivery, Saturday delivery, collection at a PostNL point or delivery to a neighbour. 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 delivery methods, international shipments, return 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 following a no-obligation consultation.
PostNL works with an API key that you create via the MijnPostNL portal. This key is sent as a header with each 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 go-live, we monitor the integration for errors, time-outs and deviations in PostNL's API responses. When PostNL's API is updated to a new version (such as the move from v2 to v4), we adapt the integration in good time. We also offer ongoing maintenance for extensions, new delivery 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 today. We will think along with you about the architecture and deliver an integration that grows with your volume. A no-obligation consultation will give you a clear picture of the possibilities within half an hour.
Current context (May 2026)
REST architecture has now become the de facto standard for web APIs, based on stateless HTTP requests and resource-oriented URLs, a pattern Roy Fielding defined in his dissertation in 2000.
Source: MDN Web Docs — REST (developer.mozilla.org)