Fashion boutiques and brands selling through ASOS quickly outgrow spreadsheets and manual re-keying. Orders arrive on the ASOS partner portal while stock lives in ERPNext, so someone copies line items into a Sales Order by hand, forgets to decrement the ASOS listing when a size sells out on your own site, and discovers oversells only when ASOS raises a late-dispatch or cancellation penalty. ERPNext core has no native ASOS channel: there is no Sales Order source for partner orders, no listing feed, no settlement matching against your Sales Invoice and Payment Entry records. You are left reconciling a marketplace remittance CSV against ERPNext by eye at month-end.

ECOSIRE builds a dedicated Frappe app — a proper installable app with its own module, DocTypes, and hooks.py — that turns ERPNext into the system of record for your ASOS channel. A ASOS Settings single DocType holds credentials and endpoint config; scheduled jobs registered under scheduler_events poll ASOS on the cadence you choose and import each order into a native ERPNext Sales Order, mapping marketplace SKUs to your Item codes (including size/colour variants via Item Variant) with idempotent handling so a re-poll never duplicates an order. A connector log DocType records every request, response, and mapping decision so failures are diagnosable rather than silent.

Inventory and pricing sync runs both ways. hooks.py doc events on Stock Ledger Entry / Bin and on your Item Price records push availability and price changes up to the ASOS listing, while inbound polls reconcile the marketplace view back to ERPNext — with configurable buffer stock and per-warehouse rules so you never publish quantity you can't ship. Listing and product-feed push maps ERPNext Item, Item Group, brand, and attribute data into the ASOS feed format. When you dispatch, a shipment writeback posts the carrier and tracking number from your Delivery Note back to ASOS to keep dispatch SLAs green. A settlement reconciliation routine ingests ASOS remittance data and matches gross, commission, and fees against Sales Invoice and Payment Entry, flagging variances instead of hiding them. Everything is exposed through whitelisted methods and the Frappe REST API, guarded by role profiles and permission rules so marketplace operators see only what they should, and client scripts add the buttons and status indicators your team needs inside the ERPNext desk.

Because this is build-to-order, we start from your real catalogue, warehouse layout, and ASOS partner setup rather than shipping a one-size-fits-all binary. After a short scoping call we confirm field mappings, sync cadence, and edge cases (variants, bundles, returns, partial dispatch), build against Frappe/ERPNext v15/v16, and validate on a staging bench with your data before go-live. Typical delivery is one working week from confirmed scope. You receive the full source, a documented install, and a support window — not a black box.