If you sell on Daraz across Pakistan, Bangladesh, Sri Lanka or Nepal, you already know the manual tax it imposes: staff copy orders out of Seller Center into ERPNext, re-key SKUs, and chase stock discrepancies that only surface as oversell penalties and cancelled orders. ERPNext core has no concept of a Daraz channel — there is no Sales Order source for Daraz, nowhere to hold a Daraz order number or DEX tracking code, and no scheduled job that reads the Daraz Open Platform API. You end up running two systems by hand, and reconciling Daraz settlement statements against ERPNext payments becomes a month-end nightmare of unmatched commissions and shipping fees.

ECOSIRE builds a proper Frappe app — not a spreadsheet import — that installs onto your ERPNext v15 or v16 bench and treats Daraz as a first-class sales channel. We add dedicated DocTypes such as Daraz Settings (per-country app key, secret and OAuth access/refresh tokens with scheduled auto-refresh), Daraz Store, Daraz Order and Daraz Item Mapping, so every Daraz order maps to an ERPNext Sales Order carrying the marketplace order number, SLA and payment method. Order import runs on a scheduler_events cron that polls the Daraz GetOrders / GetOrderItems endpoints, deduplicates against existing records, and creates the Customer, Sales Order, Delivery Note and Sales Invoice against a warehouse and tax template you nominate. Every request is signed with the Daraz HMAC-SHA256 signature and rate-limited, and failures are captured in an Error Log with retry rather than silently dropped.

Inventory and price stay in step through a two-way bridge. hooks.py doc events on Stock Ledger Entry and Item Price (plus a reconciliation scheduler for drift) push available quantity and price to Daraz via Product/Update and Product/PriceQuantityUpdate, while inbound webhooks and polling reflect Daraz-side changes back into ERPNext — all keyed on the SKU-to-Daraz Item Mapping table so your ERPNext Item Code and the Daraz SellerSku never diverge. Listing and SKU push lets you create or update Daraz products from ERPNext (attributes, images, variants), and the DEX / 3PL workflow generates shipping labels, requests pickups and writes tracking numbers back onto the Delivery Note. A Daraz Settlement importer parses the payout/transaction statements and reconciles commission, shipping fee and refund lines against the matching Sales Invoices so finance can close the month cleanly.

Because this is build-to-order, nothing ships as a blind download. We start with a short scoping call, confirm which Daraz countries, which flows (orders only, or full inventory + settlement), your ERPNext version and any custom fields, then fix the scope in writing. Typical delivery is 2–4 weeks from confirmed scope. You get the app built and demoed on a staging bench first, a UAT sign-off, then a supervised go-live on your production instance with a rollback plan and a post-go-live support window — plus the full git repository so you own the code.