Skip to main content

Overview

Elevate Apparel is a product information management (PIM) add-on for apparel and fashion brands on Microsoft Dynamics 365 Business Central. It adds a Style, Colour, and Size matrix model on top of standard Business Central, generates the platform's Item and Item Variant records from that matrix, and layers attributes, images, certifications, collections, lifecycle management, GTIN barcodes, and bills of materials on top.

The problem it solves

Standard Business Central manages Items and Item Variants. It has no concept of a "Style" that comes in several colours and sizes, no matrix view, no season planning, and no apparel-specific lifecycle. Elevate Apparel adds all of that as a layer above the standard Item, so a merchandiser works in apparel terms (Style, Colour, Size, Collection, Drop) while the underlying inventory, sales, and purchasing still run on ordinary Business Central Items.

The Style, Colour, Size matrix

The core idea is a matrix: colours down the rows, sizes across the columns. You define the design once as a Style, choose which colours and sizes it comes in, then generate a sellable unit for each cell of the grid.

  • A Style is the design, independent of colour and size. It carries the brand, the category, the attributes that describe the design, and the rules that govern every unit generated from it.
  • A Product is a Style plus one Colour.
  • A SKU is a Product plus one Size: the actual sellable unit, materialised as a Business Central Item (or Item Variant).

Every generated SKU keeps a link back to the Style, Colour, and Size it came from, so you can always trace a plain Business Central Item back to the design it belongs to.

Who it is for

Elevate Apparel is built for merchandisers, product managers, and administrators at apparel and fashion brands who plan ranges by season and drop, carry the same design in many colourways and size runs, and need that structure to sit cleanly on top of Business Central's inventory, sales, and purchasing.

How to read these pages

You can read the areas start to finish as an onboarding path, or jump straight to the one covering the task in front of you.

  • Concepts explains the model and the patterns that repeat across the product.
  • Getting started covers first-time setup for an administrator.
  • Reference data covers the master lists everything else builds on.
  • Styles and SKUs is the day-to-day core: building a Style and generating its sellable units.
  • The remaining areas cover enriching a Style, planning collections, running the lifecycle, bills of materials, working from the item side, integration, worked business scenarios, and troubleshooting.

Throughout these pages, field names, actions, and page names are shown in bold, and the exact wording of an error or confirmation message is shown in quotes. Where a step has a specific, checkable outcome, it is written as Result: so you can confirm the system behaved as expected.