Apparel PIM: one style record, and the eight systems that read it
A style in four colors and six sizes is one design, four colorways and twenty four SKUs. Order entry wants the season. The warehouse wants the weight. A retailer's EDI catalog wants a UPC on every cell and standardized color and size codes. Shopify wants variants. In AIMS360 all of them read the same style record, which is why the definition is worth getting right the first time.
What is apparel PIM, and why is a generic product catalog not enough?
Product information management is the discipline of keeping one authoritative record per product that every other system reads. In apparel it has a wrinkle most catalogs were not built for: the thing you design, the thing a buyer picks and the thing a scanner reads are three different levels of the same product.
The style is the design. One number, one description, one size scale, one season, whether it comes in one color or nine. The style color is the colorway, which is what gets photographed, dated, repriced or cancelled on its own. The style color size is the SKU, which carries the UPC, the stock count and the pick ticket line.
A style in four colors on a six size scale is one style, four colorways and twenty four SKUs. A flat catalog makes you manage twenty four things. An apparel system lets you define one and inherit twenty four, then work at whichever level the task needs: cost the style, cancel the colorway, count the SKU.
Five decisions worth making before you create your first style
Most of the style record can be edited later. These five are either permanent or expensive to change once a season is in flight, so they are worth twenty minutes at the start rather than a migration at the end.
| Decision | Why it is hard to undo |
|---|---|
| Your style number convention | Up to fifteen letters and numbers with hyphens. It is the key every other module hangs on, and a style already in use cannot be renamed without becoming a new style. Decide whether the number encodes anything before you have five hundred of them. |
| The size scale | Pick the scale, disable the sizes that style does not offer, and the matrix appears. Once the style is on an order, in production, costed or adjusted, the scale is final. This is the one that catches people out. |
| Season, or year-round | A style with a season goes only on orders for that season. A style sold across deliveries is set to year-round and goes on any order. It is what stops spring goods landing on a fall order, and it is also what stops a core style being orderable if you set it wrong. |
| Divisions | Womens, mens, kids, a licensed line, a second label. Divisions drive views, reports, rep assignment and what a B2B buyer is allowed to see, so they are an access decision as much as a merchandising one. |
| Whether you need retail color and size codes | The standardized three digit codes that retail EDI speaks in, maintained for decades by the National Retail Federation and moved to GS1 US in 2020. Optional if you never sell through EDI. Not optional the day you sign your first department store. |
Everything else on the style is editable: description, prices, dates, weight, origin, fabric content, images, attributes, and the colors themselves. Colors come from a company wide library, so navy means the same thing on a shell fabric, a zipper and a finished jacket, and a new seasonal color can be added from the color picker without leaving the style.
Eight systems that read the style, and what each one needs from it
This is the part worth understanding, because almost every product data problem shows up somewhere else. A carton mislabeled, a catalog rejected, an invoice line a retailer will not accept: each traces back to a field that was blank or keyed twice.
| Reader | What it takes off the style |
|---|---|
| Order entry | Season and division to decide whether the style belongs on this order, the size scale to draw the grid, the wholesale price unless a price sheet overrides it, and the available and cancel dates, which trigger a warning when a delivery falls outside the window |
| The warehouse | The SKU and its UPC for the barcode on the ticket, and the net and packaged weight, which feed shipping rate quotes and packing |
| Retailer EDI | A UPC per cell, standardized color and size codes, the description truncated to whatever that partner caps it at, the country of origin and the minimum order quantity |
| The EDI catalog | The same codes published as a catalog document, which is how a retailer's system learns what you sell before the first purchase order |
| Your online store | Suggested retail as the retail price, the variants generated from the matrix, and the images flagged for that channel |
| The B2B portal and rep app | The collection the style sits in, the images flagged for that channel, and the price category that applies to the account looking at it |
| Costing and production | The style as the parent record a bill of materials, a cut ticket and a vendor purchase order hang from |
| Reporting | Division, season and your own attributes as the columns everything is grouped and filtered by, which is why attributes set badly show up as reports nobody can run |
Change the record and the change travels. There is nothing to sync, because there is no second copy. That is the whole argument for keeping product information in the system that also takes the orders and ships the goods, rather than in a catalog tool that feeds it.
Recent changes to the style record: color descriptions can run to 100 characters, up from 45, and wrap on confirmations and invoices (May 2026); size scale codes can be up to five letters or numbers (September 2026); and body codes are in AIMS360 Runway (October 2026). See What's New.
Size scales, and the categories that need two of them
Scales are defined once and reused
A size scale is a named list of sizes: S through 3XL, womens 0 to 16, waists 28 to 40, half sizes 5 to 13. Attach it to every style that uses it and misses alpha means exactly the same thing on every style, every season and every report.
A seasonal line of twenty four styles on shared scales is twenty four definitions rather than a thousand hand keyed products, and consistency becomes structural instead of depending on everyone typing size names identically forever.
When one axis is not enough
Plenty of products have a size. A meaningful share have two, and flattening them into a single mangled string is how product data gets corrupted. Denim needs waist and inseam. Tailored clothing needs chest and length. Dress shirts need neck and sleeve. Intimates need band and cup. Footwear needs size and width.
In AIMS360 the second dimension is part of the scale definition, so a 42R is a cell at the intersection of chest 42 and length regular, not a string that happens to contain a 42. That matters the moment you want sell through by length, or a retailer's order specifies both axes in codes.
The matrix is generated, not keyed. Attach the color range and the scale and every combination becomes a SKU with its own UPC from your GS1 company prefix, satisfying the one identifier per variant rule that retailers and marketplaces enforce. Adding a colorway mid season extends the matrix in one step rather than starting a new setup. The size matrix page covers scales, dimensions and UPC assignment in full.
Prepack, case pack and bundle are three different things
They get used interchangeably in conversation and behave nothing alike in a system. Mixing them up is the single most common reason a stock figure stops reconciling.
| Type | What it is | Effect on inventory |
|---|---|---|
| Prepack | A quantity per size set up against the size scale, so a buyer orders three of the usual run instead of typing eight numbers. A shortcut, and a way to enforce a minimum | None. The units stay ordinary loose units, and nothing is boxed or set aside |
| Case pack | A style number of its own, standing for a specific packing. It goes on an order, allocates, picks, ships and invoices like any style | Its own stock figure. Packing converts loose units into the case pack style, and cases can be unpacked again |
| Bundle | A multi unit offer priced as a set, configured when the order is placed rather than assembled in advance | Derived. Availability is the limiting component: for each item, available divided by quantity needed, rounded down, lowest result wins |
The rule of thumb: if you are about to create a case pack because you wanted a size run on an order, you wanted a prepack. Case packs carry inventory and prepacks do not, and that difference is what turns up six months later as a stock figure nobody can reconcile. How each one behaves in the system.
Ten fields you name yourself, and images per channel
Attributes without a developer
Up to ten dropdown attributes on the style, each with a name you choose and a list of values. Fit, fabric group, gender, collection, licensed property, planning class: whatever your merchandisers argue about. An attribute can be set once for the style or differently per colorway, so a print can carry a different collection tag than the solid.
They appear as columns in list views, so you can filter every style by fit and collection, save the view for a role and export it. The view is the report.
One image for the design, one per color, one per channel
A default image represents the style regardless of color. Images per color appear when that color is selected and on reports and line sheets that print images. Every image carries a sort order, where sort one is the default, and switches for each connected channel.
So the lifestyle shot goes to your online store and the flat lay goes to the B2B portal, from one upload rather than two libraries.
Practical rules worth knowing before a bulk season load: image file names use letters, numbers, hyphens and underscores; keep files under 4 MB because AIMS360 does not resize them; and naming files to the style and color lets you load a whole season at once.
What to know before you plan around it
| Constraint | Detail |
|---|---|
| Design and development connect in | Color approvals, fit sessions and design work run in a connected PLM such as Centric PLM, WFX or BeProduct, and draft styles and samples are tracked in AIMS360 before the style is final. The style master holds styles that are approved, costed and ready to sell, and takes the finished style from the PLM when you have one. |
| The size scale locks once the style is used | On an order, in production, costed or adjusted, and the scale is final. Adding sizes to a style already selling means a new style number, so decide the run before the first order. |
| A style in use cannot be renamed | The style number is the key every other module hangs on. Changing it means creating a new style, which is why the numbering convention is a first week decision rather than a later one. |
| Descriptions get truncated by partners | Fifty characters on the style, but retail EDI partners commonly cap them at twenty to twenty five. Keep the first twenty meaningful, because that is what arrives on their side. |
| Images are not resized | Keep files under 4 MB. AIMS360 stores what you upload rather than generating derivatives, so the file you load is the file every channel receives. |
| Custom fields are a view, not a printed report | Your own attributes appear as columns in list views and exports. They are not on the standard printed reports, so plan to work with saved views rather than expecting them on a report you already run. |
| Bundle availability refreshes on a schedule | The calculation runs on a timed basis rather than recomputing on every movement, which keeps it accurate without loading the system all day. It is close to live, not instantaneous. |
What each part of product management does
The style master, the size matrix and the three kinds of pack, each in full.
Common questions
What merchandisers, operations leads and EDI coordinators ask before they move product data into one system.
Product information management keeps one authoritative record per product that every other system reads. In apparel it has three levels rather than one: the style is the design, the style color is the colorway, and the style color size is the SKU with its own barcode and stock count. A generic catalog treats all three as flat product entries, which is how a style in four colors and six sizes becomes twenty four things to maintain instead of one definition that generates twenty four.
A style is one design with one number, one description, one size scale and one season, whether it comes in one color or nine. A colorway is that style in one color, with its own status, dates, country of origin and images, and it is what a buyer picks off a line sheet. A SKU is one color in one size, with its own UPC, its own stock figure and its own line on a pick ticket. You cost the style, cancel the colorway and count the SKU.
Four fields are required: the style number, the season, the size scale and at least one color. Everything else is optional in the system but required by something downstream. Order entry wants the dates and the wholesale price, the warehouse wants the weight, retail EDI wants a UPC per cell plus standardized color and size codes and a country of origin, and your store wants the suggested retail and the images. The style will save without them. The EDI catalog will not accept it.
Not once it is in use. The style number is up to fifteen letters and numbers with hyphens allowed, and it is the key that orders, production, stock and reporting all hang on. Renaming means creating a new style, which is why the numbering convention is worth deciding in the first week rather than after five hundred styles exist.
No. Pick the size scale, disable the sizes that style does not offer, and the matrix appears. Once the style is on an order, in production, costed or adjusted, the scale is final. Extending a run for that style means a new style number. Scales themselves are reusable and can be extended for future styles, so inclusive sizing rolls out deliberately rather than one style at a time.
Per cell of the matrix, from your own GS1 company prefix, when the color range and the size scale generate the SKUs. That satisfies the one identifier per variant rule retailers and marketplaces enforce, and it means the barcode on the ticket, the line on the EDI order and the entry in the catalog are the same number. Cases carry a different identifier from the garment inside them, which is what lets a warehouse receive or ship a case without opening it.
They are the standardized codes retail systems speak in, maintained for decades by the National Retail Federation and moved to GS1 US in 2020. They map what a buyer's system calls color 001 in size 32X32 to what your team calls black in a 32 waist, 32 inseam. They are optional if you never sell through retail EDI, and not optional the day you sign your first department store. In AIMS360 they sit on the color library and the size scale, so they are set once and inherited by every style.
As a genuine second axis rather than a mangled size name. The second dimension is part of the size scale definition, so a 42R is a cell at the intersection of chest 42 and length regular, and a 32x34 is waist 32 by inseam 34. That distinction sounds academic until you want sell through by length, a buying curve by inseam, or a retailer order that specifies both axes in codes. Denim, tailored clothing, dress shirts, intimates and footwear all need it.
A prepack is a shortcut, a case pack is a product, and a bundle is a calculation. A prepack is a predefined quantity per size that makes order entry fast and moves no physical goods at all. A case pack is a style number in its own right, with its own stock figure, assembled from loose units and unpackable again. A bundle is a multi unit offer whose availability is derived from the stock of its components, taking the limiting one. Mixing them up is the most common reason a stock figure stops reconciling.
By the limiting component. For each item in the pack, divide the available stock by the quantity the pack needs and round down, then take the lowest result across all of them. Fifteen mediums where the pack needs two is seven packs. Twelve larges where the pack needs three is four. The large is the constraint, so the bundle shows four, and selling one more large drops it to three without anyone touching a stock figure. It works both ways: selling bundles reduces the loose units, and selling units reduces the bundles.
Up to ten dropdown attributes on the style, each with a name you choose and your own list of values, set up without a developer. An attribute can apply to the whole style or differ per colorway. They become columns in list views, so you can filter every style by fit and collection, save that view for a role and export it. They are not on the standard printed reports, so the saved view is the report. The same module adds custom fields to customers, orders, vendor purchase orders, cut tickets, materials and pick tickets.
Yes. Every image carries a sort order, where sort one is the default, and a switch per connected channel. So the lifestyle shot goes to your online store and the flat lay goes to the B2B portal from one upload rather than two libraries, and a swatch flagged for a marketplace stays a swatch there. Two practical rules: file names use letters, numbers, hyphens and underscores, and files should stay under 4 MB because AIMS360 stores what you upload rather than resizing it.
Product management is the style master side of the AIMS360 production and PLM solution. Draft styles and samples, bills of materials, costing and spec sheets run in AIMS360, while color approvals, fit sessions and design work run in a connected PLM such as Centric PLM, WFX or BeProduct. A finished style comes across into the style master and takes over from there. If you do not run a connected PLM, the AIMS360 production and material tracking side covers what most brands actually need.
Usually not, and adding one creates the problem it was bought to solve. The value of a single product record is that there is no second copy to drift, and a separate catalog tool feeding the ERP reintroduces exactly that. Most of the data failures brands blame on EDI or on a marketplace, a mislabeled carton, a rejected catalog, an invoice line a retailer will not accept, trace back to product information that was keyed twice in two places. Where a separate tool earns its place is enriched marketing content for a large direct business, which is a different job from the operational record.
Where product data touches the rest of the system
Last reviewed 20 October 2026 by the AIMS360 team. Field limits, locking rules and channel behavior reflect the AIMS360 configuration as of that date and are confirmed for your setup during implementation. Standardized retail color and size code tables are maintained by GS1 US. Product and company names belong to their owners.
Bring one style with a difficult size run
Two dimensions, a color that only exists in three sizes, a prepack your biggest account insists on and a case pack for the club program. We will set it up once and show you the same style arriving in order entry, on a pick ticket, in an EDI catalog and as variants on your store.
