AICTE-Recognised Art Marketplace: Artwala Engineering Teardown

Independent Indian artists were selling through Instagram DMs and WhatsApp — manually negotiating prices, screenshotting UPI payments, coordinating delivery themselves. Artwala Foundation needed to give them a government-recognised storefront where the entire flow worked without artists touching a single line of code.

This is the engineering teardown of Artwala Foundation — why Razorpay Route was the linchpin, how we built non-technical-seller workflows, and what AICTE recognition demanded from the data architecture.

The Problem

Artists in this segment have three traits that broke every standard e-commerce solution:

• No technical skill. They can use Instagram and WhatsApp; they cannot configure Shopify themes or set up payment gateways.
• No logistics experience. They've never printed shipping labels, never dealt with a fulfilment provider, never thought about return policies.
• Need direct, fast payouts. Through Instagram DMs they got paid same-day via UPI. A marketplace that holds payments for 14 days would have crushed adoption.

Plus the foundation needed AICTE recognition, which required structured seller onboarding data, category taxonomy, transaction logs, and GST compliance metadata built from day one — not as a v2 retrofit.

The Architecture

A Next.js marketplace with Supabase data layer:

• Next.js + TypeScript frontend — Public catalog, artist storefronts, checkout
• Supabase Postgres — Artists, products, orders, taxonomy, audit log
• Supabase Auth — Artist + buyer authentication, with Magic Link as primary flow
• Cloudinary — Image upload pipeline with auto-optimisation
• Razorpay + Razorpay Route — Payment processing with split routing to artist accounts
• Shiprocket API — Logistics integration for label generation
• Vercel — Hosting

Key Technical Decisions

Razorpay Route for Direct Artist Payouts

Standard marketplace flow: customer pays → marketplace holds money → marketplace pays artist after N days. This kills cash flow for the seller side and creates a foundation-as-intermediary structure that doesn't fit Artwala's mission.

Razorpay Route changes the flow. The buyer's payment is split at the gateway level: artist's share goes directly to their bank account; foundation's commission goes to the foundation's account. Within 2 business days, minus the fee.

This required:

• Per-artist Razorpay sub-account creation as part of onboarding (handled via Razorpay's API)
• KYC + bank account verification flow built into the onboarding wizard (artists upload docs, we POST to Razorpay)
• Order webhook handling with reconciliation (each order generates a payment_split record)
• Fallback handling for artists whose KYC hasn't completed (orders held; artist gets a notification)

The result: the foundation never touches the artist's money. Audit, compliance, tax — all simpler.

Cloudinary Auto-Optimisation Pipeline

Artists upload high-resolution photographs of physical artworks (some 20MP+). Naïve upload-and-display wastes bandwidth, kills load times, and looks bad on small screens.

Every image goes through a Cloudinary transform pipeline on upload:

1. Auto-crop to aspect-ratio variants (square thumbnail, 4:3 catalog, original)
2. Watermark with the foundation's mark
3. Generate WebP + JPEG fallbacks
4. Apply auto-quality and auto-format based on viewer device
5. Cache at the edge

Artists upload a single high-res file. The site serves the optimal version for every viewer's device, automatically. Image-related performance issues — typically the #1 perf problem for image-heavy sites — disappeared.

Shiprocket Integration That a Non-Logistics Artist Can Use

The hardest UX problem. Shiprocket has a great API but its native portal is dense; artists couldn't use it.

We built a thin abstraction layer:

• On order confirmation, our backend calls Shiprocket's API to generate a prepaid dispatch label
• The label PDF is emailed to the artist with a one-line instruction: "Print this label, attach to package, hand to courier"
• The Shiprocket courier pickup is automatically scheduled
• Tracking number flows back to the buyer via order-status emails

Artists never log into Shiprocket. They just print the email-attached label. We handled all the API complexity behind the scenes.

For broader perspective on building software for non-technical operators, see Custom Software vs Off-the-Shelf — Artwala is a textbook case for custom over generic e-commerce.

AICTE Recognition: Architecture from Day One

AICTE recognition required:

• Structured seller onboarding capturing legal entity, GSTIN, category taxonomy
• Audit-grade transaction logs (all order events with timestamps + actor)
• Category taxonomy mapping AICTE's classification standards
• Annual reporting capability across all sellers

Most marketplaces add compliance metadata as a retrofit when regulators ask for it. We built the data model assuming compliance scrutiny from week one. order_events is an immutable audit table; seller_onboarding captures every required field with timestamps; category_taxonomy maps to AICTE's classification system natively.

The AICTE application succeeded the first time, with no architectural rework. The cost was ~5% extra build effort upfront vs ~30%+ rework if we'd added it later.

Why This Matters for E-Commerce Builders

Artwala demonstrates that vertical e-commerce for niche segments is its own design discipline. Generic Shopify-style storefronts assume:

• Sellers can manage their own listings
• Sellers can set up their own payments
• Sellers can handle their own logistics
• Sellers know their own SEO

For art, regional crafts, agriculture, or any other niche where sellers are non-technical individuals, every one of those assumptions fails. The build is twice as hard but the user-facing simplicity is what makes the marketplace work.

For the broader business framing on when custom builds beat off-the-shelf, see Custom Software vs Off-the-Shelf. For MVP-stage cost considerations, MVP Development Cost in India 2026.

What We'd Do Differently

• Add bulk-upload via spreadsheet from day one. Artists with large catalogs wanted CSV import; we shipped this as v2.
• Build the buyer order-tracking page with shipment milestones earlier. We initially relied on emails; richer in-app tracking was a clear enhancement.
• Use Cloudflare R2 + Bunny.net for image hosting if cost optimisation becomes a priority. Cloudinary is excellent but has the highest unit cost.

Where Nexolve Fits

We build vertical e-commerce and marketplace platforms via our SaaS & Web Apps service. For the full project context, see the Artwala Foundation case study.