Amazon sellers running operations in ERPNext hit the same wall: orders live in Seller Central while stock, costs, and fulfillment live in ERPNext, so someone spends hours a day re-keying orders, chasing oversell alerts, and reconciling FBA inventory by hand. ERPNext core has excellent Sales Order, Delivery Note, and Stock Ledger machinery, but nothing that speaks the Amazon Selling Partner API (SP-API). The legacy ecommerce_integrations Amazon piece is read-only order import at best and does not cover listing sync, inventory push-back, FBA/FBM mapping, or multiple marketplace regions. That gap is exactly what this connector fills.

We build a proper Frappe app — its own module, DocTypes, and hooks.py wiring — installed onto your bench alongside ERPNext. A dedicated Amazon Settings (single DocType) holds LWA credentials, refresh token, and per-region marketplace IDs, with secrets stored as Password fields (encrypted at rest). Amazon orders are pulled on scheduler_events (a periodic cron/hourly job through the Frappe scheduler) and mapped into ERPNext Sales Orders, with a link DocType recording the Amazon Order ID, marketplace, and fulfillment channel so every record is traceable back to Seller Central. Listing sync maps ASIN/SKU to ERPNext Items, and inventory is pushed from the Stock Ledger back to Amazon so available quantity reflects real warehouse bin levels — the single biggest lever against oversell.

Technically, the app leans on Frappe primitives rather than fighting them. Document events in hooks.py (on_submit, on_update) trigger fulfillment status writes and shipment mapping; whitelisted server-side methods expose sync actions to the desk and to the Frappe REST API; client scripts add "Sync now" buttons and status indicators on the relevant forms; and role profiles plus permission rules keep marketplace credentials and sync controls off limits to users who should not touch them. FBA and FBM shipments are modeled explicitly — FBA orders reconcile against Amazon's fulfillment records while FBM orders drive ERPNext Delivery Notes and write tracking back to Amazon. Multi-marketplace support is region-aware (e.g. North America, Europe, and Far East endpoints), so a brand selling across several Amazon regions runs them from one ERPNext instance. Everything targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, there is no instant download. We start with a short scoping call to confirm your marketplaces, catalog size, FBA/FBM mix, and how you want orders and returns to land in ERPNext. From confirmed scope, typical delivery is one working week: we build against your requirements, run UAT on a staging bench, then install on production with a rollback plan and hand over the git repository. You own the source for your version, and a post-go-live support window is included.