Multichannel sellers running ERPNext for inventory, invoicing, and accounting almost always run ShipStation for the last mile — rate-shopping carriers, printing labels, and batching pick/pack. ERPNext core has no native bridge to ShipStation, so the two systems drift apart: warehouse staff re-key order lines into ShipStation, and tracking numbers printed on labels never make it back into the ERPNext Delivery Note. Customers email asking where their parcel is while the tracking sits in a browser tab nobody copied over. ERPNext's built-in shipping is limited to a manual Shipment DocType and generic tracking fields; it does not speak ShipStation's order or webhook API.

ECOSIRE builds a proper Frappe app — its own module, DocTypes, and hooks.py doc events — that closes that loop in both directions. On the outbound side we hook the submit event of Delivery Note (or Sales Order, depending on where you cut over to fulfillment) and map each document to a ShipStation order via the ShipStation REST API, carrying line items, ship-to address, requested service, weight, and your store/warehouse identifiers. Authentication is handled through a dedicated ShipStation Settings single DocType that stores the API key and secret encrypted in the site config, so credentials never live in code. Inbound, a whitelisted method receives ShipStation's SHIP_NOTIFY webhook (with a scheduled polling fallback via a scheduler_events cron for stores where webhooks are unreliable), matches the shipment back to the originating ERPNext document, writes the carrier, tracking number, and shipped timestamp, and can auto-submit the Delivery Note or mark the linked Sales Invoice as fulfilled.

The connector is multi-store and multi-warehouse aware: a mapping DocType lets you route a given ERPNext Warehouse or company to the correct ShipStation store and tag orders so your existing ShipStation automation rules (preset service, package, and insurance selection) keep firing untouched. Every sync writes to a log DocType with the request/response payload and status, so a failed push is retryable and auditable rather than silently lost. Field mapping, address formatting, and which trigger event to use are configured per your instance during the build — we do not ship a rigid one-size template. Because it is a real Frappe app it respects ERPNext permissions and role profiles, is upgrade-safe across Frappe/ERPNext v15 and v16, and adds client scripts only where a human needs a manual "Push to ShipStation" or "Refresh tracking" button.

This is a build-to-order product, not an instant download. After a short scoping call we confirm your carriers, stores, warehouse layout, and the exact document lifecycle you fulfill against, then build against your version of ERPNext. Typical delivery is one working week from confirmed scope. You get the installable app source for your version, deployment onto your staging site for UAT, and a post-go-live support window — ECOSIRE builds it, installs it, and stands behind it.