Magento Developer, Ahmedabad

Yes, I’m physically based in Ahmedabad, Gujarat, and have been since 2017. This is the only city page on the site where I can credibly offer same-day in-person meetings, every other city page (Mumbai / Bangalore / Pune / Delhi / Surat / Dubai / London / NYC / SF / etc.) is remote-first with optional travel. In Ahmedabad I’m available for coffee at SG Highway (Iscon Cross Roads / Vastrapur Lake), lunch at Prahlad Nagar or Bodakdev, war-room days at GIFT City SEZ (30 km in Gandhinagar, great for fintech / RBI-regulated merchants), or a kickoff session near the IIM-A / Vastrapur area. Reply to any quote with your preferred zone and I’ll suggest a venue.

Three published tiers, all GST-inclusive on the invoice (18% GST is added to the listed prices below). Audit (₹39,000 / ~$499) covers a 3-5 day pre-purchase scope: payment-gateway health, GST/eWaybill posture, DPDP readiness, Hyvä migration scope, Lighthouse audit on Jio 4G. Standard (₹2,00,000+ / ~$2,499+ USD) covers a 6-10 week Hyvä migration + full Razorpay + UPI + DPDP + GST wiring, this is the most-booked tier for ₹5L, 1Cr GMV stores. Enterprise (₹15,00,000+ / from $18k USD) covers 3-6 month builds for 50k+ SKU B2B catalogues (Maskati textile / Zydus pharma style), Adobe Commerce migration to AWS Mumbai, multi-warehouse routing across Gujarat + Maharashtra. Pay by UPI / NEFT / IMPS / Razorpay Card for Indian clients; Stripe / Wise / PayPal for international.

Yes, this is table-stakes for any Indian Magento merchant and we wire it on every build. GST: CGST/SGST/IGST split per shipping address (intra-state = CGST + SGST, inter-state = IGST), reverse-charge mechanism for unregistered suppliers, composition-scheme override for < ₹1.5 Cr turnover merchants. eWaybill: Gujarat eWaybill auto-generation for shipments > ₹50,000 (mandatory under Gujarat eWaybill notification 2018+), we integrate with the GSTN API directly or via a connector like ClearTax / TallyPrime. HSN: 6-digit HSN code mandatory above ₹5 Cr turnover (8-digit for exports), we wire the catalog product attribute and ensure it ships on every invoice and eWaybill. GSTR-1 / GSTR-3B export-ready reports are part of the Standard tier. We can also wire reverse-charge for B2B platform sales (OIDAR rules).

Both are mandatory and both are wired into every Standard-tier build. DPDP (Digital Personal Data Protection Act 2023), India’s GDPR-equivalent, came into effect 2023, full enforcement expected 2026-27. We implement: explicit consent capture (no pre-ticked boxes), purpose-limitation per data field, data-principal rights (access / correction / erasure / nomination), 72-hour breach notification to the Data Protection Board, and a DPO contact surface in the privacy policy. Consent + DSAR automation is configured per store-view, not site-wide. RBI Card Tokenisation (CoFT) 2022+, merchants and payment aggregators can NOT store raw card PANs anymore. Only network-issued tokens (via Visa / Mastercard / Rupay / Amex token vaults) are allowed. We wire your Razorpay / CCAvenue / PayU vault correctly so your Magento DB never sees a card number. RBI cross-border data residency (proposed) we keep an eye on, for now, payment data must be stored in India only.

Yes, we’ve integrated all of them, often as a single multi-rail checkout. UPI is now 35-60% of Indian online transactions (NPCI data, 2024-25) so it’s checkout-rail-#1 for almost every Indian Magento merchant. We wire UPI Intent (auto-opens PhonePe/GPay/Paytm app), Collect (push payment request to a saved VPA), and Dynamic-QR (for high-ticket / Hyvä minicart). Razorpay is the dominant aggregator, we’ve shipped the official Razorpay-Magento module on 100+ stores, plus the Razorpay-Hyvä bridge for Hyvä storefronts. PhonePe Business is excellent for Gujarat / Mumbai / Bangalore merchants, lower fees than Razorpay on UPI rails, slightly higher on cards. Paytm Payments we wire for Tier-2 / Tier-3 customer demos. For B2B subscriptions, we add UPI Autopay (eMandate), recurring payments under ₹15,000/month without re-authorisation.

Yes, we’ve shipped Magento B2B for several Gujarat textile and diamond merchants. A representative anonymised case: a 50,000-SKU B2B textile catalogue for a Maskati-Mahajan member-mill (women’s ethnicwear + dress-material), launched on a Hyvä storefront in 8 weeks, with Razorpay + PhonePe + UPI Intent, GSTIN-verified B2B buyer onboarding, distributor-tier price lists (Premium / Wholesale / Retail), and Gujarat eWaybill auto-generation for shipments > ₹50k. 3× checkout conversion uplift at Diwali season vs the previous Shopify build. For Surat diamond wholesale we’ve wired GIA-cert-attached PDP, HSN 7102 + 7103 product tax codes, eWaybill for inter-state Surat→Mumbai movement, and KYC-gated B2B login (only verified GSTIN + Aadhaar/PAN can see prices). Real client names are NDA’d, happy to share case-study decks under signed MNDA on a discovery call.

Ahmedabad is India’s pharma capital, Zydus Lifesciences, Cadila Healthcare, Torrent Pharma, Intas Pharmaceuticals, Sun Pharma’s major plants, so we get pharma B2B asks frequently. Magento builds for pharma distributors need: (1) Drug-Licence-verified buyer onboarding (Form 20B / 21B retail licence, Form 20F / 21F wholesale licence checked at signup), (2) Schedule H / H1 / X drugs gated behind verified pharmacist Aadhaar, (3) batch + expiry tracking per SKU + FEFO (first-expiry-first-out) inventory allocation, (4) GSTIN-validated B2B price lists per distributor tier, (5) eWaybill auto-gen for shipments above ₹50k (mandatory in Gujarat / Maharashtra / Karnataka), (6) CDSCO-compliant cold-chain shipping rules for biologics. We build all of this on Magento Open Source + custom modules, no need for Adobe Commerce licence unless you’re > ₹50 Cr GMV.

Yes, we run these in pure IST (no overlap-stress), with full in-person kickoff at SG Highway / Prahlad Nagar / Bodakdev or remote on Google Meet. Typical timelines: Shopify Plus → Magento takes 6-10 weeks (we use Magento’s Data Migration Tool for products / orders / customers; custom scripts for Shopify metafields, sections, and app-specific data like Bold / Recharge subscriptions). WooCommerce → Magento takes 4-8 weeks (cleaner because both are PHP/MySQL, we map wp_posts → catalog_product_entity directly). Hosting: AWS Mumbai region (ap-south-1) is the default for Indian stores, ~25ms from Ahmedabad. Alternatives: Hyvä Cloud (managed), Cloudways Mumbai, ESDS Nashik (1-hr latency to AHM but cheaper). URL preservation (301 redirects) is critical, we map every old URL to the new one to keep Google ranking equity.

Yes, Hyvä is our default frontend recommendation for any Indian Magento merchant, and we’re an active part of the Hyvä community. Why Hyvä matters specifically for India: (1) sub-1.5s LCP achievable on a Reliance Jio 4G connection from Tier-2 / Tier-3 cities (where most of your customers are), the default Luma theme struggles to hit 4s LCP on the same network, (2) Razorpay + PhonePe + UPI Intent / Collect work natively in Hyvä Checkout, (3) mobile-first design matches Indian buyer behaviour (90%+ mobile traffic on most stores we’ve shipped). We’re also Adobe-Certified on stock Luma, so if you’re on Luma we can either optimise it heavily (~3.0s LCP achievable) or migrate to Hyvä in 6-10 weeks. Hyvä commercial licence (~€1,000 one-time) is a Standard-tier inclusion.

Yes, this is the differentiator of working with an Ahmedabad-based developer rather than a remote-only one. GIFT City SEZ (30 km north in Gandhinagar) is ideal for fintech-regulated merchants, if your store sits under IFSCA rules (cross-border B2B, neo-banks, payment aggregators with SEZ status), we can meet on-site at one of the GIFT City fintech towers. IIM-Ahmedabad / Vastrapur area is a great venue for design-led kickoffs, quiet co-working at WeWork Prahlad Nagar, casual at Kanha Cafe near IIM-A, or formal at the Hyatt Regency Vastrapur. SG Highway / Prahlad Nagar / Bodakdev covers most tech/SaaS merchants, we have go-to spots at each. Day-long war-room sessions (full team, whiteboard, deep architecture work) are usually at a co-working day-pass venue, we book it on your behalf.

Honest answer: for ~95% of Indian merchants, Magento Open Source + Hyvä + a small extension stack is the right call, not Adobe Commerce. Adobe Commerce licence in India is > ₹15 Lakh/year (Pro tier, after the Indian-market discount), which only makes sense if you’re > ₹50 Cr GMV with complex B2B requirements (shared catalogs across companies, requisition lists, parent/child corporate accounts, built-in quote workflow, Adobe Sensei AI features). For Indian DTC stores under ₹25 Cr GMV, Magento Open Source + Hyvä + Mageplaza / Amasty / Mirasvit extensions costs around ₹25,000-50,000/year in licences, you get the same Magento 2 core, and the savings cover a developer’s annual retainer. Adobe Commerce makes sense for: Reliance Retail / Tata CLiQ-scale players, B2B pharma / chemical distributors with 50+ sub-tier accounts, or merchants who must pay for the SLA. We’ll write a candid recommendation in the audit, usually against Adobe Commerce.

This is the make-or-break moment for any Indian merchant. The pattern: traffic 5-15× baseline from Navaratri start (typically Sep-Oct) through Diwali (Oct-Nov), with a second peak at EOSS (End-of-Season Sale, Jan-Feb for fashion / textile / Surat-saree segments). Our 8-week pre-Diwali playbook: (W-8) load-test on AWS Mumbai with k6 / Apache JMeter at 10× baseline RPS, identify DB / Redis / OpenSearch bottlenecks; (W-6) upgrade EC2 instance class + add ElastiCache Redis cluster + enable Varnish; (W-4) Hyvä LCP audit on Jio 4G, image lazy-load, critical-CSS inline, defer GTM; (W-2) Razorpay / PhonePe / Paytm sandbox load-test, ensure UPI fallback to card on aggregator timeout; (W-1) war-room days at GIFT City / on-site at your office for cutover rehearsal; (Launch night) on-call till 2 AM IST, post-launch coverage for 14 days including all Diwali festival days. Diwali is non-negotiable, we plan for it 8 weeks out, not 2.