Most ERPNext D2C brands lose the post-purchase moment. Once a Delivery Note is submitted, the customer's experience jumps straight to the carrier's generic tracking page (with a competitor's logo and ads), while your support inbox fills with "where is my order?" tickets. ERPNext core tracks the fulfillment internally, but it has no customer-facing tracking experience, no unified view across DHL, FedEx, Aramex, Bluedart, Shippo or a local 3PL, and no branded proactive notification layer. The native portal shows documents, not a delivery journey — so brands bolt on Aftership-style SaaS that re-charges per shipment and keeps your customer data on someone else's platform.

We build a proper Frappe app (its own module, installed via bench get-app / bench install-app) that lives inside your ERPNext site and owns the tracking experience end to end. A new Shipment Tracking DocType links to the Delivery Note / Shipment and stores the carrier, tracking number, current status, checkpoints (as a child table), and computed ETA. A hooks.py doc_events handler fires on Delivery Note on_submit to create the tracking record and enroll the shipment, and a scheduler_events job (every 15-30 min) polls each carrier's API, normalizes their status codes into a single canonical state machine (Label Created → In Transit → Out for Delivery → Delivered / Exception), and appends checkpoints. Customers land on a branded, mobile-first, localized tracking page rendered as a Frappe web page / portal route — your logo, colors, fonts, and language, keyed by a signed tracking token (no login required), served over your own domain.

On top of that we wire the notification layer: server-side triggers send email (Frappe Email Queue), SMS, and WhatsApp (via your provider — Twilio, Meta Cloud API, or a local gateway) on each meaningful status transition, using editable Frappe templates so marketing controls the copy in every language. The page displays the estimated delivery date, an interactive checkpoint timeline, and a "Start a return" action that creates a Return / Material Request-backed RMA in ERPNext with your rules (return window, eligible items, reason codes) — no email tennis. Everything is exposed through whitelisted methods and the Frappe REST API so your storefront, mobile app, or Shopify/WooCommerce front end can embed live status. Access is governed by Frappe permissions and a dedicated role profile so support agents see everything and customers see only their signed token.

Because this is build-to-order, nothing ships as a one-click marketplace download. We start with a short scoping call to lock your carriers, notification channels, return rules, languages, and branding, then build against your actual ERPNext v15 or v16 site. Typical delivery is one working week from confirmed scope. You get the installable source for your version, UAT on a staging bench with a rollback plan, install and configuration on your site, documentation, a training session, and a post-go-live support window — plus the git repository handed over so it is genuinely yours.