Briefing your upload team on activewear collections starts with one decision: whether your collections organize by activity (yoga, running, gym), by product category (leggings, tops, sports bras), or by both. Most activewear stores use both layers, and the team handling your activewear collections for upload needs that mapping in writing before the job starts, or they will make calls you will want to change later.
Key takeaways
- Activewear collections typically use activity as a primary organizing layer (yoga, running, gym, cycling, swim), which differs from general apparel's seasonal and category structure.
- Performance data fields specific to activewear (fabric technology name, UPF rating, compression level, bra support level) are brand-proprietary and cannot be guessed from a supplier file; they need to be agreed before upload.
- A product can belong to more than one collection in Shopify; the brief must list all collection memberships for ambiguous products, such as a legging that fits both yoga and gym.
- Collection names in Shopify become URL handles on creation; locking the exact names in the brief before the job starts prevents a renaming and redirect fix after go-live.
- A one-page activewear collections brief cuts down the most common reason activewear upload jobs pause mid-way: a team member facing a product that could fit two or three collections without a written decision rule.
Why activewear collection structure is different from general apparel
General apparel stores typically organize collections by two or three familiar layers: season (Spring/Summer, Fall/Winter), product category (Dresses, Tops, Outerwear), and sometimes brand range or line. These layers map onto what most shoppers browse by, and a team can infer reasonable assignments even with a loose brief.
Activewear adds a third organizing dimension that does not exist in general apparel: activity type. A running-focused brand has different inventory from a yoga brand, and a multi-activity store needs collections that reflect each use case:
- Yoga: high-rise waistbands, non-see-through fabric, pockets for keys or cards
- Running: reflective detailing, phone-pocket waistbands, lightweight moisture-wicking
- Gym or training: compression levels, squat-proof construction, reinforced stitching
- Cycling: padded shorts or bibs, stretch fabric with pocket placement at the back
- Swim or resort: quick-dry fabric, chlorine-resistant construction
Without an activity taxonomy in the brief, an upload team will either create one broad "Activewear" collection (losing the filtering that performance shoppers use) or assign products by judgment calls the merchant will want to revisit. Either outcome creates editing work after go-live.
In Shopify, a product can belong to more than one collection (as of October 2026, there is no limit on how many collections a product can appear in). Activewear stores take advantage of this: a pair of yoga leggings can sit in "Yoga", "Women's Leggings", and "New In" simultaneously. The brief needs to specify these multi-collection memberships, not leave them to inference.
For a full set of activewear upload guides, see the activewear upload topic hub.
What to include in an activewear collections brief for the upload team
The collection brief is the document you send to your upload team before the job starts. For activewear, it needs to cover four areas.
1. Collection list with exact naming
Write out every collection you want created, using the exact name you want in Shopify. The names the team creates become the URL handles (for example, "Women's Yoga" becomes /collections/womens-yoga), so case, spacing, and punctuation matter. Use a numbered list:
- Women's Yoga
- Women's Running
- Women's Gym
- Men's Training
- Men's Cycling
- New In
- Sale
Note whether each collection is manual (the team assigns products by hand) or automated (Shopify applies conditions automatically). For automated collections, provide the exact conditions: which field, which operator, and what value. A condition based on a tag, for example, requires the team to know the exact tag format you use.
2. Activity collection assignment rules
Explain how to decide which collection a product belongs to when it is not obvious. A track jacket that is suitable for both running and gym training needs a rule. Write it out:
- "Assign to all matching activity collections. If a product fits both Running and Gym, assign it to both."
- "Activewear that is also suitable for casual wear gets tagged 'casual' but is not assigned to a separate Casual collection."
- "Resort and swim products go into 'Swim/Resort' only, not into a generic Women's or Men's collection."
Without these rules, the team will make a reasonable call that may not match how you think about your own range.
3. Performance data fields
Activewear has product fields that do not exist in general apparel, and many of them are brand-proprietary: your supplier's fabric technology has a name that only you and your supplier use. These fields cannot be inferred from a product image or a standard supplier spreadsheet. The brief must list them explicitly.
The fields most activewear brands need to specify:
| Field | What to supply | Example |
|---|---|---|
| Fabric technology name | Exact brand name or fabric description from the supplier | "DuraFlex", "CoolWeave 2.0", "AirKnit" |
| UPF rating | Numeric value or "UPF 50+" if not graded further | UPF 50+ |
| Compression level | Your store's scale, not a generic one | Light, Medium, High (or 1, 2, 3) |
| Bra support level | Your scale, or omit if not applicable to the product range | Light, Medium, High, Maximum |
| Moisture-wicking | Yes or No, or the specific finish name | Yes / "WickAway" |
| Inseam length | Your standard values, in both metric and imperial if you serve international customers | 18 cm (7 in), 55 cm (22 in), 69 cm (27 in) |
Send these fields as an additional column in your supplier CSV, or as a separate reference document alongside it. If a field only applies to some products (UPF to tops, inseam to leggings), mark it "N/A" for products where it does not apply, so the team does not leave it blank by mistake.
For a broader look at how upload teams handle data fields across product categories, see Shopify product data entry.
4. Size run and fit conventions
Activewear sizing often includes extended size runs (XS through 4XL) and, for some brands, separate fits (Regular vs. Tall vs. Curve). Document these before the upload:
- "Our size runs are XS, S, M, L, XL, 2XL, 3XL, 4XL. Enter them in this order."
- "We carry Regular and Tall lengths in leggings. Regular inseam is 69 cm (27 in); Tall inseam is 79 cm (31 in). These are separate variants, not a separate product."
- "Sports bras use a letter-number sizing system (32A, 34B, etc.) for structured styles, and the standard XS to XL run for pull-on styles. These are different options on the same product type: do not mix them."
Shopify enters variant options in the order they are uploaded, not alphabetically, so the size run order in the brief becomes the order in the Shopify admin and on the product page. If your size run should go XS first and 4XL last, say so explicitly. For more on how variant order works in Shopify, see product options in the Shopify Help Center (as of October 2026).
An activewear collections brief template
Copy this one-page template and fill in your own values before sending it to your upload team. The brief can be a single document alongside your product file.
Collections to create
[List each collection name, one per line. Note: manual or automated. For automated, add the exact conditions.]
Multi-collection assignment rules
[Explain what to do when a product fits more than one activity. For example: "Assign to all matching activity collections."]
Performance fields to enter
- Fabric technology: [exact name from supplier, or "N/A" if not applicable]
- UPF: [numeric value or "UPF 50+", or "N/A"]
- Compression: [your scale, e.g., Light / Medium / High]
- Support (bra styles): [Light / Medium / High / Maximum, or "N/A"]
- Moisture-wicking: [Yes / No / finish name]
- Inseam: [your standard lengths, metric and imperial]
Size run
[List your sizes in the order you want them to appear, e.g., XS, S, M, L, XL, 2XL, 3XL, 4XL]
Fit variants (if applicable)
[Regular, Tall, Curve, etc. Note whether these are separate variants or separate products.]
Send this brief alongside your product file. For activewear, the brief replaces the usual "I'll describe it when you ask" approach: the questions come up often enough and quickly enough that answering them upfront saves time for everyone.
For more on how the timing side of an activewear upload works, including how to hand over seasonal drops to a team, see Activewear Drop Timelines: What Upload Teams Plan For.
For a general guide to structuring Shopify collections before any upload, see Shopify Collection Structure: What Your Upload Team Needs to Know.
Our fashion product upload service handles activewear catalogs including setting up collections, entering performance data fields, and standardizing size runs against your naming rules.
Frequently asked questions
Does every activewear brand need activity-based collections?
Not necessarily. If you sell one activity category (yoga only, or swim only), a single collection per gender plus a seasonal layer may be enough. Activity-based collections make the most sense when you sell across multiple activities and your shoppers filter by what they do. An upload team can set up the structure either way, but they need the decision stated in the brief, not made by inference mid-job.
What if a product fits multiple activity collections?
In Shopify, a product can belong to more than one collection, so there is no technical problem with assigning a product to both Yoga and Gym. The practical question is whether you want it in both. State it in your brief: "Assign to all matching activity collections" or "Assign to the primary activity only." Without a rule, the team will choose one, and it may not be the collection you had in mind.
How do performance data fields relate to collection conditions?
For automated collections, Shopify uses field values to decide which products go in. If your Yoga collection runs on a tag condition (tag equals "yoga"), every product needs that tag entered before the collection auto-populates. If you use a product type condition instead, the product type values need to be set first. Performance fields like compression level or UPF are typically stored as metafields or as tags, not as built-in Shopify fields, so the brief needs to say where they go and in what format. See Shopify automated collections for how conditions work (as of October 2026).
Can an upload team create collection names without a brief?
They can, but activewear naming is one category where the team's reasonable defaults may not match your brand voice. "W Running" and "Women's Running" and "Run" are all logical choices, and they generate different URL handles and navigation labels. Giving the team the exact names up front means you get the URLs you want from day one, without a redirect to add later. For a womenswear equivalent of this problem, see Womenswear Collections for Upload Teams: A Briefing Guide.
Do I need to send performance data fields for every product, or only the ones that apply?
Only the ones that apply. Mark non-applicable fields as "N/A" rather than leaving them blank, so the team knows the field was considered and not left out by accident. A blank cell and an N/A cell look different in a spreadsheet and in a Shopify product record. Consistency in how you mark skipped fields saves the team from asking for clarification on every third product.
