A build-to-order Frappe app that connects your Zid (KSA/GCC) storefront to ERPNext, syncing orders, inventory, pricing, shipping and settlements. ECOSIRE scopes, builds, installs and supports it for you. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that connects your Zid (KSA/GCC) storefront to ERPNext, syncing orders, inventory, pricing, shipping and settlements. ECOSIRE scopes, builds, installs and supports it for you.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
GCC merchants selling on Zid quickly hit a wall running ERPNext natively: Zid holds the live orders, stock levels and prices, but ERPNext knows nothing about them until someone re-keys each order into a Sales Order by hand. Stock sold on Zid keeps showing as available in ERPNext, oversells happen, price changes get out of step between the two systems, and finance has no clean line from a Zid payout back to the invoices it covers. ERPNext core has no Zid awareness at all — there is no standard connector, no OAuth handshake to the Zid Merchant API, and no reconciliation of Zid settlements against your Sales Invoice and Payment Entry records.
Zid Merchant API OAuth token exchange and automatic refresh handled server-side, with credentials encrypted in site config rather than stored in plain DocType fields
Inbound Zid order webhooks received on signature-verified whitelisted endpoints and converted into ERPNext Sales Orders with customer, item, tax and shipping lines mapped
Two-way inventory sync between ERPNext Bin quantities and Zid stock, driven by Stock Ledger Entry doc events so sold-on-Zid stock decrements in ERPNext and vice versa
Two-way price sync between ERPNext Item Price (per selected price list) and Zid product pricing, with currency and rounding rules honored
Product and catalog push from ERPNext Item records to Zid, including variants, images and category mapping via a configurable field map
Shipping and tracking writeback that posts carrier, tracking number and fulfillment status from ERPNext Delivery Note back to the Zid order
The ERPNext Zid Connector is a proper Frappe application (not a script pasted into the console) that ECOSIRE designs, builds and installs on your bench for your exact catalog and workflow. It ships as its own module with dedicated DocTypes — a Zid Settings single DocType for API credentials and sync toggles, a Zid Store mapping, and Zid Sync Log for a full audit trail — plus item and warehouse mapping tables so your Zid SKUs and locations line up with the right ERPNext Item and Warehouse. Zid authentication (OAuth token exchange and refresh) is handled server-side and stored encrypted in site config, never in plain DocType fields.
Technically, the connector runs on the patterns ERPNext teams expect. Inbound Zid orders arrive via Zid webhooks handled by whitelisted endpoints (@frappe.whitelist(allow_guest=True) with signature verification) and are converted into ERPNext Sales Order documents with the correct customer, taxes and shipping lines. Outbound stock and price changes are driven from hooks.py doc events (on_update/on_submit on Stock Ledger Entry, Item Price and Bin) so an update in ERPNext pushes to Zid, while scheduler events (cron/hourly in scheduler_events) run reconciliation and catch-up polling so nothing is lost if a webhook is missed. Everything talks over the Frappe REST API / RPC layer, respects role-based permissions through a dedicated Zid Manager role profile, and is compatible with Frappe/ERPNext v15 and v16. Where you need storefront-side or list-view tweaks, we add targeted client scripts rather than forking core.
Because this is build-to-order, delivery starts with a short scoping call, not a shopping cart. We confirm your Zid store setup, catalog size, warehouse layout, tax and settlement requirements, then agree a fixed scope. Typical delivery is 2 to 4 weeks from confirmed scope. You get the version we build for you as installable source code, deployed first to a staging bench for UAT, then cut over to production with a rollback plan — followed by a defined post-go-live support window. There is no instant download: you are buying an engineered, installed and supported integration.
A KSA or wider GCC retailer whose live storefront runs on Zid while the back office runs on ERPNext, needing orders, stock and prices to stay in step without manual re-keying.
Owns fulfillment and inventory accuracy across warehouses; wants Zid orders landing automatically as Sales Orders and stock levels reconciled so oversells stop.
Responsible for matching Zid settlements and fees against Sales Invoices and Payment Entries in ERPNext, and needs a clean audit trail for VAT and reconciliation.
Runs the ERPNext bench and wants a maintainable Frappe app with proper DocTypes, hooks, role permissions and source handover rather than fragile console scripts.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 ERPNext Zid Connector 应用程序 ZIP。
将 ZIP 解压到您的 bench 的 apps 文件夹中,或者使用解压缩的应用程序的路径运行“bench get-app”。
运行 `bench --site SITE_NAME install-app APP_NAME`,然后运行 `bench migrate` 以安装 ERPNext Zid Connector 并应用其架构。
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Zid order to Sales Order import | Automatic via signature-verified webhooks, idempotent on order id | Possible but you build and test the webhook and mapping yourself | Often generic e-commerce import not tuned to Zid | |
| Two-way inventory and price sync | Driven by Stock Ledger and Item Price doc events plus scheduler catch-up | Achievable with significant in-house Frappe effort | Sometimes one-way or platform-limited | |
| Settlement reconciliation | Matches Zid payouts to Sales Invoice / Payment Entry, flags fees | Rarely built; usually left as a spreadsheet | Typically not covered | |
| Fit to your catalog and workflow | Scoped and built for your SKUs, warehouses and tax setup | Fully bespoke but on your time and risk | Configurable within fixed assumptions | |
| Frappe v15/v16 compatibility and code quality | Proper Frappe app: DocTypes, hooks, role profile, tested | Depends on your team's Frappe expertise | Varies; may lag core version updates | |
| Delivery model | Build-to-order, 2-4 weeks from confirmed scope | Open-ended in-house schedule | Instant install but generic | |
| Support and ownership | Post-go-live support window plus full source and git handover | You own and support everything | Vendor support, no source access typically | |
| UAT and rollback | Staging UAT with sign-off and documented rollback plan | Only if you set it up | Usually just install docs |
This is build-to-order, not an instant download. After a short scoping call to confirm your Zid store, catalog and reconciliation needs, we agree a fixed scope and typically deliver in 2 to 4 weeks from that confirmed scope. Larger catalogs or extra requirements can extend the timeline, which we confirm up front.
No. ECOSIRE builds, installs and supports the connector for your specific ERPNext instance and Zid store. It is not an existing Frappe Cloud Marketplace download. You receive installable source code and a git repository for the version we build for you.
We build for Frappe/ERPNext v15 and v16. During scoping we confirm your exact version and bench setup so the app installs cleanly and the DocTypes, hooks and scheduler events run correctly on your instance.
Inbound Zid orders create Sales Orders that decrement ERPNext stock, while ERPNext Stock Ledger Entry and Item Price doc events push updated quantities and prices back to Zid. Hourly scheduler jobs run catch-up reconciliation so a missed webhook does not leave the two systems out of step.
Every engagement includes a defined post-go-live support window for bug fixes and adjustments. Beyond that window we offer ongoing support and enhancement retainers. Because you receive the full source and git history, your own team can also maintain and extend the app.
Zid OAuth tokens are exchanged and refreshed server-side and stored encrypted in site config, not in plain DocType fields. Webhook endpoints verify signatures, and access to sync configuration is restricted through a dedicated Zid Manager role profile and per-DocType permissions.
Yes. The connector matches Zid settlement and payout lines against ERPNext Sales Invoice and Payment Entry records, separates out platform fees, and flags unmatched amounts so finance has a clean, auditable trail for VAT and month-end close.
A build-to-order Frappe app that connects your Zid (KSA/GCC) storefront to ERPNext, syncing orders, inventory, pricing, shipping and settlements. ECOSIRE scopes, builds, installs and supports it for you.