GCC apparel brands selling on Namshi hit the same wall: Namshi is a first-party-style marketplace with its own seller portal, but ERPNext core has no concept of it. Orders arrive in Namshi's dashboard, get exported to spreadsheets, and are keyed back into ERPNext by hand — so stock allocated on Namshi is invisible to the warehouse, prices drift between the two systems, and finance spends the month-end untangling Namshi's settlement report against what was actually sold. ERPNext gives you excellent native Sales Order, Stock, and Accounts machinery, but it stops at the edge of your own site — there is no built-in bridge to Namshi's order, inventory, or payout APIs.

We build that bridge as a proper Frappe app installed on your bench — not a script pasted into the desk. The app ships a Namshi Settings single DocType holding credentials and sync toggles, a Namshi Order staging DocType that mirrors the raw marketplace payload for auditability before it becomes an ERPNext Sales Order, and a Namshi Sync Log DocType so every pull and push is traceable. Scheduled jobs registered under scheduler_events in hooks.py poll Namshi on the cadence you choose (typically every 10-15 minutes) to import new and updated orders, and doc_events hooks on Sales Order, Delivery Note, and Item fire the reverse direction — writing fulfillment, tracking, and inventory changes back to Namshi. All marketplace calls run through whitelisted methods (@frappe.whitelist()) with idempotency keys so a retried webhook or a duplicate poll never creates a second Sales Order.

On the inventory side, the connector maps your ERPNext Item and its variant attributes (size, colour) to Namshi's SKU and listing model, and pushes available quantity from a nominated warehouse or a computed "sellable" figure so you never oversell a size that is committed elsewhere. Price and promotion updates flow from your Item Price list to Namshi on the same scheduler, and listing/variant creation can be pushed for new styles. Settlement files from Namshi are ingested and reconciled line-by-line against the originating Sales Orders and Payment Entries, with commissions, shipping fees, and returns broken out so your accounts team gets a clean, matched view instead of a raw payout dump. Role profiles and permission rules scope who can edit credentials versus who can only view the sync logs, and client scripts add the operational buttons your team actually presses on the order screen.

Because this is build-to-order, nothing is pre-listed for instant download — we scope it to your exact Namshi seller setup, warehouse layout, and ERPNext version (Frappe/ERPNext v15 or v16), then build, install on a staging site, run UAT with your data, and cut over to production. Typical delivery is one working week from confirmed scope. You receive the full source, a git repository handover, and a post-go-live support window so the connector keeps working through Namshi API changes and your own ERPNext upgrades.