Why Fashion Breaks Generic ERP: The Style-Color-Size Matrix Problem

Why Fashion Breaks Generic ERP: The Style-Color-Size Matrix Problem

Nov 13, 2026 · Look Cloud

Ask a fashion planner how many products they sell and you will get two answers: the number of styles, and the number of SKUs. The gap between those numbers is where most ERP projects in fashion and footwear run into trouble.

Generic ERP systems are built around the item. One item, one code, one stock level, one price. Fashion does not work that way. A buyer thinks in styles, a customer orders by color and size, and the warehouse ships individual SKUs. A system that cannot move between those levels forces people to do the translation by hand.

01

The matrix, explained

Matrix Structure · SKUs

Every fashion product is a grid. The style defines the design, materials and price. Colors and sizes multiply it into individual SKUs. Footwear often adds a third dimension, such as width.

Take a single sneaker style:

Dimension Values Count
Colors Black, White, Navy, Grey 4
Sizes 36 to 45 10
Widths Regular, Wide 2
SKUs for one style — 80

Now multiply by a 300-style collection and you are managing 24,000 SKUs every season, most of which live for only a few months. Each one needs a code, a barcode, a cost, a price and a stock level, and all of them need to stay consistent with their parent style.

Style-Color-Size Matrix Overview
02

Where generic ERP breaks

Operational Bottlenecks
  • Item creation. Creating 80 items one by one, with consistent descriptions, barcodes and prices, is slow and error-prone. Changing the price of the style later means updating 80 records.
  • Order entry. A wholesale customer orders 12 styles across colors and sizes. In a line-by-line sales order that can mean hundreds of lines instead of a quick grid entry.
  • Size curves and prepacks. Buyers and customers buy in ratios: a size curve, or a prepack of mixed sizes in one carton. A generic ERP has no concept of either, so prepacks are tracked outside the system, or not at all.
  • Planning and purchasing. Plans are made at style level but purchased at SKU level. Breaking a style quantity into sizes, and consolidating SKUs into one PO per supplier, becomes a spreadsheet job.
  • Reporting. Sales and stock reports show long lists of SKUs. To answer “how is this style selling, and which sizes are running out?” someone has to pivot the data by hand.
03

The usual workarounds, and what they cost

Workarounds · Spreadsheets

Companies rarely stop to fix the matrix problem. They work around it. Item codes get built with clever naming conventions, user-defined fields hold the color and size, and Excel fills every gap: item creation templates, order grids, size breakdowns and pivot reports.

It works until it does not. Spreadsheets drift from the ERP, codes get typed wrong, and knowledge sits in the heads of two or three people. Every new season repeats the same manual effort. The ERP becomes a place where transactions are recorded, not where the business is actually run.

04

How Look Cloud solves it

Look Cloud · ERP Sync

Look Cloud adds the fashion layer that generic ERP is missing, while keeping SAP Business One, SAP S/4HANA or Acumatica as the system of record.

  • Style-first product data. Products are created once at style level, with their colors, sizes and size scales. Look generates every SKU, code and barcode automatically and syncs them to the ERP.
  • Grid-based entry. Orders, purchases and stock are entered and viewed as a style-color-size grid, not as hundreds of separate lines.
  • Size curves and prepacks. Look manages size curves and generates prepacks per model, creating the corresponding bill of materials in the ERP with the size curve built in.
  • Planning down to the SKU. Range plans and buys are made by style, and allocation breaks them down to SKU level using size ratios or the sell-through of similar products. Look then creates the buying transactions in the ERP, consolidating SKUs into purchase orders per supplier based on lead time.
  • Style-level analytics. Sales and stock roll up from SKU to color to style, so planners see performance where they make decisions and spot broken size runs early.
Look Cloud Grid Entry and Size Curve Management

Keep your ERP, fix the matrix: The answer to the matrix problem is not replacing your ERP or building another spreadsheet. It is adding a layer that thinks the way fashion people think, in styles, colors, sizes and curves, and keeps the ERP accurate underneath.

Running a fashion or footwear business on a generic ERP? Contact Argentis Systems to see how Look Cloud handles the style-color-size matrix with your own products.