Pakistani e-commerce sellers running on ERPNext live and die by cash-on-delivery, and PostEx is one of the dominant COD couriers with its instant-advance payout model. But ERPNext core has no concept of a PostEx booking: staff copy order addresses into the PostEx merchant portal by hand, paste tracking numbers back into a text field, and then spend the end of every week trying to match a lump-sum PostEx advance-payment settlement against dozens of individual Sales Invoices. Delivery Note and the stock ledger know nothing about the parcel's real courier status, and finance has no clean audit trail from Sales Order to delivered-and-paid.

We build a proper Frappe app (postex_connector) installed on your own bench, not a spreadsheet workaround. It ships a PostEx Settings single DocType (API token stored encrypted as a Password field, base URL, default pickup address, city-map cache) and a PostEx Shipment DocType linked to Sales Order/Delivery Note/Sales Invoice, carrying tracking number, order status, COD amount, and the payout reference. Booking is a whitelisted server method (@frappe.whitelist()) that validates city serviceability against PostEx's operational-cities endpoint before it calls the create-order API, so an unserviceable pincode is caught before the parcel is committed. A hooks.py doc event on Delivery Note submit can auto-create the shipment, and a client script adds a one-click "Book with PostEx" button plus a live status badge on the linked forms.

Tracking and reconciliation run on Frappe's scheduler. A scheduler_events hook polls PostEx for the tracked parcels, writes status transitions (booked, picked, in-transit, delivered, returned) back onto PostEx Shipment, and appends a timeline comment so support can see the full history without leaving ERPNext. When PostEx issues its advance/COD payout, a reconciliation routine matches each settled tracking number to its Sales Invoice and drafts the corresponding Payment Entry — turning the weekly settlement headache into a reviewable, one-approval batch. Bulk label generation calls the PostEx label endpoint for a filtered list of shipments and returns a merged, print-ready PDF so a packing desk can dispatch a whole batch at once.

Access is governed by a dedicated Role and Role Profile, so warehouse staff can book and print while only finance can post the reconciliation Payment Entries; every external call is logged for audit. The app is built against Frappe/ERPNext v15 and v16 and delivered as installable source in a git repository you own.

Because this is build-to-order, nothing is a shrink-wrapped download. We start with a short scoping call to confirm your PostEx merchant account setup, COD workflow, and which documents trigger booking, then hand you a fixed scope and quotation. Typical delivery is one working week from confirmed scope. We build on a staging copy of your bench, run UAT with your team against real test orders, then install to production with a rollback plan, training, and a post-go-live support window.