Picture the message. Your salesman sends the new book to a retailer in Kolkata at 11 in the morning. The file is 41 MB. At 11:26 the reply comes: "not opening bhai", and then "phone hang ho raha hai". And that is the good version, because most of the time there is no reply at all. He just does not order.
If you sell sarees or fabric from Surat, you have sent that file. I have watched it happen at a counter on the textile market side, and it is the reason Fabrary Book exists. This is what we learned fixing it.
Why the file is so big
Your catalogue is designed for a press. The printer needs 300 dpi images, embedded fonts, colour profiles, and bleed. All of that is correct for paper and useless on a 6-inch screen. The PDF you get back is 30 to 40 MB, and on a retailer's phone it does three bad things.
- It stalls on his data pack. A 40 MB download on a shared plan in a market with weak signal takes minutes, if it finishes.
- It hangs his phone. Older Android phones open big PDFs in memory. Twenty catalogues later, the phone is full and everything is slow.
- He never tells you. Nobody types "your file is too big". They move on to the next supplier whose book opened.
What Navdurgaa Saree did
Navdurgaa Saree is a saree wholesaler in Surat. Their salesmen carried a bag of printed books on the floor and forwarded PDFs on the road. We built Fabrary Book at their counter, on the catalogues they actually print, and the shop runs on it today.
Three changes did the work.
Every book compressed once, on the way in. The print PDF is coded for the screen when it lands on the shelf. Measured on 39 real catalogues, the files came down 22 to 36 times. A book that was 40 MB is now around 500 KB, and it opens on the first tap.
The rate rides in the file name. A book called by its name and its rate, for example the piece count and ₹875, means the retailer can quote his own customer without calling your man back. And for a party who should not see the rate, it is sent without.
One shelf, not one bag of books per salesman. Every catalogue ever printed sits on one wall, with its cover, code, fabric, pieces and colour chart. Every man on the floor and on the road sees the same wall. He searches by name, fabric or rate band, picks the books for one party, and sends them together on WhatsApp. The app logs who was sent what, and when.
What changes at the counter
The first thing you notice is that the colour question dies. The colour chart sits under the cover on the thumbnail, so the salesman answers "which colours?" before anyone downloads anything.
The second is that the retailer stops waiting. He gets his own link. Your newest books appear on it whenever he opens it, he picks what he wants, sends the selection back, and reorders without your salesman needing to reach his shop.
The third is quieter. A new salesman who joined last month can talk about a book he has never opened, because the keywords are read off the pages. That used to take a season to learn.
If you want to fix it yourself first
You do not need us to get the first win. Here is the order.
- Compress the ten books that sell most, using any PDF tool, to under 1 MB each. Send those instead of the print files for one week and watch the reply rate.
- Rename each file with the book's name and rate. Stop sending "SHUBHAM VOL-1104.pdf".
- Keep one folder that every salesman sends from, so the retailer gets the same file whoever he talks to.
- When that folder has two hundred books and three people updating it, that is the day it becomes an app problem. Message me and I will show you the Navdurgaa shelf on your own phone.
There is a working slice of the app on the Fabrary Book page. Open the wall, read a book, pick it for one party and send it to your own number. No sign-up, nothing to install.