The first thing I look for on a team cap order is the size list, and on the reference flow I checked, it wasn't there. The page hands the question to the players: teammates choose their own sizes through a sharing integration, and the caps ship straight to their door. No buyer-side roster, no spreadsheet passed back and forth.
That one line rearranges the approval sheet. Size stops being data you collect and becomes a field you confirm per variant, which is the field most teams sign off blind because everyone is looking at the logo. The document that actually prevents remakes is the size-and-color variant matrix. Artwork gets re-checked at every handoff; a roster gets approved once, by whoever answers that email, and then never opened again.
The Size Field Breaks Team Cap Signoff First
When I opened the custom baseball hat page and read the ordering steps, I found the team-size problem solved by routing it away from the buyer. Teammates pick their own sizes and shipping goes to each address instead of one dock.
Set that against how team orders usually get approved. A buyer collects a roster in a spreadsheet, guesses at a few sizes, sends one number to the supplier, and the caps arrive in a distribution that fits the spreadsheet rather than the people wearing them. Per-person selection removes the guess and moves the decision somewhere procurement can't see it. Nobody on your side is checking those size values.
If any part of the order routes sizes to individuals, the approval sheet has to carry a size value on every variant line, navy with the home number next to grey with the away number, because colorway and size fail independently. One size for the whole order assumes a uniform set of heads, which a team order almost never has.
Four Variant Fields to Lock Before Quoting
Before a supplier can quote, four fields have to be fixed on every line: style, one design covering artwork and any added text, colorway, and quantity broken out by size. That is the unit the reference flow asks for, a style, an upload, then quantities and sizes.
The gain for procurement is that the quote sheet becomes one line per variant instead of one line per order. Suppose three graphics across two colorways in five sizes: that isn't one purchase, it's thirty lines that can each be priced, keyed, and checked. A transposed size or a colorway attached to the wrong graphic shows up as a wrong line before it becomes a production change, which is the difference between a five-minute correction and a remake.
Options on that page belong to that page. It names its own colors, black, white, red, green among them, and it lists its own styles, and none of that transfers to another supplier's catalog or to a factory you haven't quoted. Use the four fields as the structure of the question, not as an answer about what any given supplier can run.
Walking the Reference Order Flow End to End
I walked the reference flow in the order it presents itself. The design page opens with a style choice, then an upload, then quantity and size selection. Style first matters more than it looks, because the blank decides the crown, the closure, and the size range, so every downstream field inherits from it.
On the baseball hat page I saw the artwork upload sitting beside an add-text field and a color picker with named options, with a mockup rendered immediately. Artwork and text are separated there, worth copying into your own sheet, because the graphic file and the name or number string get approved by different people and fail for different reasons.
Then I found where the size data goes, and it doesn't go back to the buyer. It goes out to the teammates.
Mirror that sequence in the signoff sheet: style approved first, then graphic and text, then colorway, then the size distribution, then delivery. Each field gets confirmed at the point the flow asks for it, by the person who owns it. I can't tell you that every supplier sequences work this way, since accounts build these sheets however the manager prefers, but the order above follows the dependency chain, and a sheet that approves color before style is approving the wrong thing.
What the Instant Mockup Cannot Prove
The mockup appears the moment artwork, text, and color are set, and it settles real questions: layout, whether the text is legible at cap scale, where each color lands on the panel. What it does not do is tell you anything about the physical cap. I checked the reference material for stitch density, thread-to-fabric color matching, embroidery registration, fabric hand, and how sizes are graded between each other, and found nothing on any of it. That isn't a knock on the page, because a preview was never built to carry those answers. It means the mockup closes exactly one approval, the artwork, and leaves the cap itself open until a sample is in someone's hands. Teams that treat a mockup signoff as the sample signoff find out at bulk delivery, when the graphic is right and the crown depth, the thread color against the fabric, or the fit across sizes is wrong, and the file everyone re-checked three times had nothing to do with it.
A mockup approves artwork. It does not approve a cap.
Keep them as two signoffs on paper, with separate dates and separate signatures. Artwork signoff can happen on screen in an afternoon. Sample approval has to happen on the variant you will actually run, not a similar one and not the hero color, because the line that gets remade is the one nobody held.
Questions to Send Before You Approve a Sample
My research for this piece captured no quote, no MOQ, no capacity review, no lead-time commitment, and no certification from any candidate supplier, so none of it is assumed here. What follows is a question set, not a finding.
Send these to each candidate and ask for the answers in writing, tied to your four fields. Ask for price per variant line, and for minimum order quantity broken out by style and by color rather than one number for the account, since a three-color order can clear MOQ on paper and stall on the smallest colorway. Ask what size range is offered and how it's graded between sizes, because the flow lets a teammate pick a size and someone has to be accountable for what that size means on a head. Ask for the sampling timeline and which variant the sample will be built from. Ask where the change cutoff sits, the date after which a size or color change becomes a new order. Ask which documents the supplier can actually produce, and take a short honest list over a long vague one.
I went looking on those reference pages for a certification statement and a lead-time commitment and found neither, which is why the questions above sit open instead of answered. That's the normal state at quoting. A supplier who answers all of it in writing, with numbers tied to your actual variant lines, has given you something no catalog page can.
Answer the Size-Field Question, Then Sign
Back to the size list I couldn't find at the start. Before you request a quote, decide who owns that field, and understand that you're choosing a shipping model as much as a data flow. Collect the roster centrally and you get one consolidated shipment and one size list on one document, and every sizing error lands on you, concentrated in a delivery you have to sort and redistribute. Route sizes to the teammates and you get per-person confirmation and split delivery, and you give up the single point of truth: nobody on your side sees the full distribution, and a wrong size becomes a conversation between the player and the carrier.
Then freeze a single line for each style, colorway, and graphic, sign the artwork separately from the sample, and approve a physical sample of the riskiest line, meaning the smallest colorway, the most detailed graphic, the size at the edge of the range. Attach the signed variant matrix to the purchase order and put a written change cutoff in front of it. Keep the matrix as the document that has to survive every handoff, not just the logo file. The logo has never been the part that goes wrong quietly.