The ERPNext ShipStation integration

1. 01

   Multiple accounts, one ERPNext instance

   Connect more than one ShipStation account to a single ERPNext site, rather than running a separate ERPNext instance per storefront.

2. 02

   Per-store mapping

   Each store inside a ShipStation account maps individually to a company, warehouse, cost center, and account heads — so two brands in one ShipStation account can post to two different companies in ERPNext.

3. 03

   Scheduled fetch of products, orders, and shipments

   The app periodically pulls products, orders, and shipments from every connected ShipStation account into ERPNext, rather than requiring a manual export/import each time.

4. 04

   Amazon marketplace hooks

   Stores connected to the Amazon marketplace are identified, and the app adds hooks that other Frappe applications can use to process those Amazon orders — the README describes this as an identification-and-hook layer, not a full Amazon order pipeline on its own.

5. 05

   Shipping label generation

   Label generation can be enabled per ShipStation account. It's an optional switch per account, not a feature that's on for every store by default.

One thing the README doesn't spell out is which specific ERPNext record type each fetched product, order, or shipment becomes — it documents what data moves, not the DocType-level mapping. If that detail matters for how your team already works in ERPNext, it's a fair question to raise on the quote call rather than something we'd guess at here.

1. 01

   Pick the branch that matches your ERPNext version

   The repository publishes version-matched branches — main-v13 (the default branch, targeting Frappe/ERPNext v13), main-v14, and main-v15. Install the one that matches the ERPNext version already running your site.

2. 02

   Get the app onto a bench

   The README's own command is bench get-app https://github.com/ParsimonyGit/shipstation_integration --branch main-v13. On Frappe Cloud, a custom app that isn't in the Marketplace needs a private bench — the same private-bench requirement already published on /erpnext-hosting — and the equivalent step is attaching the repository and branch to that bench through the dashboard instead of a terminal.

3. 03

   Install it on the site and migrate

   bench --site <site_name> install-app shipstation_integration, then bench --site <site_name> migrate to apply the app's database migrations. This is the same two-command shape every Frappe app install ends with, on Frappe Cloud or self-hosted.

4. 04

   Open ShipStation Settings in the desk

   Connect one or more ShipStation accounts with an API key and secret. This is where every account the site will sync gets added.

5. 05

   Map each store

   For every store inside a connected account, set the company, warehouse, cost center, and account heads it should post to.

6. 06

   Turn on sync — and labels, if you want them

   Enable scheduled sync so products, orders, and shipments keep pulling in on their own, and turn on shipping label generation per account for any store that should use it.

bench get-app https://github.com/ParsimonyGit/shipstation_integration --branch main-v13
bench --site <site_name> install-app shipstation_integration
bench --site <site_name> migrate

• Version-specific: main-v13 is the default branch and targets Frappe/ERPNext v13 specifically. main-v14 and main-v15 exist as separate branches — there's no single branch that covers every version.
• Depends on a third-party Python client: the app is built on the ShipStation client library maintained by AgriTheory, not a package Parsimony or Frappe publishes.
• It's a custom app, not a Marketplace install: on Frappe Cloud that means a private bench, which is a different plan tier than the shared plans self-serve Frappe Cloud sites start on.
• The README documents what data moves — products, orders, shipments — but not sync frequency, retry behavior, or which specific ERPNext DocType each fetched record lands in. Confirm that mapping on the quote call if it matters to how your team works.
• Each ShipStation account needs its own API key and secret; there's no ERPNext-side credential that stands in for a ShipStation account you haven't connected.

01

What does the ERPNext ShipStation integration actually sync?

Per the repository README, it connects one or more ShipStation accounts to a single ERPNext instance, maps each ShipStation store to a company, warehouse, cost center, and account heads, and periodically fetches products, orders, and shipments from every connected account. It can also generate shipping labels, which is enabled per account rather than on by default.

02

Which Frappe and ERPNext versions does it support?

The app ships as version-matched branches on GitHub: main-v13 is the repository's default branch and targets Frappe/ERPNext v13, with separate main-v14 and main-v15 branches for those versions. You install the branch that matches your ERPNext version, not a single universal release.

03

Does it generate shipping labels?

Yes — the README lists shipping label generation as a feature that can be enabled per ShipStation account, so it's optional rather than automatic for every connected store.

04

Does it handle Amazon marketplace orders?

It identifies which connected stores are tied to the Amazon marketplace and adds hooks that other Frappe applications can use to process those Amazon orders. The README doesn't describe it processing Amazon orders on its own beyond that identification and hook layer.

05

Is the ERPNext ShipStation integration open source?

Yes. The repository is MIT licensed and published at github.com/ParsimonyGit/shipstation_integration. Installing and running the code is free; what Parsimony quotes separately is the work of installing it on a managed Frappe Cloud bench, mapping your stores, and maintaining it alongside your ERPNext site.