Why the ERPNext Success Package Was Important in This Project
Quest Retail operated in a high-speed retail and warehouse environment where even small ERP failures had an immediate impact on order fulfillment, stock accuracy, and customer experience. Their ERPNext system had become unreliable due to misconfigurations, faulty custom code, and unstable integrations.
The Success Package became critical to:
- Provide dedicated engineering ownership over the system
- Conduct deep audits and fix long-standing technical debt
- Stabilize core retail workflows used across warehouses, stores, and logistics
- Rebuild broken logic to ensure predictable future operations
- Enable smooth coordination between inventory, sales, finance, and integration teams
This engagement transformed an error-prone ERP into a stable, predictable, and scalable retail platform.
Client Overview
Quest Retail is one of India’s fastest-growing beauty and personal care retail chains, offering a curated collection of global and homegrown brands. Also have an international presence. With 250+ stores, large-format warehouses, 4Mn+ loyalty members, and the best multi-brand partners in the market for two decades. With the rapidly expanding omnichannel footprint, Quest serves thousands of daily customers through seamless online and offline experiences.
Their operations span procurement, warehousing, supply chain, in-store sales, digital commerce, and customer fulfillment, making ERP reliability essential to their business continuity and retail excellence.
- Industry: Retail
- ERP Stage Before Engagement: Implemented, but unstable and inconsistent
Modules in Scope:
- Buying
- Selling
- Stock & Warehouse Management
- Integration with FLIGHT ERP
Challenges
Quest Retail faced major P1-level breakdowns that disrupted daily business operations:
Functional & Operational Challenges
- Missing invoices in the stock ledger
- Stock quantities are dropping to zero unexpectedly
- Serial & batch mismanagement across warehouses
- Incorrect valuation rates in invoices and credit notes
- Intermittent invoice PDF failures
- Internal customer invoices have not been generated
- Stock transfers and pick lists are not created consistently
Technical & Code-Level Challenges
- Invoice naming series jumping unexpectedly
- AWB auto-generation is producing duplicates
- Incorrect and inconsistent batch picking logic
- Wrongly implemented stock reservation conditions
- Custom code built outside ERPNext standards
- No cleanup job for large API logs, causing DB bloat
These issues collectively impacted order fulfillment, stock accuracy, financial correctness, and customer experience.
Solution
A multi-layered Success Package approach was implemented to stabilize the system:
1. Comprehensive System & Code Audit
- Deep review of configurations, workflows, and custom scripts
- Identified incorrect business logic and non-standard ERPNext implementations
- Prepared a structured roadmap for fixes and system hardening
2. Rebuild of Core Logic
- Rewrote the invoice series generator
- Rebuilt AWB auto-generation with validations
- Standardized naming series and batch picking logic
- Corrected stock reservation logic end-to-end
3. Stabilizing Warehouse & Stock Operations
- Repaired serial and batch workflows
- Corrected stock transfer and pick list generation
- Cleaned stock ledger inconsistencies
- Validated stock movement and reservation rules
4. Restoring Selling & Billing Processes
- Repaired pricing inconsistencies in GRN and stock transfers
- Stabilized invoices, credit notes, and posting logic
- Resolved intermittent PDF issues
5. Infrastructure & Data Health Improvements
- Implemented scheduled cleanup for bulky API logs
- Improved database performance and long-term system reliability
Impact
- System stability restored across sales and the warehouse
- Elimination of P1 issues impacting billing, stock accuracy, and order fulfilment
- Predictable, scalable retail workflows across multi-location warehouses
- Higher team confidence due to consistent behaviour and reliable integrations
- Stronger ERP foundation ready for future expansion and automation
Key Finding
- Most critical failures originated from incorrect custom code, not ERPNext limitations.
- Retail operations are highly sensitive; even minor logic issues can break end-to-end workflows.
- Rebuilding core processes (invoice series, AWB, stock reservation) created long-term stability.
- Proper integration governance is essential when connecting to systems like FLIGHT
Key Learnings Going Forward For Team
- Conduct code quality audits before go-live or vendor handover.
- Avoid custom code that contradicts ERPNext core principles.
- Maintain SOPs for naming series, batch management, and stock reservations.
- Enforce structured UAT cycles and API-contract testing for all integrations.
Want a stable, scalable ERPNext setup like Quest Retail? Talk to us today!!!
