Configure Apparel PIM Setup
Before creating any Styles, an administrator configures the company-wide defaults. Open Apparel PIM Setup. It is a single record; opening the page creates it automatically if it does not exist yet.
Defaults group
These values every new Style inherits, filling blank fields only, never overwriting something already typed.
- Set Default Brand to the brand most new Styles will use.
- Set Default Numbering Scheme to the company-wide fallback numbering scheme. See the full cascade in Numbering and barcodes.
- Set Style Nos. and Colour Nos. if you want Style Codes and Colour Codes drawn automatically from a Business Central number series, rather than typed by hand. Leave both blank to keep manual coding, which is the default and requires no extra setup.
- Set Default Style Item Mode to Unique Item Per SKU or Variants Mode. Remember this locks once any SKU has a real inventory transaction.
- Set Default Variant Dimension (Colour or Size) if Item Mode is Variants Mode.
- Set Default Size Scale, Default Country of Origin, Default Primary Vendor No., and the three posting groups (Default Inv. Posting Group, Default Gen. Prod. Post. Group, Default VAT Prod. Post. Group) and Default Tax Group Code so new Styles and generated SKUs inherit sensible values without retyping them every time.
- Set Default Category Template Code to the template most new Styles should start from.
- Set Default Unit of Measure (for example Each) to the base unit of measure that new and generated Items should start from. From the point you set it, any Item the app creates, including SKUs generated from a Style and rows loaded through a bulk import, defaults its base unit of measure to this value.
SKU Behaviour group
- Set SKU Display Name Template and, if wanted, SKU Description 2 Template to control how a SKU's Item Description is built from its Style, Colour, and Size. Both accept the tokens
{Style},{StyleCode},{Colour},{ColourCode},{Size}, and{SizeName}. Leaving the Description 2 template blank means no SKU ever gets a generated Description 2 at all; leaving the main template blank falls back to{Style} {Colour} {Size}. - Leave Block Retired Code Reuse on (the default) unless you have a specific reason to let a permanently retired SKU code be reused. See Retired codes.
- Set Bulk Lifecycle Reversal Days to how many days a bulk lifecycle change should stay reversible (default 7).
- Set Default GTIN Pool Code and Auto-Allocate GTIN if you want barcodes to attach to SKUs automatically as they are generated. See Numbering and barcodes.
Images and Compliance groups
- Set Image URL Probe Enabled if you want the system to check that image URLs are actually reachable when saved, and Image Licence Warning Days for how far ahead an expiring image licence should flag on the role centre.
- Set Cert Expiry Warning Days for how far ahead an expiring certification should flag on the role centre.
Style Release Requirements group
All of these are off by default, meaning a Style can release with these fields blank until you deliberately tighten policy.
- Turn on Require Category on Release, Require COO on Release, Require Vendor on Release, and Require Post Groups on Release individually, according to how strict your release policy needs to be.
Result: the setup record holds every company default, and any Style created from this point on inherits them.
The Setup page as a launch point
The Setup page's ribbon is also the fastest way to reach every master list in the product: Brands, Collections, Colours, Size Scales, Numbering Schemes, SKU Statuses, GTIN Pools, Attribute Definitions, Category Templates, Tag Catalogue, Image Roles, Personalisation Payload Mapping, and the SKU Import worksheet all have a navigation tile here, grouped as Masters, SKU and Numbering, Attributes and Categories, Images, Fulfilment, and Data Import. It also runs Primary Collection Worklist, for deciding Primary Collection across the whole catalogue at once; see Bulk-assigning Primary Collection.