Manufacturing software that tracks each job from cutting table to shelf

It is the JAI CRM module for making things when a job takes time. You write a bill of materials (the parts and steps for one item), raise a manufacturing order, and release it to the floor as job cards on stations. The system tracks work in progress, time in minutes, quality inspections where you have a rule, and what each run actually cost against the estimate.

Yes. The manufacturing module requires Inventory. Every component out and every finished item in goes through the Inventory stock ledger, the same one a delivery challan or goods receipt uses. Bills of materials live in Inventory too, and an active BOM has a "Make some" button that opens a new run, already filled in.

Work in progress is the gap between two stock entries. Components leave the shelf when a run starts. The finished item arrives when the run completes. In between, the value sits on the run itself, and the actual materials cost is written onto it as they come off. So half-made goods count neither as raw material you could issue nor as finished stock you could sell.

Probably not, and we would rather tell you so. An assembly is one act in one stock entry: components out and finished item in, at the same moment. It is the right answer for a gift box made up at the counter, or a table put together in an afternoon. Assemblies stay exactly where they are and keep working. This module is for what an assembly cannot show: a job that takes long enough that someone has to answer where the goods are halfway through. If you never need to answer that, use assemblies and skip all of this.

Yes, and that is the normal case, not a special one. A hand-made sample run and a machine production run are two BOMs for one shirt. The order screen offers only active BOMs. So retiring a BOM stops it being chosen for new runs without deleting anything. Orders already raised from it are untouched, because they copied what they needed at the time. If someone tries to start a run from an inactive BOM, it is refused. The message tells you to mark it active again if it is still how the item is made.

Confirming an order raises a child run for every component that has its own active BOM. Each child run is already confirmed, takes the same warehouse, owner and start date, and is linked to the parent, so both ends show on the record. A shirt and its cut panel become two orders that know about each other, so nobody has to keep them in step by hand. It goes one level down only, not to the bottom of the tree. Confirming twice does not raise them twice.

No. The refusal tells you how many jobs have not finished and what they are called. Marking the order done anyway would say the shirt was sewn by a card that says it never started, and the costing would believe the order instead of the floor. Quality works the same way on a released run: completion is refused while any inspection on it has not passed.

Yes, and it is a proper option, not a fallback. The worker gives a start and an end, and the minutes are saved. The only check is that the end is after the start, which catches a wrong date as well as a wrong time. Offering only a timer makes shops like this make up numbers, and made-up numbers are worse than none. Either way, a card's minutes are the sum of its time logs and are never typed in directly, so the card and the logs cannot disagree.

Yes. Confirming and releasing need the approve permission, which is separate from edit. So someone who can fix a typo on a draft cannot commit the floor to building it. Creating an order with "confirm" already ticked checks for approve too, because signing off while creating is still signing off. Permissions are set separately for orders, job cards, work centres and operations. The menu shows only the sections each person can actually use.

Every component that left the shelf goes back through the stock ledger. All unfinished job cards are force-closed, and the reason you give is added to the notes. The actual component cost is cleared back to empty, not to zero, because "nothing yet" and "it cost nothing" are different facts. Cancelling a draft undoes nothing, because nothing was done. A cancelled run cannot be brought back. Raise a new one instead, so the abandoned run stays on record as abandoned.

Only for items where you have written a quality rule. For those, releasing the run raises the inspection straight away, not when someone wants to close it, so the inspector gets notice. A released run cannot complete until it has passed. The order also names the rule that applies before any inspection exists, so the screen can say one is coming instead of implying there is nothing to do. Where there is no rule, nothing is in the way.

Yes, by warehouse, and the restriction applies to the buttons, not just the list. Opening the record, opening the cost view, confirming, releasing, starting, completing, cancelling and setting tracking each check again whether that user may touch that record, for read or write as needed. A restriction that covered the list and the comment feed but not the button that moves stock would not be a real restriction.

Numbers follow the Indian financial year, and GST does not attach to the run itself. BOMs, runs and job cards each have their own number series. A run raised today reads MO/2026-27/0001, with four digits, and the counter resets on 1 April, not 1 January. Making something is a stock and cost event, not a tax document. The HSN code (the product code used for GST) and the GST rate live on the item the run makes, so the finished goods invoice at the right rate the moment they are sold.