Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $499.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
Amazon Marketplace Connector
A build-to-order Frappe app that keeps Amazon listings, orders, inventory, and shipments in sync with ERPNext. ECOSIRE scopes, builds, installs, and supports it — no off-the-shelf download.
$499.00USD
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Temel Özellikler
Own Frappe app and module installed on your bench, versioned in a git repo you receive at handover
Amazon SP-API integration using LWA (Login with Amazon) refresh-token auth, credentials held in an `Amazon Settings` single DocType with encrypted Password fields
Scheduled order import via Frappe `scheduler_events` (hourly/cron), mapping Amazon orders to ERPNext Sales Orders with marketplace and fulfillment-channel tags
Link DocType storing Amazon Order ID, ASIN/SKU, marketplace ID, and channel for full traceability back to Seller Central
Product and listing sync mapping ASIN/Seller SKU to ERPNext Items, with a mapping DocType for unmatched or ambiguous SKUs
Inventory level push-back from the ERPNext Stock Ledger to Amazon available quantity, throttled to respect SP-API rate limits
FBA order reconciliation against Amazon fulfillment records; FBM orders drive ERPNext Delivery Notes with tracking written back to Amazon
Fulfillment status sync wired through `hooks.py` document events (`on_submit`, `on_update`) rather than manual polling
Whitelisted server methods exposing sync actions to the Frappe REST API and to desk buttons
Client scripts adding 'Sync now' controls and live status indicators on Sales Order and settings forms
Role profiles and permission rules restricting marketplace credentials and sync controls to authorized users
Multi-marketplace, region-aware endpoints (North America, Europe, Far East) run from a single ERPNext instance
Idempotent sync with dedup on Amazon Order ID and structured Error Log entries so retries never double-create documents
Configurable field mapping for tax, shipping, and order-item lines to match your ERPNext chart of accounts and Item setup
Targets Frappe/ERPNext v15 and v16, with migration-safe DocType definitions and `patches` where schema changes are needed
Bu Ürün Hakkında
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.
Neden Amazon Marketplace Connector
Own Frappe app and module installed on your bench, versioned in a git repo you receive at handover
Amazon SP-API integration using LWA (Login with Amazon) refresh-token auth, credentials held in an `Amazon Settings` single DocType with encrypted Password fields
Scheduled order import via Frappe `scheduler_events` (hourly/cron), mapping Amazon orders to ERPNext Sales Orders with marketplace and fulfillment-channel tags
Link DocType storing Amazon Order ID, ASIN/SKU, marketplace ID, and channel for full traceability back to Seller Central
Product and listing sync mapping ASIN/Seller SKU to ERPNext Items, with a mapping DocType for unmatched or ambiguous SKUs
Inventory level push-back from the ERPNext Stock Ledger to Amazon available quantity, throttled to respect SP-API rate limits
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 2–4 weeks: 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.
Ne elde edeceksin
- Installable source code for your version of the connector, delivered as a proper Frappe app
- Installation and configuration on your bench, including `Amazon Settings`, LWA credentials wiring, and scheduler setup
- Technical documentation: DocType reference, hooks and scheduler events, whitelisted methods, and REST endpoints
- User guide plus a live training session for your operations and finance team
- UAT on a staging bench with sign-off, and a documented rollback plan before production install
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with full commit history so you own and can extend your version
- Deployment notes for v15/v16 compatibility, environment variables, and SP-API credential rotation
Bu kimin için
Amazon-first D2C brand on ERPNext
Sells its own catalog across one or more Amazon regions and runs stock, purchasing, and accounting in ERPNext. Needs orders and inventory to flow both ways automatically so a growing SKU count does not mean more manual re-keying and oversell.
Multi-marketplace seller / aggregator
Operates across North America, Europe, and Far East Amazon marketplaces under one ERPNext instance. Needs region-aware sync with per-marketplace mapping and a single reconciliation view instead of separate spreadsheets per region.
Mixed FBA/FBM operations lead
Runs part of the catalog through FBA and part through FBM. Needs FBA orders reconciled against Amazon fulfillment while FBM orders generate ERPNext Delivery Notes with tracking pushed back — without two disconnected processes.
ERPNext implementation partner / internal IT
Owns the client's ERPNext bench and wants a clean Frappe app with proper DocTypes, hooks, and a git repo they can maintain, rather than brittle server scripts glued together in production.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Amazon Marketplace Connector uygulamasının ZIP dosyasını indirin.
Uygulamayı bankınıza ekleyin
ZIP dosyasını tezgahınızın uygulamalar klasörüne çıkarın veya çıkarılan uygulamanın yolunu içeren "bench get-app" komutunu çalıştırın.
Sitenize yükleyin
Amazon Marketplace Connector yüklemek ve şemasını uygulamak için `bench --site SITE_NAME install-app APP_NAME` komutunu ve ardından `bench move'u çalıştırın.
Lisansınızı etkinleştirin
Sitenizdeki ECOSIRE Lisans ayarlarını açın ve lisans anahtarınızı etkinleştirin. Ücretsiz ecosire_connect ve ecosire_license_client uygulamalarını gerektirir.
Amazon Marketplace Connector Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Amazon SP-API coverage | Orders, listings, inventory, and FBA/FBM shipments, scoped to your needs | Whatever you have time to build and maintain | Often order-import only; listing and inventory push limited | |
| Two-way inventory sync | Stock Ledger pushed back to Amazon, rate-limit throttled | Possible but you own the throttling and edge cases | Sometimes one-way or add-on gated | |
| Multi-marketplace / region | Region-aware NA/EU/FE endpoints from one instance | Buildable, significant extra effort per region | Varies; often single-region or per-region licensing | |
| FBA vs FBM handling | Explicit modeling; FBA reconcile, FBM Delivery Notes + tracking | Must design the distinction yourself | Frequently FBM-oriented, FBA partial | |
| Fit to your ERPNext setup | Field mapping to your accounts, Items, and tax during scoping | Fully yours, if you have the engineering time | Fixed schema; you adapt to it | |
| Code ownership | Git repo handover; you own your version | You own it entirely | Usually closed-source, subscription-locked | |
| Delivery and cost | 2–4 weeks from confirmed scope, fixed build engagement | Unpredictable timeline and internal cost | Instant install but recurring per-seat/order fees | |
| Support and updates | Post-go-live window + optional SP-API maintenance | Entirely on your team | Vendor SLA, tied to subscription |
Amazon Marketplace Connector hakkında Sıkça Sorulan Sorular
+Is this a ready-to-download app from the Frappe Marketplace?
No. This is build-to-order. ECOSIRE scopes your requirements, builds the connector as a proper Frappe app for your marketplaces and FBA/FBM mix, then installs and supports it. There is no instant download — you receive source you own for your version.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The clock starts once we have agreed on your marketplaces, catalog mapping, order and returns flow, and FBA/FBM split during the scoping call. Larger multi-region catalogs sit at the upper end of that range.
+Which Amazon and ERPNext versions are supported?
The connector integrates with the Amazon Selling Partner API (SP-API) using LWA refresh-token authentication, and targets Frappe/ERPNext v15 and v16. We confirm your exact bench version during scoping and build DocType patches to stay migration-safe.
+How do you handle support and future updates?
A post-go-live support window is included for defect fixes and configuration changes. Because you receive the git repository, your team or partner can extend the app afterward. We also offer ongoing support and SP-API update maintenance as a separate arrangement — Amazon evolves its API, and we can keep pace with it for you.
+Will it prevent overselling across channels?
That is a core goal. Inventory is pushed from the ERPNext Stock Ledger back to Amazon available quantity on a schedule, throttled to respect SP-API rate limits, so listings reflect real warehouse bin levels. It reduces oversell substantially, though propagation is bounded by Amazon's own update cadence.
+How are FBA and FBM orders treated differently?
FBA orders reconcile against Amazon's fulfillment records so ERPNext reflects Amazon-shipped stock, while FBM orders drive ERPNext Delivery Notes and write tracking numbers back to Amazon. The fulfillment channel is recorded on each order so reporting stays clean across both models.
+What happens if a sync fails or runs twice?
Sync is idempotent — deduplicated on the Amazon Order ID — so retries never double-create Sales Orders. Failures are written to the Frappe Error Log with context, and scheduled jobs retry on the next cycle. We review edge cases with you during UAT on staging before production go-live.
Teklif isteyin
Amazon Marketplace Connector
A build-to-order Frappe app that keeps Amazon listings, orders, inventory, and shipments in sync with ERPNext. ECOSIRE scopes, builds, installs, and supports it — no off-the-shelf download.
- Own Frappe app and module installed on your bench, versioned in a git repo you receive at handover
- Amazon SP-API integration using LWA (Login with Amazon) refresh-token auth, credentials held in an `Amazon Settings` single DocType with encrypted Password fields
- Scheduled order import via Frappe `scheduler_events` (hourly/cron), mapping Amazon orders to ERPNext Sales Orders with marketplace and fulfillment-channel tags
- Link DocType storing Amazon Order ID, ASIN/SKU, marketplace ID, and channel for full traceability back to Seller Central