I am kanak, buying head at Paras Gallery Fabrics in Central Market II, Lajpat Nagar, Delhi. We are a 29-year-old family fabric shop. Two of us handle 900+ SKUs across nine fabric categories, three karigar batches a month, and roughly 40 boutique-buyer accounts. This is our actual documentation workflow, not a case study. Take what is useful for your own shop.
Why we skipped every PIM we evaluated
PIM software assumes SKU-first thinking. Our SKUs change every 6-8 weeks. A yellow georgette at 60 GSM in September becomes a different SKU in November if the karigar batch is different, even if the fabric looks identical. Every PIM we tried (Akeneo, Plytix, Salsify, three Indian ones) wanted us to freeze SKU attributes upfront. Fabric does not work that way.
We also did not want to train a second person on a database interface. Our counter runs from 11 am to 8 pm and I cannot pull my hand from a boutique-buyer conversation to open a laptop.
The two-layer system
Layer 1: Ruled notebook on the counter. Half-page per fabric thaan when it arrives. Handwritten. Fields: thaan number, karigar batch ID, fabric type, GSM (measured on the shop scale), width, length in metres, ex-Krishna Nagar cost per metre, our sell-in band, colour swatch stapled to the top-right corner. Total cost of a notebook: ₹80. Total setup time: 3 minutes per thaan.
Layer 2: Airtable base, reconciled every Friday evening. I take photos of every notebook page from that week, upload the 6-inch swatch as a base image, and populate one row per thaan. Airtable takes about 45 minutes on Friday. The base is called "PGF_Stock_2026" and it currently holds 923 active rows.
There is a linked "Karigars" table with 6 partner batches (three Krishna Nagar, three Chandni Chowk). Each karigar row has average lead days, current WIP thaan count, and last payment cycle.
Weekly reconciliation, in three steps
Friday 6 pm, counter close. I take the notebook, my phone, and a cup of chai to the back room. Photo every new page from Monday to Friday.
Populate Airtable in one sitting. Attachments upload from phone directly to base. I fill Cost_Per_Metre and Sell_Band from the karigar's ex-workshop rate sheet, which I keep in a separate Google Sheet.
Trigger three automations. One sends a WhatsApp message to boutique buyers on our reorder list for anything with a Reorder_By_Date within 21 days. One emails the accountant a Friday delta report (new SKUs added, old SKUs sold out). One posts a summary count to our own Paras Gallery Fabrics blog via Airtable's Shopify integration, so the site knows what is fresh on the counter.
What we tracked before Airtable (2016-2022)
Only the notebook. No digital layer. Boutique-buyer reorder calls happened by memory or by flipping through 40 pages. We missed roughly 12-15% of reorder cycles a year, and karigars complained they were being called for stock we already had upstairs. Airtable killed that gap in the first quarter it was used.
What still lives outside Airtable
Boutique-buyer credit terms (Google Sheet, restricted access, only I edit).
Karigar payment cycles (separate Airtable base, "PGF_Karigar_Payments_2026", so employees can see what they need without seeing customer data).
Customer WhatsApp threads (native WhatsApp Business, no CRM).
The one Airtable formula we cannot live without
Reorder_By_Date = DATEADD(Received_Date, {Karigar_Batch_ID.Avg_Lead_Days} * 0.85, "days")
_
_
The 0.85 is our safety factor. We reorder 15% earlier than the karigar's stated lead time. It has held up across 18 months.
For anyone reading this from a fabric shop, tailoring unit, or boutique
Start with the notebook. Do not skip it. If you go directly to a digital tool, you will lose the fabric-by-hand knowledge that lets you write meaningful notes in Field 14. My father ran the counter for 20 years on the notebook alone. Airtable is the second lens, not the first.
For SMB-scale operations under 1,500 SKUs, PIM is over-engineered. Under 500 SKUs, Airtable alone is over-engineered — a well-kept notebook is enough.
One request
If you are running a similar retail operation with a physical inventory that resists SKU-first thinking (fabric, hand-loomed clothing, produce, jewellery components), reply below with what you use. I want to see if there is a common shape to the two-layer solution across sectors.
kanak, Paras Gallery Fabrics, Lajpat Nagar, Delhi.
