Pakistani e-commerce sellers running ERPNext hit the same wall the moment an order is ready to ship: ERPNext's core Shipment and Delivery Note DocTypes have no idea TCS exists. Staff copy the consignee name, address, phone, COD amount, and weight into the TCS portal by hand, paste the CN number back into ERPNext (or a spreadsheet), and then manually reconcile which parcels were delivered and which COD cash actually returned. At 50+ orders a day this is slow, error-prone, and it silently breaks COD reconciliation — the exact place where a courier integration should be earning its keep.

ECOSIRE builds a proper Frappe app that wires TCS directly into your order-to-ship flow. It ships as a standard app (a tcs_connector app with its own module) so it installs cleanly via bench get-app / bench install-app and upgrades like any other Frappe app. A TCS Settings single DocType holds your TCS COD API credentials (username, password, cost-center / account number) and toggles sandbox vs. production; secrets use the Password fieldtype and are never rendered in plain text. Role profiles and DocType permissions are set so only your shipping team can book or void consignments.

Booking is driven from the Delivery Note (or a linked Shipment). A whitelisted server method (@frappe.whitelist()) authenticates against the TCS COD API, posts the consignment with the correct service type and COD amount, and writes the returned CN / tracking number back onto the document — alongside a child TCS Consignment DocType record that captures the full request and response for audit. A hooks.py doc event on Delivery Note submit can auto-book (or stay manual, your call), and a client script adds a "Book with TCS" button plus a one-click label print via a Print Format sized for TCS airway bills. City serviceability is validated against a cached TCS City list before booking so bad destinations fail fast instead of at the counter.

Tracking stays current without anyone refreshing a portal. A scheduler event (scheduler_events in hooks.py, typically hourly) walks open consignments, calls the TCS tracking endpoint, and updates a status field plus a timeline entry on the source document — so "in transit", "delivered", or "returned" is visible right on the order. Everything is reachable through the standard Frappe REST API and whitelisted methods, so your storefront or a custom dashboard can trigger bookings or read status the same way the desk UI does.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm exactly which TCS services, COD flows, and edge cases (multi-parcel, partial COD, returns) you need, then build and test on a staging bench before touching production. Typical delivery is one working week from confirmed scope. You receive the installable source for your version, install and configuration on your instance, technical and user documentation, a training session, and a post-go-live support window — plus the git repository so you fully own what we built.