Retail software becomes useful when it follows the counter instead of asking the shopkeeper to maintain a separate notebook, WhatsApp thread, spreadsheet, and printer workaround for every exception. HisabLekha's current public product documentation now calls out seven workflow updates for Indian apparel, fabric, footwear, boutique, uniform, and multi-store retailers. They are practical additions rather than a promise that every shop has the same hardware or plan configuration.
What is included in the 2026 workflow update?
- Clothing alteration jobs: Record the garment, work instruction, promised date, tailor, status, optional charge, measurements, printable slip, and ready-for-collection handover.
- Eligible completed purchase corrections: Review supported price, date, freight, notes, and child-line changes while explicit variant-parent guardrails refuse quantity increases, parent inserts, and parent-to-child moves before a write.
- Combined estimates and deposits: For participating shops, record shop-scoped deposits, show the amount received and balance pending across the estimate, and carry the scoped deposit into the final shop-wise sale conversion.
- Hosted invoice and estimate links: Create a secure customer-facing link for supported sale, return, exchange, and estimate documents, then copy, share, or revoke it from the billing workflow.
- Per-roll fabric barcode copies: Select open physical rolls and choose how many labels each roll should receive, instead of treating every roll like one generic SKU quantity.
- Inline taxonomy setup: Owners can create a category or a category-scoped subcategory while adding a SKU, without abandoning the product form.
- Desktop A4/A5 document printing: Save a system printer for sheet-fed bills, test the route, and keep document printing separate from the shop's thermal receipt printer.
1. Keep alteration jobs connected to the garment sale
A fitting, hem, repair, or other clothing alteration is easy to lose when the bill is in one place and the tailor's instruction is in another. The documented alteration workflow keeps the customer or walk-in, garment, work description, promised date, notes, tailor assignment, status, and optional charge together. A job can be started from the alteration worklist, a customer record, or an eligible sale line that needs work.
Saved customers can keep versioned customer measurements in a profile. When a new measurement is saved, the earlier version remains available for review instead of being silently overwritten. The current profile can be attached to the job and its printable slip. The worklist then separates pending, in-progress, ready, delivered, and cancelled jobs, with due-date signals for the counter.
This is deliberately a retail handover workflow. In the current v1 boundary, alteration writes are online-only, measurements require a saved customer, and a combined multi-shop bill cannot carry an alteration job. It does not claim cutting-room planning, full custom-tailoring production management, or tailor payroll. Read the alteration management software page and the clothing alteration guide for the full workflow and limitations.
2. Give customers a hosted invoice or estimate link
Customers often want a bill on their phone rather than another paper copy. For supported sale, return, exchange, and estimate documents, the billing workflow can create a hosted link with a share token, copy it, use the device share action, or offer the WhatsApp sharing path. Staff can see the link status and revoke a link when it should no longer be available.
The useful distinction is between a link the shop controls and a screenshot that can be forwarded without context. A hosted document can present the customer-facing invoice facts in one place, while the shop retains a record of the link's status. Expiry, revocation, plan entitlements, document eligibility, and the actual deployment still need a live test; do not promise a hosted link for a purchase document or for a transaction type the shop has not verified.
For the product surface, start with the HisabLekha product overview, then test one completed sale, one return or exchange, and one estimate on the shop's real phone. The pricing page remains the source of truth for plan scope and renewal terms.
Review completed purchase corrections with explicit variant guardrails
A completed supplier bill should not be changed by silently rewriting a stock number. In the current production workflow, eligible completed purchase records can be opened for supported price, date, freight, notes, and child-line corrections. The edit path keeps the purchase, stock, and supplier-ledger update connected while the shop reviews the result.
The variant rules are explicit. If a historical line belongs to a parent that was later split into sizes or colours, a quantity increase, a new parent line, or a parent-to-child move is refused before a write and the counter receives plain guidance. Extra pieces should be recorded as a purchase of the exact size or colour; a reversal should use the purchase-return workflow. Completed size-leaf purchase edits remain outside this published scope, so verify the exact variant shape, stock result, supplier balance, and return path in a demo.
Combined estimates with shop-scoped deposit handoff
A customer may choose items from two participating shops and pay a deposit before the final sale is ready. A supported combined-estimate flow keeps the estimate tied to the participating shops, records the deposit associated with each shop, and shows the combined amount received and balance still pending instead of making the counter team reconstruct the visit from separate notes.
When the customer confirms the order, the scoped deposit can be carried into the conversion to separate shop-wise GST invoices. The conversion validation counts the deposit only for the estimate actually being converted and only for the shops still participating. If one shop is dropped, its estimate and deposit remain separate rather than silently paying for the other shop's sale. Start with the multi-store POS workflow and verify the branch permissions, estimate status, payment allocation, and printed or hosted output on the actual deployment.
3. Print barcode copies per physical fabric roll
A fabric shop may have one fabric SKU represented by several physical rolls, each with its own roll code, barcode, and remaining metres. Printing one generic label count for the SKU does not give the stockroom a useful identity for each roll. The updated barcode workflow loads open physical rolls for metre-tracked products, lets staff select the actual rolls, and gives each selected roll its own copy count.
The bulk copy control also applies to the selected open rolls, so a shop can choose several rolls and set the same number of labels per roll before printing. The generated barcode objects use the individual roll barcode and retain the roll code and remaining-metre context. Piece-based products continue to use their normal SKU-level copy behaviour.
Before printing a large batch, select two real rolls with different remaining lengths and scan the labels back into the inventory flow. Confirm that the label identifies the physical roll the staff member intended, rather than assuming that a shared fabric SKU is enough.
4. Finish category setup while adding a SKU
Product entry often breaks the counter rhythm when the right category does not exist yet. The inline taxonomy controls let an owner create a category or create a subcategory under the selected parent from the SKU form, then continue with the item setup. A subcategory cannot be created as an orphan: the parent category must be selected first.
This control is intentionally owner-only because the underlying permission policy does not allow every staff account to change shop taxonomy. It is also online-only. When the device is offline, the control is disabled so the form does not suggest that a change was saved when the server could not create it. Owners should create the category, confirm it is selected, and then save the SKU as one short test path.
5. Route A4 and A5 bills to the right desktop printer
Sheet-fed document printing and thermal receipt printing are different jobs. A shop that chooses A4 or A5 for its bill should not have to send that document to an 80mm receipt printer by accident. In the HisabLekha desktop app, the document-printer setting can list the computer's system printers, save the selected printer for the shop, and print an A5 diagnostic page before the counter starts using it.
The bill still follows the shop's selected document size, while the thermal receipt path remains separate. Browser and mobile users continue with the ordinary device print dialog because a browser tab cannot name an operating-system printer in the same way as the desktop app. Test the actual paper, margins, printer driver, and invoice template before promising a particular output to a customer.
How to test the seven workflows in one demo
- Alteration: Save a test customer, complete an eligible fixed-price garment sale, attach measurements, assign a tailor, print the slip, and move the job to ready.
- Completed purchase correction: Open an eligible completed supplier bill, change a supported field, confirm the variant-parent guidance for a guarded line, and review the resulting purchase, stock, supplier balance, and edit history.
- Combined estimate: Use two participating shops, record a deposit for each, print or open the combined estimate, convert it to the sale, and confirm the deposit is counted once in the remaining balance.
- Hosted document: Create a link for a supported sale or estimate, open it on a second phone, use the share or WhatsApp path, and revoke it to confirm the status change.
- Fabric rolls: Load two open metre-tracked rolls, select both, set a per-roll copy count, print, and scan each physical label.
- SKU setup: As the owner, create a category and a parent-linked subcategory while online, then finish the SKU without reloading the form.
- Documents: On desktop, choose A4 or A5, select the system printer, print the diagnostic page, and compare the result with the browser/mobile print flow.
Know the boundaries before rollout
These features are strongest when the shop tests the exact edge conditions instead of relying on a feature name. Alteration writes are currently online-only. Reusable measurements need a saved customer. Completed purchase corrections are limited to eligible supported fields and child-line changes; variant-parent quantity increases, parent inserts, parent-to-child moves, and completed size-leaf edits are not a blanket editing promise. Combined estimate deposits are scoped to the participating shops and the estimate being converted; a dropped shop keeps its own estimate and deposit. Hosted links apply to supported document types and remain subject to expiry, revocation, plan, and deployment checks. Per-roll labels are for open physical rolls, not an unlimited substitute for SKU-level labelling. Inline categories are owner-only and online. Direct operating-system printer selection is a desktop capability; mobile and browser printing use the normal print dialog.
Next step for an Indian retail shop
Use the product overview to see the wider billing, inventory, GST, and shop-operations context, then compare the alteration workflow or multi-store estimate workflow with the shop's real process. Review current pricing and plan terms, and book a workflow-specific demo with the shop's products, phone, scanner, and printer ready. That test is more useful than a generic claim that a retail system supports everything.