Skip to main content

Troubleshooting

Common errors and what they mean

  • "Style Code, Colour Code and Size Code are all required." One of the three key columns is blank on an SKU Import row. This does not mean the Style or Colour has to already exist; it means the column itself cannot be empty, unless you deliberately choose a blank-code resolution option. See Generating SKUs.
  • "[Field] is required on Style X and cannot be cleared." Brand, Size Scale, and Colour Set can be set once, but never cleared back to blank afterward.
  • "Style X is Discontinued and read-only." Move the Status away from Discontinued before editing anything else on the Style.
  • A Colour or Size will not delete. Something still references it: a Style's Colours list, a Colour Set membership, a generated SKU, or a per-Style size override. The error names what.
  • "Item No. X belongs to a retired SKU and cannot be reused." See Retired codes: either change the numbering scheme so the new code does not collide, or turn off Block Retired Code Reuse if reuse is genuinely intended.
  • A Cell Attribute value does not seem to apply. Check whether the attribute is flagged Override Allowed; if not, the Style-level value always wins regardless of anything entered at Colour or SKU level. See Attributes and their scopes.
  • "Web tag X is not in the Tag Catalogue." Either add the tag to the catalogue first, or ask an administrator for the free-tag permission if this really is meant to be a one-off, ad-hoc tag.
  • The release-scope prompt does not appear when you expected it. It only appears when a Style has a genuine, non-empty subset of cells already created; a Style with nothing created yet, or with every possible cell already created, always releases the full matrix without asking.
  • A Lifecycle Batch will not reverse. Either the reversal window (set on Apparel PIM Setup, snapshotted per batch when it ran) has expired, or the batch has already been reversed once.
  • A SKU discontinued from the Rationalisation report cannot be reversed. That action applies the status change directly, without creating a reversible Lifecycle Batch; use the Collection's Bulk Lifecycle Change instead when reversibility matters.
  • An image URL is rejected outright. Only secure HTTPS addresses are accepted; a plain HTTP link, or anything else, is always refused.
  • A GTIN will not validate. It must be exactly 12, 13, or 14 digits, entirely numeric, and its last digit must match the official GS1 check digit calculated from the rest.
  • The role centre's setup notification will not go away. It only clears once Run Setup Jobs on the Apparel Setup Hub has been run successfully; if the action itself errored (for example, the Job Queue is not active for this company), nothing was scheduled and the notification correctly keeps appearing.
  • The Apparel Setup Hub's status fields still read "Not yet run" after clicking Run Setup Jobs. The two jobs run on the Job Queue, not instantly; give the queue a moment to process the scheduled entries, then reopen the hub, or check the standard Job Queue Entries page for their actual status if the delay seems longer than expected.