Every GST-registered business in India that moves goods above the state threshold must carry a valid e-way bill, yet ERPNext core out of the box stops at generating the JSON payload you upload manually into the NIC portal or an external GSP. For a busy dispatch dock that is a bottleneck: no in-record EWB number, no Part-B vehicle update when the truck actually changes, no consolidated e-way bill for a multi-invoice trip, no way to cancel within the 24-hour window without leaving ERPNext, and validity that no one is tracking until a consignment is stopped at a checkpoint. Teams end up running a parallel spreadsheet and a second login, and the two systems drift.

ECOSIRE builds eway_bill_manager, a proper Frappe app installed on your bench, that closes that gap by talking to the NIC e-way bill API (directly or through your chosen GSP/e-invoice provider) from inside ERPNext. We add an E-Way Bill DocType that links to Sales Invoice, Delivery Note and, where relevant, Purchase Invoice, plus a Transporter master and a Vehicle child table. hooks.py doc events fire on submit to build and validate the EWB request, and whitelisted server methods (eway_bill_manager.api.generate, .update_part_b, .cancel, .extend_validity) handle the round-trip, storing the returned EWB number, generated date, valid-upto and the raw NIC acknowledgement against the source document. Distance is auto-resolved from consignor/consignee PIN codes with a manual override, and validity days are computed from distance and cargo type so the record shows exactly when the bill lapses.

The app is designed for real dispatch workflow, not just the happy path. Client scripts add "Generate E-Way Bill", "Update Part-B", "Cancel" and "Extend" buttons on the linked documents with contextual guards, so a dispatcher only sees the action that is legal for the current EWB state. Bulk generation and the consolidated e-way bill (single EWB grouping several part-generated bills for one vehicle and route) run as background jobs via the Frappe job queue with per-record error capture, so one rejected invoice never blocks the batch. A scheduler event flags bills nearing expiry and can auto-attempt extension where your policy allows. Role profiles and DocType permissions keep generation, cancellation and master maintenance separated across your dispatch, accounts and transport-desk roles, and every NIC call is logged for audit.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your exact flow — direct NIC vs GSP, which documents trigger EWBs, your distance and validity rules, and any state-specific handling — then build and configure the app against Frappe/ERPNext v15 or v16 on a staging copy of your site. You get UAT on staging, the full Git repository, install and configuration docs, a user guide and a live training session, and a post-go-live support window. Typical delivery is one working week from confirmed scope. You own the source code and can extend it yourself, or keep ECOSIRE on for updates as the NIC API and GST rules evolve.