ERPNext Zid Connector

Key Features

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

Settlement reconciliation that matches Zid payout/settlement lines against ERPNext Sales Invoice and Payment Entry, flagging fees and unmatched amounts

Dedicated DocTypes: Zid Settings (single), Zid Store, item/warehouse mapping tables, and Zid Sync Log for a complete searchable audit trail

Scheduler events (hooks.py scheduler_events) for hourly catch-up polling and nightly reconciliation so missed webhooks are recovered automatically

hooks.py doc events on Item, Item Price and Stock Ledger Entry to trigger outbound syncs without manual intervention

Idempotent order import keyed on the Zid order id to prevent duplicate Sales Orders on webhook retries

Role-based access via a Zid Manager role profile and per-DocType permissions, keeping API config and sync controls away from general users

Configurable retry with backoff and error capture into Zid Sync Log, with failed jobs re-runnable from the ERPNext desk

Compatible with Frappe/ERPNext v15 and v16, delivered as a versioned Frappe app installable on your own bench

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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.

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.

What you get

Installable source code of the exact connector version we build for your Zid store and ERPNext instance, as a proper Frappe app

Installation and configuration on your bench (staging then production), including Zid API credential setup and scheduler wiring

Technical documentation: DocType reference, hooks and scheduler event map, field mappings, and API/webhook endpoints

User guide plus a live training session for your operations and finance team on running syncs and reading the Zid Sync Log

UAT on a staging bench with sample Zid orders, sign-off checklist, and a documented rollback plan before production cutover

Defined post-go-live support window for bug fixes and adjustments after launch

Git repository handover with full commit history so your team owns and can extend the code

Data mapping workbook covering item/SKU, warehouse, tax and price-list alignment between Zid and ERPNext

Who this is for

GCC Zid merchant on ERPNext

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.

ERPNext operations manager

Owns fulfillment and inventory accuracy across warehouses; wants Zid orders landing automatically as Sales Orders and stock levels reconciled so oversells stop.

Finance / accounts lead

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.

IT lead / Frappe administrator

Runs the ERPNext bench and wants a maintainable Frappe app with proper DocTypes, hooks, role permissions and source handover rather than fragile console scripts.

How ERPNext Zid Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
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	None; orders re-keyed by hand
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	No Zid-aware sync at all
Settlement reconciliation	Matches Zid payouts to Sales Invoice / Payment Entry, flags fees	Rarely built; usually left as a spreadsheet	Typically not covered	Manual bank and ledger matching only
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	Not applicable
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	N/A
Delivery model	Build-to-order, 2-4 weeks from confirmed scope	Open-ended in-house schedule	Instant install but generic	Immediate but no functionality
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	Community support only
UAT and rollback	Staging UAT with sign-off and documented rollback plan	Only if you set it up	Usually just install docs	N/A

Frequently Asked Questions about ERPNext Zid Connector

How long does delivery take?

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.

Is this a ready-made app I can download right now?

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.

Which versions of ERPNext and Frappe are supported?

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.

How does the two-way inventory and price sync avoid overselling?

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.

What about updates and support after go-live?

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.

How is my Zid API access kept secure?

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.

Can you handle settlement reconciliation against our accounts?

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.