ERPNext ShipStation Connector

ECOSIRE builds a proper Frappe app — a versioned, installable module with its own DocTypes, not a pile of ad-hoc server scripts — that wires ERPNext directly into the ShipStation API. When a Sales Order or Delivery Note reaches a state you define, a hooks.py document event (or a scheduler-driven batch) serializes the order, ship-to address, item weights and package dimensions into ShipStation's schema and creates the order there over authenticated REST calls. Staff pick a carrier and service, or let rate shopping choose across the carriers ShipStation aggregates, then generate the shipping label and packing slip without leaving the flow. Credentials live in an encrypted ShipStation Settings single DocType, and a background job handles retries and rate limits so a slow carrier API never blocks the transaction.

The write-back path is where the integration earns its keep. A scheduler event polls ShipStation (or receives its webhooks through a whitelisted endpoint) and writes the tracking number, carrier, service, and shipment status onto the matching ERPNext document — updating the Delivery Note, stamping the tracking URL, and optionally triggering the customer notification ERPNext already knows how to send. Multi-warehouse routing is handled by mapping each ERPNext Warehouse to a ShipStation ship-from location and store, so an order fulfilled from your Texas warehouse ships and reports back distinctly from one fulfilled in the UK. Every mapping, field transform, and status rule is configurable through DocTypes rather than hard-coded, so your ops team can adjust behavior without a redeploy.

Because this is built to order, nothing ships until we agree on scope. We start with a short scoping call to confirm your ERPNext version (v15 or v16), your channels and warehouses, which documents trigger export, and how you want rate selection and status write-back to behave. We build against a staging bench, run UAT with your real order patterns, and only then install on production behind a rollback plan. Permissions are enforced with dedicated role profiles so only fulfillment roles can trigger label creation, and the whole app is handed over as a git repository you own. Typical delivery is 2–4 weeks from confirmed scope, depending on the number of carriers, channels, and custom field mappings involved.