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 one working week 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.