Skip to content
English
Signature Locker
  • There are no suggestions because the search field is empty.

How to Build a Uniform

Effective as of December 3rd,  2024

Last updated: June 22nd, 2026

DOWNLOAD:  UNIFORM TEMPLATE  | PACKAGE CODE | UNIFORMS DO'S & DON'TS

 

1. Click on the UNIFORM TEMPLATE link. 

2. Use the template to guide you in filling out the necessary information. 

I.E: Team Name is the program's name, "Amesbury Youth Lacrosse" and uniform pieces include the "3 Piece Player Game Package." 
Team Name Drop Down 1-5 is allocated for the inner teams of the program, for example, U8, U10, Grade 1-2, Premier/Select, etc. 
It is NOT necessary to place the name of the program in any other section other than the TEAM NAME slot. 

All Uniform SKU information can be found in the Properties section on the Ziflow workflow, under Pieces & Packages. All Team Name Drop Down information can be found in the Uniform Number Range/Team Names section. 

Make sure to include the UNIFORM PACKAGE ID. All package IDs can be found on the link PACKAGE CODE. If you do not see the designated package code, then please slack Shane Giunta. 

3. Once all of the information is filled out correctly, it should look like the example below.

Please go through each sheet and make sure all handles are correct. A good example of a good handle for the package above is: amesbury-youth-lacrosse-men-s-3-piece-player-package


4. Rename all of your Piece1_name/Piece2_name/Piece3_name, etc with the name of the piece of the uniform. Ex. Piece1_name should be renamed to Sleeveless Game Pinnie, and Piece2_name should be renamed to Game Shorts. etc. This will make it easier to find the piece file when loading it in. 

5. Save each individual piece as it's own CSV, 

6. Log into Shopify and search for Matrixify in the app. 

7. Load in each CSV file, the entire uniform package and each uniform piece. 

8. Once everything has been loaded in, go to Products and go to Collections. 

9. Press "Create Collections" and begin the title with "team-collection" 

You will now go back to the uniform template sheet take the handle of each product and add it to the team-collection portion of the title. It should look like this: "team-collection-amesbury-youth-lacrosse-men-s-3-piece-player-package". 

Please make sure to also place the handle in the Products section as well. It should look like the screen below: 


Make sure to check all of the boxes that pertain to the exact handle as this is what ties in the drop-down menu. 

You will want to do this for all of the pieces.


10. Once you tie in all of the handles, go back to Products and search for the uniform pieces now loaded in. 

11. Place all of the images that belong to each of the uniform products. 

12. Click on the "mother" product of the package and all of the individual pieces and press "bulk edit." Once you are in the bulk sheet, add collection_[TEAM ID NUMBER] and make sure to link all of the uniform pieces to their proper team store. 

13. Check the team's team store to make sure it is properly tagged and loading in correctly. A good example of a uniform upload is found below: 

14. Submit your uniform through the Ziflow proof to send to Account Managers and Clients. 

CONGRATULATIONS! 
You have completed your uniform! 


If you have any questions, please feel free to reach out to patricia@signaturelocker.com or through slack. 

 

Uniform Build — Do's & Don'ts

Signature Locker E-Commerce Team

This guide covers the most common mistakes made during uniform builds and what to do instead. It is based on real errors caught during QC reviews. When in doubt, stop and ask — a question takes 2 minutes, a reprint takes days.

 

1. SKUs — Verifying & Entering

✓ DO

✗ DON'T
  • Always pull SKUs from the master SKU sheet in Ziflow (Pieces & Packages section)
  • This is your single source of truth — never guess or copy from another build
  • Check the main SKU AND all variant/child SKUs individually
  • Cross-reference the SKU version number against the product version in the name
  • Flag any SKU with '000' in the style field and confirm before proceeding
  • Example: S|1118|26-3|000|1109 — '000' means no style assigned
  • When something looks off or unusual, stop and ask Patty to confirm
  • Don't copy SKUs from a previous build or a different team's sheet
  • Don't take SKUs at face value — always double-check against the proof
  • Errors have caused full program reprints because SKUs weren't verified
  • Don't proceed if a SKU seems wrong or unfamiliar — flag it first
  • Don't enter the same SKU on two different products

 

2. Product Naming

✓ DO

✗ DON'T
  • Give every product a unique, descriptive name that includes the team name, gender, and piece
  • Example: bayfa-men-s-3-piece-player-package
  • Match the version number in the product name to the version in the SKU
  • If SKU is V1, name it V1 — not V2 or V3
  • Use lowercase with hyphens for handles (apostrophes → hyphens: men's → men-s)
  • Confirm your handle is unique before uploading via Matrixify
  • Don't reuse or generically name products
  • If two builds share a name, Shopify will overwrite SKUs from the earlier build
  • Don't rename a product on the backend after upload without checking for SKU copy-over risk
  • Don't name a build V2 when the SKU is V1 (or any version mismatch)
  • Don't use the same handle for two different uniform builds

 

3. Piece Naming & Tags

✓ DO

✗ DON'T
  • Rename Piece1_name, Piece2_name, etc. to the actual piece name before saving the CSV
  • Example: Piece1_name → Sleeveless Game Pinnie, Piece2_name → Game Shorts
  • For 3-piece packages with socks, use the tag: piece3_socks
  • For apparel collections with a SKU, use the tag: special-drop (not uniform-delivery-window)
  • Verify all piece tags are correct before importing to Matrixify
  • Don't leave default Piece#_name labels — rename them to the actual piece
  • Don't use Piece3_name:Socks for 3-piece sock packages
  • This causes production to reprocess all orders — use piece3_socks tag instead
  • Don't use uniform-delivery-window on apparel collections that contain a SKU

 

4. Collections & Team Store Tagging

✓ DO

✗ DON'T
  • Tag every product with collection_[TEAM ID NUMBER] so it shows in the correct team store
  • Verify all products are under the correct collection ID before submitting
  • Create the team-collection title using the exact product handle
  • Example: team-collection-amesbury-youth-lacrosse-men-s-3-piece-player-package
  • Check the team store after upload to confirm all products are visible and correctly linked
  • Don't assign products to the wrong program ID or collection
  • Products not tagged to the right collection won't appear in the team store at all
  • Don't skip the team store visual check after upload
  • Don't forget to tag all uniform pieces — not just the package product

 

5. Product Type — Youth vs. Adult

✓ DO

✗ DON'T
  • Check the style number in Fulfill Engine to confirm youth vs. adult before naming
  • Y in the style code = youth (e.g. BC3413Y is a youth tee — not adult)
  • Make sure the product name, FE style, and proof all agree on youth vs. adult
  • When in doubt, check the proof and the FE style page before proceeding
  • Don't name a youth product as 'Adult' or vice versa
  • This causes customers to receive the wrong sizing — results in reprints and returns
  • Don't assume a product is adult just because it's labeled that way on the proof — verify the style code

 

6. Missing Items & Pre-Submission Checklist

✓ DO

✗ DON'T
  • Do a line-by-line check of the master SKU sheet vs. what is live in Shopify before submitting
  • Confirm every piece listed on the proof has been uploaded (including socks)
  • Verify the correct number of packages matches the proof (e.g. 12 packages, not 13)
  • Check that sizing is active on all products (FE variants or Infinite Options for non-FE items)
  • Confirm the correct sizing chart is assigned — ask Patty or the AM if unsure
  • Don't mark a build complete without confirming every item is loaded and live
  • Don't submit a proof if any items are missing — flag it first
  • Don't leave sizing blank on any product
  • Orders will come through with no size selected, causing fulfillment errors
  • Don't apply Signature Swag sizing charts to non-standard styles (volleyball, Nike, etc.) without confirming

 

7. Embroidery & Logo Proofs

✓ DO

✗ DON'T
  • Always check the thread count on a logo before submitting a proof
  • Keep all logo proofs at or under 25,000 stitches (this is a hard limit)
  • Flag anything over 25k to Patty before submitting — do not submit and hope it passes
  • Don't submit an embroidery proof without checking the stitch count first
  • A 112k stitch logo was submitted — it had to be rejected and redigitized
  • Don't assume a logo that looks small is within the stitch limit — always check

 

 

Golden Rule

If a SKU looks weird, a name looks familiar, or a count doesn’t add up — stop. Confirm before you upload. Errors at the build stage cost the whole team.