Ü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 Talabat Vendor Connector
A build-to-order Frappe app that links your Talabat vendor account to ERPNext — publishing menus, syncing live orders, pushing stock and availability, and reconciling commission settlements. ECOSIRE scopes, builds, installs, and supports it; this is not an instant marketplace 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
Custom Frappe app with its own module, DocTypes, and `hooks.py` wiring — installs cleanly on your bench alongside ERPNext v15/v16
`Talabat Order` link DocType stores the raw payload, external order id, branch, and channel status for traceability and idempotent replay
Inbound orders materialize as native `Sales Order` / `Sales Invoice` (or POS Invoice for dark stores) against a dedicated Talabat customer and price list
Menu/catalog publish from ERPNext `Item` masters with an Item Group → Talabat category map and per-branch availability child table
Whitelisted REST methods for Talabat webhook callbacks plus scheduled `scheduler_events` pollers so missed webhooks are reconciled, never lost
Stock and availability push driven by `hooks.py` doc events on `Item` and `Stock Ledger Entry`, debounced through the background queue
Order-status and rider-handoff sync mapped to ERPNext status fields with a status-history child table via server scripts
`Talabat Settings` single DocType for encrypted credentials, branch/store mappings, tax, and commission configuration
Settlement and commission reconciliation: import Talabat payout reports and match against ERPNext invoices with a variance report
Idempotency guards keyed on external order id prevent duplicate Sales Orders on webhook retries or poller overlap
Dedicated role profile and permission rules isolate channel operators from the rest of the ERPNext ledger
Integration Log DocType records every request/response for audit, error triage, and safe manual reprocessing
Client scripts surface Talabat order state, rider status, and one-click resync inside the standard ERPNext desk
Multi-branch and multi-outlet aware — each Talabat store maps to its own ERPNext warehouse and price list
Bu Ürün Hakkında
MENA restaurants, grocers, and dark stores running on Talabat live in two systems at once. Orders land in the Talabat vendor portal or a Talabat-provided tablet, while inventory, purchasing, kitchen costing, and accounting sit in ERPNext. Someone re-keys each order, stock counts drift the moment a busy lunch rush hits, an out-of-stock SKU keeps selling because nobody updated the Talabat menu, and at month-end the finance team squints at a Talabat settlement report trying to match payouts and commission against sales that were never booked in ERPNext. ERPNext core has no native concept of a Talabat channel — there is no order source, no menu-publish target, and no settlement matcher out of the box — so the gap gets filled with spreadsheets and overtime.
Neden ERPNext Talabat Vendor Connector
Custom Frappe app with its own module, DocTypes, and `hooks.py` wiring — installs cleanly on your bench alongside ERPNext v15/v16
`Talabat Order` link DocType stores the raw payload, external order id, branch, and channel status for traceability and idempotent replay
Inbound orders materialize as native `Sales Order` / `Sales Invoice` (or POS Invoice for dark stores) against a dedicated Talabat customer and price list
Menu/catalog publish from ERPNext `Item` masters with an Item Group → Talabat category map and per-branch availability child table
Whitelisted REST methods for Talabat webhook callbacks plus scheduled `scheduler_events` pollers so missed webhooks are reconciled, never lost
Stock and availability push driven by `hooks.py` doc events on `Item` and `Stock Ledger Entry`, debounced through the background queue
We build a dedicated Frappe app — a proper installable app with its own module, DocTypes, and hooks.py wiring — that treats Talabat as a first-class sales channel inside ERPNext. Incoming Talabat orders are pulled via the Talabat Integration Platform and materialized as native Sales Order / Sales Invoice documents (or POS Invoices for dark-store flows) against a dedicated Talabat customer and price list, with a Talabat Order link DocType retaining the raw payload, external order id, branch, and status for traceability and idempotent replays. Menu publishing runs the other direction: your ERPNext Item records (with an Item Group → Talabat category mapping and a per-branch availability child table) are transformed and pushed to your Talabat catalog, so the menu customers see is driven by the same master data your kitchen and purchasing teams already maintain.
Technically, order intake is handled by whitelisted methods exposed over the Frappe REST API for webhook callbacks plus scheduled bench poller jobs registered under scheduler_events for reconciliation and retry, so nothing is lost if a webhook is missed. hooks.py document events (for example on_update / on_submit on Item and Stock Ledger Entry) trigger stock and availability pushes to Talabat when quantities cross the availability threshold, debounced through the background queue so a busy period doesn't hammer the API. Order-status and rider-handoff transitions map cleanly onto ERPNext status fields and a status-history child table, driven by server scripts and reflected in the agent UI via client scripts. A Talabat Settings single DocType holds credentials (stored encrypted), branch/store mappings, tax and commission configuration, and toggles; a dedicated role profile and permission rules keep channel operators out of the rest of your ledger. Every integration event is logged for audit and safe reprocessing, and the app targets Frappe/ERPNext v15 and v16.
Because this is build-to-order, nothing ships blind. We start with a short scoping call to confirm your Talabat account type, branch topology, menu structure, tax setup (VAT by market), and how you want settlements reconciled. We then build against your exact ERPNext version and item model, ship the source to a staging site for UAT, and only go live once you have signed off — typical delivery is 2–4 weeks from confirmed scope. You receive the installable app source, a git repository handover, install and configuration on your infrastructure, technical and user documentation, a training session, and a post-go-live support window with a documented rollback plan.
Ne elde edeceksin
- Installable Frappe app source code, built and pinned to your ERPNext v15 or v16 version
- Installation and configuration on your infrastructure (self-hosted bench or Frappe Cloud private bench)
- Technical documentation: DocType reference, hooks/scheduler map, API endpoints, and configuration guide
- End-user guide plus a live training session for operators and finance
- UAT on a staging site with an agreed acceptance checklist and a documented rollback plan
- Post-go-live support window for defect fixes and configuration help
- Git repository handover with full commit history and deployment notes
- Settlement/commission reconciliation report template configured to your Talabat payout format
Bu kimin için
Multi-branch restaurant operator
Runs several outlets on Talabat and needs every channel order booked in ERPNext automatically, with menus and prices driven from one item master instead of edited branch-by-branch in the vendor portal.
Dark store / q-commerce grocer
Fulfils high-volume Talabat grocery orders and needs live stock and availability pushed the instant ERPNext quantities change, so out-of-stock SKUs stop selling and pickers work from accurate orders.
Finance & reconciliation lead
Owns month-end and needs Talabat settlements, commissions, and VAT matched against ERPNext invoices with a clear variance report — not a manual spreadsheet crosscheck against payout PDFs.
IT / ERP administrator
Maintains the ERPNext instance and wants a proper versioned Frappe app with encrypted credentials, scoped permissions, an integration log, and a git handover — not brittle glue code or a black-box connector.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden ERPNext Talabat Vendor 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 Talabat Vendor 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 Talabat Vendor Connector Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Talabat order → ERPNext | Native Sales Order / POS Invoice with idempotent replay | Buildable but you design the whole pipeline | Generic import, rarely Talabat-specific | |
| Menu / catalog publish | Pushed from ERPNext Item masters + category map | Hand-rolled per project | Usually one-way import only | |
| Stock & availability push | Event-driven on Stock Ledger, branch-aware | Depends on developer effort | Batch or absent | |
| Settlement reconciliation | Payout match + commission/VAT variance report | Extra scope, often skipped | Rarely covered | |
| Fit to your ERPNext version | Pinned to your v15/v16 and item model | Whatever you scope | Lowest-common-denominator | |
| Reliability & audit | Integration Log, poller fallback, reprocess | You build the safety nets | Limited logging | |
| Ownership & lock-in | Full source + git repo handover | You own it, you built it | Vendor-controlled, closed | |
| Support path | Go-live window + upgrade retainers | Your team only | Tiered SaaS support |
ERPNext Talabat Vendor 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 scopes it to your Talabat account, branch topology, and ERPNext version, then builds, installs, and supports it. There is no instant download and no pretense of one — you get source code tailored to your setup.
+How long does delivery take?
Typically 2–4 weeks from confirmed scope. The timeline depends on the number of branches, your menu and tax complexity, and how you want settlements reconciled. We lock the scope on the initial call, build against your ERPNext version, and go live only after UAT sign-off on staging.
+Which ERPNext and Frappe versions are supported?
We build and test against Frappe/ERPNext v15 and v16. The app is pinned to your specific version at delivery so it stays compatible with your bench, and we can advise on upgrade paths as new versions land.
+How do you handle support and future updates?
Every build includes a post-go-live support window for defect fixes and configuration help. Beyond that we offer ongoing support and version-upgrade retainers. Because you receive the full git repository, you are never locked in — your own team or any Frappe developer can maintain it.
+How does the Talabat order sync actually work under the hood?
Orders arrive via the Talabat Integration Platform through whitelisted REST webhook methods, with scheduled poller jobs as a safety net for missed webhooks. Each order is stored raw in a `Talabat Order` DocType and materialized as a native ERPNext Sales Order or POS Invoice, with idempotency guards on the external order id to prevent duplicates on retries.
+Can it keep stock and menu availability accurate across multiple branches?
Yes. Each Talabat store maps to its own ERPNext warehouse and price list. Stock and availability pushes are triggered by `hooks.py` document events on Item and Stock Ledger Entry and debounced through the background queue, so when a SKU goes out of stock in ERPNext it stops selling on Talabat without manual portal edits.
+How is access controlled and audited?
Talabat credentials live encrypted in a `Talabat Settings` single DocType, a dedicated role profile limits channel operators to what they need, and an Integration Log records every request and response so failed syncs can be triaged and safely reprocessed.
İlgili Modüller
Teklif isteyin
ERPNext Talabat Vendor Connector
A build-to-order Frappe app that links your Talabat vendor account to ERPNext — publishing menus, syncing live orders, pushing stock and availability, and reconciling commission settlements. ECOSIRE scopes, builds, installs, and supports it; this is not an instant marketplace download.
- Custom Frappe app with its own module, DocTypes, and `hooks.py` wiring — installs cleanly on your bench alongside ERPNext v15/v16
- `Talabat Order` link DocType stores the raw payload, external order id, branch, and channel status for traceability and idempotent replay
- Inbound orders materialize as native `Sales Order` / `Sales Invoice` (or POS Invoice for dark stores) against a dedicated Talabat customer and price list
- Menu/catalog publish from ERPNext `Item` masters with an Item Group → Talabat category map and per-branch availability child table