Skip to main content

Business scenarios

Each scenario below is a short playbook cross-referencing the detailed steps elsewhere in these pages, for the situations a merchandiser or administrator actually runs into. This page covers the range-building scenarios; the fulfilment scenarios page covers selling, bundling, barcodes, and re-issue.

Launching a new seasonal drop​

  1. Create the Collection with Type Drop, and set its Release Window.
  2. Create each new Style for the drop, or re-issue one from a prior season.
  3. Build each Style's matrix: colours, sizes, and attributes.
  4. Add imagery, certifications, and web tags.
  5. Tag each Style into the Collection as Launch.
  6. Release each Style.
  7. Watch the Collection's rollups as pre-orders and sales come in.

Bulk-loading an existing catalogue​

Use this when onboarding a range that already exists elsewhere (a spreadsheet, a legacy system export, a previous platform).

  1. Set up Brand, Colour, Size Scale, and Numbering Scheme masters first, so the import can resolve them.
  2. Export the SKU Import template, fill it with every Style, Colour, and Size row from the source catalogue, and import it back in.
  3. If the exact codes to use are not known in advance, either leave Style Code and Colour Code blank and let the import draw them from a number series, or research and type the correct existing codes so the import matches into the right existing records rather than creating duplicates.
  4. Run Process. Review the Result column for any failed rows and correct them.
  5. Enrich the resulting Styles with attributes and images at your own pace; Process only creates the bare Style, Colour, Size, and SKU records.

Adding a colourway mid-season​

  1. On the existing Style, add the new Colour row; confirm the ad-hoc prompt if the colour is outside the Style's Colour Set.
  2. Generate the new colour's cells, either by clicking them in the matrix, or with Bulk Create Cells scoped to just the new colour.
  3. Release, choosing "release only the cells already created" if the rest of the Style is already live and you only want this one new colourway to go out now.
  4. If the new colourway should show up under a different tag than the rest of the Style's launch (for example, it is a mid-season re-show rather than part of the original launch), add a separate Colour-scoped Collection tag for it.

Retiring end-of-season stock​

  1. Run the SKU Rationalisation report to find genuine candidates: never sold, slow movers, or nothing received recently.
  2. For a whole Collection's worth of stock, use the Collection's Bulk Lifecycle Change instead, so the change is recorded as a reversible batch.
  3. Check the resulting Lifecycle Batch for any Open Doc Warnings and follow up on those documents separately; the transition itself is not blocked by them.
  4. If a code needs to be reused later for a genuinely new product, remember retired codes are never reused automatically.