Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $799.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
Food Delivery Aggregator Connector for ERPNext
A build-to-order ERPNext connector that syncs your menu and prices out to Talabat, Uber Eats, Deliveroo, Zomato and Swiggy and pulls every delivery order back into a single ERPNext feed. ECOSIRE builds, installs and supports it for your specific outlets and aggregator accounts.
$799.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
Custom Frappe app with its own module, installed via `bench get-app` and `bench install-app` — clean uninstall, no core patches
`Aggregator Channel` DocType holding per-platform store IDs, API credentials (stored via Frappe's encrypted fields), currency and commission percentage
Inbound orders received on `@frappe.whitelist()` REST endpoints that verify each aggregator's signature/HMAC before processing
Idempotent order ingestion — dedupe by external order id so webhook retries never create duplicate Sales Orders or POS Invoices
Automatic creation of POS Invoice / Sales Order per inbound order, routed to ERPNext POS and the Kitchen Display (KDS)
`Channel Item Map` DocType linking each ERPNext Item Code to the matching menu SKU on Talabat, Uber Eats, Deliveroo, Zomato and Swiggy
Two-way menu and price sync driven by `hooks.py` doc events — `Item`/`Item Price` `on_update` queues an outbound push to every mapped channel
Stock-aware availability: a `scheduler_events` job pushes item enable/disable to each platform from projected quantity or your 86 list
Consolidated multi-platform order dashboard as a Frappe workspace + report view — live status, channel, prep time and value in one screen
Per-channel commission and payout records with reconciliation against each aggregator's settlement statement, flagging mismatches
Background job queue (`frappe.enqueue`) for all outbound calls so menu pushes and order processing never block the UI
Client scripts adding in-form actions — accept, re-sync menu, cancel, mark ready — plus status indicators on the order form
Role profiles and permission rules so kitchen, cashier and finance staff each see only the relevant DocTypes and actions
Structured `Integration Log`-style error capture with retry, so a failed platform call is visible and re-triggerable, not lost
Built and tested against Frappe/ERPNext v15 and v16
Bu Ürün Hakkında
Multi-outlet restaurants and cloud kitchens end up running a tablet per aggregator, re-keying menus five times, and manually copying orders into ERPNext. When a dish sells out, someone has to remember to 86 it on every platform; when a price changes, it drifts out of sync across channels; and at month-end nobody can reconcile what Talabat or Deliveroo actually paid out against their commission. ERPNext native gives you excellent Item, Sales Order, POS and Stock DocTypes, but out of the box it has no concept of a Talabat store, an Uber Eats webhook, or a per-channel commission split — so the last mile between the aggregator and your ERPNext ledger stays manual and error-prone.
Neden Food Delivery Aggregator Connector for ERPNext
Custom Frappe app with its own module, installed via `bench get-app` and `bench install-app` — clean uninstall, no core patches
`Aggregator Channel` DocType holding per-platform store IDs, API credentials (stored via Frappe's encrypted fields), currency and commission percentage
Inbound orders received on `@frappe.whitelist()` REST endpoints that verify each aggregator's signature/HMAC before processing
Idempotent order ingestion — dedupe by external order id so webhook retries never create duplicate Sales Orders or POS Invoices
Automatic creation of POS Invoice / Sales Order per inbound order, routed to ERPNext POS and the Kitchen Display (KDS)
`Channel Item Map` DocType linking each ERPNext Item Code to the matching menu SKU on Talabat, Uber Eats, Deliveroo, Zomato and Swiggy
ECOSIRE builds a proper Frappe app (its own module, installable via bench get-app / bench install-app) that closes that gap. We model each integration as first-class DocTypes — Aggregator Channel (credentials, store IDs, currency, commission %), Aggregator Order (the raw inbound payload plus a link to the ERPNext Sales Order / POS Invoice it created), and Channel Item Map (your ERPNext Item Code to each platform's menu SKU). Inbound orders arrive on whitelisted REST endpoints (@frappe.whitelist() methods that verify each aggregator's HMAC/signature), are validated, deduplicated by external order id, and turned into POS Invoices or Sales Orders routed straight to your Kitchen Display. Outbound menu and price sync runs both on demand and on hooks.py doc events — a Item/Item Price on_update handler queues a push so a price edit in ERPNext propagates to every mapped channel without anyone touching a tablet.
Availability stays honest because stock drives it: a scheduler_events job (and optional Stock Ledger doc-event hook) reads projected quantity or your 86 list and pushes item enable/disable to each platform, so you stop taking orders for things you can't make. A consolidated Aggregator Order Dashboard (Frappe workspace + report view) shows live orders across all five platforms in one place with channel, status, prep time and value. For finance, we generate per-channel commission and payout records so you can reconcile each aggregator's statement against the orders and fees ERPNext recorded, and flag mismatches. Everything respects ERPNext permissions — we ship role profiles and permission rules so kitchen, cashier and finance users each see only what they should, and client scripts add the in-form actions (re-sync, accept, cancel) your staff actually use. 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 which aggregators, which of their APIs/partner programs you have access to, your outlet and menu structure, and your commission model. We then build against your sandbox, prove it on a staging bench under UAT, and only then install on production — typical delivery is 2 to 4 weeks from confirmed scope. You receive the full source, a git repository handover, documentation and training, and a post-go-live support window.
Ne elde edeceksin
- Installable source code for your version of the connector as a proper Frappe app (module, DocTypes, hooks, scripts)
- Installation and configuration on your bench — channel setup, API credentials, item mapping and scheduler wiring
- Technical documentation: DocType reference, hooks/endpoints, scheduler events, and how to add a new aggregator later
- User guide plus a live training session for kitchen, cashier and finance staff
- UAT on a staging bench against aggregator sandboxes, with a documented rollback plan before production install
- Post-go-live support window for bug fixes and sync issues after the confirmed handover date
- Git repository handover with full commit history so your team (or any Frappe developer) can maintain and extend it
Bu kimin için
Multi-outlet restaurant operations manager
Runs several branches, each juggling four or five aggregator tablets. Needs every online order landing in ERPNext POS and the KDS automatically, with prices and availability consistent across all channels so staff stop re-keying and stock-outs stop reaching customers.
Cloud kitchen / dark-kitchen owner
Runs virtual brands that exist only on delivery apps. Wants a single ERPNext order feed across brands and platforms, menu and price changes pushed once, and clear per-brand, per-channel revenue and commission visibility.
Finance / accounts lead
Owns month-end reconciliation. Needs each aggregator's payout matched to the orders ERPNext recorded and the commission it charged, with mismatches flagged, instead of manually cross-checking five platform statements against sales.
IT manager or Frappe developer on staff
Responsible for the ERPNext instance. Wants a clean, documented Frappe app with the source and git history handed over — versioned for v15/v16, respecting permissions and scheduler conventions — that they can maintain and extend without vendor lock-in.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Food Delivery Aggregator Connector for ERPNext 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
Food Delivery Aggregator Connector for ERPNext 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.
Food Delivery Aggregator Connector for ERPNext Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Fit to your aggregators & menu | Built to your exact channels, outlets and item mapping | Fully bespoke but you scope and build it yourself | Generic feature set, rarely matches all five platforms | |
| Order ingestion into ERPNext | Auto POS Invoice / Sales Order to KDS, deduped | Possible, but you build the webhook and dedupe logic | Often one-way or partial import | |
| Menu & price sync | Two-way, doc-event driven on `Item`/`Item Price` | Achievable with significant in-house effort | Usually one-direction or push-only | |
| Stock-aware availability (86 push) | Scheduler + stock-driven enable/disable per channel | Must design and maintain yourself | Rarely tied to real ERPNext stock | |
| Commission & payout reconciliation | Per-channel records matched to aggregator statements | Build your own reconciliation reports | Typically absent or basic | |
| ERPNext version & permissions | v15/v16, role profiles and permission rules shipped | Depends entirely on your developer | Version support varies; permissions often loose | |
| Source, git handover & ownership | Full source + git history handed over, no lock-in | You own it because you built it | Usually closed-source subscription | |
| Support & delivery model | Build-to-order, 2-4 wks, post-go-live support window | Timeline and support entirely on you | Instant install but generic, self-serve support |
Food Delivery Aggregator Connector for ERPNext hakkında Sıkça Sorulan Sorular
+Is this an existing app I can download and install today?
No. It is build-to-order. ECOSIRE builds the connector for your specific aggregators, outlets, menu structure and commission model, then installs and supports it. There is no instant Frappe Cloud Marketplace download — you receive source built and tested for your ERPNext instance.
+How long until it is live?
Typically 2 to 4 weeks from confirmed scope. After a short scoping call we build against your aggregator sandboxes, prove it on a staging bench under UAT, and then install on production. Timeline depends on how many aggregators are in scope and how quickly their API/partner access is granted.
+Which aggregators and platforms does it cover?
The connector is designed for Talabat, Uber Eats, Deliveroo, Zomato and Swiggy. Actual coverage depends on which platforms you have live partner/API access to — each aggregator gates its menu and order APIs behind a partner program. We confirm exactly what is available for your accounts during scoping, and the `Aggregator Channel` design lets us add more platforms later.
+How does the menu and order sync actually work technically?
Outbound menu and price sync is driven by `hooks.py` doc events on `Item`/`Item Price` plus on-demand pushes, all run through Frappe's background queue. Inbound orders hit whitelisted (`@frappe.whitelist()`) REST endpoints that verify each aggregator's signature, dedupe by external order id, and create POS Invoices or Sales Orders routed to your KDS. Availability is pushed by a scheduler job driven by ERPNext stock and your 86 list.
+Which ERPNext versions are supported?
We build and test against Frappe/ERPNext v15 and v16. If you are on an older version we will flag that during scoping and discuss upgrade or backport options before any work starts.
+What about support and future updates?
Every build includes a post-go-live support window for bug fixes and sync issues. Because you receive the full source and git repository, your own team or any Frappe developer can maintain it. Ongoing support, aggregator API changes, and new-platform additions can be handled under a separate support or retainer arrangement.
+Do we own the code, or are we locked in?
You own your build. We hand over the complete Frappe app source and the git repository with full history. It is a standard installable app with no core patches, so nothing is hidden and there is no lock-in — you can extend or move it freely.
İlgili Modüller
Teklif isteyin
Food Delivery Aggregator Connector for ERPNext
A build-to-order ERPNext connector that syncs your menu and prices out to Talabat, Uber Eats, Deliveroo, Zomato and Swiggy and pulls every delivery order back into a single ERPNext feed. ECOSIRE builds, installs and supports it for your specific outlets and aggregator accounts.
- Custom Frappe app with its own module, installed via `bench get-app` and `bench install-app` — clean uninstall, no core patches
- `Aggregator Channel` DocType holding per-platform store IDs, API credentials (stored via Frappe's encrypted fields), currency and commission percentage
- Inbound orders received on `@frappe.whitelist()` REST endpoints that verify each aggregator's signature/HMAC before processing
- Idempotent order ingestion — dedupe by external order id so webhook retries never create duplicate Sales Orders or POS Invoices