ERPNext Salla Connector

We build the ERPNext Salla Connector as a proper Frappe app installed on your bench — its own module, its own DocTypes, and its own settings, not a pile of loose scripts. A Salla Settings single DocType holds your OAuth2 credentials, store ID and sync toggles; child DocTypes and a Salla Sync Log give you a full audit trail of every record that moved and every error that didn't. Inbound, we register a whitelisted endpoint (via @frappe.whitelist()) that receives Salla webhooks for order.created, order.updated and order.status.updated, verifies the signature, and maps the payload to a Sales Order (or draft Sales Invoice) with the right Customer, Item codes, taxes, shipping line and payment reference. Outbound, hooks.py doc events on Stock Ledger Entry, Item Price and Item push inventory and price changes back to Salla through its REST API, so a stock movement in your warehouse updates the storefront without anyone touching a keyboard.

Technically it is built to ERPNext conventions so your team can own it. Two-way inventory and price sync is reconciled against ERPNext as the source of truth, with configurable warehouse-to-Salla mapping and a scheduled scheduler_events job that sweeps for anything a webhook missed and reprocesses failed rows with backoff. Catalog push creates or updates Salla products from ERPNext Item records (name, SKU, price, variants, images). Shipping and tracking numbers written on the Delivery Note flow back to Salla to move the order to shipped and notify the customer. Invoice mapping is structured to be ZATCA-compatible — VAT breakdown, buyer/seller fields and the data points Saudi e-invoicing (Fatoora Phase 2) expects — so it lines up cleanly with your ZATCA setup rather than fighting it. Everything respects ERPNext permissions and role profiles, ships with client scripts for the operator-facing actions, and targets Frappe/ERPNext v15 and v16.

Because every Salla store and ERPNext instance is configured differently, this is build-to-order — not a one-click marketplace download. We start with a short scoping call to map your exact order flow, tax setup, warehouses and edge cases, then build the connector against your real data on a staging bench. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source code, install it on your bench (or we do), and get a UAT sign-off on staging plus a rollback plan before go-live. After launch you keep a support window and the git repo, so nothing about the integration is a black box.