·6 min read
Production Order Tracking for Garment Konveksi: Know Where Every Order Is From Cutting to Delivery
Missed deadlines, missing pieces and endless 'where is my order?' calls usually come from one gap: nobody records what happens at each production stage. Here is how small konveksi can track orders stage by stage, count pieces per tailor and log rejects, starting with a simple spreadsheet.
- garment
- konveksi
- production tracking
- made-to-order
- work in progress
- piece rate
- quality control
- sme
It is three weeks before the new school year. You have 40 open orders: 1,200 school uniforms, 300 polo shirts for a bank branch, a run of event T-shirts with sablon, and a batch of embroidered jackets. The phone keeps buzzing with the same question: 'where is my order?' To answer it, you walk down to the workshop, ask the cutter, call two outside tailors and flip through a notebook. Production order tracking for garment konveksi solves exactly this problem: one place that shows which stage every order is in, how many pieces are where, and what has been rejected. This post explains how to set it up, starting with tools you already have.
Why orders get lost between stages
A typical konveksi order passes through five or six pairs of hands: cutting, sewing (often by makloon tailors working from home), sablon or bordir (sometimes at another vendor), quality control, ironing and packing. Every handover is a point where information can disappear.
The usual symptoms:
- Counts drift. You cut 500 pieces, the tailor returns 488, and nobody knows whether the other 12 are still being sewn, were damaged, or went missing.
- Delays are discovered too late. The sablon vendor is two days behind, but you only find out on the day the order should ship.
- Pay disputes. A tailor says she returned 300 pieces, your notebook says 280, and there is no record that both of you trust.
- The owner becomes the tracking system. Everything lives in your head and your WhatsApp chats, so you cannot take a day off.
None of this is caused by lazy staff. It happens because nothing records the order at each stage in a consistent way.
What production order tracking for garment konveksi looks like
Good tracking does not need to be complicated. It rests on three ideas.
1. Every order moves through the same fixed stages
Define your stages once, for example: Waiting for fabric, Cutting, Sewing, Sablon/Bordir, QC, Packing, Ready to ship, Delivered. Every order moves through them in the same order (some simply skip sablon). When you look at the list, you can see at a glance that six orders are sitting in Sewing and two are waiting at the sablon vendor.
2. Count pieces at every handover
This is the rule that does most of the work. Whenever pieces change hands, someone writes down how many, per size, with the date. Then one simple check must always balance:
Pieces received = pieces passed on + pieces rejected + pieces still in process
If 500 went to sewing and 488 came back, the record must say where the other 12 are. That single habit is what stops pieces from quietly disappearing.
3. A due date per stage, not just per order
If the customer deadline is the 20th, work backwards: packing done by the 19th, QC by the 18th, sablon back by the 16th, sewing back by the 13th. Now a delay in sewing shows up on the 13th, while you still have a week to react, add a tailor, or warn the customer honestly instead of making excuses on the last day.
Piece counts per worker and outside tailors
Most konveksi pay sewing by the piece (borongan). That means piece counts per worker can double as your payroll record.
For each tailor, in-house or makloon, log:
- Date and order number
- Item and size (for example, school shirt, size M)
- Pieces taken out (cut panels, usually in bundles)
- Pieces returned finished, and pieces returned as rejects
At the end of the week, good pieces multiplied by the rate gives the pay. If the rate is Rp 5,000 per shirt and a tailor returned 320 good shirts, that is Rp 1,600,000, backed by a record both sides can check. Disputes drop sharply when the tailor confirms the count at the moment of handover, not a week later.
The same data shows your real capacity. If you know your five regular tailors return around 1,500 shirts a week between them, you can tell a customer whether 2,000 uniforms in ten days is realistic before you accept the order, not after.
Reject logging that people actually use
Most workshops know they have rejects. Few know how many, why, or where they come from. A reject log needs only a few fields: order, stage, worker or vendor, quantity and reason.
Keep the reasons to a short fixed list so nobody has to type an essay:
- Crooked or loose stitching
- Wrong size or measurement
- Sablon smudged, faded or misaligned
- Embroidery error
- Fabric defect or stain
Also mark whether each piece can be reworked or must be replaced. Replacement means new cutting, and new cutting needs fabric, so you want to know early.
After a month or two, patterns appear. Maybe one tailor runs at 6% rejects while the others sit at 1 to 2%. Maybe most rejects on dark shirts come from one sablon vendor. That tells you exactly where a conversation or a change will pay off. It also helps you set a realistic cutting allowance, for example cutting 2 to 3% extra on large orders instead of guessing.
Start simple: from paper to an app
You do not need to buy software on day one. Here are the realistic options, from cheapest to most capable.
- A job card that travels with the bundle (almost free). A printed card per order with stages, counts and signatures. Better than nothing, but cards get lost, and you still have to walk the floor to see status.
- A shared Google Sheet plus a simple form (free). One tab for orders and stages, one for handovers, one for rejects. Staff fill in the form from their phones. This works well for up to a few dozen active orders. The weak point: it depends on discipline, and formulas break when someone edits the wrong cell.
- Ready-made production or ERP apps (roughly Rp 200,000 to 1,500,000 per month). Quick to start, but many are designed for factories and do not handle makloon tailors or piece-rate pay without awkward workarounds.
- A custom web app (often Rp 25 to 80 million to build, depending on scope). Built around your stages, your tailors and your pay rules, possibly with a status page customers can check themselves. It makes sense once the spreadsheet is clearly holding you back, not before.
Our honest advice: run the spreadsheet version for at least a month. It will show you which fields you actually use and where people skip steps. That knowledge makes any later software cheaper to build and far more likely to fit how your workshop really runs.
This week, pick your five most urgent orders and track only those: fixed stages, counts at every handover and a reject log. Within two weeks you should be able to answer 'where is my order?' without leaving your desk. If you want help turning that sheet into a tool that fits your workshop, CodeWorks can review your current process with you and tell you honestly whether a spreadsheet is enough or a custom app is worth the investment.