Ü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
ERPNext eMAG Marketplace Connector
A build-to-order Frappe app that connects your eMAG Marketplace seller account (Romania, Bulgaria, Hungary) to ERPNext — importing orders, publishing and editing offers, syncing stock and price two ways, and driving eMAG courier AWBs. ECOSIRE builds, installs, and supports it after a scoping call; it is not an instant 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
eMAG Marketplace API integration for Romania, Bulgaria, and Hungary with per-country platform hosts and separate credentials in an encrypted `eMAG Settings` DocType
Scheduled order import via Frappe `scheduler_events` into an `eMAG Order` DocType, idempotently mapped to native ERPNext Sales Orders with dedupe on the eMAG order id
Offer publishing and editing through whitelisted server methods — create new `eMAG Offer` records and push price, stock, handling time, and status changes to eMAG
Two-way inventory sync: `hooks.py` doc events on Bin/Stock Ledger push ERPNext stock to live offers, and marketplace confirmations flow back to keep counts truthful
Two-way price sync from Item Price / pricing rules to the corresponding eMAG offer, with configurable currency and margin guards
eMAG courier and AWB workflow: generate shipping labels, book pickups, and write tracking numbers onto the ERPNext Delivery Note
Commission and settlement reconciliation that reads eMAG payment statements and matches them against Sales Invoices, flagging fee and payout mismatches
Item-to-offer mapping layer keyed on part number / EAN so your ERPNext catalog links cleanly to eMAG product categories and characteristics
Background processing with `frappe.enqueue` so API-heavy syncs run on workers and never block the desk UI
eMAG API rate-limit handling with retry, backoff, and a full-fidelity `eMAG Sync Log` DocType recording every request and response
Client Scripts adding operator actions (Fetch Orders, Publish Offer, Print AWB, Retry Sync) directly on the relevant DocType forms
Dedicated Role Profile and permission rules so warehouse and finance staff see only their relevant eMAG data
Standard Frappe REST API and whitelisted endpoints exposed for your own automations and reporting
Built and tested for Frappe/ERPNext v15 and v16, delivered as versioned, self-owned source
Bu Ürün Hakkında
If you sell on eMAG in Romania, Bulgaria, or Hungary and run ERPNext, the day-to-day reality is a lot of manual copy-paste. Orders arrive in the eMAG Seller/Marketplace dashboard and get keyed into ERPNext by hand; stock counts drift between what ERPNext thinks you have and what your eMAG offers advertise; price changes made in ERPNext never reach the marketplace until someone remembers to update each offer; and reconciling eMAG's commission and settlement statements against your Sales Invoices is a spreadsheet chore. ERPNext core has no concept of eMAG — there is no marketplace order source, no offer DocType, no AWB workflow — so out of the box you are bridging two systems with human effort, and every hour of lag is an oversell risk or a late dispatch.
Neden ERPNext eMAG Marketplace Connector
eMAG Marketplace API integration for Romania, Bulgaria, and Hungary with per-country platform hosts and separate credentials in an encrypted `eMAG Settings` DocType
Scheduled order import via Frappe `scheduler_events` into an `eMAG Order` DocType, idempotently mapped to native ERPNext Sales Orders with dedupe on the eMAG order id
Offer publishing and editing through whitelisted server methods — create new `eMAG Offer` records and push price, stock, handling time, and status changes to eMAG
Two-way inventory sync: `hooks.py` doc events on Bin/Stock Ledger push ERPNext stock to live offers, and marketplace confirmations flow back to keep counts truthful
Two-way price sync from Item Price / pricing rules to the corresponding eMAG offer, with configurable currency and margin guards
eMAG courier and AWB workflow: generate shipping labels, book pickups, and write tracking numbers onto the ERPNext Delivery Note
ECOSIRE builds a proper Frappe application (its own installable app with a dedicated module) that turns eMAG into a first-class channel inside ERPNext. The connector talks to the eMAG Marketplace API and stores credentials and per-country settings (RO/BG/HU each have their own platform host) in an eMAG Settings DocType with encrypted password fields. Incoming orders are pulled on a Frappe scheduler_events cron into an eMAG Order DocType, then mapped to native ERPNext Sales Orders — with idempotent dedupe on the eMAG order id so a retried poll never double-books. Product catalog is modeled as an eMAG Offer DocType linked to your ERPNext Item; whitelisted server methods (@frappe.whitelist()) publish new offers and push edits (price, stock, handling time, status) to eMAG, while hooks.py doc events (on_update on Item / Item Price / Bin) fire the reverse direction so a stock or price change in ERPNext propagates back to the live offer. The eMAG courier/AWB workflow generates shipping labels and writes tracking numbers onto the Delivery Note, and a settlement routine reads eMAG's commission and payment statements to reconcile against Sales Invoices and flag mismatches.
Technically it is built the way a Frappe engineer would expect: custom DocTypes with controller classes, hooks.py for doc events and scheduler jobs, background workers (frappe.enqueue) for the API-heavy sync so the UI never blocks, retry-and-log handling for eMAG rate limits, and an eMAG Sync Log DocType for full auditability of every request and response. We expose the connector through whitelisted methods and the standard Frappe REST API, add Client Scripts for the buttons your operators press (Publish Offer, Fetch Orders, Print AWB), and wire a dedicated Role Profile plus permission rules so warehouse and finance staff only see what they should. It targets Frappe/ERPNext v15 and v16 and is delivered as versioned source you own.
Because every eMAG seller's ERPNext is configured differently — your Item naming, warehouses, tax templates, fulfilment model, and which of the three countries you sell in — this is build-to-order, not a marketplace download. We start with a short scoping call to confirm exact requirements, then build against your real field mappings, validate on a staging bench with your data, run UAT, and cut over with a rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the complete git repository, install and configuration, documentation, a training session, and a post-go-live support window — you are never locked to us.
Ne elde edeceksin
- Installable source code of the connector app, built for your Frappe/ERPNext version (v15 or v16)
- Installation and configuration on your bench, including eMAG credentials, per-country settings, and field mappings
- Technical documentation covering DocTypes, hooks, scheduler jobs, whitelisted methods, and the settlement logic
- End-user guide plus a live training session for your operations and finance team
- UAT on a staging bench with your real data, followed by a supervised production cutover with a rollback plan
- Post-go-live support window for bug fixes and adjustments to the delivered scope
- Full git repository handover so you own and can extend the code with no vendor lock-in
- Configured Role Profile and permission set for warehouse and finance users
Bu kimin için
CEE eMAG seller running ERPNext
A Romania, Bulgaria, or Hungary based online retailer already live on eMAG Marketplace and on ERPNext, tired of re-keying orders and reconciling settlements by hand, who wants the channel to behave like a native part of their ERP.
Operations / warehouse manager
Owns dispatch accuracy and stock truth. Needs orders to land in ERPNext automatically, AWBs generated without leaving the system, and inventory that stays synced so the team never oversells a live offer.
Finance / accounting lead
Responsible for margin and reconciliation. Wants eMAG commission and settlement statements matched against Sales Invoices automatically, with mismatches flagged, instead of rebuilding it all in spreadsheets each month.
Frappe/ERPNext partner or in-house developer
Values a properly structured Frappe app — real DocTypes, hooks, whitelisted methods, background jobs, and a clean git repo — that they can read, extend, and maintain rather than an opaque black box.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden ERPNext eMAG 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
ERPNext eMAG 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.
ERPNext eMAG Marketplace Connector Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| eMAG order import | Scheduled auto-import to Sales Orders, deduped by eMAG order id | Possible but you design and test the dedupe logic yourself | Generic marketplace apps rarely support eMAG specifically | |
| Offer publish & edit | Whitelisted methods push new offers and edits from ERPNext | Build from scratch against the eMAG API | Often Shopify/Amazon focused, no eMAG offers | |
| Inventory & price sync | Two-way sync via hooks and background workers | Depends on the developer wiring the doc events | One-way or channel-limited if present | |
| AWB / courier workflow | eMAG AWB generation with tracking on Delivery Note | Extra scope to build and test | Usually not eMAG courier aware | |
| Settlement reconciliation | Statements matched to Sales Invoices, mismatches flagged | Bespoke build, often skipped for budget | Rarely included | |
| Frappe v15/v16 fit | Proper app with DocTypes, hooks, roles, tested on both | Quality varies by developer | May lag ERPNext version support | |
| Ownership & lock-in | Full git repo handover, you own the code | You own it but carry the full build cost and risk | Closed source, subscription lock-in common | |
| Delivery & support | 2-4 weeks from scope, UAT, training, support window | Timeline and support depend on your hire | Self-serve install, limited eMAG support |
ERPNext eMAG Marketplace Connector hakkında Sıkça Sorulan Sorular
+Is this an instant download from the Frappe Cloud Marketplace?
No. This is a build-to-order product. ECOSIRE builds the connector against your specific ERPNext configuration, eMAG countries, and field mappings, then installs and supports it. It is not an off-the-shelf app you download and self-install.
+How long does delivery take?
Typically 2 to 4 weeks from confirmed scope. After a short scoping call we lock requirements, build against your real ERPNext data, validate on a staging bench, run UAT, and schedule the production cutover. Complex catalog mappings or all three countries at once can extend the timeline, which we confirm before starting.
+Which eMAG countries and ERPNext versions are supported?
eMAG Marketplace for Romania, Bulgaria, and Hungary — each with its own platform host and credentials. The app is built and tested for Frappe/ERPNext v15 and v16. Tell us your version and countries during scoping and we build to match.
+What happens with support and updates after go-live?
You get a post-go-live support window for bug fixes and adjustments to the delivered scope. Because you receive the full git repository, your own team can also maintain and extend the code. Ongoing support, new features, or adapting to future eMAG API changes can be arranged as a separate engagement.
+Do I own the code, or am I locked in?
You own it. We hand over the complete git repository and versioned source. There is no vendor lock-in — you can host it on your own bench, read every line, and extend it with any Frappe developer.
+How does inventory stay in sync without overselling?
ERPNext stock changes trigger `hooks.py` doc events that push updated quantities to your live eMAG offers, and marketplace order confirmations flow back into ERPNext. Sync runs on Frappe background workers with rate-limit handling and a full sync log, so counts stay truthful and every push is auditable.
+Can it handle our commission and settlement reconciliation?
Yes. The connector reads eMAG's commission and settlement statements and matches them against your ERPNext Sales Invoices, flagging fee or payout mismatches so finance can review exceptions instead of rebuilding the reconciliation manually each period.
İlgili Modüller
Teklif isteyin
ERPNext eMAG Marketplace Connector
A build-to-order Frappe app that connects your eMAG Marketplace seller account (Romania, Bulgaria, Hungary) to ERPNext — importing orders, publishing and editing offers, syncing stock and price two ways, and driving eMAG courier AWBs. ECOSIRE builds, installs, and supports it after a scoping call; it is not an instant download.
- eMAG Marketplace API integration for Romania, Bulgaria, and Hungary with per-country platform hosts and separate credentials in an encrypted `eMAG Settings` DocType
- Scheduled order import via Frappe `scheduler_events` into an `eMAG Order` DocType, idempotently mapped to native ERPNext Sales Orders with dedupe on the eMAG order id
- Offer publishing and editing through whitelisted server methods — create new `eMAG Offer` records and push price, stock, handling time, and status changes to eMAG
- Two-way inventory sync: `hooks.py` doc events on Bin/Stock Ledger push ERPNext stock to live offers, and marketplace confirmations flow back to keep counts truthful