Les détails du produit sont affichés en anglais. Traductions à venir.
Faits en bref
- Prix
- $499.00 USD
- Versions ERPNext
- —
- Temps d'installation
- 30 minutes
- Licence
- Perpétuel unique
- Langues
- 11 langues
Achat unique
ERPNext Amazon SP-API Connector Pro
A build-to-order Frappe app that connects Amazon Seller Central to ERPNext over the SP-API, syncing orders, FBA/FBM inventory, listings, settlements, and returns in both directions. ECOSIRE builds, installs, and supports it for your account and marketplaces.
$499.00USD
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Fonctionnalités clés
SP-API Orders ingestion that creates idempotent ERPNext `Sales Order` and `Sales Invoice` documents keyed on `AmazonOrderId` (no duplicate creation on retried polls)
FBA + FBM multi-fulfillment-channel inventory sync: pulls FBA on-hand from the FBA Inventory API, pushes ERPNext available stock to FBM listings
Listing and price push from ERPNext `Item` master to Amazon via the Listings Items / Feeds API, with per-marketplace price overrides
Settlement Report import that parses the SP-API settlement flat file and maps referral, FBA, storage, and refund fees to nominated GL accounts and cost centers
Returns and refunds sync that reflects Amazon returns as ERPNext credit notes / stock movements for accurate reconciliation
Multi-marketplace support (US/EU/UK/UAE/IN) under a single seller account, each modeled as an `Amazon Marketplace` DocType with its own endpoint and currency
Dedicated `Amazon SP-API Settings` DocType holding LWA refresh token, region/endpoint, and encrypted credentials — no secrets in code
Amazon LWA OAuth token exchange with automatic refresh and SP-API rate-limit backoff honoring `x-amzn-RateLimit-Limit` headers
Scheduler-driven polling via `hooks.py` scheduler events (configurable `cron`/`hourly`) so sync runs unattended with no manual CSV uploads
`doc_events` document automation — e.g. submitting a `Sales Invoice` can trigger an Amazon acknowledgment or fulfillment call
Whitelisted server-side methods and Frappe REST API endpoints for on-demand `Sync now` actions and external triggers
Full `Amazon Sync Log` DocType capturing each API call, payload summary, and error for audit and reprocessing of failed records
Purpose-built Role Profile and DocType-level permissions so warehouse, sales, and finance users get least-privilege access
SKU/Item mapping layer (child table) to reconcile Amazon seller-SKU/ASIN against ERPNext `Item Code`, including bundle and multi-listing cases
Built and tested against ERPNext/Frappe v15 and v16
À propos de ce produit
If you sell on Amazon and run ERPNext, the gap between the two systems is where your margin quietly leaks. Orders land in Seller Central but not in ERPNext, so someone exports Order Reports and re-keys them as Sales Orders. FBA inventory lives in Amazon's fulfillment network while your Bin and Stock Ledger Entry say something different, and by the time the numbers disagree you have already oversold. Settlements arrive as opaque flat files that nobody reconciles against actual fees. ERPNext core has no native concept of Amazon marketplaces, fulfillment channels, or SP-API authentication — so out of the box the answer is always another CSV upload. This is where native ERPNext runs out of road.
Pourquoi choisir ERPNext Amazon SP-API Connector Pro
SP-API Orders ingestion that creates idempotent ERPNext `Sales Order` and `Sales Invoice` documents keyed on `AmazonOrderId` (no duplicate creation on retried polls)
FBA + FBM multi-fulfillment-channel inventory sync: pulls FBA on-hand from the FBA Inventory API, pushes ERPNext available stock to FBM listings
Listing and price push from ERPNext `Item` master to Amazon via the Listings Items / Feeds API, with per-marketplace price overrides
Settlement Report import that parses the SP-API settlement flat file and maps referral, FBA, storage, and refund fees to nominated GL accounts and cost centers
Returns and refunds sync that reflects Amazon returns as ERPNext credit notes / stock movements for accurate reconciliation
Multi-marketplace support (US/EU/UK/UAE/IN) under a single seller account, each modeled as an `Amazon Marketplace` DocType with its own endpoint and currency
ECOSIRE builds a proper Frappe app — not a script bolted onto a scheduler — that speaks the Amazon Selling Partner API (SP-API) directly and maps it cleanly onto ERPNext documents. The app ships as an installable Frappe module with dedicated DocTypes for Amazon Marketplace, Amazon SP-API Settings (credentials, LWA refresh token, region/endpoint), and a Amazon Sync Log for full auditability. Orders pulled from the Orders API are converted into ERPNext Sales Order and Sales Invoice documents via whitelisted server-side methods, with idempotent handling keyed on AmazonOrderId so a retried poll never double-creates. Inventory reconciliation runs off hooks.py scheduler events (cron / all / hourly) that push available quantity from ERPNext Item stock into listings for FBM and pull FBA on-hand from the FBA Inventory API, keeping fulfillment-channel stock honest on both sides.
Technically, the connector is built the way a senior Frappe engineer would want to inherit it. Amazon LWA/OAuth token exchange and AWS SigV4-style request signing are encapsulated in a versioned Python client with backoff on SP-API's rate-limit x-amzn-RateLimit-Limit headers. Document automation is wired through doc_events in hooks.py (for example, submitting a Sales Invoice can trigger a fulfillment or acknowledgment call back to Amazon), and light UI behavior — marketplace badges, a "Sync now" button on the settings form — is delivered as client scripts. Settlement Report ingestion parses the SP-API settlement flat file into ERPNext, mapping Amazon fee lines (referral, FBA, storage, refunds) to the GL accounts and cost centers you nominate, so finance reconciles against real numbers instead of guessing. Access is governed with a purpose-built Role Profile and DocType permissions so warehouse, sales, and finance users each see only what they should. Everything targets ERPNext/Frappe v15 and v16 and is delivered against your own site, not a shared multi-tenant black box.
Because this is build-to-order, we start from your actual Seller Central setup, not a generic template. During scoping we confirm your marketplaces (US/EU/UK/UAE/IN under one seller account), whether you run FBA, FBM, or both, your item and SKU mapping, tax treatment, and how settlements should hit your chart of accounts. We then build your version of the connector, prove it on a staging site with real UAT against your ERPNext data, and go live behind a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the source code, the git repository, documentation, a training session, and a post-go-live support window — there is no instant download, because we are building and installing software tailored to your account.
Ce que vous obtenez
- Installable source code for your version of the connector as a proper Frappe app
- Installation and configuration on your ERPNext site (SP-API credentials, marketplaces, SKU mapping, scheduler)
- Technical documentation: DocType reference, hooks/scheduler map, whitelisted methods, and configuration guide
- End-user guide plus a live training session for your sales, warehouse, and finance teams
- Post-go-live support window for defect fixes and configuration adjustments
- UAT on a staging site against your real ERPNext data, with a documented rollback plan before go-live
- Handover of the git repository with full commit history and branch/tag for your release
Pour qui c'est
Amazon FBA/FBM seller on ERPNext
Runs a growing Amazon business on ERPNext and is drowning in manual Order Report exports and CSV inventory uploads. Needs orders and stock to flow automatically so the team stops re-keying and stops overselling.
Multi-marketplace brand owner
Sells the same catalog across US/EU/UK/UAE/IN under one seller account and needs each marketplace's orders, currency, and pricing handled correctly inside a single ERPNext instance rather than five spreadsheets.
Finance / accounts lead
Responsible for reconciling Amazon payouts. Wants the SP-API settlement report parsed into ERPNext with referral, FBA, and storage fees mapped to the correct GL accounts so books reflect real Amazon economics, not estimates.
ERPNext systems administrator
Owns the ERPNext instance and will maintain the app after handover. Wants a clean Frappe app with proper DocTypes, hooks, permissions, a sync log, and v15/v16 compatibility — plus the git repo and docs to support it internally.
Aperçu de l'installation
Télécharger depuis ECOSIRE
Achetez la licence sur ecosire.com et téléchargez le ZIP de l'application ERPNext Amazon SP-API Connector Pro depuis le tableau de bord de votre compte.
Ajoutez l'application à votre banc
Extrayez le ZIP dans le dossier d'applications de votre banc ou exécutez « bench get-app » avec le chemin d'accès à l'application extraite.
Installer sur votre site
Exécutez `bench --site SITE_NAME install-app APP_NAME` suivi de `bench migrate` pour installer ERPNext Amazon SP-API Connector Pro et appliquer son schéma.
Activez votre licence
Ouvrez les paramètres de licence ECOSIRE sur votre site et activez votre clé de licence. Nécessite les applications gratuites ecosire_connect et ecosire_license_client.
Comment ERPNext Amazon SP-API Connector Pro se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Two-way SP-API order + inventory sync | Built in, FBA and FBM channels handled explicitly | Possible but you build the SP-API client and mapping yourself | Often one-way or FBM-only; FBA support varies | |
| Settlement fee reconciliation to GL | Settlement flat file parsed, fees mapped to your accounts | Only if you scope and build the parser | Rarely included; usually orders/inventory only | |
| Multi-marketplace (US/EU/UK/UAE/IN) | Modeled as `Amazon Marketplace` DocTypes, one seller account | Achievable with extra development effort | Sometimes limited to one region or per-marketplace fees | |
| Fit to your ERPNext data model | Built to your SKU mapping, tax, and account structure | Fully bespoke, but full cost and timeline on you | Generic mapping you adapt to | |
| Source code and ownership | Full source + git repo handover, no lock-in | You own it entirely | Usually closed / subscription-gated | |
| ERPNext v15/v16 compatibility | Built and tested against both | Depends on your team | Depends on vendor's update cadence | |
| Delivery model | Build-to-order, 2–4 weeks from confirmed scope, UAT + rollback | Weeks to months depending on team | Instant install but generic; integration work still on you | |
| Ongoing SP-API change maintenance | Support window + optional maintenance retainer | Your team tracks Amazon API deprecations | Vendor-dependent; tied to subscription |
Foire aux questions sur ERPNext Amazon SP-API Connector Pro
+How long does delivery take?
This is a build-to-order product, so there is no instant download. Typical delivery is 2–4 weeks from confirmed scope — the clock starts once we have agreed your marketplaces, fulfillment model (FBA/FBM), SKU mapping, and settlement/tax treatment. We then build, run UAT on a staging site, and go live behind a rollback plan. Complex multi-marketplace or heavily customized setups may extend the timeline, which we confirm during scoping.
+Do I get the source code and can my team maintain it?
Yes. You receive the full source code as a proper Frappe app and a handover of the git repository with commit history, plus technical documentation covering the DocTypes, `hooks.py` events, scheduler jobs, and whitelisted methods. Your ERPNext administrator can maintain, extend, or re-deploy it. There is no license lock-in or hidden runtime dependency on ECOSIRE.
+What about support and updates after go-live?
Every build includes a post-go-live support window for defect fixes and configuration adjustments. Beyond that window, we offer ongoing support and maintenance retainers — including keeping the connector current with Amazon SP-API changes and new ERPNext releases. Because Amazon periodically deprecates API models and rotates auth requirements, an ongoing arrangement is recommended for production sellers, but it is optional.
+Which ERPNext versions and Amazon marketplaces are supported?
The connector is built and tested for ERPNext/Frappe v15 and v16. It supports multiple Amazon marketplaces (for example US/EU/UK/UAE/IN) under a single Seller Central account, each modeled as its own `Amazon Marketplace` record with the correct SP-API endpoint and currency. If you run a marketplace outside that list, tell us during scoping and we confirm SP-API region coverage.
+Do I need my own Amazon SP-API / developer credentials?
Yes. Amazon SP-API access is tied to your Seller Central account and requires a registered developer application (LWA client credentials and a refresh token authorized for your account roles). We guide you through obtaining or authorizing these during onboarding and store them securely in the `Amazon SP-API Settings` DocType — credentials never live in the app code. You retain ownership of your Amazon access.
+How does inventory stay accurate across FBA and FBM?
The connector treats fulfillment channels explicitly. For FBM items it pushes ERPNext available quantity to your Amazon listings so buyers can't order what you can't ship; for FBA items it pulls on-hand from the FBA Inventory API so ERPNext reflects what Amazon holds. Sync runs on Frappe scheduler events at the interval you choose, and every reconciliation is written to the `Amazon Sync Log` so discrepancies are traceable rather than silent.
+Can it reconcile Amazon fees and payouts in ERPNext?
Yes. The Settlement Report importer parses the SP-API settlement flat file and maps Amazon's fee lines — referral, FBA fulfillment, storage, refunds, and adjustments — to the GL accounts and cost centers you nominate during scoping. Finance reconciles ERPNext against the actual Amazon payout instead of estimating fees, which is one of the biggest sources of unexplained margin loss for Amazon sellers.
Modules associés
Demander un devis
ERPNext Amazon SP-API Connector Pro
A build-to-order Frappe app that connects Amazon Seller Central to ERPNext over the SP-API, syncing orders, FBA/FBM inventory, listings, settlements, and returns in both directions. ECOSIRE builds, installs, and supports it for your account and marketplaces.
- SP-API Orders ingestion that creates idempotent ERPNext `Sales Order` and `Sales Invoice` documents keyed on `AmazonOrderId` (no duplicate creation on retried polls)
- FBA + FBM multi-fulfillment-channel inventory sync: pulls FBA on-hand from the FBA Inventory API, pushes ERPNext available stock to FBM listings
- Listing and price push from ERPNext `Item` master to Amazon via the Listings Items / Feeds API, with per-marketplace price overrides
- Settlement Report import that parses the SP-API settlement flat file and maps referral, FBA, storage, and refund fees to nominated GL accounts and cost centers