How to Implement TallyPrime for Garment & Apparel Business (2026 Guide)

1Who TallyPrime fits

TallyPrime fits small and mid-size garment and textile businesses that need correct books, GST returns, e-invoices and a trustworthy stock ledger, and that are willing to run their production planning, sampling and floor tracking somewhere else. It is accounting and inventory software with manufacturing vouchers. A Tally project goes well when everyone accepts, from the first meeting, that production planning and the floor sit elsewhere.

In South Asia, Tally is often already in the building. The accountant knows it, the auditor reads its reports, and the GST filings come out of it. So the useful question for a garment factory is what Tally should hold and what should sit beside it. TallyPrime covers the ledger, GST, stock by godown and batch, BoMs with by-products and scrap, the Manufacturing Journal and job work in both directions. It has no documented style-colour-size variant model, no routings or work centres, no production planning and no shop-floor screens.

Signs TallyPrime is the right book of record

Tally works as the ledger when the factory values compliance and speed of accounting over an all-in-one system.

• Finance and GST already run in Tally, and the auditor and the tax consultant rely on its reports.
• The factory has a few hundred active colour-size combinations per season, not tens of thousands.
• Merchandising, sampling and production follow-up already live in spreadsheets or another tool, and the goal is to make that tool proper, not to move it into Tally.
• A local Tally partner is available for TDL work, and the factory is ready to keep that TDL small.

Signs to slow down

Slow down when the plan asks Tally to do the work of a production system.

• The owner expects Tally to show which line is late on which order today. It has no lines.
• A partner proposes a large TDL add-on to hold styles, samples, T&A and cutting. That is a second system living inside the accounts, and it has to survive every Tally release.
• Colour-size combinations run into the thousands per season. Each is a stock item in standard Tally.
• The factory has several plants or companies and expects one planning view across them.

2Why no ERP fits apparel on its own

No general ERP or accounting system fits apparel out of the box, because it is built around a known item with one bill of materials, while a garment order starts as a style that is quoted, sampled and approved before any item exists. TallyPrime is an accounting system first, so it meets this wall earlier than a manufacturing ERP does; SAP, NetSuite, Dynamics 365 and Odoo meet the same wall a little later. The same wall stands in front of brands and buying agents that never sew a garment, because their development, sampling and factory follow-up happen before and outside any transaction too (section 33).

An ERP is built around the transaction: a known item, a fixed bill of materials, a price, a receipt, an invoice. It is right to be strict about that, because strictness keeps the books correct. A garment order does not start there.

Forcing an accounting system to do all of this means heavy customisation in the one system that most needs to stay standard. The ledger fills with data finance never reads, every release gets harder, and the merchandisers keep their spreadsheets anyway. The durable answer is to give Tally the books and give the operations to a system built for them. Section 3 summarises that model and section 35 shows it in full.

3The recommended architecture, in short

With TallyPrime, the split is almost drawn for you: Tally keeps the books, and an operations system built for apparel runs everything from the style to the shipment. This is the model where an operations layer fits most naturally, because Tally never tried to be the production system.

With this split, the Tally project stays close to standard: few or no TDL add-ons, clean upgrades to each new release, and an accountant who recognises every screen. The rest of this guide still explains how far Tally can be pushed toward garment production, because some factories choose to do that, and because a consultant needs to know what each choice costs. Where an area moves out of Tally under the recommended model, the section ends with a short note.

4Business types, and what each needs from TallyPrime

The business type decides who owns the material, what is invoiced, and which Tally vouchers carry weight. Settle it in the first discovery meeting, because a factory often runs two types at once, for example full package for one buyer and CMT for another, and Tally treats the two very differently.

These are general implementation practice, not a Tally statement. Treat them as the starting point for the workshop questions in section 6. Businesses that do not manufacture at all (brands, buying agents and own-label retailers) have their own part of this guide, section 33, because Tally is often a very good fit for their books.

5Who should be on a TallyPrime apparel project team?

A Tally apparel project needs the finance head and the factory's operations heads in the same room, because most of the design questions are about what Tally should not hold. The Tally partner configures and writes any TDL; the factory decides how items, units, batches, costs and job work are recorded.

Write one name against every decision. "Accounts and merchandising will agree" produces no decision, and the stock item list is where that shows first.

6What should discovery workshops for a garment factory on Tally cover?

Run one workshop per department, each walking a real recent order from start to finish, and for every step ask two questions: where is this recorded today, and does it belong in the books. In a Tally project the second question matters more than in any other, because anything that is not a financial or stock event is better held outside Tally.

Merchandising

• How does a buyer order arrive, and how often is it amended after confirmation?
• How many colour-size combinations did last season create? That number is the stock item count in Tally.
• What quantity tolerance do buyers allow, and who checks it before shipment?
• Is one order split into several deliveries with their own dates?
• Where is the T&A calendar kept today?

Development and sampling

• Which sample types does each buyer require, and where are rounds and comments recorded?
• Who prepares the quotation cost, and from what inputs?

Purchasing and stores

• In which unit is each material bought, stocked and issued? Which fabrics are bought in kg and cut in m?
• How are dye lots and rolls labelled, and can the store find every roll of one lot today?
• Which materials are nominated or supplied by the buyer?
• Are import charges (freight, clearing, duty) added to material cost today, and when do those bills arrive?

Production and job work

• At what point is a garment "produced" for the books: end of line, after finishing, after packing?
• Which processes go to job workers (print, embroidery, wash, CMT), and how are pieces counted out and back?
• Does the factory also work as a job worker for other principals?
• How are rejects and seconds recorded, and are seconds sold?

Quality and shipping

• Which inspections run, and where are the reports kept?
• How are cartons packed, and which documents does each buyer and each LC require?

Finance

• Which currencies are used, and how are forex gains and losses booked today?
• How are buyers paid: advance, LC, open account? Which buyers deduct chargebacks?
• Is the factory an exporter under LUT or bond, in a special economic zone, or under another scheme? What reports does that require?
• Which GST returns, e-invoices and e-way bills are produced, and by whom?

Each workshop ends with a findings list mapped to the fit-gap lines in section 7 and a decision owner per finding.

7The apparel fit-gap checklist for TallyPrime: 52 lines

A fit-gap checklist lists every requirement an apparel business has and records, line by line, whether the system meets it as standard, with configuration, with custom code, or better outside it. For TallyPrime, the pattern is clear: finance and stock movements are standard or configurable, product development and the floor are not.

The answers are our assessment of TallyPrime 7.x for a typical full-package garment factory in India. Confirm each line against your release and your partner's add-ons before you sign a scope.

Key: Standard works as delivered · Configure masters, features and settings · Custom build TDL work or a third-party add-on · Operations layer better run in an apparel operations system and passed to Tally

Counted from this table, 6 of the 52 lines are standard, 17 need configuration, 15 need TDL or an add-on and 14 are better run outside Tally. That count is our assessment for a typical full-package factory, not a survey. A CMT factory drops most of the costing and material lines and finds Tally's job-worker flow a close fit.

8Which TallyPrime edition and hosting does a garment factory need?

Most garment factories need TallyPrime Gold, because more than one person (accounts, stores, purchasing) works in the same data at the same time on the office network. Silver is for a single user on a single machine. TallyPrime Server suits larger offices with many concurrent users.

A licence comes with a year of Tally Software Services (TSS), which Tally's licensing page describes as covering upgrades to new releases, online e-way bill and e-invoice generation, reports in a browser and data synchronisation. An Indian exporter that raises e-invoices needs TSS kept active. Prices change and differ by rental or lifetime purchase; take them from tallysolutions.com at the time of quoting.

Where does Tally run, and why does it matter for integration?

TallyPrime is desktop software: in most factories it runs on a machine in the office, and other users connect over the LAN. That shapes every integration, because a cloud system cannot call a PC that sits behind the factory's router. Section 34 explains the usual answer, a small connector inside the network that talks to Tally locally and to the cloud outbound.

9TallyPrime vs Zoho Books for a garment business

TallyPrime and Zoho Books are the two accounting systems small Indian garment businesses most often weigh, and neither is a production system. Tally is stronger on manufacturing vouchers and job work; Zoho is cloud-first with a REST API and webhooks. Choose on how production is recorded and how the operations layer will connect.

For a factory that makes garments, Tally's job work and Manufacturing Journal usually outweigh Zoho's cloud convenience. For a brand that buys finished goods, Zoho's cloud model and API are often the easier base. In both cases the style, the samples and the floor sit in an operations layer, so the choice is about the books and the connection. Other options at this size are compared in the ERPNext chapter and on the comparison page.

10How should stock groups, categories and materials be set up in TallyPrime for apparel?

Use stock groups for what a thing is (fabric, trims, packing, garments) and stock categories for a second, independent cut such as season or buyer, and give every material one main unit chosen for how it is issued. A stock group in Tally is a hierarchy for classifying stock items; a stock category is a parallel classification that cuts across groups.

Choose the valuation method per item with finance. Tally's inventory features page lists average cost, FIFO, LIFO, last purchase cost, standard cost and monthly average cost; for fabric and trims, a factory usually keeps one method throughout so the auditor sees consistent values.

11How do you handle sizes and colours in TallyPrime?

TallyPrime has no documented style-colour-size variant model, so each colour-size combination becomes its own stock item, grouped under a stock group for the style. A style/colour/size matrix is the grid of colours by sizes that defines every sellable version of a style; in Tally that grid is held by a naming rule, not by the software.

This works when the combinations are counted in hundreds per season. It becomes painful in thousands, because every item needs its own BoM, rates and GST details. Three rules keep it under control.

• A fixed code pattern. Style, colour, size, in that order and always the same length: P2041-NVY-M. Reports sort and filter on it.
• Create items by import, never by hand. The operations layer or a sheet generates the list for a new style; Tally imports it.
• One stock group per style. Stock summaries then roll up to the style without extra reports.

Some Tally partners sell TDL add-ons that add size-colour grids to vouchers. They can help order entry, but they live inside your Tally and must be re-tested at every release (section 24).

12How do you convert kilograms to metres for fabric in TallyPrime?

Give knit fabric a main unit of metres and an alternate unit of kilograms, then enter both quantities on every receipt line, because Tally lets the conversion be changed per voucher. Tally's own FAQ states that with alternate units the conversion factor can differ for different items and vouchers, and gives the example of changing a box from 10 pieces to 5 at voucher level. Compound units, by contrast, are fixed (1 kg = 1,000 g).

This matters because knit fabric's metres per kilogram depend on the weight and width of each roll. The formula is metres per kg = 1000 ÷ (GSM × width in metres). A fixed factor in the stock item master is only a planning figure.

With operations on top: the measured lot record (GSM, width, shrinkage) is captured per receipt in the operations layer, and the metres and kilograms it reports are what Tally receives.

13How do you track dye lots and fabric rolls in TallyPrime?

Switch on batch-wise details, treat each batch as a dye lot (or a roll within a dye lot), and make the batch mandatory on fabric receipts and issues. A dye lot is fabric dyed in one batch; pieces from different dye lots can differ in shade and must not be mixed in one garment.

Tally's documentation enables batches under F11: Features ‣ F2: Inventory Features with Maintain batch-wise details, and on the stock item with Maintain in Batches. Manufacturing and expiry dates are optional; a garment factory usually leaves expiry off and uses the manufacturing date field, if at all, for the mill's dye date.

Tally has one batch identifier per line. If you need both the dye lot and the roll, put both in the batch name with a fixed pattern such as A/R01, so that the lot can be read from any roll. Width, GSM and shade group are not batch fields in standard Tally; they need TDL or another system.

Tally will not stop a user from issuing two lots to the same cut. The rule "one dye lot per cut" is enforced by people or by the operations layer.

14How do you handle size-dependent fabric consumption in TallyPrime BoMs?

Because every size is its own stock item, give every size its own BoM with its own fabric quantity. This is one of the few places where Tally's item-per-combination model helps: size-graded consumption falls out of the design, as long as the BoMs are generated and imported rather than typed.

Tally's documentation switches a BoM on with Set Components (BOM) on the stock item, allows several BoMs per item, and, with Define Type of Component for BOM set through F12, classifies each line as a component, co-product, by-product or scrap.

With operations on top: the classified two-level bill of materials (fabric and trims, with yarn linked to fabric) and the consumption engine (marker efficiency, shrinkage, woven construction) run in the operations layer. Tally receives per-size BoMs only if finance wants the Manufacturing Journal to consume from them.

15How do you record garment production in TallyPrime: Manufacturing Journal or Stock Journal?

Use the Stock Journal to move material between godowns (store to cutting, cutting to sewing, to and from a QC hold) and the Manufacturing Journal to record that finished garments were made, consuming components by the BoM and recording co-products, by-products and scrap. Tally has no work centres, routings or operation times, so production planning and line tracking always sit outside it.

The Manufacturing Journal is a mode of the Stock Journal voucher. In the TallyPrime documentation, you open the Stock Journal from Alt+G ‣ Create Voucher ‣ Alt+F7 and press Ctrl+H to switch to Manufacturing Journal; choosing the product and BoM fills the components, and a Type of Additional Cost field adds costs such as labour.

What the Manufacturing Journal should mean in a garment factory

Decide one moment at which a garment counts as made for the books, and post the Manufacturing Journal then, never earlier. Most factories choose end of finishing, before packing. Posting per line per day is possible but turns the accounts into a floor log. Posting per order at the end loses the month-end WIP picture. A weekly post per style-colour is a common middle ground; this is practice, not a Tally rule.

With operations on top: planning (the 52-week heat-map of lines and subcontractors), production orders, job cards per department, floor capture and the WIP board run in the operations layer. Tally receives the material issues and the finished quantities, for stock value.

16Where do sampling, approvals and the T&A calendar live when the books are in Tally?

Outside Tally. A PP sample (pre-production sample) is a garment in bulk fabric and trims that the buyer approves as the reference for production, and a T&A calendar (time and action calendar) is an order's milestones worked back from the ex-factory date; neither is a financial or stock event, so Tally has nowhere to hold them.

What Tally can hold is the money side of sampling: sample fabric bought, courier bills, sample charges invoiced to a buyer. Keep those in a "Sampling" cost centre so that development cost per buyer can be reported. The rounds, comments, verdicts and dates belong in the operations layer.

With operations on top: lab dips, strike-offs, samples and shipping marks run as rounds with parcel and courier details, the buyer's verdict and T&A wiring; the approved PP round locks the style version for the order.

17How does job work work in TallyPrime, as principal and as job worker?

TallyPrime documents job work in both directions. As a principal manufacturer, you raise a Job Work Out Order, send materials with Material Out and receive processed goods with Material In; as a job worker, you raise a Job Work In Order, receive the principal's material with Material In and return goods with Material Out. Job work is the Indian term for sending goods to another business to process and return; in garments it covers CMT, embroidery, printing and washing.

In the documentation, the vouchers are created from Alt+G (Go To) ‣ Create Voucher ‣ F10 (Other Vouchers). Each job worker gets a godown, so stock at the embroiderer or printer shows in the godown summary. If the processed item has a BoM with Track Components set to Yes, the components expected back are shown against the order.

With operations on top: subcontract steps are planned on the heat-map alongside the factory's own lines, and output from subcontractors is followed per order. Tally keeps the job work vouchers that move and value the goods.

18How do you cost a garment in TallyPrime, and where does the costing sheet live?

Tally values stock by the valuation method you choose, adds freight and other charges to purchases with additional cost of purchase, and shows actual cost and profit per order through cost centres used for job costing. The garment costing sheet that produces a quote lives outside Tally, because it is built before any stock item or BoM exists.

Tally's Cost Estimation report works from an existing BoM. That is useful after the style is set up, to compare the BoM's cost with the quote, but it is not a quotation tool.

How do you add freight, clearing and duty to imported fabric in Tally?

Use additional cost of purchase: create each charge as a ledger with a method of appropriation, and enter it in the purchase voucher so Tally spreads it over the stock items. A landed cost is every cost of bringing goods to the factory beyond the supplier's price: freight, insurance, customs duty, clearing and bank charges.

Tally's documentation names two methods, Appropriate by Qty and Appropriate by Value, set on the ledger as Method of appropriation in purchase invoice (enabled through F12 if the field is hidden). The page describes the charges entered within the same purchase voucher. It does not describe attaching a freight or clearing bill that arrives weeks later from another party to an earlier purchase; agree with your auditor how late charges are treated, and check your release.

With operations on top: the cost engine (fabric, trims, decoration, CMT, overhead, margin to FOB, with landed cost and dated exchange rates), the standard cost sheet and quotations with approval thresholds run in the operations layer. Tally holds the landed cost that actually hit the purchases.

19Can TallyPrime run quality control and AQL inspection?

No. TallyPrime has no inspection object and no sampling tables, so quality control runs outside it, and Tally records only the stock result: goods held in a QC godown, released by Stock Journal, and rejects or seconds recorded as items. AQL (acceptance quality limit) is an inspection method that checks a random sample from a lot and accepts or rejects the lot by the number of defects found, using ISO 2859-1 tables.

With operations on top: typed inspections (incoming, cutting, PP, DUPRO, final AQL, pre-shipment, measurement), the AQL engine on ISO 2859-1 with the buyer's level, CAPA, needle and metal control, and quality grades run in the operations layer.

20How do you handle cartons, packing lists and shipping documents with Tally?

Tally raises the delivery note, the export invoice and the e-way bill; the carton plan, the packing list by carton and buyer carton labels are built outside Tally or through TDL. Tally has no carton or package object.

A dye-lot rule makes the carton count different from the simple division. For the polo order in solid-size cartons of 10, one lot per carton gives 298 full cartons and 4 part cartons (S lot A 7, S lot B 3, M lot A 3, M lot C 7 pieces), 302 cartons instead of 300.

With operations on top: per-delivery shipments, packing and cartonisation, and ship clearance against buyer terms run in the operations layer. Tally receives the dispatch and raises the invoice and e-way bill.

21How does TallyPrime handle foreign currency, advances, letters of credit and chargebacks?

TallyPrime handles foreign currency, forex gain and loss and bill-wise advances as standard; a letter of credit is recorded through ledgers and bill references, since there is no LC object; chargebacks are ledgers, one per reason. Tally's multi-currency pages describe rates of exchange defined by date, forex gain or loss calculated when rates move, and reports in base or foreign currency.

A letter of credit (LC) is a bank's promise to pay the exporter when documents matching the credit's terms are presented. Keep the LC number, expiry, latest shipment date and presentation period somewhere the shipping team sees daily; in a Tally-only factory, that is a register outside Tally or a TDL master.

How do you see profit per order in Tally?

Enable cost centres, create one per order with Use for job costing set to Yes, and allocate every purchase, job work bill, expense and sale for that order to it. Tally's job costing page describes this set-up and a Job Work Analysis report that shows cost, revenue and net profit or loss per cost centre.

Chargebacks

A chargeback is an amount a buyer deducts from a payment for a claimed failure such as a late shipment or a wrong carton label. In Tally, open one ledger per reason (for example "Chargebacks: labelling" and "Chargebacks: ASN") and clear the short payment against them with a journal. If an open-account buyer deducts USD 100.00 for labels and USD 89.46 (1% of 8,946.00) for a late ASN, the payment received is 8,946.00 − 189.46 = 8,756.54, and the two ledgers show where the money went.

22Does TallyPrime handle GST, e-invoicing and e-way bills for garment exporters?

For India, yes: TallyPrime generates e-invoices (IRN and QR code) and e-way bills online from the invoice, singly or in bulk, through Tally's GST Suvidha Provider, with an active Tally Software Services subscription. Tally's help pages also describe an option to send e-way bill details with the e-invoice.

• Job work and GST. Indian GST requires a principal to report goods sent to and received from job workers (form ITC-04). Tally records the job work vouchers that the report is built from; check that your release produces the return in the form your tax consultant files.
• Exports. Confirm with the tax consultant how exports under a letter of undertaking or a special economic zone are set up in your release before the first export invoice.
• Other countries. Tally is used in several markets beyond India. Tax, VAT and e-invoicing support differs by country edition; check your country's release with Tally before relying on it.

23In what order should you set up TallyPrime for a garment factory?

Set up TallyPrime in dependency order: company and statutory details, features, ledgers and cost centres, units, godowns, stock groups and categories, stock items with batches and BoMs, then voucher types and job work. Each step depends on the ones before it, and changing a unit or a batch rule after transactions exist is painful.

1. Company, GST and statutory details. Registration, state, financial year, base currency.
2. Features (F11). Inventory features including batch-wise details, multiple godowns, order processing, cost centres, multi-currency, job work.
3. Ledgers. Buyers, suppliers, job workers, GST ledgers, forex gain and loss, additional-cost ledgers with their method of appropriation, chargeback ledgers per reason.
4. Cost centres. One per order (with Use for job costing), plus Sampling and Overheads.
5. Units. Simple units (m, kg, pcs, pair, cone), compound units (dozen, gross), and the alternate-unit plan per material (section 12).
6. Godowns. Main store, QC hold, Cutting, Sewing, Finishing, Packing, one per job worker, one for principals' stock if the factory is also a job worker.
7. Stock groups and categories. As in section 10.
8. Stock items. Materials first, then finished items by import, each with batches where needed and a BoM for finished items (section 14).
9. Voucher types. Numbering per series, and the Manufacturing Journal, Material In and Material Out types.
10. Integration user and connector. Last, once the masters it maps to exist (section 34).

Menu paths change between releases. The ones quoted in this guide are from the TallyPrime 7.x help pages; confirm them on your release.

24How far should you customise TallyPrime with TDL for apparel?

Keep TDL small: use it for fields and reports that finance or stores genuinely need, and never to build a second production system inside the books. TDL (Tally Definition Language) is Tally's own language for extending the product and integrating it; programs are compiled into TCP files and loaded locally or deployed centrally as account TDLs, according to Tally's developer reference.

Keep a register of every TDL loaded, who wrote it, what it changes and who tests it at each release. TDL differs from site to site, and an integration written against one factory's TDL will not match another's.

25Which systems does a Tally-based garment business integrate with?

A Tally-based garment business typically connects Tally to one operations system, the bank, and the GST portal through Tally's own GSP; EDI, if a buyer requires it, goes through a connector or provider. Every connection to Tally is shaped by where Tally runs.

Rules for every connection

• One writer per field. A value typed in Tally and also sent by the operations layer will drift.
• Link on permanent ids. Store Tally's MasterID or GUID for each voucher, never only the voucher number, which users can renumber.
• Make every call safe to repeat. A connector that retries after a network drop must not create a second voucher.
• Name the company. Tally's JSON documentation warns that, without the company name, data can be exchanged with the wrong company.

26How do you migrate apparel data into TallyPrime?

Migrate masters and open items only (ledgers, stock items with BoMs, batches in stock, open orders and open bills), load them in dependency order through import files, and have each owner sign off the totals. Many factories already run Tally for the books, in which case "migration" means cleaning and restructuring stock items rather than moving systems.

TallyPrime imports XML and JSON, and its help pages describe importing data with mapping templates. Take the exact file format from your release's import screen.

Stock item,Group,Category,Unit,Alt unit,Alt conversion,Batches,Alias
P2041-NVY-S,P-2041,AW26,pcs,,,No,BY-77310-410-S
P2041-NVY-M,P-2041,AW26,pcs,,,No,BY-77310-410-M
P2041-NVY-L,P-2041,AW26,pcs,,,No,BY-77310-410-L
P2041-NVY-XL,P-2041,AW26,pcs,,,No,BY-77310-410-XL
P2041-NVY-XXL,P-2041,AW26,pcs,,,No,BY-77310-410-XXL
Navy jersey 180,Knit fabric,,m,kg,3.086 m = 1 kg,Yes,

Open sales order SO/P2041 (USD):
P2041-NVY-S 300 × 4.26 = 1,278.00
P2041-NVY-M 750 × 4.26 = 3,195.00
P2041-NVY-L 900 × 4.26 = 3,834.00
P2041-NVY-XL 750 × 4.26 = 3,195.00
P2041-NVY-XXL 300 × 4.26 = 1,278.00
Open purchase order PO/0457: navy jersey 925 kg, 0 received
Stock: button 15 mm navy, 9,504 pcs, Main store

The cut-off rule and cleansing

Write the cut-off as a date and time, count stock by godown and batch at that moment, and load what was counted. Before loading, merge duplicate stock items ("Navy Jersey 180", "Jersey 180 NVY"), retire styles with no order in two seasons, and give every fabric one main unit.

27How should you test a TallyPrime set-up for apparel end to end?

Test with end-to-end scenarios that follow one real order from the buyer's order to cash, run by the factory's key users on a copy of the company with migrated data, each step with an expected result written in advance. Checking screens one by one proves the set-up; only scenarios prove the business works.

Test script: short shipment within tolerance

The buyer allows ±3%. The factory ships 2,940 pieces, 30 short in M and 30 short in L: 60 short is 2.0%, inside the tolerance. Tally has no tolerance field, so the check is made before invoicing by the shipping head or the operations layer. The invoice is 2,940 × 4.26 = USD 12,524.40, less the 3,834.00 advance, leaving 8,690.40 due; the sales order lines for the 60 pieces are closed rather than left pending.

28How should you train a garment factory's staff on TallyPrime?

Train each role only on the vouchers it will post, on the factory's own items and orders, in the local language; most accountants already know Tally, so the training effort goes to stores and production staff who will post batch-wise receipts, Stock Journals and job work.

Hours are an example plan from practice, not a standard.

29What does a cut-over plan look like for a garment factory moving onto Tally?

A cut-over plan is a dated list of steps from freezing the old records to the first live vouchers, each with an owner and a go or no-go point. Rehearse it once on a copy of the company.

30When should a garment factory go live on a new Tally set-up, and how long is hypercare?

Go live between seasons and at the start of a month, and keep the partner in close support until the first month-end close and GST filing are done on the new set-up. Hypercare is the period right after go-live when the project team fixes issues daily. Practitioners commonly plan four to eight weeks; that range is judgement, not a measured standard. Avoid the financial year-end and audit weeks.

31What are the most common mistakes when using Tally for a garment business?

The common mistakes are asking Tally to be the production system, typing stock items by hand until the list is unusable, one kg-to-metre factor for every roll, one BoM for every size, and integrations built on the assumption that Tally is always reachable. The list comes from implementation practice, not from Tally's documentation.

1. Tally as the production system.A large TDL add-on for samples, T&A and cutting, which then blocks every release upgrade.
2. Stock items typed by hand.Inconsistent names, duplicates, sizes that sort wrongly.
3. The master conversion used on every receipt.Metres in the books that the cutting room never finds.
4. One BoM shared by all sizes.Fabric under-bought for large sizes.
5. Batches optional on fabric.Dye lots lost at the first issue.
6. Manufacturing Journal posted at the wrong moment.Posted at cutting, it shows garments that do not exist yet; posted at shipment, WIP disappears from the books.
7. No cost centre per order.Nobody can say which order made money.
8. The Tally machine treated as always on.An integration fails every night because the PC is off, or TallyPrime is open on another company.
9. Linking on voucher numbers.A renumbered series breaks every link to the operations layer.
10. TSS allowed to lapse.Online e-invoice generation and upgrades depend on it, according to Tally's licensing page.

The 15 general failure modes, and how each shows up with Tally

32What must be decided before a garment factory goes live on Tally?

Decide what Tally holds and what it does not, the stock item code pattern, the unit and batch design for fabric, the moment a Manufacturing Journal is posted, cost centres per order, and how the operations layer connects, before go-live. Each is expensive to change once vouchers exist.

• What stays outside Tally: styles, samples, T&A, planning, floor, quality.
• The stock item code pattern and who creates items (by import).
• Main and alternate units per material; both units entered on fabric receipts.
• Batch meaning: dye lot, roll, or both in one name.
• The moment a Manufacturing Journal is posted, and how often.
• Seconds and rejects as co-products and scrap.
• Godowns per stage and per job worker.
• Valuation method per stock group.
• How late import charges reach material cost.
• Cost centre per order, allocated on every voucher.
• Edition (Silver, Gold, Server or Cloud Access) and TSS renewal.
• The TDL register and who tests it at each release.
• The integration method, the connector's machine, and what happens when Tally is closed.

33Is TallyPrime a good fit for clothing brands, buying houses and own-label retailers?

Yes, for the books. A brand, a buying agent or an own-label retailer that does not manufacture needs accounts, GST, supplier and buyer ledgers, foreign currency and landed cost, which are exactly what Tally does well, and it needs none of the manufacturing vouchers. What it also needs, and Tally cannot give, is development, sampling and follow-up across many factories.

Who this part is for

• A brand or wholesaler that designs and sells clothing while factories make it, on FOB or CMT terms.
• A buying agent or buying house that sources for buyers across factories, earns a commission and holds no stock.
• A retailer developing its own label with factories, often called private label sourcing.

What they need from TallyPrime

They need purchasing, landed cost, payments and sales, with no production. Switch on only what is needed.

A buying agent is the simplest Tally company there is: no inventory, no goods payables or receivables, only commission invoices, expenses, foreign receipts and GST on services. How export of services is taxed is a question for the agent's tax consultant, not for this guide.

What TallyPrime handles poorly for them

• Development and sampling with many factories. Lab dips, strike-offs and fit samples travel between the brand, the agent and several factories; Tally sees only the courier bill.
• T&A across factories. Each order's milestones sit at a different factory; Tally has no calendar.
• Following production that happens outside. Cutting, sewing and finishing happen in someone else's building. Tally sees the purchase order and, weeks later, the goods.
• Inspections at the vendor. AQL inspections at the factory decide whether goods ship; Tally has no inspection record.
• One status per order. A merchandiser following 40 orders across 12 factories and 6 buyers needs one status per order, and Tally's pending-order reports list quantities, not stages.

This is the gap that sourcing agent software and ERP for fashion brands try to close. For a Tally user, the practical answer is to keep Tally for the books and add an operations layer for the sourcing work.

What should a brand or agent switch on in Tally, and what should it leave off?

Switch on only what the books need, because every feature left on is a screen someone must keep correct.

• Brand: order processing for purchase and sales orders, multiple godowns if stock sits in more than one place, multi-currency, cost centres per season or per order, additional cost of purchase for freight, duty and clearing.
• Brand: batches only if the brand must trace goods by shipment or by factory lot for recalls or buyer claims.
• Agent: accounting only, multi-currency, a service ledger for commission income, one cost centre per buyer so commission can be reported by account.
• Both: leave BoMs, the Manufacturing Journal and job work off. They add screens nobody needs and invite postings that do not describe the business.

An own-label retailer usually already has a retail system for stores and point of sale. In that case Tally holds the supplier side and the general ledger, and the retail system posts summarised sales into it. Where the line between the two sits is a decision for the retailer's finance team and is outside what this guide can settle.

The MerchandiserOS model for brands and agents

MerchandiserOS runs development, samples and approvals, T&A, the orders placed with factories, sourcing, the planning view across subcontracted factories, quality inspections and shipping follow-up. Its workspace set-ups include "Brand" and "Buying agent". TallyPrime keeps the books. Retail back-office work (stores, point of sale, allocation and open-to-buy) is outside MerchandiserOS's scope, so an own-label retailer keeps its retail system for that.

34How do you integrate with TallyPrime: XML, JSON or ODBC?

Integrate by sending XML, or JSON from TallyPrime 7.0, over HTTP to the running TallyPrime application, and use ODBC only to read. TallyPrime acts as an HTTP server on port 9000 by default when you enable it, accepts Import, Export and Execute requests, and needs to know which loaded company the data belongs to. Tally's integration documentation describes no webhooks and no OAuth, so a cloud system cannot be told when something changes in Tally.

The shape of a Tally integration

• A connector inside the factory's network. Tally usually runs on an office PC behind the router. A small service on the same network talks to Tally on localhost or the LAN, and to the cloud outbound over HTTPS, so no port is opened to the internet.
• Tally must be running with the company loaded. The HTTP interface is served by the TallyPrime application itself, and Tally's JSON documentation requires the loaded company's name. If the PC is off, or TallyPrime is open on another company, the connector waits and retries; it never guesses.
• Polling, not events. The connector asks Tally for vouchers changed since the last run. Tally keeps an AlterID that it uses for its own synchronisation; reading vouchers above the last AlterID seen is a common approach. Test it on your release.
• Permanent ids. Tally keeps a MasterID for every master and voucher and a GUID built from the company's GUID. Store one of them as the link, never the voucher number.
• TDL differs by site. Custom fields added by one factory's partner do not exist in the next factory's Tally. A connector reads standard fields unless the site's TDL is documented.

With TallyPrime Cloud Access, Tally runs in Tally's hosted environment rather than on the office PC; check with Tally how an integration connector reaches the HTTP interface there before designing for it.

POST http://localhost:9000

<ENVELOPE>
 <HEADER>
  <VERSION>1</VERSION>
  <TALLYREQUEST>Import</TALLYREQUEST>
  <TYPE>Data</TYPE>
  <ID>Vouchers</ID>
 </HEADER>
 <BODY>
  <DESC><STATICVARIABLES>
   <SVCURRENTCOMPANY>Polo Exports Pvt Ltd</SVCURRENTCOMPANY>
  </STATICVARIABLES></DESC>
  <DATA><TALLYMESSAGE>
   <VOUCHER VCHTYPE="Purchase Order" ACTION="Create">
    ... party, date, stock item "Navy jersey 180", 925 kg ...
   </VOUCHER>
  </TALLYMESSAGE></DATA>
 </BODY>
</ENVELOPE>

How does MerchandiserOS connect to Tally?

MerchandiserOS publishes an ERP API that a Tally connector can call: it collects approved purchase requests and other documents, and sends Tally's purchase-order numbers back for a person to approve. No money amounts travel through it.

POST /api/v1/erp/po-status
Idempotency-Key: tally-po-7c2e19a4-0000481b-create

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "7c2e19a4-5b0d-4e8f-9a61-2d3c4b5a6f70-0000481b",
           "erp_po_number": "PO/0457",
           "status": "Open",
           "date": "2026-10-21"}]}

The no-code option. Where nobody will run a connector, the same exchange works as files: MerchandiserOS exports the documents, the accountant imports them into Tally, and Tally's purchase-order numbers go back as a file that a person reviews before anything changes.

·Glossary of apparel and Tally terms

Short definitions of the apparel and TallyPrime terms used in this guide.

Alternate unit

In Tally, a second unit for a stock item, such as kilograms for fabric kept in metres, with a conversion that can be changed per voucher.

AQL

Acceptance quality limit: an inspection method that checks a random sample from a lot and accepts or rejects it by the defects found, using ISO 2859-1 tables.

Batch

In Tally, an identified quantity of a stock item, optionally with manufacturing and expiry dates; used here as a dye lot or roll.

BoM

Bill of materials: the components and quantities to make one item. In Tally, lines can be components, co-products, by-products or scrap.

Buying agent

A business that sources and follows orders for buyers across factories and earns a commission, holding no stock.

Chargeback

An amount a buyer deducts from a payment for a claimed failure, such as a late shipment or wrong label.

CM, CMT

Cut and make, or cut, make and trim: the labour charge for making a garment, and the model where the buyer supplies the fabric.

Co-product

In a Tally BoM, a second item produced alongside the main one; used here for second-quality garments.

Cost centre

In Tally, a unit to which income and costs are allocated; with job costing, one per order gives profit per order.

Dye lot

A batch of fabric dyed together; pieces from different dye lots can differ in shade and must not be mixed in one garment.

Ex-factory

The date goods leave the factory for shipment.

FOB

Free on board: the price of goods loaded at the port of shipment; the usual quoted price per piece in garment trade.

Godown

In Tally, a storage location; used here for stores, production stages, QC hold and each job worker.

GSM

Grams per square metre: the weight of fabric.

GUID, MasterID, AlterID

Identifiers Tally keeps for masters and vouchers: the GUID is built from the company's GUID, the MasterID is unique per object, and the AlterID changes when a record is altered.

IRN

Invoice reference number: the number India's e-invoice system issues for a registered invoice.

ITC-04

The Indian GST form in which a principal reports goods sent to and received from job workers.

Job work

Processing of one business's goods by another, which returns them; in garments, CMT, embroidery, printing and washing.

Lab dip

A small dyed fabric sample sent to the buyer to approve a shade before bulk dyeing.

Landed cost

Every cost of bringing goods to the factory or warehouse beyond the supplier's price: freight, insurance, duty, clearing, bank charges.

Letter of credit (LC)

A bank's promise to pay an exporter when documents matching the credit's terms are presented.

Manufacturing Journal

A mode of Tally's Stock Journal that records production: components consumed and items produced by a BoM, with additional costs.

Own-label retailer

A retailer that develops and sells clothing under its own label, made by factories.

PP sample

Pre-production sample: a garment in bulk fabric and trims that the buyer approves as the reference for production.

Stock group, stock category

In Tally, two independent ways to classify stock items; used here for material type and season.

Stock Journal

A Tally voucher that moves stock between godowns or records consumption and production without a sale or purchase.

Style/colour/size matrix

A grid of colours by sizes that defines every sellable version of a style.

T&A calendar

Time and action calendar: an order's milestones with dates worked back from ex-factory, actual dates and owners.

TDL

Tally Definition Language: Tally's language for customising and integrating the product, compiled into TCP files.

TSS

Tally Software Services: the subscription that comes with a licence and covers upgrades and online services.

·Checklists: a TallyPrime apparel set-up on one page

The checklists below repeat the decisions and checks from each part of this guide, in project order.

Discovery

• Business type settled for each buyer: CMT (job worker), full package, or both; or brand, agent or own-label retailer.
• One decision owner named per area.
• All 52 fit-gap lines answered with evidence, decision and owner.
• What Tally holds and what sits outside it, agreed in writing.
• Edition and TSS renewal confirmed.

Design

• Stock groups, categories and valuation method.
• Stock item code pattern; items created by import.
• Main and alternate units per material; both units on fabric receipts.
• Batch meaning: dye lot, roll or both.
• Per-size BoMs with co-products and scrap.
• When the Manufacturing Journal is posted.
• Godowns per stage and per job worker.
• Additional-cost ledgers and appropriation methods.
• Cost centre per order; forex; chargeback ledgers; GST and e-invoicing.

Build, data and testing

• Set-up done in dependency order on the go-live release.
• TDL register with owners and a release test plan.
• Connector linked on MasterID or GUID; safe to repeat; waits when Tally is closed.
• Import loaded in order, with a cut-off rule and signed totals.
• All 13 end-to-end scenarios passed by key users.

Go-live

• Stores and production staff trained on batch-wise and job work vouchers.
• Cut-over rehearsed once.
• Go-live between seasons, away from year-end and audits.
• Hypercare until the first month-end close and GST filing.

·Sources

Tally Solutions pages were checked on 26 September 2026. Menu paths are from the TallyPrime help pages current at that date (TallyPrime 7.x).

1. TallyPrime, Inventory management features (BoM, by-products, scrap, job work, batches, valuation methods) · tallysolutions.com
2. TallyPrime help, Manage inventory in manufacturing (BoM, component types, Manufacturing Journal, Stock Journal, Cost Estimation) · help.tallysolutions.com
3. TallyPrime help, Job Work Out for a principal manufacturer · help.tallysolutions.com
4. TallyPrime help, Job Work In for a job worker · help.tallysolutions.com
5. TallyPrime help, Manage inventory batch-wise · help.tallysolutions.com
6. TallyPrime help, Stock items FAQ (alternate and compound units, per-voucher conversion) · help.tallysolutions.com
7. TallyPrime help, Additional cost of purchase · help.tallysolutions.com
8. TallyPrime help, Job costing with cost centres · help.tallysolutions.com
9. TallyPrime help, Multi-currency and forex gain or loss · help.tallysolutions.com · help.tallysolutions.com
10. TallyPrime help, Generate e-invoice (IRN) and e-way bill · help.tallysolutions.com · help.tallysolutions.com
11. TallyPrime help, Licensing (Silver, Gold, Server, TSS) · help.tallysolutions.com
12. TallyPrime Cloud Access · tallysolutions.com
13. TallyPrime help, XML integration (HTTP server, port 9000, envelope) · help.tallysolutions.com
14. TallyPrime help, Integration using JSON (TallyPrime 7.0, headers, loaded company) · help.tallysolutions.com
15. TallyPrime help, Integration methods and technologies · help.tallysolutions.com
16. TallyPrime help, ODBC integration · help.tallysolutions.com
17. TallyPrime developer reference, identifying vouchers (MasterID) and synchronisation (AlterID) · help.tallysolutions.com · help.tallysolutions.com
18. TallyPrime developer reference, Tally Definition Language and deploying TDLs · help.tallysolutions.com · help.tallysolutions.com
19. Zoho Inventory, manufacturing support and composite items · zoho.com · zoho.com
20. ISO 2859-1, Sampling procedures for inspection by attributes · iso.org
21. AQL tables and acceptance numbers · qima.com

Corrections. Tally Solutions releases TallyPrime regularly, and a menu path or a feature can change in a single release. If you find a statement here that your release contradicts, report a correction with the release and the page you checked; we correct the guide and note the change and its date at the top of this section. We re-check the Tally facts in this chapter at least once a year and after each major TallyPrime release.

TallyPrime and Tally are trademarks of Tally Solutions Pvt. Ltd., used here only to name the products. This guide is not endorsed by Tally Solutions. Zoho is a trademark of Zoho Corporation. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.