<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
  <title>UniformsOS Blog</title>
  <link>https://uniformsos.com/blog</link>
  <atom:link href="https://uniformsos.com/blog/rss.xml" rel="self" type="application/rss+xml" />
  <description>Plain guides on factories, products and SKUs, jerseys, production tracking, team stores, pricing and the software that runs a custom apparel shop.</description>
  <language>en-us</language>
  <lastBuildDate>Fri, 20 Nov 2026 00:00:00 GMT</lastBuildDate>
  <item>
    <title>Apparel ERP software: what it does and how to choose one</title>
    <link>https://uniformsos.com/blog/apparel-erp-software-guide</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/apparel-erp-software-guide</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Apparel software</category>
    <description>What apparel ERP software covers, how it differs from accounting, PLM and shop management tools, and which type fits which apparel business.</description>
    <content:encoded><![CDATA[<p>Apparel ERP software runs the operating core of an apparel business in one system: products with size and color variants, quotes and orders, purchasing, production tracking, inventory, invoicing and reporting. Choose it by how you make money: stock, made to order or team sales. The test is whether one order can go from quote to shipment without being retyped.</p>
<h2 id="what-erp-means-in-apparel">What ERP means in apparel</h2>
<p>ERP stands for enterprise resource planning. In plain terms it is the one system where orders, products, purchasing, production and money are connected, so a change in one place shows up in the others.</p>
<p>Generic ERP systems struggle with apparel for four reasons:</p>
<ul>
<li>The size and color matrix. One style is dozens of variants, and people need to enter and read them as a grid.</li>
<li>Decoration. The same blank becomes a different product once artwork, names and numbers go on it.</li>
<li>Made to order. Many apparel orders are produced after the sale, with a roster attached.</li>
<li>Outside factories. Production often happens at another company, and you still have to know where every order is.</li>
</ul>
<p>Software that calls itself apparel ERP should handle all four without workarounds.</p>
<h2 id="what-it-covers">What it covers</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Area"><table>
<thead>
<tr>
<th>Area</th>
<th>What it handles</th>
<th>What apparel adds</th>
</tr>
</thead>
<tbody><tr>
<td>Products</td>
<td>Styles, variants, pricing</td>
<td>Size and color grid, decoration options</td>
</tr>
<tr>
<td>Sales</td>
<td>Quotes, orders, approvals</td>
<td>Artwork <a href="https://uniformsos.com/glossary/art-proof">proofs</a>, rosters with names and numbers</td>
</tr>
<tr>
<td>Purchasing</td>
<td><a href="https://uniformsos.com/glossary/purchase-order">Purchase orders</a> to factories and suppliers</td>
<td>One order split across factories</td>
</tr>
<tr>
<td>Production</td>
<td>Stages and <a href="https://uniformsos.com/glossary/wip">work in progress</a></td>
<td>Days in stage, ship-by dates</td>
</tr>
<tr>
<td>Inventory</td>
<td>Stock by variant</td>
<td>Blanks and finished goods</td>
</tr>
<tr>
<td>Finance</td>
<td>Invoices, payments</td>
<td>Deposits and balances, sync to accounting</td>
</tr>
<tr>
<td>Customers</td>
<td>Accounts, contacts, history</td>
<td>Teams, schools, leagues, reorders</td>
</tr>
<tr>
<td>Online stores</td>
<td><a href="https://uniformsos.com/glossary/team-store">Team stores</a> and customer portals</td>
<td>Timed stores, bulk checkout</td>
</tr>
<tr>
<td>Reporting</td>
<td>Sales, margin, on-time rate</td>
<td>By rep, by factory, by product</td>
</tr>
</tbody></table>
</div>
<p>Few businesses need every row on day one. Most need three or four of them to work together.</p>
<h2 id="erp-and-its-neighbors">ERP and its neighbors</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Tool"><table>
<thead>
<tr>
<th>Tool</th>
<th>What it is for</th>
<th>Where it stops</th>
</tr>
</thead>
<tbody><tr>
<td>Accounting software</td>
<td>The books: ledger, tax, payroll</td>
<td>It does not know where an order is on the floor</td>
</tr>
<tr>
<td>PLM</td>
<td>Developing products: <a href="https://uniformsos.com/glossary/tech-pack">tech packs</a>, samples, costing before the sale</td>
<td>It ends where orders begin</td>
</tr>
<tr>
<td>Shop management for decorators</td>
<td>Quotes, art approvals and job scheduling for print and embroidery shops</td>
<td>Usually light on factories and inventory</td>
</tr>
<tr>
<td>E-commerce platform</td>
<td>The storefront and checkout</td>
<td>It does not run production</td>
</tr>
<tr>
<td>Spreadsheets</td>
<td>Anything, for one person</td>
<td>They break when two people edit and nothing updates itself</td>
</tr>
</tbody></table>
</div>
<p>An ERP does not replace accounting software. It feeds it.</p>
<h2 id="match-it-to-how-you-make-money">Match it to how you make money</h2>
<p>A stock brand sells from inventory to retailers and consumers. It needs inventory by variant, allocation, wholesale ordering and often EDI with retailers. This is the classic apparel ERP.</p>
<p>A made-to-order team dealer sells uniforms and gear to teams, schools and leagues. It needs fast quoting, artwork approval, rosters, team stores, factory purchase orders and production tracking. Inventory matters much less.</p>
<p>A decorator prints or embroiders for other businesses. It needs job scheduling, art approval and blank purchasing.</p>
<p>A factory makes for brands and dealers. It needs production planning, capacity and materials.</p>
<p>Buying the wrong type is the most common mistake. A stock-brand ERP makes a team dealer fight the software on every roster.</p>
<h2 id="how-to-choose">How to choose</h2>
<ol>
<li>Write down the path one order takes, from first inquiry to delivery. Mark every point where someone retypes it or has to remember to send something.</li>
<li>Turn those marks into your must-have list. Leave the nice-to-haves for later.</li>
<li>Run the demo with your own order. Bring a hard one: three products, forty players with names and numbers, two factories, a deposit and a late change.</li>
<li>Check how data gets in and out. Can you import products and customers? Can you export everything if you leave?</li>
<li>Check the connections you rely on: accounting, payments, shipping.</li>
<li>Ask for the total cost of the first year. Subscription, users, setup, training and any modules priced separately.</li>
<li>Talk to a customer of the vendor who is your size and sells the way you do.</li>
<li>Pilot with one rep or one product line before moving everyone.</li>
</ol>
<h2 id="questions-to-ask-the-vendor">Questions to ask the vendor</h2>
<ul>
<li>Can I enter an order as a size grid, and add a roster to it?</li>
<li>Does the customer approve artwork inside the system?</li>
<li>Can one order produce purchase orders to more than one factory?</li>
<li>Can a factory update its own status, and can I limit what it sees?</li>
<li>What does my customer see, and can they pay there?</li>
<li>What happens to my data if I cancel?</li>
<li>Who do I call when something breaks, and how fast do they answer?</li>
</ul>
<h2 id="signs-you-have-outgrown-spreadsheets">Signs you have outgrown spreadsheets</h2>
<ul>
<li>The same order is typed three times: the quote, the factory sheet and the invoice.</li>
<li>Nobody can answer &quot;where is my order&quot; without making a call.</li>
<li>You find out an order is late when the customer tells you.</li>
<li>You learn your margin at the end of the year.</li>
<li>One person holds the whole operation in their head, and takes it with them on vacation.</li>
</ul>
<h2 id="going-live">Going live</h2>
<p>Clean the product and customer lists first. Bad data moved into new software is still bad data.</p>
<p>Turn on one area at a time, starting with the one that hurts most. Run the old way next to it for one full order cycle, then stop. Running both for months guarantees that neither is right.</p>
<p>Setup takes anywhere from a few weeks for a small shop with a clean catalog to several months for a larger business with inventory and integrations.</p>
<h2 id="where-uniformsos-fits">Where UniformsOS fits</h2>
<p>UniformsOS is software for custom apparel, uniform and merch businesses: brands, shops, decorators and factories. Quotes, orders, team stores, purchase orders, production tracking and payments run on one set of records. Each module is priced on its own, and the free trial runs 30 days with every module on and no card. See the <a href="https://uniformsos.com/platform">platform</a> and <a href="https://uniformsos.com/pricing">pricing</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>AQL inspection for apparel: sample sizes, limits and a final checklist</title>
    <link>https://uniformsos.com/blog/apparel-aql-inspection-guide</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/apparel-aql-inspection-guide</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Factories</category>
    <description>How AQL sampling works for garment orders: lot size, inspection level, sample size, accept and reject numbers, defect classes and a final inspection checklist.</description>
    <content:encoded><![CDATA[<p>AQL sampling decides whether a shipment passes by inspecting a set number of pieces pulled at random. Lot size and inspection level give the sample size, and the AQL gives how many defective pieces it can hold. A common apparel setup is General Level II with zero critical defects, 2.5 for major and 4.0 for minor. Pieces with a name or number are checked one by one against the roster.</p>
<p><a href="https://uniformsos.com/glossary/aql">AQL</a> is how a buyer and a factory agree, before production, on what a passed shipment looks like. You do not open every carton. You pull a set number of pieces at random, count the defects, and the count decides whether the lot ships. This guide shows how to read the table, what the table does not protect you from, and the checklist we would run on a team order.</p>
<h2 id="what-aql-means">What AQL means</h2>
<p>AQL stands for acceptance quality limit. It is the worst average defect rate you are willing to live with across many shipments from the same factory. The sampling tables come from the standard ANSI/ASQ Z1.4, and the same plans are published internationally as ISO 2859-1.</p>
<p>You make three choices, and they belong in the <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a>:</p>
<ol>
<li>Lot size. The number of pieces in the shipment being inspected.</li>
<li>Inspection level. General Level II is the default when the order does not say otherwise. Level I samples fewer pieces and Level III samples more.</li>
<li>The AQL for each class of defect. A common setup for apparel is zero critical defects, 2.5 for major defects and 4.0 for minor defects.</li>
</ol>
<h2 id="the-sampling-table">The sampling table</h2>
<p>General Level II, single sampling, normal inspection:</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Lot size"><table>
<thead>
<tr>
<th>Lot size</th>
<th>Code letter</th>
<th>Pieces to inspect</th>
<th>AQL 2.5: accept / reject</th>
<th>AQL 4.0: accept / reject</th>
</tr>
</thead>
<tbody><tr>
<td>91 to 150</td>
<td>F</td>
<td>20</td>
<td>1 / 2</td>
<td>2 / 3</td>
</tr>
<tr>
<td>151 to 280</td>
<td>G</td>
<td>32</td>
<td>2 / 3</td>
<td>3 / 4</td>
</tr>
<tr>
<td>281 to 500</td>
<td>H</td>
<td>50</td>
<td>3 / 4</td>
<td>5 / 6</td>
</tr>
<tr>
<td>501 to 1,200</td>
<td>J</td>
<td>80</td>
<td>5 / 6</td>
<td>7 / 8</td>
</tr>
<tr>
<td>1,201 to 3,200</td>
<td>K</td>
<td>125</td>
<td>7 / 8</td>
<td>10 / 11</td>
</tr>
<tr>
<td>3,201 to 10,000</td>
<td>L</td>
<td>200</td>
<td>10 / 11</td>
<td>14 / 15</td>
</tr>
<tr>
<td>10,001 to 35,000</td>
<td>M</td>
<td>315</td>
<td>14 / 15</td>
<td>21 / 22</td>
</tr>
</tbody></table>
</div>
<p>Accept is the most defective pieces the sample can hold and still pass. One more and the lot fails.</p>
<h2 id="a-worked-example">A worked example</h2>
<p>An order of 600 jerseys falls in the 501 to 1,200 row. The inspector pulls 80 pieces at random, spread across cartons, colors and sizes.</p>
<ul>
<li>Critical defects: one is enough to fail the lot.</li>
<li>Major defects at AQL 2.5: up to 5 pieces pass. At 6 the lot fails.</li>
<li>Minor defects at AQL 4.0: up to 7 pieces pass. At 8 the lot fails.</li>
</ul>
<p>Each class is counted on its own. A lot can pass on minor defects and fail on major ones.</p>
<h2 id="defect-classes-for-team-apparel">Defect classes for team apparel</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Class"><table>
<thead>
<tr>
<th>Class</th>
<th>What it means</th>
<th>Examples</th>
</tr>
</thead>
<tbody><tr>
<td>Critical</td>
<td>Unsafe for the wearer</td>
<td>A broken needle tip left in a seam, a sharp edge on a trim</td>
</tr>
<tr>
<td>Major</td>
<td>The customer would send it back</td>
<td>Wrong size label, open seam, hole, a number or logo clearly out of position, panels that do not match in shade, a measurement outside <a href="https://uniformsos.com/glossary/tolerance">tolerance</a></td>
</tr>
<tr>
<td>Minor</td>
<td>Most customers would not notice</td>
<td>An untrimmed thread, light puckering, a small mark inside the garment</td>
</tr>
</tbody></table>
</div>
<p>Write your own list into the purchase order with photos where you can. The factory and the inspector should grade the same defect the same way.</p>
<h2 id="what-aql-will-not-catch">What AQL will not catch</h2>
<ul>
<li>It is a sample. A lot that passes can still hold defective pieces. AQL 2.5 is not a promise that 2.5 percent or less of this shipment is defective.</li>
<li>Personalization. Every jersey with a name and number is one of one. Checking 80 pieces out of 600 says nothing about the other 520. Names, numbers and sizes are checked piece by piece against the roster.</li>
<li>Small lots. Under about 90 pieces the plans shrink to a handful of pieces. For a team order of 15 or 40, skip the table and check every piece.</li>
</ul>
<h2 id="final-inspection-checklist">Final inspection checklist</h2>
<ol>
<li>Count. Quantities by style, color and size against the purchase order.</li>
<li>Roster. Every name, number and size against the roster, on every piece.</li>
<li>Measurements. Key points against the <a href="https://uniformsos.com/blog/tech-pack-checklist">spec sheet</a> on several pieces per size, inside the agreed tolerance.</li>
<li>Color. Body and trim against the approved <a href="https://uniformsos.com/glossary/strike-off">strike-off</a> or <a href="https://uniformsos.com/glossary/lab-dip">lab dip</a>, under the same light.</li>
<li>Decoration. Placement, size and straightness. Measure number heights with a ruler.</li>
<li>Construction. Seams closed, the stitch type that was specified, no skipped stitches, threads trimmed.</li>
<li>Labels. Fiber content, country of origin, care and size, plus a tracking label on children&#39;s products. See the <a href="https://uniformsos.com/blog/us-apparel-labeling-requirements">US labeling rules</a>.</li>
<li>Packing. Bagged and labeled the way the order says, by player or by size. Carton marks and the <a href="https://uniformsos.com/glossary/packing-list">packing list</a> match what is inside.</li>
</ol>
<h2 id="when-to-inspect">When to inspect</h2>
<ul>
<li>First pieces off the line. This is the cheapest moment to catch a wrong color, a wrong number style or a bad measurement.</li>
<li>Final inspection. Do it when production is finished and most of the order is packed, so the sample comes from the real shipment.</li>
</ul>
<h2 id="if-the-lot-fails">If the lot fails</h2>
<p>Settle this in the purchase order before production starts: who sorts the lot, who pays for the second inspection, and how many days a remake gets. The usual sequence is that the factory sorts every piece, repairs or remakes the defective ones, and the lot is inspected again from the start.</p>
<p>For the other terms a purchase order needs, see <a href="https://uniformsos.com/blog/managing-factories-and-purchase-orders">managing factories and purchase orders</a>. For a factory you have not used before, see <a href="https://uniformsos.com/blog/how-to-vet-apparel-manufacturer">how to vet a custom apparel manufacturer</a>.</p>
<h2 id="remakes-and-late-orders-in-uniformsos">Remakes and late orders in UniformsOS</h2>
<p>UniformsOS does not run the sampling for you. It keeps the record around it. A factory reports each purchase order through a fixed list of stages that includes checking and final check. When pieces have to be made again, you or the factory raise a redo request on the purchase order with a reason: color, sizing, defect, quality or a missing item. An approved request becomes a redo order with its own purchase order. Each factory&#39;s page counts its open redo requests and its late purchase orders. See <a href="https://uniformsos.com/platform/manufacturers">Manufacturers and Vendors</a> and <a href="https://uniformsos.com/platform/production-wip">Production WIP</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Art approval for custom apparel: a proof process that prevents remakes</title>
    <link>https://uniformsos.com/blog/apparel-art-approval-process</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/apparel-art-approval-process</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Production</category>
    <description>A proof process for custom apparel that prevents remakes: what a proof must show, who signs, revision rounds, roster and color sign-off, and when changes stop.</description>
    <content:encoded><![CDATA[<p>A proof is the record of what the customer agreed to. It shows every view to scale, sizes in inches, color codes, the decoration method, and a version number and date. One named person approves it. The roster and the color are approved separately, and a change after approval is a change order with a price and a new ship date.</p>
<p>Most remakes start at approval, not in production. A misspelled name, a shade the coach pictured differently, a logo that looked fine on a phone and came out the size of a coaster. The factory made what it was sent. A <a href="https://uniformsos.com/glossary/art-proof">proof</a> is the contract for how the product looks: what the customer signs is what gets made. This is the process we would run on every order.</p>
<h2 id="what-a-proof-must-show">What a proof must show</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: On the proof"><table>
<thead>
<tr>
<th>On the proof</th>
<th>Why it is there</th>
</tr>
</thead>
<tbody><tr>
<td>Front, back and side views, drawn to scale</td>
<td>Placement is judged against the whole garment</td>
</tr>
<tr>
<td>Height and width in inches for every logo, name and number</td>
<td>A screen hides real size</td>
</tr>
<tr>
<td>Color callouts by name and code</td>
<td>Two screens never show the same red</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/blog/jersey-decoration-methods-compared">Decoration method</a> for each element</td>
<td>It changes the look, the cost and the minimum</td>
</tr>
<tr>
<td>Garment style, fabric and body color</td>
<td>So the proof matches the quote</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/blog/team-uniform-sizing-guide">The size range</a>, and anything that changes by size</td>
<td>A chest logo that fits an adult large can swallow a youth small</td>
</tr>
<tr>
<td>Name and number font, with a sample name and number</td>
<td>Fonts are the most common surprise</td>
</tr>
<tr>
<td>Version number and date</td>
<td>So everyone is looking at the same file</td>
</tr>
<tr>
<td>Approval line: name, date, approved as shown</td>
<td>So approval is a record and not a feeling</td>
</tr>
</tbody></table>
</div>
<p>For an embroidered logo, see <a href="https://uniformsos.com/glossary/embroidery-digitizing">embroidery digitizing</a>.</p>
<h2 id="one-approver-named-at-the-quote">One approver, named at the quote</h2>
<p>Decide who approves before the first proof goes out. On a team order it might be the coach, the athletic director or a parent who runs the booster club. It cannot be all three. Put one name on the quote. Other people can comment, and the approver collects the comments and sends one answer.</p>
<h2 id="revision-rounds">Revision rounds</h2>
<ol>
<li>State the number of included rounds in the quote. Two is enough for most orders.</li>
<li>Ask for all changes from a round in one message.</li>
<li>Every change makes a new version with a new number and date.</li>
<li>Mark the old version superseded. Never edit an approved file in place.</li>
<li>Charge for rounds beyond the included number, and say so before you start one.</li>
</ol>
<h2 id="the-roster-is-its-own-approval">The roster is its own approval</h2>
<p>Art approval covers the design. The roster covers names, numbers and sizes, and it fails in different ways.</p>
<ul>
<li>Take the roster as a spreadsheet, not as photos or text messages.</li>
<li>Send back a typed list in the font that will be used, and have the approver sign that list.</li>
<li>Spelling belongs to the customer. Checking that <a href="https://uniformsos.com/blog/jersey-number-rules-high-school">every number is legal for the sport</a> belongs to you.</li>
<li>Set a <a href="https://uniformsos.com/blog/league-uniform-ordering-timeline">roster lock date</a>. Late additions become a second, smaller order with its own date.</li>
</ul>
<h2 id="color-cannot-be-approved-on-a-screen">Color cannot be approved on a screen</h2>
<p>A proof shows where color goes. It cannot show what the color will look like on fabric. Use one of these:</p>
<ul>
<li>A physical color card from the factory, with the customer choosing by code.</li>
<li>A <a href="https://uniformsos.com/glossary/strike-off">strike-off</a>, which is a small printed or dyed sample of the actual color on the actual fabric, for a new color or a brand match.</li>
<li>A reference from a previous order, where the instruction is to match what was delivered last season.</li>
</ul>
<p>Write the method on the proof. Color approved from the factory card is a different promise than color approved from a strike-off.</p>
<h2 id="when-changes-stop">When changes stop</h2>
<p>Approval starts <a href="https://uniformsos.com/blog/apparel-production-stages">the production clock</a>. After approval, a change is a change order with a price and a new ship date, and the customer agrees to both in writing before anything moves. This is the rule that protects the date for everyone else in the queue.</p>
<h2 id="how-approvals-go-wrong">How approvals go wrong</h2>
<ul>
<li>Approval arrives as a screenshot or a thumbs up, with no version named.</li>
<li>The proof was reviewed on a phone and nobody saw the small text.</li>
<li>Three people replied and two of them disagreed.</li>
<li>The proof showed the design on one size only.</li>
<li>The logo came in as a small image, was redrawn, and nobody compared it with the original.</li>
<li>The quote said <a href="https://uniformsos.com/glossary/screen-printing">screen print</a> and the proof was drawn as <a href="https://uniformsos.com/glossary/sublimation">sublimation</a>.</li>
</ul>
<h2 id="the-process-start-to-finish">The process, start to finish</h2>
<ol>
<li>Collect the logo as a <a href="https://uniformsos.com/glossary/vector-file">vector file</a>, the colors, the roster deadline and the name of the approver.</li>
<li>Send proof version 1 with every item in the table above.</li>
<li>Collect one consolidated reply. Revise and send the next version.</li>
<li>Get approval on a named version, with name and date.</li>
<li>Approve color by card, strike-off or reference.</li>
<li>Lock and approve the roster.</li>
<li>Release to production with the approved version attached to the <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a>.</li>
<li>Keep the approved proof and roster with the order. They settle every later question, and they are the starting point for the reorder.</li>
</ol>
<p>See the <a href="https://uniformsos.com/blog/tech-pack-checklist">tech pack checklist</a> for what else goes to the factory with the approved proof.</p>
<h2 id="approvals-in-uniformsos">Approvals in UniformsOS</h2>
<p>In <a href="https://uniformsos.com/platform/designs">Designs</a> each design request holds its proofs as numbered versions. The customer approves a version or asks for changes on a link, and the answer is saved with its note, its date and who gave it. A version that has been replaced is marked Superseded, and each request has a set number of revisions. The roster sits on the order line, one row per player with size, name and number.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Custom apparel marketing: how to win team, school and league accounts</title>
    <link>https://uniformsos.com/blog/custom-apparel-marketing</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/custom-apparel-marketing</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Apparel marketing</category>
    <description>Marketing for custom apparel and team uniform businesses: who buys, a season calendar, a named prospect list, mockups, proof, your website and team stores.</description>
    <content:encoded><![CDATA[<p>Custom apparel is sold to a small number of buyers who reorder every season: coaches, athletic directors, league boards and booster clubs. The marketing that works is specific and local. Keep a named list of programs, a calendar tied to their seasons, fast mockups, proof from teams like theirs and a system for reorders. A reorder is the cheapest sale you will make.</p>
<h2 id="know-who-buys">Know who buys</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Buyer"><table>
<thead>
<tr>
<th>Buyer</th>
<th>What they buy</th>
<th>What they care about</th>
</tr>
</thead>
<tbody><tr>
<td>Youth league board</td>
<td>Uniforms for every team</td>
<td>Price per player, delivery before the first game, one invoice</td>
</tr>
<tr>
<td>High school coach or athletic director</td>
<td>Uniforms, practice gear, <a href="https://uniformsos.com/glossary/spirit-wear">spirit wear</a></td>
<td>Durability, school colors, approved vendors, <a href="https://uniformsos.com/glossary/purchase-order">purchase orders</a></td>
</tr>
<tr>
<td>Club or travel team director</td>
<td>Full kits, warmups, bags</td>
<td>The look, and parents paying for their own</td>
</tr>
<tr>
<td>Booster club or parent group</td>
<td>Spirit wear and fundraisers</td>
<td>Money raised and no work for volunteers</td>
</tr>
<tr>
<td>Businesses and events</td>
<td>Staff shirts and event tees</td>
<td>Speed</td>
</tr>
</tbody></table>
</div>
<p>Each one buys differently. A message written for all five lands with none of them.</p>
<h2 id="build-a-named-list">Build a named list</h2>
<p>List every league, school and club you can realistically serve. For each one, record the sport, the season start, the person who decides, the current supplier if you know it and the date of your last contact.</p>
<p>League websites, school athletics pages, state association directories and tournament listings give you most of it for free.</p>
<p>Two hundred named programs with a contact and a date are worth more than any number of followers. This list is the marketing plan.</p>
<h2 id="work-a-season-calendar">Work a season calendar</h2>
<p>Uniform decisions are made about three to four months before a season starts. Reach out before the decision, not during the season.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Season"><table>
<thead>
<tr>
<th>Season</th>
<th>Typical US school sports</th>
<th>Starts</th>
<th>Reach out</th>
</tr>
</thead>
<tbody><tr>
<td>Fall</td>
<td>Football, soccer, volleyball, cross country</td>
<td>August and September</td>
<td>April to June</td>
</tr>
<tr>
<td>Winter</td>
<td>Basketball, wrestling, hockey</td>
<td>November</td>
<td>July and August</td>
</tr>
<tr>
<td>Spring</td>
<td>Baseball, softball, lacrosse, track</td>
<td>February and March</td>
<td>October to December</td>
</tr>
</tbody></table>
</div>
<p>Youth leagues and clubs keep their own calendars. Put each program&#39;s real dates on your list. See the <a href="https://uniformsos.com/blog/league-uniform-ordering-timeline">league uniform ordering timeline</a> for what the buyer is doing in those weeks.</p>
<h2 id="lead-with-a-mockup">Lead with a mockup</h2>
<p>A mockup in their colors with their name on it gets a reply when a catalog does not. It shows that you looked at their program and that you are fast.</p>
<p>Send it the same day they ask. Keep it to one concept and two rounds of changes before a deposit, or mockups turn into free design work for whoever they buy from.</p>
<h2 id="show-proof">Show proof</h2>
<ul>
<li>Photos of real teams wearing what you made, used with permission.</li>
<li>A sentence from a coach, with a name and a program. Real ones only.</li>
<li>Your on-time record, if you track it.</li>
<li>A sample they can hold. Fabric and stitching sell better in the hand than on a screen.</li>
</ul>
<p>Never invent a testimonial. Coaches talk to each other.</p>
<h2 id="make-the-website-answer-the-buyer-s-questions">Make the website answer the buyer&#39;s questions</h2>
<p>Buyers search for specific things: basketball uniforms, football jerseys, spirit wear for a school. Give each sport and each product type its own page, with real photos.</p>
<p>On every page, answer what they are about to ask:</p>
<ul>
<li>What is the minimum?</li>
<li>How long does it take?</li>
<li>Roughly what does it cost per player?</li>
<li>Can parents order and pay for their own?</li>
</ul>
<p>Keep the quote form short: sport, quantity, date needed and a logo upload. Every extra field costs you requests.</p>
<p>Set up a Google Business Profile with photos of your work, and ask happy customers for reviews. Local searches are where a coach looks first.</p>
<h2 id="use-team-stores-as-marketing">Use team stores as marketing</h2>
<p>Every <a href="https://uniformsos.com/glossary/team-store">team store</a> puts your name in front of every parent on the roster. Some of those parents coach another team, sit on a league board or run a business.</p>
<p>Put your name and a contact link in the store footer and on the <a href="https://uniformsos.com/glossary/packing-list">packing slip</a>. One line is enough: you make uniforms and gear for teams, schools and companies.</p>
<h2 id="reorders-and-referrals">Reorders and referrals</h2>
<p>Send last season&#39;s customers a message a few weeks before they need to order again, with last year&#39;s order attached. Reordering should take them one reply.</p>
<p>Ask for a referral at delivery, when the boxes are open and the coach is happy. Ask a specific question: which other coach in your league should I talk to?</p>
<p>Track your reorder rate: the share of last season&#39;s accounts that ordered again. When it drops, something went wrong with delivery or service, and no amount of new leads will cover it.</p>
<h2 id="channels-ranked-for-this-business">Channels, ranked for this business</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Channel"><table>
<thead>
<tr>
<th>Channel</th>
<th>Good for</th>
<th>Watch out for</th>
</tr>
</thead>
<tbody><tr>
<td>Direct outreach by email, phone and in person</td>
<td>Landing specific programs on your list</td>
<td>It takes a list and persistence</td>
</tr>
<tr>
<td>Referrals</td>
<td>Usually the easiest sale</td>
<td>You have to ask</td>
</tr>
<tr>
<td>Local search and Google Business Profile</td>
<td>Coaches searching nearby</td>
<td>It needs reviews and photos</td>
</tr>
<tr>
<td>Sport and product pages, and articles</td>
<td>Steady inbound requests</td>
<td>It takes months to build</td>
</tr>
<tr>
<td>Instagram and Facebook</td>
<td>Showing finished work to coaches and parents</td>
<td>It rarely closes a sale alone</td>
</tr>
<tr>
<td>Tournaments and events</td>
<td>Meeting many coaches in one day</td>
<td>Follow up within two days or it is wasted</td>
</tr>
<tr>
<td>Paid search</td>
<td>Testing demand quickly</td>
<td>Send clicks to a specific page, not the home page</td>
</tr>
</tbody></table>
</div>
<h2 id="what-to-measure">What to measure</h2>
<ul>
<li>Requests by source.</li>
<li>Time to first response.</li>
<li>Share of quotes that become orders.</li>
<li>Reorder rate.</li>
<li>Average order.</li>
<li>Cost to win a new account.</li>
</ul>
<h2 id="mistakes">Mistakes</h2>
<p>Marketing to everyone. Pick the sports and programs you serve best.</p>
<p>Posting products. Post teams wearing them.</p>
<p>Slow quotes. The first shop to send a clear quote and a mockup usually gets the order.</p>
<p>No follow-up after the mockup. One message three days later recovers a lot of them.</p>
<p>Ignoring existing customers to chase new ones.</p>
<p>Competing only on price. Somebody online is always cheaper.</p>
<h2 id="the-sales-side-in-uniformsos">The sales side in UniformsOS</h2>
<p>UniformsOS keeps leads in a pipeline, routes each new one to a rep and holds the next follow-up date and the tasks on the lead. Orders, quotes and saved designs sit on the customer record, and each store in <a href="https://uniformsos.com/platform/team-stores">Team Stores</a> has its own link for the team to share. See <a href="https://uniformsos.com/platform/sales-crm">Sales Reps and CRM</a> and <a href="https://uniformsos.com/platform/customers">Customer Management</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Custom apparel production stages: from approved order to shipped box</title>
    <link>https://uniformsos.com/blog/apparel-production-stages</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/apparel-production-stages</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Production</category>
    <description>The stages a custom apparel order goes through in production, what happens at each one, what goes wrong and the check that catches it.</description>
    <content:encoded><![CDATA[<p>A made-to-order sublimated uniform goes through eight stages: pre-production check, file preparation, test print, printing and heat transfer, cutting, sewing, quality control and packing. Each stage has one typical failure and one check that catches it. Most late orders were delayed before production began, at approval or at the pre-production check.</p>
<h2 id="the-stages-at-a-glance">The stages at a glance</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Stage"><table>
<thead>
<tr>
<th>Stage</th>
<th>What happens</th>
<th>What goes wrong</th>
<th>The check</th>
</tr>
</thead>
<tbody><tr>
<td>1. Pre-production check</td>
<td>The order is read against the approved <a href="https://uniformsos.com/glossary/art-proof">proof</a> and the roster</td>
<td>Missing sizes, unapproved art, duplicate numbers</td>
<td>Nothing is released until the proof is signed and the roster is complete</td>
</tr>
<tr>
<td>2. File preparation</td>
<td>Art is scaled to every size and laid out for printing with names and numbers</td>
<td>The wrong name on the wrong size</td>
<td>Every panel carries the order number, size and player</td>
</tr>
<tr>
<td>3. Test print</td>
<td>A sample is printed on the real fabric</td>
<td>Colors shift from the screen to the fabric</td>
<td>Compare to the approved color reference before the full run</td>
</tr>
<tr>
<td>4. Printing and heat transfer</td>
<td>The design is printed on paper and pressed into the fabric</td>
<td>Ghosting, banding, light patches</td>
<td>Inspect panels as they come off the press</td>
</tr>
<tr>
<td>5. Cutting</td>
<td>Printed panels are cut to shape</td>
<td>Panels cut off-register, mixed sizes</td>
<td>Keep each jersey&#39;s panels bundled together</td>
</tr>
<tr>
<td>6. Sewing</td>
<td>Panels are assembled, hemmed and labeled</td>
<td>Wrong panels joined, weak seams, wrong size label</td>
<td>Check the first piece of each size before the rest are sewn</td>
</tr>
<tr>
<td>7. Quality control</td>
<td>Every piece is checked against the order</td>
<td>Something from stages 2 to 6 that nobody caught</td>
<td>Count, measure and read every name and number against the roster</td>
</tr>
<tr>
<td>8. Packing</td>
<td>Pieces are sorted, bagged and boxed</td>
<td>The right jerseys in the wrong bags</td>
<td>Pack from the roster, one player at a time</td>
</tr>
</tbody></table>
</div>
<h2 id="1-pre-production-check">1. Pre-production check</h2>
<p>This is the gate. Before anything is printed, one person confirms four things: the proof is approved, the roster is complete, every size has a quantity, and the deposit is in.</p>
<p>The work done here is small and the cost of skipping it is large. A duplicate number caught now is a message to the coach. Caught at packing, it is a remake.</p>
<p>Hold orders that fail the check, and tell the customer the same day what is missing. The ship date does not start until the order is released.</p>
<h2 id="2-file-preparation">2. File preparation</h2>
<p>The approved design is one picture. Production needs a separate file for every panel of every size, with each player&#39;s name and number in place.</p>
<p>A youth small and an adult 2XL are not the same artwork scaled up. Logos, numbers and stripes have to be placed for each size so they sit correctly on the body.</p>
<p>The risk is in the personalization. A roster of 40 players is 40 chances to put the right name on the wrong size. Each panel should carry a small printed tag in the seam allowance with the order number, the size and the player, so anyone on the floor can tell what it is.</p>
<h2 id="3-test-print">3. Test print</h2>
<p>A printed sample on the production fabric, often called a <a href="https://uniformsos.com/glossary/strike-off">strike-off</a>. <a href="https://uniformsos.com/glossary/sublimation">Sublimation</a> colors change with the fabric, the paper, the ink and the press settings, so the only reliable proof is a print.</p>
<p>For a repeat customer with an approved color standard, the test can be a small swatch checked in-house. For a new customer or a brand color that has to be exact, send it or photograph it next to the reference in daylight and get a yes in writing.</p>
<h2 id="4-printing-and-heat-transfer">4. Printing and heat transfer</h2>
<p>The files are printed in mirror image onto transfer paper. Paper and fabric then go through a heat press together. Flat presses handle cut pieces. Rotary presses, also called calenders, run fabric and paper continuously from rolls.</p>
<p>The common faults:</p>
<ul>
<li>Ghosting. A blurred double image, caused by the paper shifting while it is still hot.</li>
<li>Banding. Fine lines across the print from a clogged print head.</li>
<li>Light or uneven color, from temperature, pressure or time being off.</li>
<li>White creases, where the fabric was folded in the press.</li>
</ul>
<p>All of them are visible at once, and none can be fixed later. Check panels as they come off, not at the end of the run.</p>
<h2 id="5-cutting">5. Cutting</h2>
<p>Printed panels are cut from the fabric, by hand, with a die or with a laser cutter. The cut has to follow the printed outline exactly, or stripes and side panels will not line up when the jersey is sewn.</p>
<p>After cutting, the panels for each jersey are bundled together: front, back, sleeves and trim, with the tag showing. A floor that mixes loose panels of different sizes will sew a medium front to a large back.</p>
<h2 id="6-sewing">6. Sewing</h2>
<p>Operators assemble the bundles: shoulders, sleeves, side seams, collar, hems and labels. The stitch types are covered in <a href="https://uniformsos.com/blog/sportswear-stitch-types">stitch types in sportswear</a>.</p>
<p>Check the first finished piece of each size against the spec before the rest are sewn. A wrong seam setting found on piece one costs a minute. Found on piece sixty, it costs the order.</p>
<p>Size labels deserve their own attention. A correctly made large with a medium label is a wrong jersey as far as the parent is concerned.</p>
<h2 id="7-quality-control">7. Quality control</h2>
<p><a href="https://uniformsos.com/blog/apparel-aql-inspection-guide">Final inspection</a> checks each piece four ways:</p>
<ol>
<li>Count. The number of pieces matches the order, by size.</li>
<li>Identity. Every name and number matches the roster, spelled exactly.</li>
<li>Measurements. A sample of each size is measured against the spec.</li>
<li>Appearance. Print quality, seams, loose threads, marks.</li>
</ol>
<p>Pieces that fail go straight back for a remake, and the order&#39;s status changes so that customer service knows before the customer asks.</p>
<h2 id="8-packing">8. Packing</h2>
<p>Pack from the roster, not from the pile. One player at a time: jersey, shorts and anything else they ordered, into one bag with a label showing the name, number and sizes.</p>
<p>Bags are grouped by team and boxed with a <a href="https://uniformsos.com/glossary/packing-list">packing list</a> on top. The person who opens the box should be able to hand out the order without sorting anything.</p>
<h2 id="other-decoration-methods">Other decoration methods</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Method"><table>
<thead>
<tr>
<th>Method</th>
<th>Stages that differ</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://uniformsos.com/glossary/screen-printing">Screen printing</a></td>
<td>Separations and screens are made before printing. Garments are printed one color at a time, then cured in a dryer</td>
</tr>
<tr>
<td>Embroidery</td>
<td>The logo is <a href="https://uniformsos.com/glossary/embroidery-digitizing">digitized</a> into a <a href="https://uniformsos.com/glossary/dst-file">stitch file</a>. Garments are hooped, stitched, trimmed and the backing is removed</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/dtf">DTF</a> and heat transfers</td>
<td>Transfers are printed, then pressed onto finished garments. There is no cutting or sewing</td>
</tr>
</tbody></table>
</div>
<p>The first and last stages are the same for every method: the pre-production check, quality control and packing.</p>
<h2 id="where-orders-really-get-delayed">Where orders really get delayed</h2>
<p>Before production. Waiting for proof approval, waiting for the last sizes and waiting for a deposit take more days from most orders than any stage on the floor.</p>
<p>Count those days. Track the time from order to release separately from the time from release to ship. If the first number is the larger one, the fix is in approvals and reminders, not in the factory.</p>
<p>Tracking the stages after release is the job of the <a href="https://uniformsos.com/blog/apparel-wip-report">WIP report</a>.</p>
<h2 id="stages-in-uniformsos">Stages in UniformsOS</h2>
<p>In UniformsOS a factory reports each <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a> against a fixed list of floor stages: design, test print, sublimation, transfer, cutting, checking, stitching, labeling, packing, final check and shipped. Those roll up into the stage shown on the order, with the days in that stage and a schedule label. See <a href="https://uniformsos.com/platform/production-wip">Production WIP</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How online team stores work, and how to run one</title>
    <link>https://uniformsos.com/blog/how-team-stores-work</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/how-team-stores-work</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Team stores</category>
    <description>How a team store runs from setup to delivery: open and close dates, batch production, bulk delivery or ship to home, and fundraising payouts.</description>
    <content:encoded><![CDATA[<p>A team store is a private online shop built for one team, school or club. It opens for a set window, usually one to three weeks. Each parent or player orders and pays for their own items. When the store closes, the shop produces everything in one batch and delivers it sorted to the team, or ships each order to the buyer's home.</p>
<h2 id="what-a-team-store-replaces">What a team store replaces</h2>
<p>Without a store, a coach or team parent collects sizes on a paper form, chases checks and hands the shop one spreadsheet. The spreadsheet is wrong somewhere, and somebody ends up covering the kid who never paid.</p>
<p>A <a href="https://uniformsos.com/glossary/team-store">team store</a> moves all of that to the buyers. Each family picks sizes, enters the name and number, and pays by card. The shop gets clean orders that are already paid for. The coach gets out of the money business.</p>
<h2 id="how-it-runs-step-by-step">How it runs, step by step</h2>
<ol>
<li>Set the products. The shop and the organizer agree on what is in the store: required uniform pieces, optional fan gear, or both, with approved artwork on each.</li>
<li>Set the prices. The shop&#39;s price, plus a fundraising amount if the team wants one.</li>
<li>Set the window. An open date and a close date.</li>
<li>Share the link. The organizer sends it to parents and players. The shop does not have their contacts. The organizer does.</li>
<li>Take orders. Each buyer chooses items, sizes and personalization, and pays.</li>
<li>Send reminders. Orders tend to come in a rush at the start and another at the deadline. A reminder three days before closing and one on the last day bring in the stragglers.</li>
<li>Close. The store stops taking orders, and the shop gets one production list: totals by product and size, and every name and number.</li>
<li>Produce. Everything is made in one batch.</li>
<li>Deliver. In bulk to the organizer, or to each home.</li>
<li>Pay out. If there was a fundraising amount, the shop pays it to the team.</li>
</ol>
<h2 id="timed-stores-and-always-open-stores">Timed stores and always-open stores</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Table"><table>
<thead>
<tr>
<th></th>
<th>Timed store</th>
<th>Always-open store</th>
</tr>
</thead>
<tbody><tr>
<td>How long</td>
<td>One to three weeks</td>
<td>All season or all year</td>
</tr>
<tr>
<td>Production</td>
<td>One batch after closing</td>
<td>Each order as it comes, or weekly batches</td>
</tr>
<tr>
<td>Price per piece</td>
<td>Lower. One setup and one run</td>
<td>Higher. Small runs or on-demand decoration</td>
</tr>
<tr>
<td>Best for</td>
<td>Uniforms, season kickoff, playoffs, events</td>
<td>Fan gear, booster clubs, late joiners</td>
</tr>
<tr>
<td>Main risk</td>
<td>People who miss the deadline</td>
<td>Slow sales and small-order costs</td>
</tr>
</tbody></table>
</div>
<p>Many programs use both: a timed store for required uniforms before the season, and an always-open <a href="https://uniformsos.com/glossary/fan-shop">fan shop</a> for parents and alumni.</p>
<h2 id="delivery-bulk-or-ship-to-home">Delivery: bulk or ship to home</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Table"><table>
<thead>
<tr>
<th></th>
<th>Bulk to the organizer</th>
<th>Ship to home</th>
</tr>
</thead>
<tbody><tr>
<td>Cost to the buyer</td>
<td>Free or low</td>
<td>Shipping on every order</td>
</tr>
<tr>
<td>Work for the shop</td>
<td>Sort and bag by player, one shipment</td>
<td>Pack and label every order</td>
</tr>
<tr>
<td>Work for the organizer</td>
<td>Hand out the bags</td>
<td>None</td>
</tr>
<tr>
<td>Best for</td>
<td>Teams that meet at practice</td>
<td>Fans, relatives in other cities, big clubs</td>
</tr>
</tbody></table>
</div>
<p>Bulk delivery only works if the order is sorted. A box of 60 loose jerseys handed to a coach is a bad evening for the coach. Bag each buyer&#39;s order and label it with the name.</p>
<h2 id="fundraising-and-payouts">Fundraising and payouts</h2>
<p>A team can add an amount to each item that goes back to the program. The shop collects it with the sale and pays it out after the store closes.</p>
<p>Agree three things before the store opens: the amount or percentage per item, when the payout happens, and who it is paid to. Pay the organization, not an individual. Send a statement with the payout that shows units sold and the amount raised per item. A payout that arrives late or cannot be explained is the fastest way to lose a program.</p>
<h2 id="minimums">Minimums</h2>
<p>Timed stores exist partly to solve minimums. <a href="https://uniformsos.com/glossary/screen-printing">Screen printing</a> needs enough pieces of one design to cover the setup. If a store closes with 7 of an item that needs 12, you have three choices: produce it at a loss, cancel and refund that item, or move it to a method with no minimum, such as <a href="https://uniformsos.com/glossary/dtf">DTF</a>. Decide which before the store opens and say so on the store page. See <a href="https://uniformsos.com/glossary/moq">MOQ</a>.</p>
<p><a href="https://uniformsos.com/glossary/sublimation">Sublimated</a> and DTF items do not have this problem, which is why they suit small rosters.</p>
<h2 id="mistakes-that-hurt">Mistakes that hurt</h2>
<p>Opening too late. Count back from the first game: production time, plus shipping, plus the <a href="https://uniformsos.com/glossary/order-window">store window</a>, plus a week of margin. That is your open date.</p>
<p>Too many products. Forty items split the orders so thin that nothing reaches its minimum. Eight to fifteen is plenty for most teams.</p>
<p>No size chart. Youth and adult sizes overlap, and brands fit differently. Put the chart on every product and say plainly that custom items cannot be exchanged.</p>
<p>Personalization with no rules. Set a character limit, say which characters are allowed and block duplicate numbers on the same team.</p>
<p>Moving the deadline again and again. One extension, announced once. After that, late orders go into a second batch with their own delivery date.</p>
<p>No plan for late orders. There are always late orders. Offer a short reopen with a later delivery date, and say so up front.</p>
<h2 id="what-to-measure">What to measure</h2>
<ul>
<li>Orders and revenue per store.</li>
<li>Participation: buyers divided by roster size. For a required uniform it should be everyone. If it is not, someone is about to play without a jersey.</li>
<li>Average order value. Fan gear and bundles raise it.</li>
<li>Days from close to delivery.</li>
<li>Orders that came in after closing. A high number means the window was too short or the reminders did not go out.</li>
</ul>
<h2 id="team-stores-in-uniformsos">Team stores in UniformsOS</h2>
<p>The <a href="https://uniformsos.com/platform/team-stores">Team Stores module</a> gives each team its own store with an opening date and a closing date. A product can take a player name and a number, each with its own fee. Every checkout can be its own order, shipped to the buyer or held for pickup, or buyers can pay until the cutoff and the whole round becomes one production order shipped to one address. The gap between the store price and your base price is tracked per store as the team&#39;s share, and payouts are recorded against it.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How to build a SKU system for custom apparel</title>
    <link>https://uniformsos.com/blog/apparel-sku-system</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/apparel-sku-system</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Products</category>
    <description>A SKU format for custom apparel that holds up as you grow: style, color and size codes, plus how to handle decoration and made-to-order products.</description>
    <content:encoded><![CDATA[<p>A SKU is your own code for one sellable variant: one style in one color in one size. Build it from fixed-length segments in that order, such as BJ201-NVY-AL for basketball jersey 201, navy, adult large. Keep it short, leave out anything that changes, never reuse a code, and keep team artwork on the order, not in the SKU.</p>
<h2 id="what-a-sku-is-and-what-it-is-not">What a SKU is, and what it is not</h2>
<p><a href="https://uniformsos.com/glossary/sku">SKU</a> stands for stock keeping unit. It is an internal code that you invent and control. It identifies one variant that you sell, stock or make.</p>
<p>Three other numbers get confused with it.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Code"><table>
<thead>
<tr>
<th>Code</th>
<th>Who assigns it</th>
<th>What it identifies</th>
</tr>
</thead>
<tbody><tr>
<td>Style number</td>
<td>You</td>
<td>A design, across all its colors and sizes</td>
</tr>
<tr>
<td>SKU</td>
<td>You</td>
<td>One style in one color and one size</td>
</tr>
<tr>
<td>GTIN, the number under a UPC barcode</td>
<td>You, from numbers licensed from GS1</td>
<td>One variant, in a form other companies&#39; systems can read</td>
</tr>
<tr>
<td>Supplier item number</td>
<td>Your supplier</td>
<td>Their code for the blank or the fabric</td>
</tr>
</tbody></table>
</div>
<p>A style number with nothing after it is not a SKU. BJ201 is a jersey design. BJ201-NVY-AL is something you can count.</p>
<h2 id="the-format">The format</h2>
<p>Go from general to specific: style, then color, then size.</p>
<p>BJ201-NVY-AL</p>
<ul>
<li>BJ201 is the style. Two letters for the category and three digits for the design.</li>
<li>NVY is the color. Always three letters.</li>
<li>AL is the size. Always two characters.</li>
</ul>
<p>Rules that keep it working for years:</p>
<ol>
<li>Fixed length for every segment. Codes then sort and scan cleanly, and a missing character is obvious.</li>
<li>Hyphens between segments. Staff can read a code aloud and spot the part that is wrong.</li>
<li>Capital letters and digits only. No spaces, slashes or symbols. They break spreadsheets, URLs and barcodes.</li>
<li>In any segment that contains digits, leave out the letters O and I. They get read as zero and one.</li>
<li>Twelve to sixteen characters in total. Long enough to carry meaning. Short enough to say on the phone.</li>
<li>Nothing that changes. No price, no season, no supplier, no customer. When those change, the code would have to change with them.</li>
<li>Never reuse a code. A retired SKU stays retired, or old orders and reports start pointing at the wrong product.</li>
</ol>
<h2 id="segment-tables">Segment tables</h2>
<p>Write the codes down once and make everyone use the same list.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Category code"><table>
<thead>
<tr>
<th>Category code</th>
<th>Category</th>
</tr>
</thead>
<tbody><tr>
<td>BJ</td>
<td>Basketball jersey</td>
</tr>
<tr>
<td>BS</td>
<td>Basketball short</td>
</tr>
<tr>
<td>FJ</td>
<td>Football jersey</td>
</tr>
<tr>
<td>SJ</td>
<td>Soccer jersey</td>
</tr>
<tr>
<td>BB</td>
<td>Baseball jersey</td>
</tr>
<tr>
<td>HD</td>
<td>Hoodie</td>
</tr>
<tr>
<td>TS</td>
<td>T-shirt</td>
</tr>
</tbody></table>
</div>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Color code"><table>
<thead>
<tr>
<th>Color code</th>
<th>Color</th>
</tr>
</thead>
<tbody><tr>
<td>BLK</td>
<td>Black</td>
</tr>
<tr>
<td>WHT</td>
<td>White</td>
</tr>
<tr>
<td>NVY</td>
<td>Navy</td>
</tr>
<tr>
<td>ROY</td>
<td>Royal</td>
</tr>
<tr>
<td>RED</td>
<td>Red</td>
</tr>
<tr>
<td>KLY</td>
<td>Kelly green</td>
</tr>
<tr>
<td>GLD</td>
<td>Gold</td>
</tr>
</tbody></table>
</div>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Size code"><table>
<thead>
<tr>
<th>Size code</th>
<th>Size</th>
</tr>
</thead>
<tbody><tr>
<td>YS, YM, YL</td>
<td>Youth small, medium, large</td>
</tr>
<tr>
<td>AS, AM, AL</td>
<td>Adult small, medium, large</td>
</tr>
<tr>
<td>XL, 2X, 3X</td>
<td>Adult XL, 2XL, 3XL</td>
</tr>
</tbody></table>
</div>
<p>A women&#39;s cut is a different pattern, so give it its own style number. Do not hide it in the size code.</p>
<h2 id="decoration-and-custom-products">Decoration and custom products</h2>
<p>This is where apparel SKUs go wrong. The test is simple. Does the difference change what you stock, or what the factory makes as a standard product?</p>
<p>A stock decorated item is its own SKU. A navy hoodie with the school crest, printed 200 at a time and sold all season, is a product. Give the decorated version its own style number.</p>
<p>A made-to-order <a href="https://uniformsos.com/glossary/sublimation">sublimated</a> jersey is different. Every team gets its own artwork, and every player gets a name and a number. If each of those were a SKU, you would create thousands of codes that are each used once.</p>
<p>So split it three ways:</p>
<ul>
<li>The SKU identifies the base product: the cut, the fabric and the size. On a sublimated style the color segment can be a fixed code such as SUB, because the color is printed.</li>
<li>The design gets a design ID that belongs to the customer or the order.</li>
<li>Names and numbers live on the order&#39;s roster.</li>
</ul>
<p>An order line then reads: SKU BJ201-SUB-AL, design D-4471, name RIVERA, number 12. The catalog stays small and every order is still fully specified.</p>
<p>Blanks that you decorate follow the same idea. Keep the supplier&#39;s item number on the product record as a reference. Do not use it as your SKU. You will change suppliers, and the product will stay the same.</p>
<h2 id="when-you-need-gtins">When you need GTINs</h2>
<p>A GTIN is a Global Trade Item Number, the number encoded in a UPC or EAN barcode. GS1 is the organization behind the system. You license numbers from GS1 and assign them to your products.</p>
<p>You need them when you sell through someone else&#39;s system. Retailers, distributors and most large marketplaces ask for a GTIN on each listing. Under GS1&#39;s GTIN Management Standard, every variation gets its own number. One style in 5 colors and 8 sizes needs 40.</p>
<p>You do not need them for made-to-order team uniforms sold direct, or for products that only move inside your own business. Your SKU does that job.</p>
<p>If you use both, store the GTIN on the variant next to the SKU. They are two labels for the same thing, and neither replaces the other.</p>
<h2 id="a-worked-example">A worked example</h2>
<p>One basketball jersey style in stock colors.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Item"><table>
<thead>
<tr>
<th>Item</th>
<th>Value</th>
</tr>
</thead>
<tbody><tr>
<td>Style</td>
<td>BJ201</td>
</tr>
<tr>
<td>Colors</td>
<td>4: BLK, WHT, NVY, ROY</td>
</tr>
<tr>
<td>Sizes</td>
<td>9: YS through 3X</td>
</tr>
<tr>
<td>SKUs</td>
<td>36</td>
</tr>
</tbody></table>
</div>
<p>The first is BJ201-BLK-YS and the last is BJ201-ROY-3X.</p>
<p>Add the matching short, BS201, and the uniform has 72 SKUs. Pairing styles by number, 201 with 201, tells anyone that the jersey and the short go together.</p>
<h2 id="mistakes-that-cost-money-later">Mistakes that cost money later</h2>
<p>Letting every salesperson create codes. Two people will code the same product two ways. One person or one written rule owns the list.</p>
<p>Using the supplier&#39;s number as your SKU. It ties your catalog to a vendor.</p>
<p>Putting the customer in the SKU. A team&#39;s name belongs on the order.</p>
<p>Skipping the size. &quot;Size is on the PO&quot; works until someone has to count stock.</p>
<p>Changing codes that are already in use. If a code is wrong, retire it and create a new one. Do not edit history.</p>
<p>One SKU for a set. A jersey and short sold together is a bundle of two SKUs. Otherwise you cannot replace one piece.</p>
<h2 id="skus-in-uniformsos">SKUs in UniformsOS</h2>
<p>In UniformsOS a product has a style number and one variant for each color and size, and each variant has its own SKU. Variants are typed in or generated from your colors and the product&#39;s size ranges, and the style number prints on quotes, orders and factory <a href="https://uniformsos.com/glossary/purchase-order">purchase orders</a>. See <a href="https://uniformsos.com/platform/products">Products and SKUs</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How to price custom apparel</title>
    <link>https://uniformsos.com/blog/how-to-price-custom-apparel</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/how-to-price-custom-apparel</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Pricing</category>
    <description>Price custom apparel from landed cost and a target gross margin. The formula, a worked jersey example, quantity breaks and what to charge separately.</description>
    <content:encoded><![CDATA[<p>Price custom apparel from the landed cost up. Add the garment, decoration, artwork time, freight, packing and payment fees to get the true cost per piece. Then set the price from a target gross margin: price equals cost divided by one minus the margin. A $14.25 landed cost at a 45 percent margin is $25.91.</p>
<h2 id="markup-and-margin-are-not-the-same-number">Markup and margin are not the same number</h2>
<p>Markup is profit divided by cost. Margin is profit divided by price. Shops that mix them up underprice every order.</p>
<p>A jersey that costs $10 and sells for $15 has a 50 percent markup and a 33 percent margin. Same jersey, same $5.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Markup on cost"><table>
<thead>
<tr>
<th>Markup on cost</th>
<th>Gross margin</th>
</tr>
</thead>
<tbody><tr>
<td>25%</td>
<td>20%</td>
</tr>
<tr>
<td>50%</td>
<td>33%</td>
</tr>
<tr>
<td>67%</td>
<td>40%</td>
</tr>
<tr>
<td>100%</td>
<td>50%</td>
</tr>
<tr>
<td>150%</td>
<td>60%</td>
</tr>
</tbody></table>
</div>
<p>Set your targets in margin. It is the number that pays the rent, because overhead is paid out of what is left from the price.</p>
<h2 id="build-the-landed-cost">Build the landed cost</h2>
<p>The <a href="https://uniformsos.com/glossary/landed-cost">landed cost</a> is everything it takes to put one finished piece in the customer&#39;s hands. The example below is a <a href="https://uniformsos.com/glossary/sublimation">sublimated</a> basketball jersey on an order of 24. The numbers are made up to show the method. Use your own.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Cost"><table>
<thead>
<tr>
<th>Cost</th>
<th>Per piece</th>
</tr>
</thead>
<tbody><tr>
<td>Jersey from the factory, sublimated</td>
<td>$9.50</td>
</tr>
<tr>
<td>Freight in and duties</td>
<td>$1.40</td>
</tr>
<tr>
<td>Artwork and setup: one hour at $30, spread over 24 pieces</td>
<td>$1.25</td>
</tr>
<tr>
<td>Sorting, bagging and packing</td>
<td>$0.60</td>
</tr>
<tr>
<td>Delivery to the customer</td>
<td>$0.75</td>
</tr>
<tr>
<td>Card fees, about 3 percent of the price</td>
<td>$0.75</td>
</tr>
<tr>
<td>Landed cost</td>
<td>$14.25</td>
</tr>
</tbody></table>
</div>
<p>The factory price is two thirds of the real cost here. A shop that prices from $9.50 thinks it is making far more than it is.</p>
<h2 id="set-the-price-from-the-margin">Set the price from the margin</h2>
<p>Price = landed cost ÷ (1 − target margin)</p>
<p>For the $14.25 jersey:</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Target margin"><table>
<thead>
<tr>
<th>Target margin</th>
<th>Price</th>
</tr>
</thead>
<tbody><tr>
<td>35%</td>
<td>$21.92</td>
</tr>
<tr>
<td>40%</td>
<td>$23.75</td>
</tr>
<tr>
<td>45%</td>
<td>$25.91</td>
</tr>
<tr>
<td>50%</td>
<td>$28.50</td>
</tr>
</tbody></table>
</div>
<p>Round to a price that reads cleanly, such as $26. Round up.</p>
<h2 id="quantity-breaks">Quantity breaks</h2>
<p>Some costs are fixed for the order. Artwork takes the same hour for 12 jerseys as for 100. Spread over more pieces, it costs less on each one, and your price can come down without touching the margin.</p>
<p>Using the same jersey, with $13.00 of per-piece cost and $30 of artwork:</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Quantity"><table>
<thead>
<tr>
<th>Quantity</th>
<th>Artwork per piece</th>
<th>Landed cost</th>
<th>Price at 45%</th>
</tr>
</thead>
<tbody><tr>
<td>12</td>
<td>$2.50</td>
<td>$15.50</td>
<td>$28.18</td>
</tr>
<tr>
<td>24</td>
<td>$1.25</td>
<td>$14.25</td>
<td>$25.91</td>
</tr>
<tr>
<td>48</td>
<td>$0.63</td>
<td>$13.63</td>
<td>$24.78</td>
</tr>
<tr>
<td>100</td>
<td>$0.30</td>
<td>$13.30</td>
<td>$24.18</td>
</tr>
</tbody></table>
</div>
<p>Factories usually lower their own price at higher quantities too, which widens the gap. Build your tiers where your costs really change, and publish them. Customers add players to reach the next tier.</p>
<p><a href="https://uniformsos.com/glossary/screen-printing">Screen printing</a> has a steeper curve, because every color is a screen and every screen is a setup. Sublimation and <a href="https://uniformsos.com/glossary/dtf">DTF</a> are flatter.</p>
<h2 id="what-to-charge-separately">What to charge separately</h2>
<ul>
<li>Artwork beyond <a href="https://uniformsos.com/blog/apparel-art-approval-process">the first proof and two rounds of changes</a>.</li>
<li>Rush orders.</li>
<li>Names and numbers, when they are not part of the print.</li>
<li>Screen or setup fees, if you do not build them into the tiers.</li>
<li>Orders below your minimum.</li>
<li>Shipping to individual homes.</li>
</ul>
<p>Put each one on its own line. A customer who can see the rush fee can decide to order earlier next season.</p>
<h2 id="check-the-price-against-the-market">Check the price against the market</h2>
<p>The margin formula gives you a floor. The market gives you a ceiling. Find out what teams in your area pay for a comparable uniform.</p>
<p>If your price at the target margin is above the market, lowering the margin is the last fix to try. Look at cost first: a different factory, a stocked fabric, a simpler cut, fewer revisions. Then look at what you are selling. Faster turnaround, better artwork and sorted delivery are worth money to a coach, and the cheapest website does not offer them.</p>
<h2 id="mistakes-that-erase-margin">Mistakes that erase margin</h2>
<p>Pricing from the garment cost alone. Freight, artwork and packing are real.</p>
<p>Unlimited free revisions. The sixth <a href="https://uniformsos.com/glossary/art-proof">proof</a> is paid for by your margin.</p>
<p>One price at every quantity. You lose the big orders and lose money on the small ones.</p>
<p>Never repricing. Suppliers raise prices. Check your landed costs every quarter.</p>
<p>Discounting the price when asked. Take something out in exchange: a longer <a href="https://uniformsos.com/glossary/lead-time">lead time</a>, one proof, bulk delivery only.</p>
<p>Never checking what the order really made. Remakes, rush freight and extra art hours do not show up on the quote.</p>
<h2 id="track-the-real-margin">Track the real margin</h2>
<p>After every order ships, compare the quoted margin with the real one: the price, minus what the order actually cost, including any remake and any freight you paid to save a date.</p>
<p>Sort by product and by customer once a quarter. The gap between quoted and real margin shows you which products are mispriced and which customers cost more than they pay.</p>
<h2 id="pricing-in-uniformsos">Pricing in UniformsOS</h2>
<p>In UniformsOS each product has a price for each quantity band, and a quote line takes the band that matches its quantity. A quote under your margin floor is held until Finance approves it, and reports show margin by product, customer and rep. See <a href="https://uniformsos.com/platform/products">Products and SKUs</a>, <a href="https://uniformsos.com/platform/sales-crm">Sales Reps and CRM</a> and <a href="https://uniformsos.com/platform/reports">Reports and Analytics</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How to start a team apparel business</title>
    <link>https://uniformsos.com/blog/start-team-apparel-business</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/start-team-apparel-business</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Teams</category>
    <description>How to start a team apparel business: pick a model, choose a niche, find factories, price from landed cost, win the first ten accounts and run orders cleanly.</description>
    <content:encoded><![CDATA[<p>Pick one model and one niche, and test a factory before you sell. Price from landed cost, which is the factory price plus freight, duty, decoration and packing. Work a named list of prospects ahead of each season, and run every order through the same steps from quote to reorder.</p>
<p>A team apparel business sells custom uniforms and fan wear to teams, schools, leagues and clubs. You can start one without owning a machine. What you need is accounts, a factory you can rely on, and a process that still works at forty open orders. Here is the order we would do it in.</p>
<h2 id="pick-a-model">Pick a model</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Model"><table>
<thead>
<tr>
<th>Model</th>
<th>What you own</th>
<th>Cash to start</th>
<th>Main risk</th>
</tr>
</thead>
<tbody><tr>
<td>Dealer</td>
<td>The customer relationship. A supplier makes everything.</td>
<td>Low</td>
<td>Dates and quality sit with someone else</td>
</tr>
<tr>
<td>Decorator</td>
<td>Printing or embroidery equipment. You decorate blank garments.</td>
<td>Medium to high</td>
<td>Equipment sits idle off season</td>
</tr>
<tr>
<td>Brand with contract factories</td>
<td>Designs, patterns and the catalog. Factories cut, sew and <a href="https://uniformsos.com/glossary/sublimation">sublimate</a>.</td>
<td>Medium</td>
<td>Minimums, lead times and quality control</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/team-store">Team store</a> operator</td>
<td>Online stores for teams and schools. Production is outsourced or in house.</td>
<td>Low to medium</td>
<td>Many small orders to fulfill correctly</td>
</tr>
</tbody></table>
</div>
<p>Most businesses end up as a mix. Start with one model and add the second when the first runs without you.</p>
<h2 id="choose-a-niche">Choose a niche</h2>
<p>Pick a sport, a level and a region you already know. A narrow start pays in three ways:</p>
<ul>
<li>You learn one product set well, including how it fits and where it fails.</li>
<li>You sell on one season calendar and one set of deadlines.</li>
<li>Coaches and athletic directors talk to each other, so referrals stay inside your niche.</li>
</ul>
<h2 id="line-up-supply-before-you-sell">Line up supply before you sell</h2>
<ol>
<li>Shortlist factories that already make your product type.</li>
<li>Ask for <a href="https://uniformsos.com/glossary/moq">minimums</a>, <a href="https://uniformsos.com/glossary/lead-time">lead times</a> by season, sample cost and payment terms.</li>
<li>Pay for a sample in your own design and wash it.</li>
<li>Place a small first order before a large one.</li>
<li>Keep a second factory warm for every product you depend on.</li>
</ol>
<p>See <a href="https://uniformsos.com/blog/how-to-vet-apparel-manufacturer">how to vet a custom apparel manufacturer</a>.</p>
<h2 id="build-a-small-catalog-and-price-it-properly">Build a small catalog and price it properly</h2>
<ul>
<li>Start with ten to twenty products you can deliver well.</li>
<li>Give every style, color and size a <a href="https://uniformsos.com/glossary/sku">SKU</a> from the first day.</li>
<li>Price from <a href="https://uniformsos.com/glossary/landed-cost">landed cost</a>, which is the factory price plus freight, duty, decoration and packing, then add the margin you need. Pricing from the factory price alone is how new shops lose money on orders that looked profitable.</li>
<li>Set quantity breaks and charge separately for rush, extra art rounds and individual names.</li>
</ul>
<p>See <a href="https://uniformsos.com/blog/apparel-sku-system">how to build a SKU system</a> and <a href="https://uniformsos.com/blog/how-to-price-custom-apparel">how to price custom apparel</a>.</p>
<h2 id="handle-the-basics">Handle the basics</h2>
<ul>
<li>Register the business, and check with the tax office of each state where you sell about collecting sales tax.</li>
<li>Learn the <a href="https://uniformsos.com/blog/us-apparel-labeling-requirements">US labeling rules</a> for fiber content, country of origin and care, and the extra rules for children&#39;s products.</li>
<li>Get permission for logos. College and professional marks are licensed trademarks. For a school or club logo, get written permission from the school or club before you sell anything with it.</li>
</ul>
<h2 id="win-the-first-ten-accounts">Win the first ten accounts</h2>
<ol>
<li>Write a list of fifty named prospects in your niche, with the person who buys.</li>
<li><a href="https://uniformsos.com/blog/league-uniform-ordering-timeline">Work backward from each season</a>. Teams order weeks before the first game, so your outreach starts well before that.</li>
<li>Send a mockup in the team&#39;s colors with the first message.</li>
<li>Carry a sample kit. Coaches buy what they can touch and size.</li>
<li>Offer a <a href="https://uniformsos.com/blog/how-team-stores-work">team store</a> for fan wear and for players who join late. It turns one order into a season of orders.</li>
<li>Ask every delivered account for one introduction.</li>
</ol>
<p>See <a href="https://uniformsos.com/blog/custom-apparel-marketing">custom apparel marketing</a>.</p>
<h2 id="run-orders-the-same-way-every-time">Run orders the same way every time</h2>
<p>Every order moves through the same steps: quote, <a href="https://uniformsos.com/glossary/art-proof">proof</a>, approval, deposit, <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a>, production, inspection, delivery, reorder.</p>
<ul>
<li>One approver per order, named at the quote.</li>
<li>A deposit before the purchase order goes to the factory.</li>
<li>A ship date you give the customer only after the factory confirms theirs.</li>
<li>A weekly <a href="https://uniformsos.com/blog/apparel-wip-report">work in progress report</a> that shows every open order, its stage and whether it is late.</li>
<li>Every piece with a name or number checked against the roster before it ships.</li>
</ul>
<h2 id="mistakes-that-sink-new-shops">Mistakes that sink new shops</h2>
<ul>
<li>Selling every sport to everyone in the first year.</li>
<li>Quoting a date the factory never confirmed.</li>
<li>Taking approvals by text message.</li>
<li>Skipping the <a href="https://uniformsos.com/blog/team-uniform-sizing-guide">sizing kit</a> and guessing sizes.</li>
<li>Running forty orders from an inbox and <a href="https://uniformsos.com/blog/spreadsheets-vs-apparel-software">a spreadsheet nobody else can read</a>.</li>
</ul>
<h2 id="a-first-90-days">A first 90 days</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Weeks"><table>
<thead>
<tr>
<th>Weeks</th>
<th>Focus</th>
</tr>
</thead>
<tbody><tr>
<td>1 to 2</td>
<td>Choose the model and niche. Shortlist factories.</td>
</tr>
<tr>
<td>3 to 5</td>
<td>Order samples. Build the catalog, SKUs and price list.</td>
</tr>
<tr>
<td>6 to 8</td>
<td>Build the prospect list. Make mockups. Start outreach.</td>
</tr>
<tr>
<td>9 to 12</td>
<td>Deliver the first orders. Fix what broke. Ask for referrals.</td>
</tr>
</tbody></table>
</div>
<h2 id="running-orders-in-uniformsos">Running orders in UniformsOS</h2>
<p>In UniformsOS a quote is the order itself, so nothing is retyped, and sending it issues the deposit invoice with a pay link. The factory gets a purchase order and reports each stage in its own portal, and orders behind their ship-by date are flagged. Each team can have its own store with a closing date. The free trial runs 30 days with every module on and no card. See the <a href="https://uniformsos.com/platform">platform</a> and <a href="https://uniformsos.com/pricing">pricing</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How to vet a custom apparel manufacturer</title>
    <link>https://uniformsos.com/blog/how-to-vet-apparel-manufacturer</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/how-to-vet-apparel-manufacturer</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Factories</category>
    <description>Five steps to vet an apparel factory before you send it real orders: fit, the questions to ask, a paid sample, references and audits, and a small first order.</description>
    <content:encoded><![CDATA[<p>Vet a factory in five steps. Confirm it already makes your type of product. Check its minimums and lead times against your real orders. Pay for a sample made to your tech pack. Check references and a recent audit report. Then place a small first order with written quality terms. A good sample proves little. The first bulk order is the test.</p>
<h2 id="start-with-fit-not-price">Start with fit, not price</h2>
<p>Factories specialize. A <a href="https://uniformsos.com/glossary/cut-and-sew">cut-and-sew</a> house that <a href="https://uniformsos.com/glossary/sublimation">sublimates</a> teamwear all day is not a <a href="https://uniformsos.com/glossary/screen-printing">screen printer</a>, and a screen printer is not an embroidery shop. The cheapest quote from a factory that does not normally make your product is the most expensive order you will place.</p>
<p>Ask what it made last month. Ask for photos of current production, not a catalog. Then ask which steps happen under its own roof. Printing, sewing, embroidery and packing are often split between companies, and every handoff is a place for delay and blame.</p>
<h2 id="the-questions-to-ask">The questions to ask</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Question"><table>
<thead>
<tr>
<th>Question</th>
<th>Why it matters</th>
</tr>
</thead>
<tbody><tr>
<td>What is your minimum, and is it per order, per style or per color?</td>
<td>The same number means very different commitments</td>
</tr>
<tr>
<td>What is your <a href="https://uniformsos.com/glossary/lead-time">lead time</a> for a sample and for bulk, now and in peak season?</td>
<td>Quoted lead times are for a quiet month</td>
</tr>
<tr>
<td>Which steps do you subcontract?</td>
<td>You need to know who is really making it</td>
</tr>
<tr>
<td>Who buys the fabric, and what do you stock?</td>
<td>Stocked fabric means lower minimums and faster starts</td>
</tr>
<tr>
<td>How do you check quality during production and before shipping?</td>
<td>You want checks on the line, not only at the end</td>
</tr>
<tr>
<td>What happens when pieces are defective or the order is late?</td>
<td>Remake, credit or refund should be agreed before there is a problem</td>
</tr>
<tr>
<td>What are your payment terms?</td>
<td>Deposits of 30 to 50 percent with the balance before shipping are common for new customers</td>
</tr>
<tr>
<td>Who is my contact, and how fast do you answer?</td>
<td>One named person. Slow answers before the order get slower after it</td>
</tr>
<tr>
<td>What shipping terms do you quote?</td>
<td>EXW, <a href="https://uniformsos.com/glossary/fob">FOB</a> and <a href="https://uniformsos.com/glossary/ddp">DDP</a> put very different costs on you</td>
</tr>
</tbody></table>
</div>
<p>On shipping terms: these are <a href="https://uniformsos.com/glossary/incoterms">Incoterms</a>, published by the International Chamber of Commerce. Under EXW you collect the goods at the factory door and pay for everything after it. Under FOB the factory gets them onto the ship at its port. Under DDP the factory delivers to your door with duties paid. Compare quotes only on the same term.</p>
<h2 id="pay-for-a-sample">Pay for a sample</h2>
<p>Send your <a href="https://uniformsos.com/glossary/tech-pack">tech pack</a> and pay for a sample made to it. A free sample pulled from the showroom tells you what the factory can make on its best day for someone else.</p>
<p>Check four things when it arrives:</p>
<ol>
<li>Measurements. Measure every point on your spec sheet and compare against your <a href="https://uniformsos.com/glossary/tolerance">tolerances</a>.</li>
<li>Color. Compare against your reference in daylight.</li>
<li>Construction. Look at the seams inside and out, the stitch type and density, the thread ends and the label placement.</li>
<li>Washing. Wash and dry it five times the way a parent would. Then check for <a href="https://uniformsos.com/glossary/shrinkage">shrinkage</a>, <a href="https://uniformsos.com/glossary/colorfastness">color bleed</a>, cracked prints and popped seams.</li>
</ol>
<p>Before bulk production, approve a <a href="https://uniformsos.com/glossary/pre-production-sample">pre-production sample</a> made on the real production line with the real fabric. Keep one signed copy and have the factory keep another. That sample is the standard the order is judged against.</p>
<h2 id="check-references-and-audits">Check references and audits</h2>
<p>Ask for two customers who buy the same type of product, and call them. Ask what went wrong and how the factory handled it. Every factory has had a bad order. You are finding out what it did next.</p>
<p>Ask for the latest audit report, not only a certificate. Check the date and the address on it. The common ones:</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Audit or standard"><table>
<thead>
<tr>
<th>Audit or standard</th>
<th>What it covers</th>
</tr>
</thead>
<tbody><tr>
<td>WRAP, amfori BSCI, SMETA, SA8000</td>
<td>Labor conditions and workplace safety</td>
</tr>
<tr>
<td>ISO 9001</td>
<td>Whether the factory runs a quality management system</td>
</tr>
<tr>
<td>OEKO-TEX Standard 100</td>
<td>Testing of textiles for harmful substances</td>
</tr>
</tbody></table>
</div>
<p>A certificate does not guarantee a good order. A factory that refuses to show any report is telling you something.</p>
<p>If the volume justifies it, visit. If it does not, ask for a live video walk through the floor, and consider paying a third-party inspection company for a day.</p>
<h2 id="place-a-small-first-order">Place a small first order</h2>
<p>Make the first order small enough to lose. Put it on a written <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a> with:</p>
<ul>
<li>the approved sample and tech pack it must match</li>
<li>quantities by size</li>
<li>the price and the payment schedule</li>
<li>the ship date</li>
<li>the quality standard and how it will be checked</li>
<li>what happens if it is late or wrong</li>
</ul>
<p>For the quality standard, most apparel buyers use <a href="https://uniformsos.com/blog/apparel-aql-inspection-guide">AQL sampling</a>. <a href="https://uniformsos.com/glossary/aql">AQL</a> stands for acceptance quality limit. An inspector pulls a set number of pieces from the finished order, based on the sampling tables in ISO 2859-1, and the order passes or fails on the number of defects found. AQL 2.5 for major defects and 4.0 for minor ones is the usual starting point for apparel.</p>
<p>Inspect before you pay the balance. For a large order, send an inspector. For a small one, ask for photos of the packed order, a count by size and measurements of a few pieces on video.</p>
<h2 id="red-flags">Red flags</h2>
<ul>
<li>It says yes to everything. Real factories have limits and tell you what they are.</li>
<li>The lowest price, the fastest lead time and no minimum, all at once.</li>
<li>It will not say what is subcontracted.</li>
<li>The sample is perfect and it cannot tell you which line will make the bulk.</li>
<li>It wants full payment up front on a first order.</li>
<li>It cannot name a customer who buys your type of product.</li>
</ul>
<h2 id="keep-score-after-the-first-order">Keep score after the first order</h2>
<p>Vetting does not end with the first shipment. Track four numbers for every factory:</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Measure"><table>
<thead>
<tr>
<th>Measure</th>
<th>How to calculate it</th>
</tr>
</thead>
<tbody><tr>
<td>On-time rate</td>
<td>Orders shipped on or before the agreed date, divided by orders shipped</td>
</tr>
<tr>
<td>Defect rate</td>
<td>Pieces rejected, divided by pieces received</td>
</tr>
<tr>
<td>Remake rate</td>
<td>Orders that needed a remake, divided by orders</td>
</tr>
<tr>
<td>Response time</td>
<td>How long a question waits for an answer</td>
</tr>
</tbody></table>
</div>
<p>Three orders tell you more than any audit. And keep a second factory qualified for each core product. One late run should not stop your season.</p>
<h2 id="tracking-a-factory-after-you-choose-it">Tracking a factory after you choose it</h2>
<p>In UniformsOS each factory gets its own purchase orders and its own login, where it accepts the job, uploads test prints and reports the stage. Every purchase order is marked on time, due soon or late against its ship-by date, and reports count late purchase orders by factory. See <a href="https://uniformsos.com/platform/manufacturers">Manufacturers and Vendors</a> and <a href="https://uniformsos.com/solutions/factories">UniformsOS for factories</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Jersey fabric guide: mesh, interlock, birdseye, dazzle and what GSM means</title>
    <link>https://uniformsos.com/blog/jersey-fabric-guide</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/jersey-fabric-guide</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Jerseys</category>
    <description>The fabrics team jerseys are made from, how they differ, what fabric weight in GSM tells you, and which fabric suits which sport and decoration method.</description>
    <content:encoded><![CDATA[<p>Almost all team jerseys are polyester knits. Interlock is smooth and prints sharply. Mesh has open holes and moves the most air. Birdseye is a light textured knit that wicks well. Dazzle is shiny and is used for trim and shorts. Fabric weight is given in GSM, grams per square meter. Most jersey fabrics fall between about 130 and 200.</p>
<h2 id="why-polyester">Why polyester</h2>
<p>Polyester is strong, light and cheap. It does not absorb much water, so it dries fast and does not get heavy with sweat. It holds color well through repeated washing. And it is the only common fiber that takes <a href="https://uniformsos.com/glossary/sublimation">sublimation</a>, which is how most custom team uniforms are printed.</p>
<p>Cotton is comfortable and breathes, but it soaks up sweat and stays wet. It is for T-shirts, hoodies and fan wear, not game jerseys.</p>
<p>Spandex, also called elastane, is added in small amounts where a garment has to stretch and recover: compression gear, fitted jerseys, baseball pants and volleyball uniforms.</p>
<h2 id="the-fabrics">The fabrics</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Fabric"><table>
<thead>
<tr>
<th>Fabric</th>
<th>What it is</th>
<th>Feel</th>
<th>Used for</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://uniformsos.com/glossary/interlock">Interlock</a></td>
<td>A smooth double knit that looks the same on both faces</td>
<td>Soft, stable, medium weight</td>
<td>Jersey bodies, warmups, most sublimated uniforms</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/mesh">Mesh</a></td>
<td>A knit with open holes, from tiny to large</td>
<td>Airy and light</td>
<td>Basketball and football jerseys, side panels, practice wear</td>
</tr>
<tr>
<td>Birdseye</td>
<td>A light knit with a small dimpled texture</td>
<td>Dry and textured</td>
<td>Soccer jerseys, training tops, polos</td>
</tr>
<tr>
<td>Micro mesh</td>
<td>A fine mesh with very small holes</td>
<td>Smooth with good airflow</td>
<td>Jersey bodies where a clean print and airflow are both wanted</td>
</tr>
<tr>
<td>Dazzle</td>
<td>A shiny, tightly knitted polyester</td>
<td>Slick and bright</td>
<td>Shoulder yokes, trim, basketball and football shorts</td>
</tr>
<tr>
<td>Double knit</td>
<td>A heavier, firm knit</td>
<td>Thick and durable</td>
<td>Baseball jerseys and pants</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/pique">Pique</a></td>
<td>A knit with a raised waffle texture</td>
<td>Textured, holds its shape</td>
<td>Coaches&#39; polos</td>
</tr>
<tr>
<td>Stretch knit with spandex</td>
<td>Polyester with 8 to 20 percent spandex</td>
<td>Tight, stretchy</td>
<td>Compression tops, fitted jerseys, volleyball</td>
</tr>
<tr>
<td>Fleece</td>
<td>A knit brushed soft on the inside</td>
<td>Warm and thick</td>
<td>Hoodies and sweatpants</td>
</tr>
</tbody></table>
</div>
<p>Names vary between mills and suppliers. One factory&#39;s &quot;pro mesh&quot; is another&#39;s &quot;air mesh&quot;. Ask for a swatch and the weight, not only the name.</p>
<h2 id="what-gsm-means">What GSM means</h2>
<p><a href="https://uniformsos.com/glossary/gsm">GSM</a> is grams per square meter. It is the weight of the fabric, and it is the most useful single number on a spec.</p>
<p>US suppliers often quote ounces per square yard. One ounce per square yard is about 34 GSM.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Weight"><table>
<thead>
<tr>
<th>Weight</th>
<th>GSM</th>
<th>Typical use</th>
</tr>
</thead>
<tbody><tr>
<td>Light</td>
<td>120 to 150</td>
<td>Soccer jerseys, running tops, summer training wear</td>
</tr>
<tr>
<td>Medium</td>
<td>150 to 190</td>
<td>Basketball and volleyball jerseys, most interlock uniforms</td>
</tr>
<tr>
<td>Heavy</td>
<td>190 to 260</td>
<td>Football and hockey jerseys, baseball double knit</td>
</tr>
<tr>
<td>Fleece</td>
<td>250 and up</td>
<td>Hoodies and sweatpants</td>
</tr>
</tbody></table>
</div>
<p>These are typical ranges, not rules. Heavier fabric is more durable and less see-through. Lighter fabric is cooler and cheaper to ship. White jerseys in a light fabric show what is under them, so check opacity on a white swatch.</p>
<h2 id="moisture-wicking">Moisture wicking</h2>
<p><a href="https://uniformsos.com/glossary/moisture-wicking">Wicking</a> means the fabric pulls sweat away from the skin and spreads it out so it dries. Polyester helps because it does not absorb the water. The knit structure does the rest.</p>
<p>Some fabrics wick because of how the yarn and knit are made. Others rely on a chemical finish, which can fade with washing. Ask the supplier which one you are buying if it matters to the customer.</p>
<h2 id="fabric-and-decoration">Fabric and decoration</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Decoration"><table>
<thead>
<tr>
<th>Decoration</th>
<th>What the fabric needs</th>
</tr>
</thead>
<tbody><tr>
<td>Sublimation</td>
<td>Polyester, white or very light. The smoother the face, the sharper the print. Open mesh prints with less detail because part of the surface is holes</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/screen-printing">Screen printing</a></td>
<td>Works on cotton and blends easily. On polyester it needs low-bleed inks so the fabric dye does not tint the print</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/tackle-twill">Tackle twill</a></td>
<td>A stable fabric that can carry the weight of sewn-on numbers</td>
</tr>
<tr>
<td>Embroidery</td>
<td>A firm knit. Thin stretchy fabrics pucker under dense stitching</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/dtf">DTF</a></td>
<td>Most fabrics, pressed at a lower temperature on polyester</td>
</tr>
</tbody></table>
</div>
<p>More in <a href="https://uniformsos.com/blog/jersey-decoration-methods-compared">jersey decoration methods compared</a>.</p>
<h2 id="by-sport">By sport</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Sport"><table>
<thead>
<tr>
<th>Sport</th>
<th>Common fabric</th>
<th>Why</th>
</tr>
</thead>
<tbody><tr>
<td>Basketball</td>
<td>Interlock or micro mesh body, mesh side panels</td>
<td>Airflow and a clean print</td>
</tr>
<tr>
<td>Football</td>
<td>Heavier mesh or stretch knit body, dazzle or stretch yokes</td>
<td>It is worn over pads and gets grabbed</td>
</tr>
<tr>
<td>Soccer</td>
<td>Light interlock or birdseye</td>
<td>Ninety minutes of running</td>
</tr>
<tr>
<td>Baseball and softball</td>
<td>Double knit, or lighter interlock for sublimated styles</td>
<td>Sliding and durability</td>
</tr>
<tr>
<td>Volleyball</td>
<td>Stretch knit with spandex</td>
<td>A close fit that moves</td>
</tr>
<tr>
<td>Hockey</td>
<td>Heavy mesh or knit, cut wide</td>
<td>Worn over pads</td>
</tr>
<tr>
<td>Lacrosse</td>
<td>Mesh</td>
<td>Heat and contact</td>
</tr>
</tbody></table>
</div>
<h2 id="what-to-test-before-you-commit">What to test before you commit</h2>
<ol>
<li>Opacity. Hold a white swatch over a dark print.</li>
<li>Stretch and recovery. Pull it and see whether it returns.</li>
<li>Snagging. Run something rough across it. Open mesh snags more.</li>
<li>Pilling. Rub two swatches together for a minute.</li>
<li>Color after washing. Wash a printed swatch five times.</li>
<li><a href="https://uniformsos.com/glossary/shrinkage">Shrinkage</a>. Measure before and after washing.</li>
<li>Feel when wet. Some fabrics cling.</li>
</ol>
<p>A swatch card from the factory with the weight written on each fabric answers most questions before a sample is made.</p>
<h2 id="what-to-put-on-the-spec">What to put on the spec</h2>
<ul>
<li>Fiber content, such as 100 percent polyester or 88 percent polyester and 12 percent spandex.</li>
<li>Knit type.</li>
<li>Weight in GSM, with a <a href="https://uniformsos.com/glossary/tolerance">tolerance</a>.</li>
<li>Color, or white for sublimation.</li>
<li>Any finish, such as wicking.</li>
<li>Where each fabric goes, if the garment uses more than one.</li>
</ul>
<p>The fabric line belongs in the <a href="https://uniformsos.com/glossary/tech-pack">tech pack</a>, so that a reorder next season is made from the same cloth.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Jersey number rules for high school sports: sizes, legal numbers and placement</title>
    <link>https://uniformsos.com/blog/jersey-number-rules-high-school</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/jersey-number-rules-high-school</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Jerseys</category>
    <description>NFHS jersey number rules for basketball, football, volleyball, soccer and softball: minimum sizes, legal numbers, contrast, and what changes in 2028 and 2029.</description>
    <content:encoded><![CDATA[<p>NFHS sets jersey number rules sport by sport. Basketball numbers are at least 4 inches high on the front and 6 on the back, using only the digits 0 to 5. Football numbers are at least 8 inches on the front and 10 on the back. Volleyball, soccer, softball and baseball set their own. Check the current rule book and your state association before production.</p>
<p>A jersey can look perfect and still be illegal. High school officials check number size, color and style before the game. The team takes the penalty and the supplier takes the remake. This is a plain summary of the number rules published by the National Federation of State High School Associations (NFHS) for the sports behind most team orders, and how to build those rules into an order so nothing ships wrong.</p>
<h2 id="the-short-version">The short version</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Sport"><table>
<thead>
<tr>
<th>Sport</th>
<th>Front number</th>
<th>Back number</th>
<th>Number rules to know</th>
</tr>
</thead>
<tbody><tr>
<td>Basketball</td>
<td>At least 4 inches high</td>
<td>At least 6 inches high</td>
<td>Only 0, 00 and numbers made from the digits 0 to 5</td>
</tr>
<tr>
<td>Football</td>
<td>At least 8 inches high</td>
<td>At least 10 inches high</td>
<td>0 to 99, no leading zero</td>
</tr>
<tr>
<td>Volleyball</td>
<td>At least 4 inches high</td>
<td>At least 6 inches high</td>
<td>0 to 99, two digits at most, leading zeros end July 1, 2028</td>
</tr>
<tr>
<td>Soccer</td>
<td>At least 4 inches, on the jersey or the shorts</td>
<td>At least 6 inches, goalkeeper included</td>
<td>Number color must contrast with the jersey</td>
</tr>
<tr>
<td>Softball</td>
<td>Not required</td>
<td>At least 6 inches high</td>
<td>Solid color that contrasts with the shirt</td>
</tr>
<tr>
<td>Baseball</td>
<td>Not required</td>
<td>At least 8 inches high</td>
<td>Plain Arabic style, solid color that contrasts with the shirt</td>
</tr>
</tbody></table>
</div>
<p>Heights are minimums. Rules change most years, so check the current NFHS rule book and your state association before production.</p>
<h2 id="basketball">Basketball</h2>
<ul>
<li>Legal numbers are 0, 1, 2, 3, 4, 5, 00, 10 to 15, 20 to 25, 30 to 35, 40 to 45 and 50 to 55. No digit goes above 5. Officials report a foul to the scorer by showing the player&#39;s number on two hands, the first digit on the right hand and the second on the left.</li>
<li>A team cannot have both 0 and 00.</li>
<li>The front number is at least 4 inches high and the back number at least 6 inches high. Each stroke is at least 3/4 inch wide, not counting the border.</li>
<li>Numbers are plain Arabic numerals, centered, in the same color and style front and back.</li>
<li>Since the 2024-25 season the number must be a solid color that contrasts with the jersey, with no more than two solid 1/4 inch borders. A number can use up to three colors.</li>
</ul>
<h2 id="football">Football</h2>
<ul>
<li>Players are numbered 0 to 99. A number with a zero in front of it is illegal, so 07 is out.</li>
<li>The front number is at least 8 inches high and the back number at least 10 inches high, measured with any border.</li>
<li>The body of the number is about 1 1/2 inches wide, not counting borders.</li>
<li>Color and style match front and back.</li>
<li>Number choice ties to position. The rule book points to Rule 7-2-5 on which numbers can line up where, so take numbers by position from the coach. Do not assign them yourself.</li>
</ul>
<h2 id="volleyball">Volleyball</h2>
<ul>
<li>Numbers run 0 to 99 with two digits at most. Beginning July 1, 2028, a number with a leading zero is no longer legal, so 01, 02 and the like go away.</li>
<li>The front number is at least 4 inches high and the back number at least 6 inches high. The body of the number is at least 3/4 inch wide.</li>
<li>Numbers are plain Arabic numerals in a solid color, and no two teammates share one.</li>
<li>Today the front number sits in one of two places: with its top no more than 5 inches below the shoulder seam, or centered no more than 5 inches below the bottom edge of the neckline ribbing, placket or seams. Beginning July 1, 2029, the front number must be centered on the upper half of the top.</li>
<li>The libero&#39;s top follows the same number specifications.</li>
</ul>
<h2 id="soccer">Soccer</h2>
<ul>
<li>Every jersey carries a back number at least 6 inches high, including the goalkeeper&#39;s.</li>
<li>A front number at least 4 inches high goes on the jersey or the shorts.</li>
<li>The number color contrasts with the jersey and reads clearly.</li>
</ul>
<h2 id="softball">Softball</h2>
<ul>
<li>A back number is required and is at least 6 inches high.</li>
<li>It is a solid color that contrasts with the shirt.</li>
</ul>
<h2 id="baseball">Baseball</h2>
<ul>
<li>A back number is required and is at least 8 inches high. The rule asks for no front number.</li>
<li>It is a plain Arabic numeral in a solid color that contrasts with the shirt.</li>
<li>No two players on a team wear the same number.</li>
<li>A border around the number is no more than 1/4 inch wide.</li>
</ul>
<h2 id="who-sets-the-rule">Who sets the rule</h2>
<p>NFHS writes the rule books most US high schools play under. State associations adopt them and can publish their own exceptions, and so can junior high associations. College, club and recreation leagues play under different books. Ask two questions before you quote: which governing body, and which season is the first one these jerseys will be worn.</p>
<h2 id="order-for-the-rule-that-is-coming">Order for the rule that is coming</h2>
<p>Schools often keep a uniform set for several seasons. A volleyball set bought today will still be in the gym after July 1, 2028, when leading zeros stop being legal, and after July 1, 2029, when the front number has to be centered. Build today&#39;s order to the later rule.</p>
<h2 id="how-to-build-the-rules-into-an-order">How to build the rules into an order</h2>
<ol>
<li>At the quote, record the sport, the level, the governing body and the first season of use.</li>
<li>Check the roster before art starts. Every number is legal for the sport, no number repeats, and a basketball roster does not hold both 0 and 00.</li>
<li>Put number heights on the <a href="https://uniformsos.com/glossary/art-proof">proof</a> in inches, front and back, with the stroke width. The coach signs a proof that shows the sizes.</li>
<li>Check contrast on the real jersey color, not on a white mockup.</li>
<li>Check the smallest size in the order. An 8 inch front number and a 10 inch back number still have to sit flat on a youth small football jersey.</li>
<li>Do not design to the minimum. Set a 6 inch minimum at 6 1/4 inches so a small shift in decoration does not make the piece illegal.</li>
<li>Measure the first finished piece with a ruler before the run continues.</li>
</ol>
<p>See <a href="https://uniformsos.com/blog/jersey-decoration-methods-compared">jersey decoration methods compared</a> for how numbers are made in <a href="https://uniformsos.com/glossary/sublimation">sublimation</a>, <a href="https://uniformsos.com/glossary/tackle-twill">tackle twill</a> and print. The <a href="https://uniformsos.com/blog/team-uniform-sizing-guide">team uniform sizing guide</a> covers sizes, and the <a href="https://uniformsos.com/blog/league-uniform-ordering-timeline">league uniform ordering timeline</a> covers dates.</p>
<h2 id="rosters-in-uniformsos">Rosters in UniformsOS</h2>
<p>UniformsOS keeps the roster on the order line, one row per player with size, name and number, and the same rows show on the <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a>. In <a href="https://uniformsos.com/platform/team-stores">Team Stores</a> a product can take a player name and a number at checkout. The app does not check a number against a rule book, so that check stays with you.</p>
]]></content:encoded>
  </item>
  <item>
    <title>League uniform ordering timeline: when to order so jerseys arrive before the first game</title>
    <link>https://uniformsos.com/blog/league-uniform-ordering-timeline</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/league-uniform-ordering-timeline</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Leagues</category>
    <description>A week-by-week timeline for ordering league uniforms, working back from the first game, with sizing, rosters, spares and the mistakes that make uniforms late.</description>
    <content:encoded><![CDATA[<p>Plan league uniforms backward from the first game. For made-to-order sublimated uniforms, allow about 12 weeks: two for design and approval, three for registration and sizes, four to five for production, one for shipping and one spare. Stock jerseys with printed numbers can be done in three to four weeks. Get the supplier's lead time in writing before you set any date.</p>
<h2 id="work-backward-from-the-first-game">Work backward from the first game</h2>
<p>Most late uniforms were ordered on time by the calendar the league had in its head. That calendar started at registration. The right calendar starts at the first game and runs backward.</p>
<p>Production times vary by supplier and by season. Custom <a href="https://uniformsos.com/glossary/sublimation">sublimated</a> uniforms commonly take three to six weeks to make, and longer in the weeks before spring and fall seasons, when every league orders at once. Ask your supplier for its current <a href="https://uniformsos.com/glossary/lead-time">lead time</a>, in writing, and build the plan around that number.</p>
<h2 id="the-timeline">The timeline</h2>
<p>This plan assumes five weeks of production. Move the dates if your supplier quotes more or less.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Weeks before first game"><table>
<thead>
<tr>
<th>Weeks before first game</th>
<th>What happens</th>
</tr>
</thead>
<tbody><tr>
<td>12</td>
<td>Choose the supplier. Get the lead time and price in writing. Set the budget</td>
</tr>
<tr>
<td>12 to 10</td>
<td>Design. Mockups, one or two rounds of changes, board approval. <a href="https://uniformsos.com/blog/apparel-art-approval-process">Sign off artwork</a>, colors and sponsor logos</td>
</tr>
<tr>
<td>10 to 7</td>
<td>Registration. Collect each player&#39;s size with the registration form</td>
</tr>
<tr>
<td>7</td>
<td>Order deadline. Teams formed, numbers assigned, order placed, deposit paid</td>
</tr>
<tr>
<td>7 to 2</td>
<td>Production</td>
</tr>
<tr>
<td>2 to 1</td>
<td>Shipping. Count the delivery against the order the day it arrives</td>
</tr>
<tr>
<td>1</td>
<td>Sort by team and hand out to coaches</td>
</tr>
<tr>
<td>0</td>
<td>First game</td>
</tr>
</tbody></table>
</div>
<p>The spare week sits at the end, between delivery and the first game. Something will use it.</p>
<h2 id="design-decide-once">Design: decide once</h2>
<p>Approve one design system for the whole league: one cut, one layout, with team colors swapped in. Letting each coach design a jersey multiplies the approvals and the mistakes.</p>
<p>Keep the design for more than one season. Fill-in orders will match, and families with a second child get another year out of a jersey.</p>
<p>Sponsor logos need <a href="https://uniformsos.com/glossary/vector-file">vector files</a> and the sponsor&#39;s approval. Chase them in week 12. A missing logo file in week 7 holds up the whole order.</p>
<h2 id="sizes-collect-them-at-registration">Sizes: collect them at registration</h2>
<p>Make size a required field on the registration form, next to a size chart with real measurements. Youth large and adult small are not the same garment, and parents guess.</p>
<p>If the supplier offers sizing samples, bring them to evaluation day and let players try them on. It is the most reliable way to get sizes right.</p>
<h2 id="rosters-and-numbers">Rosters and numbers</h2>
<p>Assign numbers centrally. When parents choose, three players on one team ask for the same number. Check <a href="https://uniformsos.com/blog/jersey-number-rules-high-school">your sport&#39;s numbering rules</a> before you assign them.</p>
<p>Decide whether names go on the back. Names make hand-me-downs and trades between teams harder, and one misspelled name means a remake. Many recreational leagues print numbers only.</p>
<p>Lock the roster at the order deadline. Players who register after it go into a second order.</p>
<h2 id="spares-and-late-registrations">Spares and late registrations</h2>
<p>There will be late registrations. Plan for them in one of two ways.</p>
<p>Order spares with the main order: a few extra jerseys per team in the most common sizes, with numbers nobody has been given. This is the fastest way to dress a late player.</p>
<p>Or plan a fill-in order. Before you choose the supplier, ask what its minimum and lead time are for a small reorder of the same design. Some will run one piece. Some will not run fewer than a dozen.</p>
<h2 id="who-buys-the-league-or-the-parents">Who buys: the league or the parents</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Table"><table>
<thead>
<tr>
<th></th>
<th>League buys in bulk</th>
<th>Parents buy in a team store</th>
</tr>
</thead>
<tbody><tr>
<td>Who pays</td>
<td>The league, from registration fees</td>
<td>Each family, at checkout</td>
</tr>
<tr>
<td>Sizes and names</td>
<td>The league collects them</td>
<td>Each family enters its own</td>
</tr>
<tr>
<td>Risk of unpaid uniforms</td>
<td>The league carries it</td>
<td>None</td>
</tr>
<tr>
<td>Control over the deadline</td>
<td>Full</td>
<td>Depends on families ordering in time</td>
</tr>
<tr>
<td>Best for</td>
<td>Required uniforms included in the fee</td>
<td>Optional gear, travel teams, fan wear</td>
</tr>
</tbody></table>
</div>
<p>Many leagues do both. The uniform comes with registration, and a store sells hoodies and extras. See <a href="https://uniformsos.com/blog/how-team-stores-work">how team stores work</a>.</p>
<h2 id="what-the-order-must-include">What the order must include</h2>
<ul>
<li>The approved design for every team, with colors</li>
<li>Sponsor logos, placed and approved</li>
<li>The roster for each team: number, size and name if used</li>
<li>Totals by size, checked against the rosters</li>
<li>Spares</li>
<li>The delivery address</li>
<li>The in-hands date</li>
</ul>
<p>Give the supplier an in-hands date, not a ship date. &quot;Ships on the 10th&quot; and &quot;in your hands on the 10th&quot; are a week apart.</p>
<h2 id="mistakes-that-make-uniforms-late">Mistakes that make uniforms late</h2>
<p>Starting the clock at registration. Start it at the first game.</p>
<p>No lead time in writing. A lead time said on the phone in January is not the lead time in March.</p>
<p>Waiting for the last few registrations. Order on the deadline with what you have and put the rest in a fill-in order.</p>
<p>Changing the design after sign-off. Every change restarts approval.</p>
<p>Not counting the delivery. Count it by team and size the day it arrives, while there is still time to fix a shortage.</p>
<h2 id="if-you-are-already-late">If you are already late</h2>
<p>Switch to stock jerseys with printed or heat-applied numbers. They can be turned in three to four weeks, sometimes less. Or play the first week in last year&#39;s jerseys or practice shirts and tell parents the real date. A clear date is easier on everyone than a promise that slips.</p>
<h2 id="league-orders-in-uniformsos">League orders in UniformsOS</h2>
<p>UniformsOS keeps the roster on the order line, one row per player with size, name and number. A store in <a href="https://uniformsos.com/platform/team-stores">Team Stores</a> with a closing date collects the size and the payment from each family. <a href="https://uniformsos.com/platform/production-wip">Production WIP</a> tracks every order against its ship-by date and flags the ones running behind.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Managing apparel factories and purchase orders</title>
    <link>https://uniformsos.com/blog/managing-factories-and-purchase-orders</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/managing-factories-and-purchase-orders</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Factories</category>
    <description>How to run day-to-day work with apparel factories: what a purchase order must contain, splitting orders, confirmations, status updates, changes and receiving.</description>
    <content:encoded><![CDATA[<p>Manage factories with one rule: every job is a written purchase order that the factory confirms. The purchase order states the product, quantities by size, artwork, price, ship-by date and quality standard. One purchase order goes to one factory. Status is reported by stage on a fixed schedule, changes are written revisions, and every delivery is counted against the purchase order.</p>
<h2 id="what-a-purchase-order-must-contain">What a purchase order must contain</h2>
<p>A <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a>, or PO, is the contract for one job. If it is not on the PO, the factory did not agree to it.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Field"><table>
<thead>
<tr>
<th>Field</th>
<th>What it holds</th>
</tr>
</thead>
<tbody><tr>
<td>PO number</td>
<td>Your number, unique, and quoted on every message and box</td>
</tr>
<tr>
<td>Factory</td>
<td>Who is making it</td>
</tr>
<tr>
<td>Product</td>
<td>Style, fabric, cut and decoration method</td>
</tr>
<tr>
<td>Quantities</td>
<td>A grid by size, with a total</td>
</tr>
<tr>
<td>Artwork</td>
<td>The approved files, by name and version</td>
</tr>
<tr>
<td>Roster</td>
<td>Names and numbers by size, if the product is personalized</td>
</tr>
<tr>
<td>Price</td>
<td>Per piece, with any setup, and the currency</td>
</tr>
<tr>
<td>Ship-by date</td>
<td>The day the goods leave the factory</td>
</tr>
<tr>
<td>Ship to</td>
<td>Address and shipping method</td>
</tr>
<tr>
<td>Shipping terms</td>
<td>Who pays freight and duties</td>
</tr>
<tr>
<td>Quality standard</td>
<td>The approved sample or spec it must match, and <a href="https://uniformsos.com/blog/apparel-aql-inspection-guide">how it will be inspected</a></td>
</tr>
<tr>
<td>Packing</td>
<td>By player, by size or bulk, and how boxes are labeled</td>
</tr>
<tr>
<td>Payment terms</td>
<td>Deposit, balance and when each is due</td>
</tr>
</tbody></table>
</div>
<p>Two fields cause most disputes: the date and the quality standard. Write a ship-by date, not a delivery date, and name the sample or spec the goods will be checked against.</p>
<h2 id="one-purchase-order-one-factory">One purchase order, one factory</h2>
<p>A customer&#39;s order often goes to more than one place. The jerseys go to a <a href="https://uniformsos.com/glossary/sublimation">sublimation</a> factory. The hoodies go to a <a href="https://uniformsos.com/glossary/screen-printing">screen printer</a>. The caps go to an embroiderer.</p>
<p>Give each factory its own PO, linked to the same customer order. Each one can then be confirmed, tracked and late independently. An order with one line for three factories shows as &quot;in production&quot; until the day it is not.</p>
<p>The customer&#39;s ship date is then set by the slowest PO, and you can see which one that is.</p>
<h2 id="get-a-confirmation">Get a confirmation</h2>
<p>A sent PO is not an accepted PO. Ask the factory to confirm three things in writing within a day: the quantities, the price and the ship-by date.</p>
<p>If the factory cannot meet the date, you want to hear it now, while you can move the job or reset the customer&#39;s expectations. A PO with no confirmation after a day gets a phone call.</p>
<h2 id="status-by-stage-on-a-schedule">Status by stage, on a schedule</h2>
<p>Agree how the factory reports progress before the first order, and use stages, not adjectives. &quot;Sewing, 60 of 140 done&quot; is a status. &quot;Going well&quot; is not.</p>
<p>Two things make this work:</p>
<ul>
<li>Fixed stages that both sides use. See <a href="https://uniformsos.com/blog/apparel-production-stages">production stages</a>.</li>
<li>A fixed rhythm. The factory updates when a job changes stage, or at the same time every day.</li>
</ul>
<p>Then you watch the exceptions. Any PO that has not moved in longer than that stage normally takes gets a question. The <a href="https://uniformsos.com/blog/apparel-wip-report">WIP report</a> is where you see them.</p>
<h2 id="changes-are-written-revisions">Changes are written revisions</h2>
<p>Customers add players. Sizes change. A sponsor logo arrives late. Every change after the PO is sent goes out as a numbered revision: PO 1042, revision 2, with what changed.</p>
<p>Ask the factory to confirm the revision and say whether the date or the price moves. A change agreed in a chat message is the one that will be missing from the box.</p>
<p>Set a cutoff. After cutting begins, changes become a new PO.</p>
<h2 id="receiving">Receiving</h2>
<p>Count every delivery against the PO the day it arrives, by size. For personalized orders, check names and numbers against the roster.</p>
<p>Record three things: what was short, what was wrong and what was damaged. Send the factory the list with photos the same day. Claims made a week later are harder to settle, and the customer&#39;s deadline has not moved.</p>
<p>Pay the balance after the count, or after a pre-shipment inspection for factories that ship direct to your customer.</p>
<h2 id="factories-that-ship-direct-to-the-customer">Factories that ship direct to the customer</h2>
<p>When the factory ships to the customer, you never see the goods. Three things replace your receiving check:</p>
<ol>
<li>Photos of the packed order and the <a href="https://uniformsos.com/glossary/packing-list">packing list</a> before it ships.</li>
<li>The tracking number the day it leaves.</li>
<li>A message to the customer asking them to count the delivery within two days.</li>
</ol>
<h2 id="scorecards">Scorecards</h2>
<p>Review each factory every quarter on the same numbers:</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Measure"><table>
<thead>
<tr>
<th>Measure</th>
<th>How to calculate it</th>
</tr>
</thead>
<tbody><tr>
<td>On-time rate</td>
<td>POs shipped on or before the ship-by date, divided by POs shipped</td>
</tr>
<tr>
<td>Confirmation time</td>
<td>Hours from PO sent to PO confirmed</td>
</tr>
<tr>
<td>Defect rate</td>
<td>Pieces rejected, divided by pieces received</td>
</tr>
<tr>
<td>Shortage rate</td>
<td>POs delivered short, divided by POs delivered</td>
</tr>
<tr>
<td>Average days late</td>
<td>For late POs only</td>
</tr>
</tbody></table>
</div>
<p>Share the numbers with the factory. Good factories want them. Then move volume toward the ones that perform, and say that this is how volume is decided.</p>
<h2 id="peak-season">Peak season</h2>
<p>Every factory is full in the same weeks, before fall and spring seasons. Three habits help:</p>
<ul>
<li>Tell your factories your expected volume a month or two ahead, even roughly.</li>
<li>Place POs as early as approvals allow. The line is first come, first served.</li>
<li>Keep a second qualified factory for each core product, and send it real work in quiet months so it knows your specs. See <a href="https://uniformsos.com/blog/how-to-vet-apparel-manufacturer">how to vet a manufacturer</a>.</li>
</ul>
<h2 id="mistakes">Mistakes</h2>
<p>Ordering by chat. Messages get buried and nobody can find the final version.</p>
<p>A delivery date with no ship-by date.</p>
<p>No size grid. &quot;140 jerseys, sizes to follow&quot; is not an order.</p>
<p>Paying the balance before counting.</p>
<p>One factory for everything. The day it is late, every order is late.</p>
<h2 id="purchase-orders-in-uniformsos">Purchase orders in UniformsOS</h2>
<p>In UniformsOS you send an order to a factory by choosing the factory and the units, and an order split across factories gets one purchase order for each. The factory signs in to its own portal, accepts the purchase order and reports the stage, and that moves the order on your side. A board shows open purchase orders by factory, by stage or by lateness. See <a href="https://uniformsos.com/platform/manufacturers">Manufacturers and Vendors</a>, <a href="https://uniformsos.com/platform/production-wip">Production WIP</a> and <a href="https://uniformsos.com/solutions/factories">UniformsOS for factories</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Spreadsheets or apparel software: when to switch</title>
    <link>https://uniformsos.com/blog/spreadsheets-vs-apparel-software</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/spreadsheets-vs-apparel-software</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Apparel software</category>
    <description>What spreadsheets do well for a custom apparel business, the eight ways they break as orders grow, and a one-week count that shows what they cost you.</description>
    <content:encoded><![CDATA[<p>Spreadsheets work for a custom apparel business while one person enters every order. They fail when two people edit at once, when the same order is typed into a quote, a factory sheet and an invoice, and when nobody can see production status without asking. Switch when the retyping and the status calls cost more each month than the software does.</p>
<h2 id="what-spreadsheets-do-well">What spreadsheets do well</h2>
<p>They are free, flexible and familiar. You can build a quote calculator in an afternoon and change it the next morning. For analysis, nothing beats them: sort last year&#39;s orders by customer, margin or month in a few clicks.</p>
<p>Plenty of shops run their first few hundred orders on a spreadsheet, and that is a reasonable way to start.</p>
<h2 id="where-they-break">Where they break</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Symptom"><table>
<thead>
<tr>
<th>Symptom</th>
<th>Why the spreadsheet causes it</th>
</tr>
</thead>
<tbody><tr>
<td>Two versions of the order</td>
<td>Files get copied, emailed and edited separately</td>
</tr>
<tr>
<td>Typing errors in sizes and names</td>
<td>The same order is retyped for the quote, the factory and the invoice</td>
</tr>
<tr>
<td>&quot;Where is my order?&quot; needs a phone call</td>
<td>A sheet does not know what happened on the floor</td>
</tr>
<tr>
<td>The invoice does not match the order</td>
<td>Nothing links the two</td>
</tr>
<tr>
<td>The factory sees too much or nothing</td>
<td>A file is shared whole or not at all</td>
</tr>
<tr>
<td>Nobody knows who changed it</td>
<td>There is no record of edits that anyone reads</td>
</tr>
<tr>
<td>Totals are quietly wrong</td>
<td>A formula was overwritten three weeks ago</td>
</tr>
<tr>
<td>Things get forgotten</td>
<td>A sheet cannot remind anyone of anything</td>
</tr>
</tbody></table>
</div>
<p>None of these is a mistake by the person using it. A spreadsheet is a grid of cells. It does not know that row 40 is an order with a customer, a factory and a deadline.</p>
<h2 id="if-you-stay-on-spreadsheets-for-now">If you stay on spreadsheets for now</h2>
<p>Fix the structure. These changes cost nothing.</p>
<ol>
<li>One master sheet with one row per order. Not one file per job.</li>
<li>An order number on every row, and on everything that refers to it.</li>
<li>Fixed columns that nobody adds to without agreement.</li>
<li>A dropdown for the production stage, so everyone uses the same words.</li>
<li>One size grid template, used for every order.</li>
<li>Locked formula cells.</li>
<li>One owner. Other people ask the owner to change the structure.</li>
<li>Sizes and rosters collected through a form that writes into the sheet, not typed from emails.</li>
</ol>
<p>A shop that does these eight things will get another year out of spreadsheets, and its data will be clean when it moves.</p>
<h2 id="the-one-week-count">The one-week count</h2>
<p>For one normal week, count three things:</p>
<ul>
<li>How many times an order&#39;s details were retyped from one place to another.</li>
<li>How many status questions needed someone to stop and look something up.</li>
<li>How many errors came from a wrong version or a typing mistake.</li>
</ul>
<p>Then put a cost on it. An example with made-up numbers:</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Item"><table>
<thead>
<tr>
<th>Item</th>
<th>Count per month</th>
<th>Minutes each</th>
<th>Hours</th>
</tr>
</thead>
<tbody><tr>
<td>Retyping: 60 orders, 3 times each</td>
<td>180</td>
<td>6</td>
<td>18</td>
</tr>
<tr>
<td>Status questions</td>
<td>120</td>
<td>5</td>
<td>10</td>
</tr>
<tr>
<td>Total</td>
<td></td>
<td></td>
<td>28</td>
</tr>
</tbody></table>
</div>
<p>At $25 an hour, that is $700 a month before a single error. One remake caused by a retyped size can add a few hundred dollars more.</p>
<p>Compare that figure with the monthly cost of software. If the software costs less, the spreadsheet is the expensive option.</p>
<h2 id="what-software-changes">What software changes</h2>
<p>One record. The quote becomes the order, the order creates the <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a> and the invoice, and nobody types it twice.</p>
<p>Status that updates. When a job moves, everyone who needs to know can see it.</p>
<p>Access by role. A factory sees its own jobs. A customer sees their own order.</p>
<p>Reminders. Approvals, deposits and deadlines are chased without someone remembering to do it.</p>
<h2 id="what-software-does-not-change">What software does not change</h2>
<p>A messy process. If nobody owns artwork approval today, software will show you that more clearly. It will not assign an owner.</p>
<p>Bad data. Duplicate customers and three spellings of one product come along unless you clean them first.</p>
<p>The need to act. Software shows a late order earlier. Someone still has to pick up the phone.</p>
<h2 id="how-to-move">How to move</h2>
<ol>
<li>Clean the customer list and the product list. Merge duplicates. Fix names.</li>
<li>Decide what to bring: customers, products and open orders. Leave old orders in the spreadsheet as an archive.</li>
<li>Pick one order type and run it in the software from start to finish.</li>
<li>Set a cutoff date. From that day, every new order starts in the software.</li>
<li>Finish the old orders where they began. Do not move an order in the middle of production.</li>
<li>After one full cycle, stop updating the old sheet.</li>
</ol>
<p>The step people skip is the cutoff date. Without one, both systems stay half alive.</p>
<h2 id="keep-the-spreadsheet-for-what-it-is-good-at">Keep the spreadsheet for what it is good at</h2>
<p>Export data from the software and analyze it in a spreadsheet. Plan a season in one. Model a price change. Those are the jobs it was built for.</p>
<p>For a guide to the software itself, see <a href="https://uniformsos.com/blog/apparel-erp-software-guide">apparel ERP software: what it does and how to choose one</a>.</p>
<h2 id="moving-to-uniformsos">Moving to UniformsOS</h2>
<p>In UniformsOS the order is one record that the quote, the invoice, the purchase order and the <a href="https://uniformsos.com/glossary/wip">WIP</a> sheet all read, so nothing is copied between tabs. The free trial runs 30 days with every module on and no card, and a new workspace can load a sample catalog to test with. Each module is priced on its own on the <a href="https://uniformsos.com/pricing">pricing page</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Stitch types in sportswear: what a jersey is sewn with</title>
    <link>https://uniformsos.com/blog/sportswear-stitch-types</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/sportswear-stitch-types</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Jerseys</category>
    <description>Lockstitch, chainstitch, overlock, coverstitch, flatlock and zigzag, with their ASTM D6193 and ISO 4915 class numbers and where each one goes on a jersey.</description>
    <content:encoded><![CDATA[<p>Most team jerseys are built from five or six stitch types. A four-thread overlock (class 514) joins the panels. A two-needle coverstitch (406) hems the sleeves and bottom. A lockstitch (301) attaches labels and plackets. A flatlock (607) joins panels on tight garments. A zigzag (304) sews down twill numbers. The class numbers come from ASTM D6193 and ISO 4915.</p>
<h2 id="why-the-numbers-matter">Why the numbers matter</h2>
<p>&quot;<a href="https://uniformsos.com/glossary/overlock">Overlock</a> the side seams&quot; means different things in different factories. Three threads or four? One needle or two? A class number removes the question. 514 is a four-thread overedge stitch in every factory in the world.</p>
<p>Two standards define the numbers. ASTM D6193 is the US standard practice for stitches and seams. ISO 4915 is the international standard for stitch types. They use the same three-digit numbers for the common stitches, so a tech pack written to one is read correctly by a factory that works to the other.</p>
<p>The first digit is the class.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Class"><table>
<thead>
<tr>
<th>Class</th>
<th>Family</th>
<th>How it is formed</th>
</tr>
</thead>
<tbody><tr>
<td>100</td>
<td>Single-thread <a href="https://uniformsos.com/glossary/chain-stitch">chainstitch</a></td>
<td>One needle thread looped through itself</td>
</tr>
<tr>
<td>200</td>
<td>Hand stitch</td>
<td>Stitches first made by hand, now also by machine</td>
</tr>
<tr>
<td>300</td>
<td><a href="https://uniformsos.com/glossary/lockstitch">Lockstitch</a></td>
<td>A needle thread locked with a bobbin thread</td>
</tr>
<tr>
<td>400</td>
<td>Multi-thread chainstitch</td>
<td>Needle threads looped with a looper thread underneath</td>
</tr>
<tr>
<td>500</td>
<td>Overedge</td>
<td>Threads wrapped around the cut edge of the fabric</td>
</tr>
<tr>
<td>600</td>
<td>Covering stitch</td>
<td>Needle threads, a looper thread underneath and a cover thread on top</td>
</tr>
</tbody></table>
</div>
<h2 id="the-stitches-on-a-jersey">The stitches on a jersey</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Stitch"><table>
<thead>
<tr>
<th>Stitch</th>
<th>Class</th>
<th>Needles and threads</th>
<th>Stretch</th>
<th>Where it goes</th>
</tr>
</thead>
<tbody><tr>
<td>Lockstitch</td>
<td>301</td>
<td>1 needle, 2 threads</td>
<td>Low</td>
<td>Labels, plackets, pockets, woven trims</td>
</tr>
<tr>
<td>Zigzag lockstitch</td>
<td>304</td>
<td>1 needle, 2 threads</td>
<td>Medium</td>
<td><a href="https://uniformsos.com/glossary/tackle-twill">Tackle twill</a> letters and numbers, elastic</td>
</tr>
<tr>
<td>Chainstitch</td>
<td>401</td>
<td>1 needle, 2 threads</td>
<td>Medium</td>
<td>Waistbands, binding, long seams on wovens</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/coverstitch">Coverstitch</a></td>
<td>406</td>
<td>2 needles, 3 threads</td>
<td>High</td>
<td>Sleeve and bottom hems, topstitching over seams</td>
</tr>
<tr>
<td>Three-thread overlock</td>
<td>504</td>
<td>1 needle, 3 threads</td>
<td>High</td>
<td>Edge finishing, light seams</td>
</tr>
<tr>
<td>Four-thread overlock</td>
<td>514</td>
<td>2 needles, 4 threads</td>
<td>High</td>
<td>Side, shoulder and sleeve seams on knits</td>
</tr>
<tr>
<td>Top and bottom coverstitch</td>
<td>602 or 605</td>
<td>2 or 3 needles, 4 or 5 threads</td>
<td>High</td>
<td>Flat decorative seams, binding, collars</td>
</tr>
<tr>
<td>Flatlock</td>
<td>607</td>
<td>4 needles, 6 threads</td>
<td>High</td>
<td>Panel seams on compression and fitted garments</td>
</tr>
</tbody></table>
</div>
<h2 id="lockstitch-301">Lockstitch (301)</h2>
<p>This is the stitch a home sewing machine makes. A needle thread and a bobbin thread lock together in the middle of the fabric. It looks the same on both sides, it does not run when a thread breaks, and it uses the least thread of any stitch here.</p>
<p>It also stretches the least. Pull a lockstitched seam on a knit and the thread breaks before the fabric gives. So on a jersey you find it only where the fabric is not meant to stretch: sewing in a label, setting the button placket on a baseball jersey, attaching a pocket or a woven patch. <a href="https://uniformsos.com/glossary/bartack">Bartacks</a>, the short dense reinforcements at stress points, are lockstitch as well.</p>
<p>The bobbin is its weak point in production. It holds a limited amount of thread, and changing it stops the machine.</p>
<h2 id="chainstitch-401">Chainstitch (401)</h2>
<p>A needle thread passes through the fabric and is looped with a separate looper thread underneath. The top looks like a lockstitch. The underside shows a chain.</p>
<p>There is no bobbin, so the machine runs longer and faster. The seam stretches more than a lockstitch. The trade-off is security. If the thread end is not locked off, a chainstitch can unravel back along the seam.</p>
<p>In sportswear it sews long seams on woven shorts and pants, attaches waistbands, usually with several needles side by side, and sets binding.</p>
<h2 id="overlock-504-and-514">Overlock (504 and 514)</h2>
<p>An overlock trims the fabric edge and wraps thread around it in one pass. It is also called an overedge stitch or serging. It joins two panels and finishes the raw edge at the same time, and it stretches with the fabric. It is the main construction stitch on knit garments.</p>
<p>504 uses one needle and two loopers, three threads in all. It finishes edges and makes light seams.</p>
<p>514 adds a second needle and a fourth thread. The extra row of needle stitching makes the seam more secure, which is why it is the usual choice for side seams, shoulders and sleeves on jerseys.</p>
<p>An overlocked seam leaves a seam allowance standing up inside the garment. On a loose jersey nobody notices. On a tight garment it can rub.</p>
<h2 id="coverstitch-406-602-and-605">Coverstitch (406, 602 and 605)</h2>
<p>Look at the hem of any T-shirt. Two parallel rows of stitching show on the outside and a looped pattern on the inside. That is a 406: two needles and one looper thread. It holds a folded hem flat and stretches with it.</p>
<p>The same stitch is run over an overlocked seam to hold the allowance down. You see it on shoulder seams and around armholes.</p>
<p>The 600-class versions add a cover thread on top, so the looped pattern shows on both faces. 602 has two needles and 605 has three. They are used for decorative seams, for binding necklines and for the flat finished look on performance wear.</p>
<h2 id="flatlock-607">Flatlock (607)</h2>
<p>Four needles and six threads. The two panels are trimmed and butted edge to edge, not stacked, and the stitch covers the join on both faces. There is no seam allowance.</p>
<p>It is the seam on compression tops, base layers, leggings and fitted training gear, where anything raised would chafe. It needs a dedicated machine. It is slower than an overlock and uses far more thread, so it costs more per seam. More in the <a href="https://uniformsos.com/glossary/flatlock-stitch">flatlock stitch</a> entry.</p>
<h2 id="zigzag-304">Zigzag (304)</h2>
<p>A lockstitch that swings from side to side. The swing gives it stretch that a straight lockstitch does not have.</p>
<p>On team uniforms its main job is tackle twill. Letters and numbers cut from twill are placed on the jersey and sewn down around every edge with a tight zigzag. It also attaches elastic.</p>
<h2 id="a-basketball-jersey-seam-by-seam">A basketball jersey, seam by seam</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Part"><table>
<thead>
<tr>
<th>Part</th>
<th>Usual stitch</th>
</tr>
</thead>
<tbody><tr>
<td>Side seams</td>
<td>514 four-thread overlock</td>
</tr>
<tr>
<td>Shoulder seams</td>
<td>514, often with a 406 coverstitch on top</td>
</tr>
<tr>
<td>Neck and armhole binding</td>
<td>406 or 605 coverstitch with a binding attachment</td>
</tr>
<tr>
<td>Bottom hem</td>
<td>406 coverstitch</td>
</tr>
<tr>
<td>Brand and size label</td>
<td>301 lockstitch</td>
</tr>
<tr>
<td>Twill numbers, if the jersey has them</td>
<td>304 zigzag</td>
</tr>
</tbody></table>
</div>
<p>A compression shirt swaps the 514 seams for 607 flatlock. A baseball jersey adds lockstitch work on the button placket.</p>
<h2 id="what-to-put-in-a-tech-pack">What to put in a tech pack</h2>
<ol>
<li>The stitch class for every seam and hem, by number.</li>
<li>Stitches per inch. Most knit teamwear is sewn at 10 to 14. Fewer stitches sew faster and hold less. Too many can pucker or damage a light knit.</li>
<li>Needle spacing for coverstitch hems, such as 1/4 inch.</li>
<li>Thread. Polyester for strength and <a href="https://uniformsos.com/glossary/colorfastness">colorfastness</a>. Textured polyester in the loopers where the seam touches skin, because it is softer.</li>
<li>The seam type. ASTM D6193 covers seams as well as stitches. ISO covers them separately, in ISO 4916.</li>
</ol>
<p>See the <a href="https://uniformsos.com/glossary/tech-pack">tech pack</a> entry for the rest of the document.</p>
<h2 id="seam-problems-and-what-causes-them">Seam problems and what causes them</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Problem"><table>
<thead>
<tr>
<th>Problem</th>
<th>Usual cause</th>
</tr>
</thead>
<tbody><tr>
<td>Thread breaks when the seam is stretched</td>
<td>A low-stretch stitch on a stretch fabric, or too few stitches per inch</td>
</tr>
<tr>
<td>Seam puckers</td>
<td>Thread tension too high, or too many stitches for the fabric</td>
</tr>
<tr>
<td>Small holes along the seam</td>
<td>A needle that is too large, damaged or the wrong point for knits</td>
</tr>
<tr>
<td>Seam unravels from the end</td>
<td>A chainstitch or coverstitch that was not secured</td>
</tr>
<tr>
<td>Seam rubs the skin</td>
<td>An overlock allowance on a tight garment. Use flatlock, or cover the seam</td>
</tr>
</tbody></table>
</div>
]]></content:encoded>
  </item>
  <item>
    <title>Sublimation, screen printing, embroidery, tackle twill or DTF: how to choose jersey decoration</title>
    <link>https://uniformsos.com/blog/jersey-decoration-methods-compared</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/jersey-decoration-methods-compared</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Jerseys</category>
    <description>Five ways to decorate team jerseys compared by fabric, quantity, feel, durability and cost drivers, with a simple way to choose between them.</description>
    <content:encoded><![CDATA[<p>For full-color team jerseys on polyester, sublimation is the default. The design is dyed into the fabric, so it cannot crack or peel, and one color costs the same as twenty. Screen printing wins on large runs of simple designs, mostly on cotton. Tackle twill gives the stitched pro look. Embroidery suits small logos. DTF covers short runs and add-on names.</p>
<h2 id="the-five-methods-at-a-glance">The five methods at a glance</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Method"><table>
<thead>
<tr>
<th>Method</th>
<th>How it works</th>
<th>Best on</th>
<th>Feel</th>
<th>Makes sense for</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://uniformsos.com/glossary/sublimation">Sublimation</a></td>
<td>Dye is printed on paper, turned to gas by heat and bonded into polyester fibers</td>
<td>White or light polyester</td>
<td>None. It is part of the fabric</td>
<td>Full-color team jerseys at any quantity</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/screen-printing">Screen printing</a></td>
<td>Ink is pushed through a mesh screen, one screen per color, then cured</td>
<td>Cotton and blends</td>
<td>A layer of ink, light to heavy</td>
<td>Runs of a few dozen and up in one to four colors</td>
</tr>
<tr>
<td>Embroidery</td>
<td>Thread is stitched from a <a href="https://uniformsos.com/glossary/embroidery-digitizing">digitized</a> file</td>
<td>Polos, caps, jackets, heavier knits</td>
<td>Raised and textured</td>
<td>Small logos, staff and coaches&#39; wear</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/tackle-twill">Tackle twill</a></td>
<td>Twill letters and numbers are cut out and sewn onto the garment</td>
<td>Football, hockey and baseball jerseys</td>
<td>Layered and stitched</td>
<td>Premium names and numbers</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/dtf">DTF</a></td>
<td>The design is printed on film with adhesive and heat-pressed on</td>
<td>Cotton, polyester and blends, light or dark</td>
<td>A thin flexible film</td>
<td>Short runs, one-offs, names on stock jerseys</td>
</tr>
</tbody></table>
</div>
<h2 id="sublimation">Sublimation</h2>
<p>Sublimation ink is a dye. It is printed onto transfer paper, then pressed against the fabric at roughly 380 to 400°F. The heat turns the dye into gas, and the gas bonds with the polyester fibers. When the fabric cools, the color is inside it.</p>
<p>Three things follow from that.</p>
<p>It only works on polyester. Cotton does not hold the dye. On a blend, only the polyester part takes color, so the print looks faded.</p>
<p>There is no white ink. White in the design is the fabric showing through, so the base fabric has to be white or very light. A black sublimated jersey is white fabric dyed black in the press.</p>
<p>Coverage and variety are free. Panels are usually printed before the jersey is sewn, so the design can run across seams and side panels. Every jersey can carry a different name and number with no extra setup, because each one is printed from its own file anyway.</p>
<p>The cost per piece is fairly flat. Ten jerseys are practical, and so are five hundred. The trade-off is time. Most sublimated jerseys are cut and sewn to order, which takes longer than decorating a blank. Exact color matches also take a test print, because the same file prints differently on different fabrics.</p>
<h2 id="screen-printing">Screen printing</h2>
<p>Each color in the design needs its own screen. Ink is pushed through the open areas of the mesh onto the garment, one color at a time, then cured with heat. Standard <a href="https://uniformsos.com/glossary/plastisol-ink">plastisol ink</a> cures at around 320°F.</p>
<p>The setup is where the cost is. Films, screens and registration have to be done before the first shirt is printed. After that, each print costs very little. So the price per piece falls quickly with quantity, and every extra color adds a screen.</p>
<p>Polyester is the hard case. Under heat, the dye in a polyester garment can migrate into the ink. A white print on a red jersey turns pink a day later. Printers deal with it using low-bleed inks, blocking underbases and lower cure temperatures.</p>
<p>Screen printing is the right tool for cotton tees, hoodies, practice shirts and fan wear in volume. It is the wrong tool for individual names and numbers, since each one would be its own setup.</p>
<h2 id="embroidery">Embroidery</h2>
<p>Artwork is converted into a <a href="https://uniformsos.com/glossary/dst-file">stitch file</a>. This is called digitizing, and it is usually a one-time charge per design. The machine then stitches the design through the garment, with a backing behind the fabric to keep it stable. Price follows <a href="https://uniformsos.com/glossary/stitch-count">stitch count</a>.</p>
<p>Embroidery looks and wears well on stable fabrics. On thin, stretchy performance fabric, dense stitching puckers, and the backing can rub against the skin. Small lettering has a floor. Below about a quarter inch in height, letters fill in and stop being readable.</p>
<p>Use it for chest logos on polos, quarter-zips, jackets and caps.</p>
<h2 id="tackle-twill">Tackle twill</h2>
<p>Letters and numbers are cut from polyester twill, often in two layers for an outline, placed on the jersey and sewn down around the edges with a zigzag stitch. It is the stitched look of traditional football, hockey and baseball jerseys.</p>
<p>It lasts as long as the garment. It also adds weight and stiffness, and every name and number is cut and sewn by a person or a programmed machine, so it costs more per piece than any printed method. On lightweight jerseys built for airflow it is less common for that reason.</p>
<h2 id="dtf">DTF</h2>
<p>DTF stands for direct to film. A printer lays down colored ink and a white layer on a clear film. Adhesive powder is applied and melted. The film is then heat-pressed onto the garment, typically at 300 to 325°F for 10 to 15 seconds, and peeled away. Polyester is pressed cooler, around 270 to 300°F, so the garment dye does not bleed into the print.</p>
<p>It works on cotton, polyester and blends, on light or dark garments, in full color, with no minimum. That makes it useful for short runs, reorders of three pieces, sponsor logos added late and names on stock jerseys.</p>
<p>The print sits on top of the fabric. Small designs feel fine. Large solid areas feel like a film and do not breathe. Durability is good when it is pressed correctly, but it is below sublimation and twill.</p>
<h2 id="how-to-choose">How to choose</h2>
<ol>
<li>Start with the fabric. Polyester performance jersey: sublimation. Cotton: screen printing or DTF.</li>
<li>Look at how many pieces are identical. Every piece different, with names and numbers: sublimation, twill or DTF. Hundreds the same: screen printing.</li>
<li>Look at the design. Full coverage, gradients or many colors: sublimation. One or two solid colors: screen printing.</li>
<li>Decide on the look. Stitched and traditional: tackle twill. A raised logo: embroidery.</li>
<li>Check the deadline. Decorating stock blanks is faster than cutting and sewing a sublimated jersey from scratch.</li>
</ol>
<h2 id="mixing-methods">Mixing methods</h2>
<p>Shops combine them all the time. A sublimated football jersey with tackle twill numbers. A screen-printed practice tee with DTF names. A sublimated warmup with an embroidered crest. The rule is one method per job it does best.</p>
<h2 id="what-drives-the-cost">What drives the cost</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Method"><table>
<thead>
<tr>
<th>Method</th>
<th>The cost is driven by</th>
</tr>
</thead>
<tbody><tr>
<td>Sublimation</td>
<td>Fabric and sewing labor. Colors are free</td>
</tr>
<tr>
<td>Screen printing</td>
<td>Setup per color, then very little per print</td>
</tr>
<tr>
<td>Embroidery</td>
<td>Stitch count</td>
</tr>
<tr>
<td>Tackle twill</td>
<td>The number of pieces and layers sewn on</td>
</tr>
<tr>
<td>DTF</td>
<td>The printed area</td>
</tr>
</tbody></table>
</div>
<h2 id="keeping-decoration-straight-across-orders">Keeping decoration straight across orders</h2>
<p>The decoration method changes what the factory needs, how long the job takes and what it costs. In UniformsOS it is part of the product record, next to variants and pricing, so the quote and the order carry the same spec. See <a href="https://uniformsos.com/platform/products">Products and SKUs</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Team uniform sizing: how to measure players and get sizes right</title>
    <link>https://uniformsos.com/blog/team-uniform-sizing-guide</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/team-uniform-sizing-guide</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Teams</category>
    <description>How to collect sizes for a team order: body and garment measurements, reading a size chart, youth and adult overlap, fit by sport and sizing kits.</description>
    <content:encoded><![CDATA[<p>To size a team, use the supplier's own size chart, measure each player's chest, waist and height, and choose the size from the chart, not from what they wear in another brand. Where a player falls between sizes, go up. For large orders, a sizing kit that players try on is the most reliable method. Wrong sizes are the most common reason for remakes.</p>
<h2 id="two-kinds-of-measurement">Two kinds of measurement</h2>
<p>A size chart shows one of two things, and you need to know which.</p>
<p>Body measurements describe the player: chest, waist, hips, height. You measure the person and find the size.</p>
<p>Garment measurements describe the jersey laid flat: chest width, body length, sleeve length. You compare them to a jersey the player already owns and likes.</p>
<p>A garment is always larger than the body it fits. The difference is called ease. A loose basketball jersey has a lot of ease. A compression top has less than none, because it stretches.</p>
<p>Mixing the two charts is how a player with a 36-inch chest ends up in a jersey that measures 36 inches around.</p>
<h2 id="how-to-measure-a-player">How to measure a player</h2>
<p>Use a soft tape. Measure over a T-shirt, not a hoodie.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Measurement"><table>
<thead>
<tr>
<th>Measurement</th>
<th>How</th>
</tr>
</thead>
<tbody><tr>
<td>Chest</td>
<td>Around the fullest part, under the arms, tape level, arms down</td>
</tr>
<tr>
<td>Waist</td>
<td>Around the natural waist, where the body bends to the side</td>
</tr>
<tr>
<td>Hips</td>
<td>Around the fullest part of the seat</td>
</tr>
<tr>
<td>Height</td>
<td>Standing against a wall, without shoes</td>
</tr>
<tr>
<td>Inseam</td>
<td>From the crotch to the ankle bone, for pants</td>
</tr>
</tbody></table>
</div>
<p>Write the numbers down. Do not let anyone round to the size they think they are.</p>
<h2 id="how-to-measure-a-garment">How to measure a garment</h2>
<p>Lay it flat and smooth, and measure straight across.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Measurement"><table>
<thead>
<tr>
<th>Measurement</th>
<th>How</th>
</tr>
</thead>
<tbody><tr>
<td>Chest width</td>
<td>Across the front, one inch below the armholes, edge to edge</td>
</tr>
<tr>
<td>Body length</td>
<td>From the highest point of the shoulder, beside the collar, straight down to the hem</td>
</tr>
<tr>
<td>Sleeve length</td>
<td>From the shoulder seam to the sleeve edge</td>
</tr>
<tr>
<td>Waist, for shorts</td>
<td>Across the waistband, relaxed</td>
</tr>
<tr>
<td>Inseam, for shorts and pants</td>
<td>From the crotch seam down the inner leg to the hem</td>
</tr>
</tbody></table>
</div>
<p>Chest width is half the distance around. A jersey that measures 21 inches across is 42 inches around.</p>
<h2 id="reading-the-chart">Reading the chart</h2>
<p>Every brand and factory has its own chart. A medium from one supplier is not a medium from another. Always use the chart for the product you are ordering.</p>
<p>Find the player&#39;s chest first. Then check height or body length. If the two point to different sizes, choose by chest for tops and by waist for bottoms, then check that the length works.</p>
<p>Between sizes, go up. A slightly loose jersey gets worn. A tight one comes back.</p>
<p>Charts list a <a href="https://uniformsos.com/glossary/tolerance">tolerance</a>, often half an inch either way. Two jerseys of the same size can differ by that much and both be correct.</p>
<h2 id="youth-and-adult-sizes-overlap">Youth and adult sizes overlap</h2>
<p>A youth XL and an adult small are close in chest and different in length and shoulder width. Players aged roughly 11 to 14 can fall into either.</p>
<p>Put youth and adult sizes on one chart, in order, so parents can see where they meet. Label them clearly: YL, YXL, AS, AM. An order that only says &quot;L&quot; will be made in whichever one the factory guesses.</p>
<h2 id="women-s-cuts">Women&#39;s cuts</h2>
<p>A women&#39;s cut is a different pattern: narrower shoulders, shorter sleeves, shaped sides and a different length. It has its own chart. Offering only men&#39;s sizes to a girls&#39; or women&#39;s team produces jerseys that fit nobody well.</p>
<h2 id="fit-by-sport">Fit by sport</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Sport"><table>
<thead>
<tr>
<th>Sport</th>
<th>Fit</th>
<th>What changes the size</th>
</tr>
</thead>
<tbody><tr>
<td>Basketball</td>
<td>Loose</td>
<td>Players often want extra length</td>
</tr>
<tr>
<td>Football</td>
<td>Fitted over pads</td>
<td>Measure or size with shoulder pads on</td>
</tr>
<tr>
<td>Hockey</td>
<td>Wide, over pads</td>
<td>Sized by the pads more than the body</td>
</tr>
<tr>
<td>Soccer</td>
<td>Regular to slim</td>
<td>Close to normal clothing size</td>
</tr>
<tr>
<td>Baseball and softball</td>
<td>Regular, tucked in</td>
<td>Body length matters for staying tucked</td>
</tr>
<tr>
<td>Volleyball</td>
<td>Close and stretchy</td>
<td>Follow the stretch chart, not a loose-fit one</td>
</tr>
<tr>
<td>Compression wear</td>
<td>Tight</td>
<td>Size by the chart. Do not size up for comfort</td>
</tr>
</tbody></table>
</div>
<h2 id="collecting-sizes-from-a-team">Collecting sizes from a team</h2>
<p>Three ways, from most to least reliable:</p>
<ol>
<li>A sizing kit. The supplier sends one jersey in each size. Players try them on at practice and someone records the result. This is the best method for any order of real size.</li>
<li>A size chart with measurements, filled in by each family in an online form or <a href="https://uniformsos.com/glossary/team-store">team store</a>.</li>
<li>Asking for &quot;usual size&quot; with no chart. Expect mistakes.</li>
</ol>
<p>Whichever you use, collect sizes in writing, tied to the player&#39;s name and number. Sizes shouted across a gym end up on the wrong line.</p>
<p>Set a deadline, and decide in advance what happens to players who miss it. A common choice is to assign a size and place the order, not hold everyone up for one player.</p>
<h2 id="custom-means-no-exchanges">Custom means no exchanges</h2>
<p>A jersey printed with a name and number cannot go back on a shelf. Say this plainly wherever sizes are collected. It makes people measure.</p>
<p>Ask the supplier what a single remake costs and how long it takes, before the order, so you know the price of a wrong size.</p>
<h2 id="mistakes-that-cause-remakes">Mistakes that cause remakes</h2>
<p>Using a chart from a different brand.</p>
<p>Guessing for a growing kid. Parents size up two sizes so it lasts, and the jersey reaches the knees. One size up is enough.</p>
<p>Confusing youth and adult sizes.</p>
<p>Ignoring length. A tall thin player needs the length checked, not only the chest.</p>
<p>No size on the roster line. Every missing size is a phone call on deadline day.</p>
<h2 id="sizes-and-rosters-in-uniformsos">Sizes and rosters in UniformsOS</h2>
<p>In UniformsOS a product carries its size ranges and a size chart, and the chart shows on the product page and in the team store. The roster sits on the order line, one row per player with size, name and number, and in <a href="https://uniformsos.com/platform/team-stores">Team Stores</a> each family picks its own size at checkout. See <a href="https://uniformsos.com/platform/products">Products and SKUs</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Tech pack checklist: the ten parts a factory needs</title>
    <link>https://uniformsos.com/blog/tech-pack-checklist</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/tech-pack-checklist</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Products</category>
    <description>A checklist of the ten parts of an apparel tech pack, what each must contain, the gaps factories complain about most and how to test yours before sending it.</description>
    <content:encoded><![CDATA[<p>A tech pack is complete when a factory that has never seen the product could make it correctly from the document alone. That takes ten parts: a cover page, flat sketches, a bill of materials, a graded measurement chart with tolerances, construction details, colorways, artwork placement, labels, packing instructions and a revision history.</p>
<h2 id="the-ten-parts">The ten parts</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Part"><table>
<thead>
<tr>
<th>Part</th>
<th>The question it answers</th>
</tr>
</thead>
<tbody><tr>
<td>1. Cover page</td>
<td>What is this, and which version am I holding?</td>
</tr>
<tr>
<td>2. Flat sketches</td>
<td>What does it look like from every side?</td>
</tr>
<tr>
<td>3. <a href="https://uniformsos.com/glossary/bill-of-materials">Bill of materials</a></td>
<td>What is it made of?</td>
</tr>
<tr>
<td>4. Measurement chart</td>
<td>How big is each size, and how exact must it be?</td>
</tr>
<tr>
<td>5. Construction details</td>
<td>How is it sewn?</td>
</tr>
<tr>
<td>6. <a href="https://uniformsos.com/glossary/colorway">Colorways</a></td>
<td>Which colors go where?</td>
</tr>
<tr>
<td>7. Artwork placement</td>
<td>Where do logos, names and numbers sit, and how big are they?</td>
</tr>
<tr>
<td>8. Labels</td>
<td>What labels go in, and where?</td>
</tr>
<tr>
<td>9. Packing</td>
<td>How is it folded, bagged and boxed?</td>
</tr>
<tr>
<td>10. Revision history</td>
<td>What changed, when, and who approved it?</td>
</tr>
</tbody></table>
</div>
<h2 id="1-cover-page">1. Cover page</h2>
<p>Style number, style name, season or date, size range, the brand or customer, your contact and the version number. Put the style number and version on every page after it as well. Pages get separated.</p>
<h2 id="2-flat-sketches">2. Flat sketches</h2>
<p>Line drawings of the garment laid flat: front, back and, if it matters, the side. Add close-ups of anything unusual, such as a collar, a pocket or a vent.</p>
<p>Sketches are drawings, not fashion illustrations. No body, no shading. Show every seam and every line of topstitching, because the factory will sew what it sees.</p>
<h2 id="3-bill-of-materials">3. Bill of materials</h2>
<p>Every physical thing that goes into one piece.</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Item"><table>
<thead>
<tr>
<th>Item</th>
<th>What to specify</th>
</tr>
</thead>
<tbody><tr>
<td>Main fabric</td>
<td>Fiber content, knit or weave, weight in <a href="https://uniformsos.com/glossary/gsm">GSM</a>, color</td>
</tr>
<tr>
<td>Secondary fabrics</td>
<td>The same, plus where each one goes</td>
</tr>
<tr>
<td>Thread</td>
<td>Type and color, for needles and loopers</td>
</tr>
<tr>
<td>Trims</td>
<td>Elastic, drawcords, buttons, zippers, with sizes</td>
</tr>
<tr>
<td>Labels</td>
<td>Brand, size, care and content</td>
</tr>
<tr>
<td>Packaging</td>
<td>Bag, sticker, <a href="https://uniformsos.com/glossary/hang-tag">hangtag</a></td>
</tr>
</tbody></table>
</div>
<p>See the <a href="https://uniformsos.com/blog/jersey-fabric-guide">jersey fabric guide</a> for what the fabric line should say.</p>
<h2 id="4-measurement-chart">4. Measurement chart</h2>
<p>The part factories use most. It lists each point of measure, how it is taken, the value for every size and the <a href="https://uniformsos.com/glossary/tolerance">tolerance</a>.</p>
<p>Typical points of measure for a jersey:</p>
<ul>
<li>Chest width, one inch below the armhole</li>
<li>Body length, from the high point of the shoulder</li>
<li>Shoulder width</li>
<li>Sleeve length</li>
<li>Sleeve opening</li>
<li>Neck width and neck drop</li>
<li>Hem width</li>
</ul>
<p>Two things are missing from most charts.</p>
<p>Tolerances. No factory hits a number exactly. State how far off is acceptable, such as half an inch on body length and a quarter inch on a neck opening. Without a tolerance, every measurement dispute is an argument.</p>
<p><a href="https://uniformsos.com/glossary/grading">Grading</a>. The chart must give every size, not one sample size with &quot;grade accordingly&quot;. The step between sizes is your decision, not the factory&#39;s.</p>
<h2 id="5-construction-details">5. Construction details</h2>
<p>For every seam and hem: the stitch type, the seam allowance and the stitches per inch. Name stitches by class number, such as 514 for a four-thread <a href="https://uniformsos.com/glossary/overlock">overlock</a>, so there is one reading. <a href="https://uniformsos.com/blog/sportswear-stitch-types">Stitch types in sportswear</a> lists them.</p>
<p>Add hem depths, needle spacing for coverstitching and any reinforcement, such as <a href="https://uniformsos.com/glossary/bartack">bartacks</a> at stress points.</p>
<h2 id="6-colorways">6. Colorways</h2>
<p>A table of every color version: which color goes on which part. Give colors as references from a color system, not as words. &quot;Navy&quot; is twenty different colors.</p>
<p>For <a href="https://uniformsos.com/glossary/sublimation">sublimated</a> products, the color standard is an approved test print on the production fabric. Keep it, and name it in the <a href="https://uniformsos.com/glossary/tech-pack">tech pack</a>.</p>
<h2 id="7-artwork-placement">7. Artwork placement</h2>
<p>For each logo, name and number: the size, and the position measured from a fixed point on the garment. &quot;Front number, 8 inches tall, centered, top edge 3 inches below the neck seam&quot; can be checked with a tape. &quot;Centered on chest&quot; cannot.</p>
<p>Say what happens across sizes. Either the artwork scales with the garment, or it stays one size and the position moves. Both are common. The factory needs to know which.</p>
<h2 id="8-labels">8. Labels</h2>
<p>List each label, its content and where it is sewn or printed.</p>
<p>In the United States, the Federal Trade Commission requires most clothing to carry a label with the fiber content, the country of origin and the identity of the manufacturer or another business responsible for it. Care instructions go on a permanent label. Check the rules for every country you sell in before you finalize this page.</p>
<h2 id="9-packing">9. Packing</h2>
<p>How each piece is folded, what bag it goes in, what the sticker says, how many go in a carton and how the carton is marked. For team orders, say whether pieces are packed by size or by player.</p>
<h2 id="10-revision-history">10. Revision history</h2>
<p>A table at the back: date, what changed, who approved it. Raise the version number with every change and send the whole document again, not a note about the change.</p>
<p>There must be one current version. Put the version in the file name. When a factory makes the old version, the first question will be which one it was sent.</p>
<h2 id="for-custom-teamwear">For custom teamwear</h2>
<p>A team dealer does not write a new tech pack for every order. The tech pack describes the style: the cut, the fabric and the construction. It is written once.</p>
<p>Each order then adds an order sheet: the team&#39;s approved artwork, the roster with sizes, names and numbers, and the ship-by date. Keeping the two apart is what lets one style serve hundreds of teams.</p>
<h2 id="the-gaps-factories-complain-about">The gaps factories complain about</h2>
<ul>
<li>No tolerances.</li>
<li>One size specified and the rest left to the factory.</li>
<li>A front sketch only.</li>
<li>Colors given as names.</li>
<li>Artwork with no dimensions.</li>
<li>Three versions in the same email thread.</li>
</ul>
<h2 id="test-it-before-you-send-it">Test it before you send it</h2>
<p>Give the tech pack to someone who has not worked on the product. Ask them to write down every question they would need answered before making it. Each question is a gap. Close them and the factory will not have to ask.</p>
<h2 id="tech-packs-in-uniformsos">Tech packs in UniformsOS</h2>
<p>In UniformsOS a tech pack is a file attached to the order. When the order goes to a factory, the file is copied onto that factory&#39;s <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a> in <a href="https://uniformsos.com/platform/manufacturers">Manufacturers and Vendors</a>, next to each line&#39;s <a href="https://uniformsos.com/glossary/sku">SKU</a>, decoration, color and sizes from the <a href="https://uniformsos.com/platform/products">product record</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>The apparel WIP report: what to track and how to read it</title>
    <link>https://uniformsos.com/blog/apparel-wip-report</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/apparel-wip-report</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Production</category>
    <description>A WIP report lists every order in production, the stage it is in and whether it will ship on time. The columns that matter, stage norms and a five-minute read.</description>
    <content:encoded><![CDATA[<p>A WIP (work in progress) report is one list of every order that has entered production and has not shipped. Each row shows the order, its units, the stage it is in, how long it has been there and its ship-by date. Its job is to show which orders will be late while there is still time to do something about it.</p>
<h2 id="what-a-wip-report-is">What a WIP report is</h2>
<p>In a custom apparel shop, an order is in <a href="https://uniformsos.com/glossary/wip">WIP</a> from the moment production starts until the box leaves the dock. On any given day a busy shop has dozens of these, spread across stages and often across factories.</p>
<p>The WIP report is the daily view of all of them. It answers three questions. What is on the floor? Where is each job? Which jobs are in trouble?</p>
<p>It is not the order list. The order list includes quotes, unpaid orders and orders that shipped last month. It is not the production schedule either. The schedule is the plan. The WIP report is what is actually happening.</p>
<h2 id="the-columns-that-matter">The columns that matter</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Column"><table>
<thead>
<tr>
<th>Column</th>
<th>What it holds</th>
<th>Why it is there</th>
</tr>
</thead>
<tbody><tr>
<td>Order number</td>
<td>Your order or PO number</td>
<td>The key everyone uses on the floor and on the phone</td>
</tr>
<tr>
<td>Customer</td>
<td>The team, school, league or brand</td>
<td>Who to call when a date moves</td>
</tr>
<tr>
<td>Product and units</td>
<td>Style and total pieces</td>
<td>Late on 300 units is not the same problem as late on 12</td>
</tr>
<tr>
<td>Factory or line</td>
<td>Who is making it</td>
<td>Where to chase</td>
</tr>
<tr>
<td>Stage</td>
<td>The current production step</td>
<td>Where the job is right now</td>
</tr>
<tr>
<td>Days in stage</td>
<td>Days since it entered that stage</td>
<td>The first sign of a stuck job</td>
</tr>
<tr>
<td>Ship-by date</td>
<td>The day it must leave to arrive on time</td>
<td>The only deadline that counts</td>
</tr>
<tr>
<td>Days left</td>
<td>Ship-by date minus today</td>
<td>The column you sort by</td>
</tr>
<tr>
<td>Status</td>
<td>On schedule, at risk or late</td>
<td>The call, made by rule</td>
</tr>
<tr>
<td>Blocker</td>
<td>One line on what the job is waiting for</td>
<td>Turns a status into an action</td>
</tr>
</tbody></table>
</div>
<p>Stop there. Price, margin and the full artwork belong on the order. A WIP report with thirty columns does not get read.</p>
<h2 id="the-stages">The stages</h2>
<p>Use the stages your floor really has. For <a href="https://uniformsos.com/glossary/sublimation">sublimated</a> teamwear a typical flow is:</p>
<ol>
<li>Not started. Approved and released to production. Nothing made yet.</li>
<li>Test print. A printed sample, also called a <a href="https://uniformsos.com/glossary/strike-off">strike-off</a>, to approve color and placement.</li>
<li>Sublimation. The design is printed to transfer paper and heat-pressed into the fabric.</li>
<li>Sewing. Panels are cut and assembled.</li>
<li>QA. Pieces are counted, checked against the order and measured.</li>
<li>Packing. Sorted by player or by size, bagged, boxed and labeled.</li>
</ol>
<p>Once the box ships, the order leaves the report.</p>
<p>A <a href="https://uniformsos.com/glossary/screen-printing">screen print</a> shop has different steps: separations, screens, printing, curing. An embroidery shop has <a href="https://uniformsos.com/glossary/embroidery-digitizing">digitizing</a>, hooping, stitching and trimming. Six to eight stages is enough for most shops. If a step takes less than a few hours, fold it into the one next to it.</p>
<h2 id="stage-norms">Stage norms</h2>
<p>Days in stage means nothing without a norm to compare it to. Set a standard duration for every stage, and set it from your own history, not from a guess.</p>
<p>Take your last 50 shipped orders. For each stage, find the median time jobs spent there. That is your norm. An example, not a benchmark:</p>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Stage"><table>
<thead>
<tr>
<th>Stage</th>
<th>Norm</th>
</tr>
</thead>
<tbody><tr>
<td>Test print</td>
<td>2 days</td>
</tr>
<tr>
<td>Sublimation</td>
<td>3 days</td>
</tr>
<tr>
<td>Sewing</td>
<td>5 days</td>
</tr>
<tr>
<td>QA</td>
<td>1 day</td>
</tr>
<tr>
<td>Packing</td>
<td>1 day</td>
</tr>
</tbody></table>
</div>
<p>Any job that has been in a stage longer than the norm gets flagged, whatever its status says.</p>
<h2 id="how-status-gets-decided">How status gets decided</h2>
<p>Status should come from a rule, not from whoever updated the row.</p>
<ul>
<li>Late: the ship-by date has passed.</li>
<li>At risk: the days left are fewer than the days the remaining stages normally take.</li>
<li>On schedule: everything else.</li>
</ul>
<p>Here is the at-risk rule at work, using the norms above. An order has been in Sewing for 2 days and has 4 days left before its ship-by date. Sewing normally takes 5 days, so it needs 3 more. QA needs 1. Packing needs 1. That is 5 days of work and 4 days to do it in. Nothing is late yet, and the order is already a day short.</p>
<p>Catching that order today, while a day can still be found, is the reason the report exists.</p>
<h2 id="how-to-read-it-in-five-minutes">How to read it in five minutes</h2>
<ol>
<li>Sort by days left, smallest first.</li>
<li>Read every late and at-risk row. Each one needs a blocker and a name next to it.</li>
<li>Scan days in stage for anything over its norm, even if the status says on schedule.</li>
<li>Count the jobs in each stage. A pile in one stage is this week&#39;s bottleneck.</li>
<li>Look for rows with no factory or line assigned. Those jobs were released and nobody owns them.</li>
</ol>
<p>Do it at the same time every day, before the floor gets busy.</p>
<h2 id="numbers-worth-tracking-over-time">Numbers worth tracking over time</h2>
<ul>
<li>On-time ship rate. Orders shipped on or before their ship-by date, divided by all orders shipped.</li>
<li>Cycle time. Days from production start to ship. Use the median, because one disaster order distorts an average.</li>
<li>Units in WIP. Total pieces on the floor. If it climbs while shipments stay flat, the floor is filling up.</li>
<li>Aging by stage. How many jobs are past the norm in each stage.</li>
</ul>
<h2 id="mistakes-that-make-the-report-useless">Mistakes that make the report useless</h2>
<p>Tracking the delivery date instead of the ship-by date. The customer cares when the box arrives. The floor can only control when it leaves. Subtract transit time and track that.</p>
<p>Updating it weekly. A weekly report describes last week. Stages should update the moment a job moves.</p>
<p>Typing the status by hand. Hand-typed statuses are optimistic. Calculate them.</p>
<p>One row for an order that is split across two factories. Each factory&#39;s part can be late on its own. Give each <a href="https://uniformsos.com/glossary/purchase-order">purchase order</a> its own row.</p>
<p>Keeping it inside production. The people who answer customer calls need it more than anyone.</p>
<h2 id="spreadsheet-or-software">Spreadsheet or software</h2>
<p>A spreadsheet works while one person updates it and can hold the whole floor in their head. It starts to fail when two people edit it, when factories report by email, or when stage changes happen somewhere the sheet does not see.</p>
<p>In UniformsOS the WIP sheet is built from the orders themselves. When a job moves on the production board, its row updates. Days in stage and schedule status are calculated, and the sheet filters by stage, factory and rep and exports to CSV. More on the <a href="https://uniformsos.com/platform/production-wip">Production WIP module</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>US labeling and safety rules for custom apparel: a plain summary</title>
    <link>https://uniformsos.com/blog/us-apparel-labeling-requirements</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/us-apparel-labeling-requirements</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Compliance</category>
    <description>What US rules require on clothing labels, and what changes for children's apparel: fiber content, country of origin, RN, care labels and flammability.</description>
    <content:encoded><![CDATA[<p>Most clothing sold in the United States needs a label with three things: fiber content, country of origin and the identity of the manufacturer or dealer. It also needs permanent care instructions. Clothing made for children 12 and under adds third-party testing, a Children's Product Certificate and a tracking label. Decorators who print on children's garments should look closely at the rules on prints.</p>
<p>This is a summary for people who run apparel businesses. It is not legal advice. The rules are enforced by the Federal Trade Commission (FTC) and the Consumer Product Safety Commission (CPSC). Read the official text, linked at the end, before you rely on any of it.</p>
<h2 id="the-rules-at-a-glance">The rules at a glance</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Requirement"><table>
<thead>
<tr>
<th>Requirement</th>
<th>Applies to</th>
<th>Agency</th>
<th>Where it lives</th>
</tr>
</thead>
<tbody><tr>
<td>Fiber content, country of origin, business identity</td>
<td>Most textile clothing</td>
<td>FTC</td>
<td>Textile Act rules, 16 CFR Part 303</td>
</tr>
<tr>
<td>Care instructions</td>
<td>Most textile clothing</td>
<td>FTC</td>
<td>Care Labeling Rule, 16 CFR Part 423</td>
</tr>
<tr>
<td>Flammability</td>
<td>All wearing apparel, with listed exceptions</td>
<td>CPSC</td>
<td>16 CFR Part 1610</td>
</tr>
<tr>
<td>Testing, certificate and tracking label</td>
<td>Products made primarily for children 12 and under</td>
<td>CPSC</td>
<td>Consumer Product Safety Improvement Act</td>
</tr>
<tr>
<td>Drawstrings</td>
<td>Children&#39;s upper outerwear</td>
<td>CPSC</td>
<td>16 CFR Part 1120 and ASTM F1816-97</td>
</tr>
</tbody></table>
</div>
<h2 id="fiber-content">Fiber content</h2>
<p>The label lists each fiber by its generic name with its percentage by weight, largest first. &quot;100% polyester.&quot; &quot;88% polyester, 12% spandex.&quot;</p>
<p>Points from the FTC&#39;s guidance that come up in teamwear:</p>
<ul>
<li>There is a 3 percent <a href="https://uniformsos.com/glossary/tolerance">tolerance</a>. A label that says 40 percent cotton can cover 37 to 43 percent. There is no tolerance when the label says 100 percent.</li>
<li>A fiber that is under 5 percent is generally listed as &quot;other fiber&quot;. The exception is a fiber with a real function at that level, such as spandex for stretch, which can be named.</li>
<li>Decoration such as embroidery or <a href="https://uniformsos.com/glossary/applique">applique</a> does not have to be counted if it covers 15 percent or less of the surface. The label can say &quot;exclusive of decoration&quot;.</li>
</ul>
<h2 id="country-of-origin">Country of origin</h2>
<p>Imported clothing names the country where it was made. Clothing made in the United States from imported fabric says so, for example &quot;Made in U.S.A. of imported fabric&quot;.</p>
<p>On a garment with a neck, the origin label goes on the inside center of the neck, midway between the shoulder seams, or next to another label that is there.</p>
<h2 id="business-identity-and-the-rn">Business identity and the RN</h2>
<p>The label must identify the manufacturer or another business responsible for the product, either by company name or by <a href="https://uniformsos.com/glossary/rn-number">RN</a>.</p>
<p>An RN is a registered identification number issued by the FTC to US businesses that make, import or sell textile products. It is optional. It lets you put a short number on the label in place of your full company name.</p>
<h2 id="care-instructions">Care instructions</h2>
<p>Care instructions must be on a label that stays attached and readable for the life of the garment. The other required information only has to stay attached until the garment reaches the consumer, so many businesses put everything on the permanent care label.</p>
<h2 id="what-this-means-for-decorators-and-dealers">What this means for decorators and dealers</h2>
<p>If you buy finished blanks and decorate them, the blank already carries its labels. Leave them in.</p>
<p>If you remove the original label and put in your own brand, you are responsible for the new one. It has to carry the required information and identify your business.</p>
<p>If you have garments cut and sewn to order, the labels are yours to specify. Put them in the <a href="https://uniformsos.com/blog/tech-pack-checklist">tech pack</a>: what each label says and where it goes.</p>
<p>Printed neck labels are common on jerseys. The same information is required, and the care instructions still have to last.</p>
<h2 id="flammability">Flammability</h2>
<p>The clothing flammability standard, 16 CFR Part 1610, applies to adult and children&#39;s apparel. It exists to keep dangerously flammable fabrics out of clothing.</p>
<p>Two groups of fabric are exempt from testing under the rule:</p>
<ul>
<li>Plain surface fabrics that weigh 2.6 ounces per square yard or more, whatever the fiber.</li>
<li>Any fabric made entirely of acrylic, modacrylic, nylon, olefin, polyester or wool, or a combination of them.</li>
</ul>
<p>Most polyester jersey fabrics fall in the second group. Fabrics that need attention are very light, sheer ones and raised surfaces such as cotton fleece. Ask the supplier of fleece garments for their flammability documentation.</p>
<p>Children&#39;s sleepwear has stricter rules of its own, in 16 CFR Parts 1615 and 1616.</p>
<h2 id="children-s-apparel">Children&#39;s apparel</h2>
<p>A children&#39;s product is one designed or intended primarily for children 12 years old or younger. Youth team uniforms for those ages are children&#39;s products.</p>
<p>The Consumer Product Safety Improvement Act adds four things:</p>
<ol>
<li>Third-party testing, by a laboratory the CPSC has accepted, for the rules that apply to the product.</li>
<li>A Children&#39;s Product Certificate, issued by the manufacturer or importer, based on that testing.</li>
<li>A tracking label: permanent marks on the product and its packaging that identify who made it, where and when, and the batch.</li>
<li>Limits on lead in the product.</li>
</ol>
<h3 id="prints-on-children-s-garments">Prints on children&#39;s garments</h3>
<p>This is the part that matters to decorators. The CPSC has determined that textiles, dyed or undyed, do not need lead testing. That determination does not extend to <a href="https://uniformsos.com/glossary/screen-printing">screen prints</a>, transfers and other prints added to the fabric.</p>
<p>If you print on children&#39;s garments, ask your ink or transfer supplier for test reports showing that their product meets the limits, and keep them on file. Read the CPSC&#39;s guidance for small businesses to see whether you need to issue a certificate of your own for the decorated product.</p>
<h3 id="drawstrings">Drawstrings</h3>
<p>Under 16 CFR Part 1120 and the standard it refers to, ASTM F1816-97:</p>
<ul>
<li>Children&#39;s upper outerwear in sizes 2T to 12 must not have drawstrings at the hood or neck.</li>
<li>In sizes 2T to 16, drawstrings at the waist or bottom may not extend more than 3 inches outside the channel when the garment is opened to its full width. A drawstring that is one continuous string must be <a href="https://uniformsos.com/glossary/bartack">bartacked</a> so it cannot be pulled out.</li>
</ul>
<p>Youth hoodies are the usual place this goes wrong. Order youth hoodies made without hood drawstrings.</p>
<h2 id="a-working-checklist">A working checklist</h2>
<p>For every product you sell:</p>
<ul>
<li>Fiber content, origin and your name or RN are on a label.</li>
<li>Care instructions are on a permanent label.</li>
<li>You have the supplier&#39;s flammability documentation for fleece and other raised or very light fabrics.</li>
</ul>
<p>For anything made for children 12 and under:</p>
<ul>
<li>You hold a Children&#39;s Product Certificate from the manufacturer or importer of the garment.</li>
<li>The garment has a tracking label.</li>
<li>You hold test reports for the inks or transfers you add.</li>
<li>Hoodies and jackets meet the drawstring rule.</li>
</ul>
<h2 id="selling-outside-the-united-states">Selling outside the United States</h2>
<p>Other countries have their own rules. Canada requires labels in English and French. The European Union has its own fiber names and labeling regulation. Check each market before you ship to it.</p>
]]></content:encoded>
  </item>
  <item>
    <title>What to automate first in a custom apparel business</title>
    <link>https://uniformsos.com/blog/apparel-business-automation</link>
    <guid isPermaLink="true">https://uniformsos.com/blog/apparel-business-automation</guid>
    <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
    <category>Automation</category>
    <description>The handoffs worth automating in a custom apparel shop, ranked: quote to order, artwork approval, deposits, purchase orders, production updates and reorders.</description>
    <content:encoded><![CDATA[<p>Automate the handoffs first: the points where an order is retyped or someone has to remember to send something. In a custom apparel business the ones that pay back fastest are quote to order, artwork approval, deposit and balance reminders, purchase orders to factories, production status updates and reorder prompts. Leave pricing exceptions and bad news to people.</p>
<h2 id="the-rule">The rule</h2>
<p>Automate a step when it is repeated, when it follows a rule and when forgetting it costs money. If a step needs judgment, keep a person on it.</p>
<p>Fix the process before you automate it. A confusing approval step sent automatically is the same confusing step, sent faster to more people.</p>
<h2 id="the-handoffs-in-the-order-to-automate-them">The handoffs, in the order to automate them</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Step"><table>
<thead>
<tr>
<th>Step</th>
<th>Trigger</th>
<th>What happens on its own</th>
</tr>
</thead>
<tbody><tr>
<td>Quote to order</td>
<td>The customer accepts the quote</td>
<td>An order is created with the same lines. Nobody retypes it</td>
</tr>
<tr>
<td>Artwork approval</td>
<td>A <a href="https://uniformsos.com/glossary/art-proof">proof</a> is sent</td>
<td>The customer approves or asks for changes online. Approval releases the order. A reminder goes out if there is no answer in two days</td>
</tr>
<tr>
<td>Deposit and balance</td>
<td>The order is confirmed</td>
<td>A deposit invoice goes out with a payment link. The balance is requested before shipping. Reminders follow</td>
</tr>
<tr>
<td>Sizes and rosters</td>
<td>The order needs sizes</td>
<td>The team gets a link to enter sizes, names and numbers. No spreadsheet by email</td>
</tr>
<tr>
<td><a href="https://uniformsos.com/glossary/purchase-order">Purchase orders</a></td>
<td>The order is approved and paid</td>
<td>A purchase order is created for each factory, with the spec, the sizes and the ship-by date</td>
</tr>
<tr>
<td>Production status</td>
<td>A job changes stage</td>
<td>The <a href="https://uniformsos.com/glossary/wip">WIP</a> report updates. The customer is told at the stages they care about</td>
</tr>
<tr>
<td>Late-risk alerts</td>
<td>Days left fall below the time the remaining stages need</td>
<td>The order is flagged to whoever owns it</td>
</tr>
<tr>
<td>Shipping notice</td>
<td>A label is created</td>
<td>The customer gets the tracking number</td>
</tr>
<tr>
<td>Reorder prompts</td>
<td>A set number of weeks before the customer&#39;s season</td>
<td>Last year&#39;s buyer gets a message with last year&#39;s order attached</td>
</tr>
<tr>
<td>Lead follow-up</td>
<td>A new inquiry arrives</td>
<td>An instant reply goes out, and a task is created for a rep. A follow-up goes out after a few days of silence</td>
</tr>
</tbody></table>
</div>
<p>Start at the top. Each step removes work from the ones below it.</p>
<h2 id="why-artwork-approval-comes-so-early">Why artwork approval comes so early</h2>
<p>In many custom shops the longest avoidable wait in an order is not production. It is the days between <a href="https://uniformsos.com/blog/apparel-art-approval-process">sending a proof and getting a clear yes</a>. Approvals sit in inboxes, come back as &quot;looks good but can you&quot; and arrive by text message with no record.</p>
<p>One approval page fixes that. It shows the proof. It has an approve button and a box for changes. It records who approved, what they approved and when. Add one automatic reminder and the wait shrinks without anyone chasing.</p>
<h2 id="what-to-leave-to-people">What to leave to people</h2>
<ul>
<li>Pricing exceptions and discounts. A rule cannot tell a good customer from a bad deal.</li>
<li>Bad news. When an order will be late, call. An automatic &quot;your order is delayed&quot; email with no person behind it loses the account.</li>
<li>The final artwork check. A person looks at every file before it goes to production. Spelling, numbers and colors.</li>
<li>Credit decisions.</li>
<li>The first runs of anything new. Read every message an automation sends for the first two weeks.</li>
</ul>
<h2 id="how-to-start">How to start</h2>
<ol>
<li>Pick one type of order, the one you do most.</li>
<li>Write down every step from inquiry to delivery.</li>
<li>Mark each step where information is retyped and each step that starts with &quot;remember to&quot;.</li>
<li>Pick the two marks that hurt most.</li>
<li>For each one, write the trigger, what should happen, and who owns it when it fails.</li>
<li>Turn it on for that one order type. Watch it for two weeks.</li>
<li>Then do the next two.</li>
</ol>
<p>Ten automations switched on in one weekend produce ten things nobody trusts.</p>
<h2 id="how-to-tell-it-is-working">How to tell it is working</h2>
<div class="table-scroll" role="region" tabindex="0" aria-label="Table: Measure"><table>
<thead>
<tr>
<th>Measure</th>
<th>What should happen</th>
</tr>
</thead>
<tbody><tr>
<td>Time from inquiry to quote</td>
<td>Shorter</td>
</tr>
<tr>
<td>Time from proof sent to approval</td>
<td>Shorter</td>
</tr>
<tr>
<td>Orders in production without a deposit</td>
<td>Fewer, then none</td>
</tr>
<tr>
<td>Days from invoice to payment</td>
<td>Fewer</td>
</tr>
<tr>
<td>On-time ship rate</td>
<td>Higher</td>
</tr>
<tr>
<td>Hours a week spent answering &quot;where is my order&quot;</td>
<td>Fewer</td>
</tr>
</tbody></table>
</div>
<p>Measure before you start. Without a starting number, you will not know what changed.</p>
<h2 id="where-ai-fits">Where AI fits</h2>
<p>AI is useful today for first drafts and for cleanup. It can turn an inquiry into a draft quote. It can turn a messy roster into clean lines. It can produce design options for a first conversation, and it can summarize a long customer thread.</p>
<p>It should not send prices, approve artwork or promise dates without a person reading the result. Treat its output as a draft from a fast new hire.</p>
<h2 id="which-of-these-uniformsos-does-today">Which of these UniformsOS does today</h2>
<p>In UniformsOS a quote in <a href="https://uniformsos.com/platform/sales-crm">Sales Reps and CRM</a> is the order itself, so nothing is retyped. Sending it issues the deposit invoice with a pay link, and <a href="https://uniformsos.com/platform/payments">Payments and Invoicing</a> issues the balance invoice when the last shipment leaves. Customers approve a design or ask for changes on a link in <a href="https://uniformsos.com/platform/designs">Designs</a>, and new leads are routed to a rep by rule. In <a href="https://uniformsos.com/platform/production-wip">Production WIP</a> a factory&#39;s stage update moves the order, and orders behind their ship-by date are flagged.</p>
]]></content:encoded>
  </item>
</channel>
</rss>
