Automation in Clothing Manufacturing: What a Small Workshop Can Automate

Order intake, tech pack checking, fabric and cutting-plan sums, production tracking and customer status updates can all be automated today with AI and no-code tools. Pattern making, marker nesting, fit approval and quality judgement cannot. In a workshop of five to fifteen people, the realistic result is a few hours saved per order, not a lights-out factory.

Machine automation, such as robotic sewing or automated cutting, is a different budget entirely. The hours a small workshop loses sit in the paperwork around the machines: retyping purchase orders, chasing a missing measurement, redoing the fabric sum, answering "where is order 1047?" for the fourth time that week.

Follow me on Instagram@sagnikteaches

Every job below follows one pattern. An AI step produces a draft, a control total or a rule tests it, and a person handles whatever fails the test. Nothing here lets an assistant approve a sample or release a cut.

Connect on LinkedInSagnik Bhattacharya

Five jobs and where the line sits

For a broader view of where a small maker might begin, where a small cut-and-sew maker starts with AI covers the first jobs. What follows is the automation wiring, the costs and the limits.

Subscribe on YouTube@sagnikteaches

Order intake: from a brand's email to a checked order row

A brand's order usually arrives as an email, a PDF purchase order and a line of caveats. Typing it into your order sheet takes ten to fifteen minutes and is where transposed quantities begin. An assistant can do the reading; a control total does the checking. Here is a sample email, anonymised:

Hi, PO 1047 attached for the Overshirt in sage and sand.
Sage: S 20, M 60, L 80, XL 40. Sand: S 20, M 60, L 80, XL 40.
Delivery to our warehouse 4 Dec. Same trims as last time, but swap
the main label for the new one. Can you confirm the price per piece?

Extract the order below into one row per colour and size.
Fields: PO number, style, colour, size, quantity, delivery date.
Then give: total quantity per colour, total for the order, and a list headed
ASK with every detail that is unclear or needs a decision from us.
Do not guess. Quote the words you relied on.

An illustrative reply:

PO 1047 | Overshirt | Sage | S20 M60 L80 XL40 = 200
PO 1047 | Overshirt | Sand | S20 M60 L80 XL40 = 200
Order total: 400 | Delivery: 4 Dec
ASK:
1. "Same trims as last time": which order? Need the trim list.
2. "The new label": artwork or file not attached.
3. Price per piece: not stated; brand is asking us to confirm.

The value is in the ASK list and the totals. The control rule is simple: size quantities must sum to the colour total and the colour totals to the PO total (200 and 200 give 400 here). If the sums disagree, the order goes to a person before it touches the sheet. The classic extraction slip is a misread digit in a scanned PDF, such as 80 read as 30, and a control total catches it where a glance does not. Run it by hand first with a chat assistant for a week; if the answers hold, wire it up.

The automated version: a mail rule labels emails with attachments from known brands; a Zapier or Make scenario picks them up, sends the text and PDF to an AI step, writes the rows to a Google Sheet, and sends the admin a message if a control total fails or the ASK list is not empty. In Zapier, triggers and filters do not count as tasks while each successful action step does. At 42 order emails a month and three action steps each, that is about 126 tasks, inside the 750 of the Professional plan ($19.99 a month billed annually) and above the 100 on Free. AI steps are metered more heavily than plain steps on both platforms, so check the current page before you rely on the estimate.

Tech pack checks: a ready-to-cut list the assistant applies

A tech pack tells the workshop what to make: sketches, a measurement chart, the bill of materials, construction notes, labels and packing. Brands send them in every state of completeness, and the cost of a missing detail arrives after the fabric is cut. Write your own minimum, a ready-to-cut list, and let the assistant apply it:

1. Style code, name and version date on every page.
2. Size range and base size.
3. Measurement chart for every size, in one unit.
4. Tolerances for each measurement.
5. Main fabric: composition, weight, width, shrinkage allowance, colourways.
6. Trims: thread, zips, buttons, interlining, labels, each with size or colour.
7. Construction notes: stitch types, seam allowances, hem depths.
8. Label and trim placement.
9. Pressing, finishing and packing instructions.
10. Who signs off the fit sample and pre-production sample.

Compare the attached tech pack with my ready-to-cut list [paste the ten items].
For each item give PRESENT, MISSING or UNCLEAR, the page number, and the
question to ask the brand. Then list any measurement inconsistencies: mixed
units, and size-to-size increments that break the pattern. Quote the text you
relied on. Do not fix or assume anything.

1 Style code/version: PRESENT p1; version date missing on p3-p5. Ask: which is current?
3 Measurement chart: PRESENT p2, sizes S-XL, cm. Notes on p4 use inches.
4 Tolerances: MISSING. Ask: tolerance per measurement?
5 Fabric: UNCLEAR. Width stated for main fabric, not for lining.
6 Trims: UNCLEAR. Zip length given, zip type missing; thread colour missing.
7 Construction: UNCLEAR. Hem stitch type not stated; seam allowance not stated.
Measurement check: chest width S 52, M 55, L 58, XL 62 cm. Increments 3, 3, 4.
  Last step breaks the pattern. Ask: intended, or a typing error?

That output is worth ten minutes of a cutter's reading. It also shows where the assistant stops. It spotted a grading step that breaks the pattern, but it cannot tell whether a 55 cm chest width on a size M produces a shirt that fits the brand's model. That is the pattern cutter's judgement, and no prompt replaces it. A second limit is reading accuracy: ask it to quote the numbers back with their page references, and have a person verify three of them against the PDF. A scanned chart with a stray mark can turn 58 into 53.

One more rule before you paste anything: designs belong to the brand. Check any confidentiality agreement you have signed, use an account that does not train on your content by default or has the model-training setting switched off, and tell the brand what you use if the contract asks you to. The brand-side view of drafting specs a factory can use shows what a good pack looks like when it arrives.

Sample rounds: a fit-comments log that closes

Sampling produces the messiest text in a workshop: fit comments in emails, photos with arrows drawn on them, voice notes. A comments log, one row per comment with an action and a status, turns that into a list someone can close. Paste the brand's feedback and ask for the log:

Turn this feedback on sample 1 into a log. Columns: number, area, comment
(quote it), type (Fit, Make or Spec change), action and who does it, status.
If a comment is not measurable, say what we must ask. Do not decide anything.

Feedback: "Sleeve a touch long, back hem pulls when arms are raised, shoulder
seams fine, button spacing uneven near the collar, can the pocket sit 1 cm higher?"

1 | Sleeve      | "a touch long"                 | Fit         | Ask the brand how much (admin)          | Open
2 | Back hem    | "pulls when arms are raised"   | Fit         | Cutter checks the pattern (cutter)      | Open
3 | Shoulder    | "fine"                         | OK          | None                                    | Closed
4 | Buttons     | "spacing uneven near collar"   | Make        | Check the marking jig (sewing lead)     | Open
5 | Pocket      | "1 cm higher"                  | Spec change | Brand to confirm in a new tech pack     | Open

Three details make this useful. "A touch long" is not a measurement, so the log turns it into a question for the brand rather than a guess by the cutter. The pocket move changes the specification, so it waits for a revised tech pack version before anyone cuts. And the last column belongs to people: "approved" needs a name and a date, entered by whoever signed the sample off. The assistant sorts the comments; it never closes one.

Cutting plans: the fabric sum, the lay plan and where CAD takes over

The cutting plan has two parts. The fabric requirement is arithmetic, and a sheet can do it. The marker, the nesting of pattern pieces on the fabric to waste as little as possible, is an optimisation that pattern software or an experienced cutter does. The fabric sum for the 400-piece order above:

Add an allowance for ends of lays and roll splices; 3% is an illustrative figure, so use your own history. That gives 649.7 metres, but sage and sand are different fabrics, so order by colour: 324.9 metres each. If the mill sells rolls of about 100 metres, that is four rolls of each colour, eight in all, with about 75 metres of each left over. Rounding the combined total instead says seven rolls and leaves one colour short, which is exactly the slip a sheet without a colour column makes. The size ratio 40:120:160:80 simplifies to 1:3:4:2, ten garments per marker, so the plan is a ten-garment marker spread across 40 plies, 20 in each colour. The sheet holds those numbers and the assistant explains them; it does not draw the marker.

Build a Google Sheet for a cut order. Inputs: order quantity by colour and size,
consumption per garment by size (metres), fabric width, wastage allowance %,
roll length. Outputs: fabric needed per size and in total, total with
wastage, rolls to order per colour (rounded up), size ratio simplified to the lowest
whole numbers, garments per marker and plies needed. Use formulas, not typed
numbers, and add a check that quantities by size sum to the order total.

The honest limit sits in the consumption figures. They come from your own markers on earlier runs, or from the pattern software, not from the assistant, and a wrong consumption number is the one that scales: a 1% error on 650 metres is 6.5 metres, and on a long run of orders it is whole rolls. Whether AI can replace CAD for pattern making explains why the marker stays with specialist software.

Answering "what is the price per piece" from the same sheet

The ASK list in the order email included the price. The fabric figure from the cut sheet now feeds a quick costing, which the assistant can lay out and you can fill from your own numbers. Illustrative sums for the 400-piece order:

The assistant's job is the layout and the arithmetic check. The inputs, especially the 34 minutes, are yours: time a few garments on the line instead of using a figure from a book. A price from this table goes back to the brand as a draft you approve, not an auto-reply. Costing a style from its tech pack goes deeper on each line.

Production tracking: station scans, a live sheet and a daily summary

Status-chasing eats hours because the answer lives in people's heads. A cheap fix is a form at each station. Pin one QR code at cutting, sewing, pressing, quality check and packing. A machinist scans the code, enters the order number, bundle number and quantity (and, at sewing, the machine number if you want faults traced later), and taps submit. Google Forms can build a pre-filled link, through More, then Pre-fill form, then Get link, so the station code can fill the stage field for you. The responses land in a sheet, and a summary reads the sheet.

Choose your granularity with the platform limits in mind. Tracking each bundle through each stage means 40 bundles of ten across five stations, or 200 records per order. Airtable's Free plan caps a base at 1,000 records and 100 automation runs, so five orders fill it. Its Team plan lists $20 a seat a month billed annually for 50,000 records. AppSheet lists Starter at $5 and Core at $10 per user a month with a 2,500-row cap per database on both, which is about twelve orders at 200 records each, and Core adds barcode and NFC scanning. Google Sheets holds far more than a workshop will log. Tracking per order per stage cuts the load to five records per order if bundle-level detail is not worth the scanning.

A scheduled automation reads the sheet each evening and asks an assistant to summarise. An illustrative output:

Order 1047, Overshirt, 400 pcs, due in 5 days (dispatch on day 4)
Cut 400 | Sewn 260 | Pressed 180 | QC passed 150 | QC failed 8 | Packed 120
Sewing: 140 left at about 70 a day = 2 days.
Pressing: 220 left at about 60 a day = 3.7 days. Pressing is the constraint.
Delivery looks achievable only if pressing does not lose a day.
Question for the manager: move a machinist to pressing for two days?

The assistant states the arithmetic and leaves the decision to the manager. The 80-piece gap between sewn and pressed is 1.3 days of pressing, which is a number a person can act on first thing in the morning rather than discover on Friday. For a broader template, summarising counts, scrap and stops each day covers the report format, and scanning stock in and out from a phone shows the scanning side of an AppSheet build.

A realistic failure: the summary said 120 pieces packed and the shelf held 104. The cause was a scanning habit, not the software. Packers scanned a bundle in when it reached the station rather than out when it was finished, so 16 pieces still on the table counted as packed. The fixes were a rule (scan at completion), a label on the form ("bundle finished"), and a weekly count of one stage against the sheet. Expect one such mismatch in the first fortnight; it is how the sheet earns trust.

The same sheet can feed customer messages. Ask the assistant to draft a status update from the latest row, in your usual tone, and mark anything about a delay or a defect for you to read and send yourself. The routine updates, such as "cut and into sewing, on track for 4 December", can go out on a schedule.

Defects: a weekly digest from the quality-check form

The quality-check station form is where free text hurts. Give it a dropdown for the defect type (skipped stitches, uneven topstitch, loose threads, stain, other), a quantity and an optional note. Dropdown answers can be counted; "hem funny" cannot. Once a week an assistant can tidy the notes into categories and write the digest. An illustrative week:

Week 47: 410 pieces inspected, 31 failed (7.6%).
Skipped stitches at hem: 14 | Uneven topstitch at collar: 8 | Loose threads: 5
Stains: 3 | Other: 1
Change on last week: hem defects up from 6 to 14.
11 of the 14 hem failures were logged against bundles sewn on machine 3.

The digest points; it does not diagnose. A person checks the needle, tension and operator handover on machine 3 before anyone concludes it is the machine. The sums are worth checking too: 14 + 8 + 5 + 3 + 1 is 31, and 31 of 410 is 7.6%. If the machine column is missing from the form, the assistant cannot invent it, and the digest should say "machine not recorded" rather than guess. That is the other reason to keep fields to what you will really use.

What the stack costs and what a month saves

The minimal stack is $40 a month (Zapier plus an assistant), or about $70 with AppSheet Core for three stations. Set-up is the real cost, perhaps 30 to 40 hours of the owner's time. For a workshop with eight staff and 14 orders a month (all figures illustrative), the minutes per order look like this:

Over 14 orders that is about 47 hours a month. At a loaded $25 an hour (use your own figure), it is roughly $1,180 of time a month against $40 to $70 of subscriptions. Time saved is not cash unless it goes somewhere: more orders handled, fewer late nights, fewer remakes. The numbers are also the most optimistic part of any plan like this, so measure your own on one live order before you believe them.

Honest limits: what this stack cannot do

• Pattern making and grading. A chat assistant is not a pattern system. It can check a grade table for inconsistencies, not draft production patterns you would cut from.
• Marker nesting. The efficiency of a marker comes from CAD or an experienced cutter. The sheet gives a consumption estimate to plan with, not the marker.
• Fit and sample approval. A person with the sample on a body decides. The assistant can list the brand's fit comments and track which are resolved.
• Defects, shade and handle. Do not rely on a phone photo and an assistant to judge a fabric fault or a shade match. Inspection stays physical.
• Sewing times. Use your own timings from past runs. An assistant has no idea how long your team takes to set a collar.
• Labels and regulated content. Fibre content, care labels and restricted-substance rules differ by market and change. An assistant can state them with confidence and be wrong; confirm with an official source for the market you sell into.
• Confidential designs. Check every client's confidentiality terms before their files go near a chat tool.

A two-week trial on one live order

Pick an order that has not started. Run the new flow beside your normal routine and score it.

If an item fails, fix the rule or the habit before widening to a second order, because a wrong total repeated across ten orders is worse than a slow manual one. When the trial passes, keep the manual routine alive for one more order and then retire it.

Questions from small workshop owners

Do I need a paid AI plan for these jobs?

One-off checks, such as a tech pack review, can run on a free plan. Automations that fire on every email need an account that connects to your mail and sheets, and client designs deserve a plan with model training off by default. Budget about $20 a month for an individual plan, or the business seat price with its two-seat minimum.

How many orders a month before tracking is worth building?

My rule of thumb: if someone spends more than half an hour a day answering where an order is, build it. Below about ten orders a month, a shared sheet updated by hand may be enough. Start with one live order either way, and count the minutes before and after before you widen it.

What if my machinists will not scan or fill in forms?

Keep the form to four fields and put the code at the station, not on a clipboard. Test it at one station for a week on a shared tablet. Make the scan replace something they already do, such as ticking the bundle ticket, rather than adding a job. Review missing scans weekly with the team, not as a reprimand.

Can the same set-up handle sampling as well as production runs?

Yes, with a separate status list. Sample rounds have different stages (first sample, fit comments, revised sample, approval) and a few pieces rather than hundreds, so give them their own sheet and form. Keep the approval stage a person's decision, because a sample sign-off is a judgement about fit and finish.

Further reads

• Quoting Custom Jobs Faster With AI in a Small Workshop — Quote custom jobs faster once the intake is tidy.
• No-Code AI Tools vs a Custom Build: When Templates Stop Working — When templates stop working and a custom build starts to pay.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Airtable and AppSheet pricing pages, Google Forms help (pre-filled links), Zapier and Make plan details (checked October 2026). Order sizes, fabric figures, minutes and costs in the examples are illustrative.