SQL vs NoSQL for building a custom multi-tenant ERP for retail chain (new build inspired by Zoho, current on MS SQL Server, debating pivot)
Interview Experience
Hey folks, We're planning a ground-up custom multi-tenant ERP build (Flutter frontend, inspired by Zoho's UX and modular patterns) to replace our current setup for a retail chain in India. Existing op
Full Details
Hey folks, We're planning a ground-up custom multi-tenant ERP build (Flutter frontend, inspired by Zoho's UX and modular patterns) to replace our current setup for a retail chain in India. Existing ops: 340+ franchise outlets (FOFO) + 10+ company-owned (COCO), scaling hard to 140+ COCO, exploding userbase, and branching into new verticals beyond pharmacy (clinics, diagnostics, wellness, etc.). The must-haves that keep us up at night: • Ironclad inventory control (zero tolerance for ghost stock, unbilled inwards, POS-inventory mismatches) • Head-office led procurement (auto-POs, MOQ logic, supplier consolidation) • Centralized product master (HO-locked SKUs, batches, expiries, formulations) • Locked-in daily reconciliations (shift handover, store closing) • Bulletproof multi-tenancy isolation (FOFO/COCO hybrid + investor read-only views) • Deep relational data chains (items → batches → suppliers → purchases → stock → billing) Current system: On MS SQL Server, holding steady for now, but with this rebuild, we're debating sticking relational or flipping to NoSQL (MongoDB, Firestore, etc.) for smoother horizontal scaling and real-time features as we push past 500 outlets. Quick scan of Indian retail/pharma ERPs (Marg, Logic, Gofrugal, etc.) shows they mostly double down on relational DBs (SQL Server or Postgres)—makes sense for the transactional grind. What we've mulled over: **MS SQL Server:** ACID transactions for zero-fail POs/reconciliations, killer joins/aggregates for analytics (ABC analysis, supplier performance, profitability), row-level security for tenancy, enterprise-grade reliability. **NoSQL:** Horizontal scaling on tap, real-time sync (live stock views), schema flex for new verticals—but denormalization headaches, consistency risks in high-stakes ops, and potential cloud bill shocks. No BS: For this workload and growth trajectory, does staying relational (maybe evolving MS SQL) make more sense, or is NoSQL the unlock we're overlooking? Who's built/scaled a similar multi-outlet retail ERP in India from the ground up? What DB powers yours, and why? Any war stories on Zoho-inspired builds or relational-to-NoSQL pivots? Appreciate the raw insights—let's cut through the hype. **TL;DR:** Ground-up ERP rebuild for 500+ outlet retail chain in India—stick with MS SQL Server for ACID/relational power, or pivot to NoSQL for scale/real-time? Need brutal takes on pros/cons for transactional inventory/procurement workflows.
About This Question
This is a candidate experience report from a zoho interview for a frontend role reported in 2025.
It covers the following topics: Sql .
Difficulty rating: Hard
Topics
More Zoho Interview Questions
About Zoho Interview Reports
This question was reported by a candidate who interviewed at Zoho. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Zoho are the higher-signal extractions to take from this report.
For broader preparation context, the Zoho interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Zoho reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Zoho Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Zoho reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.