Quick commerce breaks the assumptions ERPNext ships with. A standard ERPNext catalogue publishes one company-wide availability number, but a 10-minute delivery platform buys from a specific dark store: if the Gulberg micro-fulfilment centre holds 12 units and the central warehouse holds 900, exposing 912 guarantees cancellations, penalty fees and a suppressed listing. Orders also arrive against a slot and a cut-off — accept one two minutes after the rider wave closes and it is already late. ERPNext core has Warehouse, Bin, Item and Sales Order, but no notion of a per-store publishable quantity net of safety buffer and in-flight picks, no cut-off calendar, no rider handoff state machine, and no way to reconcile a platform settlement where commission, picking fees, ad spend and shortage penalties are netted off before payout.

ECOSIRE builds Quick Commerce Connector as a proper Frappe app — its own module inside a versioned repository, not scripts pasted into a production site. Dark stores are modelled as ERPNext Warehouses linked to a Quick Commerce Store DocType that carries the channel identifier, timezone, service radius and cut-off calendar. A scheduled job (registered in hooks.py under scheduler_events) recomputes a publishable quantity per store-item — actual_qty less reserved, less allocated picks, less a per-item safety buffer — and pushes deltas to the platform, with a full-catalogue reconciliation sweep on a slower cadence so drift never accumulates silently. Inbound orders land on a whitelisted endpoint (@frappe.whitelist(allow_guest=True) with HMAC signature verification and idempotency on the channel order id), are staged in a Quick Commerce Order DocType, then converted to a Sales Order against the correct dark-store warehouse and customer group. The cut-off engine evaluates the store calendar before acceptance and routes late or out-of-window orders to an exception queue instead of dropping them into fulfilment.

On the fulfilment side, a courier handoff state machine tracks picking, packing, rider assigned, picked up, delivered and failed-delivery — each transition timestamped and written back to the channel through a retry-safe outbound queue so a transient platform 5xx never leaves ERPNext and the app disagreeing. Doc events on Pick List and Delivery Note drive substitution and shortage handling: when a picker cannot fulfil a line, the app records the shortage reason, applies your configured substitution policy (equivalent SKU, partial fulfilment or line cancellation), adjusts the Sales Order and Delivery Note consistently, and emits the corresponding channel message so the customer refund and the ERPNext accounting entry agree. Client scripts give store supervisors an in-form view of live cut-offs and open exceptions without leaving the Sales Order.

Settlement is where margin usually leaks. The app ingests platform payout and fee files into a Quick Commerce Settlement DocType, matches lines back to Sales Invoices, and posts commission, picking, advertising and penalty components to the accounts you nominate — leaving an explicit unmatched bucket rather than silently absorbing variance. Role profiles separate a store operator (who resolves shortages) from a channel manager (who edits cut-offs and fee mappings) from finance (who posts settlements), and every outbound call is logged with request, response and retry count so a disputed order has an audit trail. Everything is exposed through the Frappe REST API and whitelisted methods, so your BI layer or a second channel connector can read the same data.

This is a build-to-order product, not an instant download. After a short scoping call we confirm your platforms, dark-store topology, cut-off rules, substitution policy and fee structure, then quote a fixed scope. Typical delivery is one working week from confirmed scope, depending on how many channels and how unusual the settlement format is. We develop against your Frappe/ERPNext version (v15 or v16), deploy to a staging site for UAT with your own SKUs and a real sandbox channel where the platform offers one, and only then go live with a documented rollback. You receive the full source repository — the app is yours to keep, fork and extend.