F&BosWeight-based billing software connects your digital weighing scale directly to your billing screen. When the counter staff places kaju katli on the scale, the weight appears instantly on the bill — no manual entry, no calculation, no rounding error. The software multiplies the weight by the per-kg rate, adds GST at the correct rate, and prints the receipt.
Who needs it?: Any sweet shop that sells mithai by weight. If you sell kaju katli, laddoo, barfi, or namkeen in loose form — weighed on a scale and priced per kg — you need this. The more products you carry, the more counters you run, and the busier your Diwali peak, the more value this software delivers.
What's covered here?: How the scale-to-bill integration works technically, the seven features that matter for a mithai shop, how gift box billing works at Diwali, GST rates and HSN codes for sweets post-September 2025, how expiry tracking reduces wastage, and a practical buyer's checklist with questions to ask before signing up with any vendor.
The problem this solves
Walk into most traditional sweet shops in India during any afternoon and you will see the same workflow: a customer asks for 500 grams of kaju katli, the counter staff puts it on the scale, reads the weight aloud, and then either keys the number into a separate billing computer, tells the cashier, or writes it on a paper token. Somewhere in that chain — especially when the shop has five customers at the counter and the counter staff is also answering questions and managing the display tray — mistakes happen. Weight gets entered as 0.5 instead of 0.56 kg. The cashier mishears 350 grams as 530 grams. A product gets charged at the wrong rate because the staff remembered the wrong per-kg price.
These are not failures of attention or honesty — they are failures of process. The weighing and the billing happen on two separate systems with a human relay in between, and human relays introduce errors, especially at volume and especially during peak festival trading. Weight-based billing software eliminates the relay. The scale and the billing screen become one system.[1]
Common manual billing errors in sweet shops: wrong weight entry (most frequent), wrong product selected in billing system, wrong rate applied (old price not updated), GST not applied or applied at wrong rate, gift box item count mismatch.
During Diwali peak trading, a medium-format sweet shop may process 400–600 transactions per day vs. a normal-day volume of 120–180. At that throughput, manual data relay between scale and billing becomes the primary source of both errors and counter slowdown.
Billing software for sweet shops: key players in India include VasyERP (₹12,999/year), Gofrugal, BillBerry, Ritaya POS, Prana POS, and Tuple POS — all offering varying levels of scale integration capability.
How Weight-Based Billing Actually Works
From scale to receipt — the technical path explained simply
You do not need to be technical to evaluate a weight billing system, but understanding how the integration works will help you ask the right questions before you commit to a vendor. There are two methods in current use among Indian sweet shop billing systems.
1.1 — Method A: Direct Scale Integration (the right way)
In direct integration, the digital weighing scale is connected to the billing computer via a cable (RS-232 serial or USB) or wirelessly (Bluetooth). The billing software listens to the weight signal continuously. When the counter staff places an item on the scale and its weight stabilises, the number appears automatically in the quantity field on the billing screen — already converted to kilograms to the nearest gram. The staff selects the product from the screen, the software multiplies weight by per-kg rate, adds GST, and the bill is ready. The only human inputs are placing the product on the scale and selecting the correct product name from the billing screen.[2]
Example: 0.56 kg × 1,200/kg × 1.05 = 705.60₹₹
Direct integration is the gold standard and what every serious mithai shop should insist on. It eliminates the entire manual relay between scale and billing. The counter staff does not type anything — weight flows electronically.
1.2 — Method B: Label-Print and Scan (the workaround)
In the label method, the weighing scale has a built-in label printer. When an item is weighed, the scale prints a barcode sticker with product name, weight, price, and date. The customer carries this sticker to the billing counter, where the cashier scans the barcode and the transaction is imported into the billing system. This is more reliable than fully manual entry but introduces a second step (the label-print and scan) and requires a more expensive scale with an integrated label printer. It is commonly used in supermarkets and large format stores. For a sweet shop counter where the same person is weighing and billing, direct integration is simpler and faster.[3]
Always ask your software vendor which method they support — direct integration or label scan — before purchasing. Some vendors advertise 'weighing scale integration' when they only support the label-scan method. For a sweet shop, direct integration (weight auto-populates in the billing screen) is strongly preferred.
Common compatible scales in India: Essae series (EC-4150, EC-4200), CAS series (SW-1C, DB-II), and Mettler Toledo models. All support RS-232 connection. Confirm your scale model is on your vendor's compatibility list before setup.
1.3 — What Happens on the Billing Screen
When the weight appears in the billing screen, here is what the operator sees in a well-designed system: a product search or quick-select list (operators typically tap the product name or scan a product QR code to select it), a weight field that is already populated from the scale, a calculated price showing weight × rate, GST breakdown (5% for most sweets), and a total. If the customer wants multiple items — say, 250g kaju katli and 300g motichoor laddoo — each item is added as a line on the same bill. The operator places the kaju katli on the scale, selects the product, weight auto-populates and the line is added to the bill. They then place the motichoor laddoo, select it, and the second line is added. The bill total updates after each line.
The Seven Features That Matter for a Mithai Shop
Not all sweet shop billing software is built the same — here is what to look for
There are dozens of billing software systems marketed to Indian retail businesses, and many of them will tell you they support sweet shops. But generic retail billing software is built for selling fixed-price packaged goods — it handles each unit as a fixed item at a fixed price. A mithai shop's requirements are different: variable weights, per-kg pricing, multiple products on a single bill, perishable inventory with expiry dates, gift box assembly, festival pricing, and specific GST treatment. The following seven features separate systems built for mithai shops from generic retail software that has been loosely adapted for them.
| # | Feature | What It Must Do | What to Check |
|---|---|---|---|
| 1 | Direct Scale Integration | Weight auto-populates in bill from connected digital scale. No manual entry. Supports RS-232/USB/Bluetooth connection to common Indian scale brands. | Ask: 'Which scale models are on your compatibility list?' Demo must show weight flowing from scale to billing screen live. |
| 2 | Per-gram / Per-kg Rate Setup | Each product must have its own rate per kg stored in the system. When the product is selected, the correct rate applies automatically. Rate changes update instantly across all counters. | Ask: 'How do I update the kaju katli price when cashew prices rise? How long does it take to reflect on all counters?' Should be instant, not a system restart. |
| 3 | Gift Box Builder | Ability to create a bill with multiple mithai items at different weights in a single gift box. System calculates total weight, total value, and adds configurable packaging charge. Box sizes (250g, 500g, 1kg, 2kg) stored as presets. | Ask: 'Can I create a 500g Diwali assorted box with 6 items at different weights on one bill?' Demo with 3–4 items to verify it works. |
| 4 | GST Auto-Calculation | Applies 5% GST on standard Indian sweets (HSN 2106 90) automatically. Different rates for namkeen, beverages, or packaged products must be configurable per product. GST invoice format must be legally compliant. | Check the GST invoice format matches the requirements under GST rules — GSTIN of buyer (if registered), HSN code, taxable value, CGST/SGST split. Ask if system was updated for Sep 2025 GST slab changes. |
| 5 | Batch Production Tracking | Records daily production quantity (how many kg of each item was made). Tracks sales against production to show remaining stock in real time. Generates wastage report (production minus sales minus adjustments). | Ask: 'At the end of the day, can I see how much kaju katli I made, sold, wasted, and have remaining?' Should be a single view, not three separate reports that need manual reconciliation. |
| 6 | Expiry / Shelf-Life Alerts | Each batch logged with production date. System flags batches approaching expiry based on configured shelf life per product (gulab jamun: 2 days; kaju katli: 5–7 days; namkeen: 30+ days). Alert before expiry, not after. | Ask: 'If kaju katli has a 6-day shelf life and I make a batch on Day 1, does the system alert me on Day 5 that the batch is expiring tomorrow?' Test this in demo. |
| 7 | Festival Pricing Switch | Allows setting alternate (festival season) prices for any product, activatable with a single toggle. When festival mode is on, all counters use festival prices. When it's off, standard prices resume. No manual re-keying of 40 product prices. | Ask: 'Can I pre-set Diwali prices and turn them on with a single click 3 days before Diwali, then turn them off afterwards?' Check if it logs when the price switch was made and by whom. |
Gift Box Billing — the Diwali Use Case
How weight billing software handles India's most complex retail scenario
Nothing tests a sweet shop's billing system more thoroughly than Diwali gift box assembly. A customer walks in and asks for an assorted gift box with six different mithai. They want kaju katli, motichoor laddoo, besan laddoo, kaju roll, rose barfi, and soan papdi — roughly 80 grams of each in a 500g box with printed ribbon. Each item is weighed separately. Each has a different per-kg rate. The box itself has a packaging charge. The customer may want GST invoice for a corporate order.[4]
Without a gift box billing module, this transaction requires the counter staff to weigh each item, record each weight on paper, then manually calculate the total, add the packaging charge, and key everything into the billing system. At a counter doing 600 transactions a day, this takes time the shop does not have. If the total is ₹600 but the customer disputes the calculation, there is no clean audit trail.
3.1 — How Gift Box Billing Works in a Proper System
- 1. Counter staff opens 'Gift Box' mode on the billing screen and selects box size (500g assorted).
- 2. They select Item 1: 'Kaju Katli'. Place it on the scale. Weight auto-populates: 83g. Line 1 added: 83g × ₹1,200/kg = ₹99.60.
- 3. Select Item 2: 'Motichoor Laddoo'. Weight: 78g. Line 2 added: 78g × ₹600/kg = ₹46.80.
- 4. Repeat for remaining 4 items. Running total visible on screen as each item is added.
- 5. System adds packaging charge (configurable — e.g., ₹35 for 500g gift box with ribbon).
- 6. GST at 5% applied on taxable value. Total displayed. Bill printed. Counter time: 90–120 seconds.
Worked Diwali gift box example — 500g assorted (6 items):
Kaju Katli 83g @ ₹1,200/kg = ₹99.60
Motichoor Laddoo 78g @ ₹600/kg = ₹46.80
Besan Laddoo 85g @ ₹480/kg = ₹40.80
Kaju Roll 80g @ ₹1,100/kg = ₹88.00
Rose Barfi 82g @ ₹650/kg = ₹53.30
Soan Papdi 88g @ ₹400/kg = ₹35.20
Subtotal: ₹363.70 | Packaging: ₹35.00 | GST 5%: ₹18.18 | TOTAL: ₹416.88
Manual calculation time: 4–6 minutes. Software time: 90 seconds. Difference at 100 gift boxes/day: ~6.5 hours saved.
3.2 — Corporate Orders and Advance Booking
A feature that higher-end sweet shop billing systems support is advance order management — a customer (often a corporate buyer) places an order for 200 gift boxes ahead of Diwali, specifying the box composition, delivery date, and billing details. The system books the order, generates a pro forma invoice, reserves the required ingredient quantities from current inventory projections, and flags production requirements. On fulfilment day, each box is assembled at the counter using the same weight billing flow, and the final invoice is generated against the advance order record.
F&Bos bills loose sweets by weight, priced per gram or kilo, with boxed items at unit prices on the same bill, GST-compliant invoices and cash, UPI and card payments. The weight is entered at the counter; direct weighing-scale hardware integration is not part of F&Bos today. Batch production costing and festival-season planning views help with the Diwali peak. See F&Bos for sweet shops.
GST Compliance for Sweet Shops
What changed in September 2025 and what your billing system must handle
GST on Indian sweets is simpler than many shop owners fear, but it has to be right on every bill. A billing system that applies the wrong rate or skips GST on a category creates a compliance liability that accumulates silently until an audit or notice. Understanding the current rates and how they must appear on a valid GST invoice is essential before choosing a billing system.[5]
4.1 — GST Rates Post-September 2025
The 56th GST Council meeting (effective 22 September 2025) eliminated the 12% GST slab, moving affected categories into either 5% or 18%. For a sweet shop, the key result is straightforward: the vast majority of traditional Indian sweets continue to attract 5% GST. The old scenario where some sweets were at 12% and some at 5% is now resolved — 5% is the standard rate for fresh and traditional mithai.
| Product Category | HSN Code | GST Rate (2026) | Notes |
|---|---|---|---|
| Traditional Indian sweets (kaju katli, barfi, laddoo, halwa, gulab jamun, rasgulla, jalebi, etc.) | 2106 90 | 5% | Applies whether sold loose by weight or pre-packaged. Both branded and unbranded. |
| Namkeen (mathri, mixture, chakli, murukku, sev) | 2106 90 / 1905 | 5% | Savoury snacks sold loose. HSN may vary by specific product — verify with your CA. |
| Packaged dry fruit and nut mixes (branded) | 0813 | 5% | Loose dry fruits sold as ingredients are 0% or 5%. Packaged branded: 5%. Verify current classification. |
| Gift boxes (assorted sweets + packaging) | 2106 90 | 5% | The composite supply (sweets + gift packaging) is taxed at 5% as the principal supply is the sweet. |
| Ice cream (if stocked) | 2105 00 | 5% | Moved from 18% to 5% effective 22 Sep 2025. |
| Beverages (tea, lassi, sharbat served in-house) | 2202 | 5–12% | Depends on category and whether with or without milk. Verify with CA. Must be configured separately in billing system. |
| Chocolates and cocoa-based sweets | 1806 | 5% | Moved from 18% to 5% effective 22 Sep 2025. |
4.2 — What Must Appear on a Valid GST Invoice from a Sweet Shop
A sweet shop registered under GST must issue a valid tax invoice for every transaction. A valid invoice must include: the shop's legal name, address, and GSTIN; invoice number and date; description of goods with HSN code (2106 90 for most sweets); quantity (by weight in kg/g for weighed items); taxable value; GST rate and amount split as CGST and SGST (or IGST for interstate); and total amount payable. If the customer is a GST-registered business buying for corporate gifting, their GSTIN must be captured on the invoice so they can claim ITC.
Billing software that does not include HSN codes on the invoice is not GST-compliant. Shops registered under GST with turnover above ₹5 crore must mandatorily include HSN codes. Below that threshold it is still strongly recommended — an invoice without HSN codes is harder to file in GSTR-1.
GST rates changed on 22 September 2025 (56th GST Council). If your billing software was last updated before this date, the rates may be incorrect. Ask your vendor when their system was last updated for GST changes and get confirmation that the current rates are correct.
Expiry Tracking and Wastage Management
The hidden profit lever that most sweet shops don't use
Every mithai shop produces perishable goods every day. Gulab jamun and rasgulla have a shelf life of 1–2 days. Kaju katli lasts 5–7 days at room temperature. Besan laddoo can last 10–15 days. Fresh ghee-based items 5–8 days. When product is not sold before expiry, the entire production cost of that batch becomes a loss. For a medium-format sweet shop doing ₹5–8 lakh/month in revenue, unmanaged wastage at 5–8% of production represents ₹25,000–₹64,000 lost per month — the equivalent of 2–3 months' rental cost written off every year in spoilage.[6]
5.1 — How Batch Tracking Works
A proper inventory and expiry tracking system for a sweet shop operates as follows: when the halwai makes a new batch — say, 8 kg of gulab jamun at 9:00 AM — the production is logged in the system with three data points: product name, quantity produced (8 kg), and production date/time. The system calculates the expiry time automatically based on the configured shelf life for gulab jamun (2 days → expiry on Day 2 at 9:00 AM or end of day). As the day progresses and gulab jamun is sold, the billing system deducts each transaction from the batch quantity. At any point during the day, the system shows: 8 kg produced, 5.4 kg sold, 2.6 kg remaining, expiry in 36 hours.
The morning of Day 2, the system flags this batch: '2.1 kg gulab jamun expiring today.' The owner can decide to: run a price markdown to clear stock quickly (system can apply a markdown price for the flagged batch), donate it, or write it off. Every outcome is recorded. At the end of the month, the wastage report shows: total production, total sold, total marked down/discounted, total written off — with the cost value of each category. This is the data needed to tighten production planning.
| Product | Shelf Life | Alert Trigger | Recommended Action at Alert |
|---|---|---|---|
| Gulab Jamun | 1–2 days | Same day (12 hr remaining) | 10–15% markdown in afternoon. Move to prominent display position. If unsold at closing: write off or donate — do NOT carry over. |
| Rasgulla / Rasmalai | 1–2 days | Same day | As above. Milk-based: no second-day extension. Strict write-off discipline required. |
| Motichoor / Boondi Laddoo | 3–5 days | Day 4 morning | Markdown on Day 4. Unsold by end of Day 5: write off. Do not extend shelf life based on visual inspection. |
| Kaju Katli | 5–7 days | Day 6 morning | Lower risk. Alert sufficient — usually clears before expiry if production is calibrated to daily demand. |
| Besan Laddoo | 10–15 days | Day 12 morninglife. | Ghee acts as preservative. Monitor texture — drying out before the date is a quality signal even if technically in shelf |
| Namkeen (mathri, mixture) | 20–45 days | Day 35+ | Low urgency. Main risk is flavour staleness. Store in sealed containers. Production should track to weekly demand. |
Multi-Counter Operations and Reporting
Managing more than one billing point — and the data every owner needs daily
A sweet shop with more than one billing counter — or more than one outlet — needs a billing system where all counters are connected. If Counter 1 sells 2 kg of kaju katli and Counter 2 sells 1.5 kg, both deductions must come from the same inventory pool. If a price is updated in the system, both counters must reflect it immediately without a manual update on each machine. If the owner is reviewing sales at 6:00 PM from a phone or a back-office screen, the data from both counters must be visible as a single consolidated view. This sounds obvious, but many small billing systems in India work as standalone units per counter — there is no centralisation.[1]
6.1 — Daily Reports Every Sweet Shop Owner Needs
| Report | What It Shows | Why It Matters |
|---|---|---|
| Daily sales by | Kg sold and revenue for | Tells you which products are moving and |
| product | each product today, vs. yesterday, vs. same day last week. | which are slow — enables same-day production adjustment for tomorrow. Identifies if one SKU is consistently under-selling. |
| Production vs. sales summary | For each product: produced today (kg), sold (kg), remaining (kg), status (fresh / near expiry / expired). | Your most important wastage-prevention report. Should be checked at 5 PM daily to identify what needs to be cleared before closing. |
| Counter-wise sales | Revenue, transactions, average bill value, and payment method breakdown per counter. | Identifies if one counter is running significantly higher or lower — may signal staffing issue, preferred counter, or billing discrepancy. |
| Peak hour heatmap | Transaction count and revenue by hour across the day. | Helps plan staffing — knowing peak hours are 11 AM–1 PM and 6–8 PM means you can roster the best counter staff for those windows and use training time in off-peak hours. |
| Festival vs. normal day comparison | Side-by-side of this Diwali week vs. last Diwali week in same format. | The most useful planning data for next year's Diwali stock and staffing decisions. If you don't capture this year's data cleanly, next year you're estimating from memory. |
| Product mix margin report | Revenue % and gross margin % by product category (dry mithai, milk-based, namkeen, beverages). | Shows if low-margin products are crowding out high-margin ones in your sales mix. Supports pricing and display decisions. |
Buyer's Checklist Before You Sign Up
The questions to ask any billing software vendor — before the demo ends
Many sweet shop owners have signed up for a billing system after a 20-minute demo and discovered critical limitations only after they had invested in hardware, training, and data migration. The following checklist covers the questions that prevent that experience. Take this into every vendor conversation.
7.1 — Scale Integration
- Does your system support direct RS-232/USB scale integration — meaning weight auto-populates in the billing screen without staff typing anything?
- Which specific scale models are on your compatibility list? (Get the list in writing, and verify your existing scale is on it before purchasing.)
- What happens if the scale connection drops mid-session? Does the system fall back to manual entry gracefully? Do bills already raised remain valid?
7.2 — GST and Compliance
- Is your system updated to reflect the September 2025 GST changes (5% slab consolidation, removal of 12% slab)?
- Does the system generate a GST-compliant invoice with HSN code, CGST/SGST split, and GSTIN of buyer when required?
- Can I configure different GST rates for different product categories (sweets at 5%, beverages at a different rate) and will the system apply them automatically?
7.3 — Gift Box and Multi-Item Billing
- Does your system have a dedicated gift box billing mode where I can add multiple weighed items to a single bill?
- Can I set packaging charges per box size, and does the system add them to the gift box total automatically?
- Can I save common gift box compositions (e.g., 'Standard Diwali 500g Mix') as templates for faster billing?
7.4 — Inventory and Expiry
- Does the system support daily production logging by batch? Does it deduct sales from the production batch in real time?
- Can I configure shelf life per product and get an automated alert when a batch is within X hours of expiry?
- Does the end-of-day report show unsold inventory by batch with expiry status?
7.5 — Operations and Support
- Is this a cloud-based system or locally installed? If cloud-based, what happens to billing if the internet goes down? (Answer must be: billing continues offline and syncs when connectivity is restored.)
- How many counters can run simultaneously on my plan? What is the per-counter cost above the base limit?
- What does onboarding include — will someone help me enter my product list and prices, or do I do it myself?
- What is your support response time during Diwali peak? (This is when you need support most urgently — and when most SaaS teams are under-staffed.)
- What is the contract term and exit process? Can I export all my data in a standard format (CSV/Excel) if I want to switch?
Run the demo with your actual product list — not the vendor's sample data. Bring a real weighing scale to the demo if possible. Ask them to demonstrate: (1) adding 0.247 kg of kaju katli at ₹1,200/kg with 5% GST, (2) building a 4-item gift box with packaging charge, and (3) running the production vs. sales report for a sample day.
A vendor who cannot demo with your data in under 30 minutes — or who needs to 'set things up first' before showing you the gift box feature — is telling you the feature is not ready for real use.
Common Questions Before Switching
The objections every sweet shop owner raises — answered directly
Q: My shop has been running fine with pen-and-paper billing. Why change?
It has been running. Whether it has been running well — catching every calculation error, tracking every batch's shelf life, flagging every GST miscalculation, showing you which products are margin winners — is a different question. Most traditional sweet shops that switch to software discover three things within the first 30 days: their wastage was higher than they thought because they were never tracking unsold batches; their average bill value was understated because of rounding errors; and their Diwali planning was essentially guesswork because there was no year-on-year data to compare. The question is not why change — it is how much longer you can afford not to.
Q: My counter staff is not tech-savvy. Will they be able to use this?
The operator interaction in a well-designed sweet shop billing system is: tap product name, place item on scale, weight appears, add to bill. Repeat for each item. Print receipt. For 80% of transactions, this is the entire workflow. Staff who can use a mobile phone — which is everyone under 40 in India in 2026 — can learn this in a single day. The complexity is in setup and configuration, which is the owner's responsibility, not the counter staff's.
Q: What is the total cost — software plus hardware?
Budget range for a Format A or B sweet shop (2026 pricing): Billing software subscription: ₹1,000–2,500/month (₹12,000–30,000/year depending on vendor and features). Weighing scale if not already owned: ₹3,500–12,000 for a Essae or CAS model with RS-232/USB port. Thermal receipt printer: ₹4,000–8,000. Billing terminal/tablet (if needed): ₹8,000–20,000 for a decent Android or Windows device. Total first-year cost for a shop starting from scratch: approximately ₹30,000–65,000 including software, hardware, and setup. Compared to a Format B shop's annual revenue of ₹65–90 lakh, this is 0.05–0.10% of annual revenue — a negligible investment relative to the wastage reduction, error elimination, and GST compliance it delivers.
Q: What about data backup and privacy? My billing data is sensitive.
Cloud-based systems store data on servers maintained by the vendor — data is accessible from any device but you are dependent on the vendor's data retention policies and security practices. Locally installed systems store data on your machine — you own it but must maintain your own backups. For most small-to-medium sweet shops, a reputable cloud vendor with automatic daily backup is more reliable than a self-managed local backup that may not happen consistently. Verify: (1) data is encrypted in transit and at rest; (2) you can export all your own data at any time in a readable format; (3) the vendor is based in India and subject to Indian data protection regulations.
Sources
- BillBerry POS, 'Best Sweet Shop Billing Software in India 2025: Features, Pricing & Why You Need It', billberrypos.com, 2025.
- Shree Shree Weighing Solutions, 'How to Connect Your Weighing Scale with a POS Machine for Smooth Billing', shreeshreeweighingsolutions.com, 2025.
- Ginesys, 'Essae Weighing Scale Integrated Successfully with Ginesys POS', ginesys.in, 2025.
- Gofrugal, 'Sweet Shop POS & Billing Software', gofrugal.com, 2025.
- Busy.in, 'New GST on Sweets 2026: 5% Rate on Indian Sweets, Mithai', busy.in, 2026.
- VasyERP, 'India's #1 Cloud-Based Sweet Shop Billing Software', vasyerp.com, 2026.
- ER4U, 'All-in-One Weighing and Billing Software System', er4u.in, 2024.
- Essae Teraoka, 'Weighing Scale and POS Integration Guide', essae.com, 2025.