Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $249.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
ERPNext Namshi Connector
A build-to-order Frappe app that connects Namshi (the GCC fashion marketplace) to your ERPNext instance — importing orders as Sales Orders, syncing inventory and prices, and reconciling settlements. ECOSIRE builds, installs, and supports it against your v15/v16 site; there is no instant download.
$249.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
Dedicated Frappe app installed on your bench with a `Namshi Settings` single DocType for API credentials, warehouse mapping, and per-sync toggles
Namshi order import into ERPNext `Sales Order` via a `Namshi Order` staging DocType that preserves the raw marketplace payload for audit and replay
Idempotent order sync keyed on the Namshi order id so retried polls or webhooks never duplicate a Sales Order
Scheduler-driven polling registered in `hooks.py` `scheduler_events` (configurable cron, typically every 10-15 minutes) for new and updated orders
Inventory writeback that pushes available quantity from a nominated warehouse or a computed sellable figure to prevent overselling
`Item` variant mapping (size/colour attributes) to Namshi SKUs, so ERPNext variants stay in lockstep with marketplace listings
Price and promotion sync from ERPNext `Item Price` to Namshi on the same scheduler
Listing and variant push for new styles, creating or updating Namshi products from ERPNext item data
Shipping and fulfillment writeback via `doc_events` hooks on `Delivery Note`/`Sales Order` — tracking numbers and status flow back to Namshi
Settlement reconciliation that matches Namshi payout lines against originating Sales Orders and `Payment Entry`, splitting out commission, shipping, and returns
All marketplace traffic routed through whitelisted server methods (`@frappe.whitelist()`) with retry, backoff, and rate-limit handling
`Namshi Sync Log` DocType plus error alerts so every pull/push is traceable and failures surface instead of failing silently
Role profiles and permission rules separating credential admins from sync-log viewers, plus client scripts adding order-screen action buttons
Built and tested against Frappe/ERPNext v15 and v16, with an upgrade-safe app structure (fixtures, patches, no core file edits)
Bu Ürün Hakkında
GCC apparel brands selling on Namshi hit the same wall: Namshi is a first-party-style marketplace with its own seller portal, but ERPNext core has no concept of it. Orders arrive in Namshi's dashboard, get exported to spreadsheets, and are keyed back into ERPNext by hand — so stock allocated on Namshi is invisible to the warehouse, prices drift between the two systems, and finance spends the month-end untangling Namshi's settlement report against what was actually sold. ERPNext gives you excellent native Sales Order, Stock, and Accounts machinery, but it stops at the edge of your own site — there is no built-in bridge to Namshi's order, inventory, or payout APIs.
Neden ERPNext Namshi Connector
Dedicated Frappe app installed on your bench with a `Namshi Settings` single DocType for API credentials, warehouse mapping, and per-sync toggles
Namshi order import into ERPNext `Sales Order` via a `Namshi Order` staging DocType that preserves the raw marketplace payload for audit and replay
Idempotent order sync keyed on the Namshi order id so retried polls or webhooks never duplicate a Sales Order
Scheduler-driven polling registered in `hooks.py` `scheduler_events` (configurable cron, typically every 10-15 minutes) for new and updated orders
Inventory writeback that pushes available quantity from a nominated warehouse or a computed sellable figure to prevent overselling
`Item` variant mapping (size/colour attributes) to Namshi SKUs, so ERPNext variants stay in lockstep with marketplace listings
We build that bridge as a proper Frappe app installed on your bench — not a script pasted into the desk. The app ships a Namshi Settings single DocType holding credentials and sync toggles, a Namshi Order staging DocType that mirrors the raw marketplace payload for auditability before it becomes an ERPNext Sales Order, and a Namshi Sync Log DocType so every pull and push is traceable. Scheduled jobs registered under scheduler_events in hooks.py poll Namshi on the cadence you choose (typically every 10-15 minutes) to import new and updated orders, and doc_events hooks on Sales Order, Delivery Note, and Item fire the reverse direction — writing fulfillment, tracking, and inventory changes back to Namshi. All marketplace calls run through whitelisted methods (@frappe.whitelist()) with idempotency keys so a retried webhook or a duplicate poll never creates a second Sales Order.
On the inventory side, the connector maps your ERPNext Item and its variant attributes (size, colour) to Namshi's SKU and listing model, and pushes available quantity from a nominated warehouse or a computed "sellable" figure so you never oversell a size that is committed elsewhere. Price and promotion updates flow from your Item Price list to Namshi on the same scheduler, and listing/variant creation can be pushed for new styles. Settlement files from Namshi are ingested and reconciled line-by-line against the originating Sales Orders and Payment Entries, with commissions, shipping fees, and returns broken out so your accounts team gets a clean, matched view instead of a raw payout dump. Role profiles and permission rules scope who can edit credentials versus who can only view the sync logs, and client scripts add the operational buttons your team actually presses on the order screen.
Because this is build-to-order, nothing is pre-listed for instant download — we scope it to your exact Namshi seller setup, warehouse layout, and ERPNext version (Frappe/ERPNext v15 or v16), then build, install on a staging site, run UAT with your data, and cut over to production. Typical delivery is 2-4 weeks from confirmed scope. You receive the full source, a git repository handover, and a post-go-live support window so the connector keeps working through Namshi API changes and your own ERPNext upgrades.
Ne elde edeceksin
- Installable Frappe app source code for your scoped version, built against your ERPNext v15 or v16 site
- Installation and configuration on your bench, including `Namshi Settings`, warehouse/item mapping, and scheduler setup
- UAT on a staging site with your real Namshi and ERPNext data, plus a documented rollback plan before production cutover
- Technical documentation: DocType reference, hooks/scheduler map, API integration notes, and configuration guide
- End-user guide plus a live training session for your operations and finance teams
- Git repository handover with full commit history so you own and can extend the codebase
- A post-go-live support window covering bug fixes and Namshi/ERPNext API adjustments
- Reconciliation runbook mapping Namshi settlement fields to ERPNext Sales Orders and Payment Entries
Bu kimin için
GCC fashion brand operations lead
Runs day-to-day Namshi order processing and warehouse allocation, and needs Namshi orders to land in ERPNext as Sales Orders automatically so the team stops rekeying and stops overselling popular sizes.
ERPNext-based apparel merchandiser
Manages styles, variants, and pricing in ERPNext and wants item quantities, prices, and new listings to push to Namshi from a single source of truth instead of being maintained twice.
Finance / accounts manager
Owns month-end and needs Namshi settlement payouts reconciled line-by-line against Sales Orders and Payment Entries — with commission, shipping, and returns separated — instead of a raw payout spreadsheet.
IT / ERPNext administrator or partner
Responsible for the bench and upgrades, and wants a proper installable Frappe app (no core edits, clean hooks, permission-scoped) that survives v15-to-v16 upgrades and comes with the source and a git handover.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden ERPNext Namshi 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 Namshi 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 Namshi Connector Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Namshi integration | Purpose-built for your Namshi seller account and flows | Possible but you specify and build everything | Rarely supports Namshi; GCC marketplaces uncommon | |
| Order import to Sales Order | Automatic, idempotent, via staging DocType | Depends on your developers' design | Generic mapping, often needs heavy config | |
| Inventory & price sync | Scheduled warehouse-aware qty and price push | Built to spec, ongoing maintenance is yours | Basic sync, limited variant handling | |
| Settlement reconciliation | Line-by-line match with commission/returns split | Custom-built, error-prone without domain input | Usually absent or shallow | |
| ERPNext version fit | Built and tested for your v15/v16 site | Whatever you target and test | May lag ERPNext releases | |
| Source & ownership | Full source + git repository handover | You own it, you also fund all of it | Closed source, license-locked | |
| Time to live | Typically 2-4 weeks from confirmed scope | Months, including hiring and ramp-up | Fast install but slow to fit your process | |
| Support & updates | Post-go-live window + API-change fixes | Your team maintains it | Vendor SLA, varies by tier |
ERPNext Namshi Connector hakkında Sıkça Sorulan Sorular
+Is this a ready-made app I can download and install today?
No. It is build-to-order. ECOSIRE builds the connector against your specific Namshi seller setup and ERPNext version, then installs, tests on staging, and hands over the source. There is no instant Marketplace download.
+How long does delivery take?
Typically 2-4 weeks from confirmed scope. The exact timeline depends on how many flows you need (orders, inventory, listings, settlement) and how clean your item/variant data is. We confirm the schedule in writing after the scoping call.
+Which ERPNext versions are supported?
Frappe/ERPNext v15 and v16. We build the app as a standard bench app with clean `hooks.py` events, fixtures, and patches — no core file edits — so it stays upgrade-safe across minor versions.
+How does it avoid overselling and duplicate orders?
Inventory writeback pushes a nominated warehouse quantity (or a computed sellable figure) to Namshi on a schedule, and order import is idempotent — keyed on the Namshi order id — so a retried poll or webhook never creates a second Sales Order.
+What about settlements and finance reconciliation?
Namshi settlement files are ingested and matched line-by-line to the originating Sales Orders and Payment Entries, with commission, shipping fees, and returns broken out so your accounts team gets a reconciled view instead of a raw payout dump.
+What support and updates do we get after go-live?
Every build includes a post-go-live support window for bug fixes and adjustments to Namshi or ERPNext API changes. Because you receive the full source and git repository, your own team or partner can also extend it; extended support and enhancements are available on request.
+What if Namshi changes its API?
Marketplace calls are isolated behind whitelisted service methods with logging, so an API change is a contained fix rather than a rewrite. Adjustments within your support window are covered; larger platform changes are scoped as a follow-up.
İlgili Modüller
Teklif isteyin
ERPNext Namshi Connector
A build-to-order Frappe app that connects Namshi (the GCC fashion marketplace) to your ERPNext instance — importing orders as Sales Orders, syncing inventory and prices, and reconciling settlements. ECOSIRE builds, installs, and supports it against your v15/v16 site; there is no instant download.
- Dedicated Frappe app installed on your bench with a `Namshi Settings` single DocType for API credentials, warehouse mapping, and per-sync toggles
- Namshi order import into ERPNext `Sales Order` via a `Namshi Order` staging DocType that preserves the raw marketplace payload for audit and replay
- Idempotent order sync keyed on the Namshi order id so retried polls or webhooks never duplicate a Sales Order
- Scheduler-driven polling registered in `hooks.py` `scheduler_events` (configurable cron, typically every 10-15 minutes) for new and updated orders