Skip to main content

Fulfilment scenarios

These scenarios cover selling, bundling, barcodes, and re-issuing a Style. For the range-building scenarios, see Business scenarios.

Selling a personalised item​

  1. Define the Personalisation BoM on the parent Item, with one component per instruction to capture (monogram text, thread colour).
  2. Configure the Personalisation Payload Mapping once, to match your fulfilment partner's contract, if it differs from the default shape.
  3. On the actual Sales Order, add the parent line as normal; fill in each generated sub-line's Personalisation Value.
  4. Release the Sales Document as normal; a missing Required value is caught here before the order goes any further.

Bundling a gift set​

  1. Create (or choose an existing) parent Item to represent the kit.
  2. Add each stocked component to its Kit Components grid, with the right Quantity per.
  3. Decide whether the kit should assemble to order (the default, once any component line exists) or be pre-built and held as Assemble-to-Stock, and set the parent Item's Assembly Policy accordingly.
  4. Sell the kit's parent Item on a Sales Order as normal; standard Assembly Order processing takes over from there.

Setting up barcodes for a new supplier batch​

  1. Create a GTIN Pool for the batch.
  2. Load the purchased numbers via Import from Excel (if the reseller supplied a list) or Generate Range (if you have a contiguous block).
  3. Decide whether new SKUs should draw a barcode automatically going forward: turn on Auto-Allocate GTIN on Apparel PIM Setup, and set this pool as the Default GTIN Pool Code (company-wide), or as a specific Brand's or Style's own override, depending on how narrowly the batch should apply.
  4. For Items that already exist without a barcode, use the Item List's Allocate GTIN action to backfill them from this pool in bulk.

Re-issuing a discontinued Style​

See Release for the full step-by-step: set the new Style's Predecessor Style Code, run Inherit from Predecessor to bring across colours and attributes, and use Predecessor Style and Re-Issued By to navigate the lineage in either direction afterward.