Choose a release model before announcing it
Stocked releases, preorders and made-to-order programmes create different obligations. A stocked release needs received and checked inventory. A preorder needs a credible production plan and a clear explanation of when dispatch is expected. Made-to-order does not remove the need for capacity planning, quality control or a returns policy. Choose a model because the operation can support it, not because scarcity sounds attractive.
Separate a campaign date from the production milestones that make it possible. Build the schedule backwards from receipt, inspection and fulfilment preparation. Include time for sample revisions and transport uncertainty. If an approval is late, reassess the announcement rather than quietly removing the quality check. The customer sees one promise, even when several suppliers and internal teams contribute to delivery.
Give each sellable variant a clear identity
Maintain a product record for every garment style, colour and size combination. An internal stock-keeping unit should identify the exact variant and remain stable across the warehouse, order system and reporting files. If a retail channel requires GTINs, use the appropriate GS1 allocation process instead of inventing a barcode number. Internal SKU codes and globally standardised product identifiers serve different purposes.
Keep player customisation separate from the base garment where the workflow allows it. Record spelling, character limits, artwork references and any approval stage. Explain who checks the submitted name and when a personalised item becomes committed to production. Do not assume a label that looks similar can be substituted: a variant error can affect both order accuracy and stock counts.
Make product information useful before purchase
Show the approved garment, not only a digital render. Include front, back and relevant detail views with consistent lighting. Describe material composition, fit, care and decoration in direct language. A size guide should explain how measurements were taken and whether the table describes the garment or the wearer’s body. If an image shows a sample with a known difference, state that difference clearly.
Provide accessible information rather than placing every important detail inside an image. W3C WCAG 2.2 is a useful reference for text alternatives, contrast and interaction design. Good alt text explains meaningful visual information; it should not repeat a long sales paragraph. Delivery estimates, taxes, destination restrictions and return conditions should be available before a customer makes a purchasing decision.

Connect stock receipt to fulfilment
Agree who receives the batch, checks quantities, inspects condition and reports discrepancies. Stock should not become available merely because a supplier marked it dispatched. Identify the handling rules for rejected items and reserve any units needed for replacements, team use or photography. Count physical stock against the same variant records used for orders.
Test the packing workflow with a representative order. Confirm that size labels are visible, personalised items can be matched reliably and the parcel protects the decoration. Ask the fulfilment provider what information is needed for shipping labels and customs declarations. Destination-specific tax, consumer and customs questions need qualified advice; a generic launch checklist cannot determine the correct treatment for every market.
Plan the conversation after dispatch
Assign responsibility for delivery questions, damaged items, sizing enquiries and returns before the first order ships. Set a practical route for escalating a repeated defect to the product owner. A customer support team needs the approved product information and the ability to identify a batch, not only a campaign slogan. Keep supplier corrections separate from the customer’s immediate need for a clear response.
Consumer rights depend on the jurisdiction and the transaction. Personalisation can affect cancellation rights in some markets, but it does not automatically remove rights relating to faulty or misdescribed goods. Obtain appropriate legal guidance and write clear policies. After the release, review actual size demand, return reasons and production issues so the next order improves on evidence rather than memory.
The release gate
Use these checks during a team review. Ticks are temporary and are not stored when you leave or reload this page.
Keep the learning loop open
A release record should close with observations as well as results. Note which information prevented questions, where approval took longer than expected and which garment details caused confusion. Keep personal customer data out of general design-review documents. Use aggregated operational findings to update the next identity brief, specification and sample review. That is how a merchandise programme becomes repeatable rather than repeatedly starting from zero.