Case study · Threads of Jaipur
One catalog, two currencies.
Threads of Jaipur will sell hand block-printed bed linen to India in rupees and to the world in dollars. The storefront detects the buyer's region and serves the right catalog and the right price list. Payments and launch are next.
2
Currencies
23
API routers
31
Pages
37
Components
Station 01 · The market
Jaipur to the world.
Hand block-printed bedsheets, dohars and pillow covers, sold to Indian homes in rupees and to buyers abroad in dollars. Same catalog, two very different price realities, and some products that should never show abroad at all.
Station 02 · The system
The region decides, the admin controls.
The storefront detects the visitor's country and lets them override it. Prices are not converted by exchange rate: the admin sets the rupee list and the dollar list separately, and the server prices, sorts and filters in the right currency.
Station 03 · The honesty
Built first, launched when ready.
Catalog, variants, dual pricing, admin and order flow are built and running locally. Payments are the next phase, and launch waits on accounts and hosting. We would rather show you a true status than a hurried one.
Station 04 · Launching soon
The loom is threaded.
The engineering that makes a global storefront honest is done: region detection, dual price lists, India-only partitioning, order stamping. When the client is ready, the rest is switches.
System map · verified
The architecture, on paper.
Shoppers
React SPA
region detect · override
Core
FastAPI storefront
region-aware pricing
Celery worker
email + images
Data
PostgreSQL
dual price lists
Redis
queue
Outside
ImageKit CDN
product media
Arrived. Now let's chart yours.
Every client gets a new flight path. Bring us the destination and we will engineer the route.