Benelux merchants running ERPNext hit a wall the moment they need to fulfil through PostNL. ERPNext ships a generic Shipment DocType and a Delivery Note, but it has no concept of a PostNL barcode, a Kies Gemak parcel-point, an evening delivery window, or an EU customs (CN23) declaration. Warehouse teams end up copy-pasting order data into MijnPostNL or a spreadsheet, printing labels in a separate portal, and re-typing tracking codes by hand — slow, error-prone, and it leaves your ERPNext instance blind to the actual shipment status the customer sees.

The PostNL Shipping Connector closes that gap. It is a proper Frappe app (postnl_shipping) with its own module, DocTypes, and role profile, installed onto your bench alongside ERPNext. A PostNL Settings single DocType holds your API key, customer code, customer number, and collection location, with a sandbox/production toggle so we validate against PostNL's test environment before go-live. From a submitted Delivery Note or Shipment, a whitelisted server method calls the PostNL Send & Track (Shipping) API to generate the barcode, book the chosen product code (standard parcel, evening delivery, signature-on-delivery, insured, or return), and retrieve the A6 label PDF, which is attached straight to the document as a Frappe File and printed to your Zebra/label station.

Under the hood the app is built the Frappe way. A hooks.py doc_events handler on Delivery Note on_submit triggers label creation (guarded by an idempotency flag so re-submits never double-book), a PostNL Shipment child/linked DocType stores the barcode, product code, insured value and label reference, and a scheduler event polls the PostNL track & trace endpoint on a cron interval to update a delivery status field and write timeline comments — no manual status hunting. For non-EU destinations the connector assembles the customs declaration from your Item weights, HS/commodity codes and country of origin, so DHL/PostNL global-pack shipments clear without a separate form. Address validation, parcel-point lookup and evening-delivery availability are exposed to the fulfilment desk through client scripts and a whitelisted lookup method, and every PostNL role — who can book, who can only view tracking — is scoped through a dedicated role profile and DocType permissions.

Because this is a build-to-order engagement, nothing is a shrink-wrapped download. We start from a short scoping call to confirm your ERPNext version (v15 or v16), your PostNL contract product codes, your label hardware and your EU/non-EU split, then build the connector against your exact bench. You get the full app source, installation and configuration on your environment, UAT on a staging site with a rollback plan, a training session for your fulfilment team, and a post-go-live support window. Typical delivery is 2–4 weeks from confirmed scope.