An apparel shop should make stock decisions at the variant level rather than only by style. Give each size and colour combination a stable identifier, separate physical stock from reservations, and record exchanges against both variants. Reordering then uses the quantities customers can actually buy, while style-level totals remain useful for broader merchandising review.
- A popular style can still have unavailable sizes.
- Reservations need owners and expiry decisions.
- Exchange records should retain both variant identities.
Give every sellable variant an identity
Start with how staff recognise a garment at the counter. Style name alone may not distinguish colour, size, fit or season. Establish a variant code that maps to the supplier label, and define how a staff member finds it when the original tag is missing.
Maintain a clear relationship between style and variant records. Style-level descriptions support browsing and buying discussions; variant records support counting and availability. Avoid treating all small sizes as interchangeable when fit or collection differences would make the replacement unsuitable for the customer.
Distinguish stock on hand from stock available
A garment physically present in the shop may be reserved, awaiting inspection or set aside for an alteration discussion. Record those states separately. The staff member promising availability should see what can be sold now rather than a gross quantity that includes unresolved commitments.
Reservations need a customer reference, responsible employee and review time. Decide what happens when the customer does not return or requests a different size. A forgotten holding pile can distort availability just as much as an incorrect opening count, especially when only one unit remains.
Keep exchanges visible in both directions
A size exchange should identify the incoming variant, outgoing variant and inspection result. Do not change the original sale’s size field to make it resemble the final purchase. That erases the distinction between what the customer first selected and what ultimately left the shop.
Aggregate exchange reasons carefully. Staff can record observations such as requested larger size or preferred different colour without claiming a product defect. These records support a merchandising conversation, but the buyer should examine actual examples before drawing conclusions about future assortment or supplier quality.
Illustrative scenario: a shirt with uneven availability
Imagine a shop showing twelve units of one shirt style. Most are extra-small and blue, while customers are asking for medium in white. A style-level quantity suggests healthy stock; the variant view reveals that the requested combination has no usable units.
Two medium white shirts are reserved pending customer visits. The buyer can review those commitments and the supplier’s order pack before requesting more stock. This illustrative scenario shows why total units are insufficient: replenishment depends on the specific combination and the status of remaining units.
Review replenishment within supplier constraints
Suppliers may sell packs containing several sizes or require an order minimum. Record pack composition so the buyer can see what an order will add to each variant. Ordering one missing size may unintentionally increase quantities of slower-moving combinations in the same pack.
Use a short review that combines variant availability, recent requests, exchanges and open supplier orders. Keep judgement visible when the buyer overrides a suggestion. An explanation such as “event collection ending” is more useful than silently changing a reorder threshold to force the preferred result.
Ask for a demonstration that includes an exchange
A useful software demonstration begins with a multi-variant receipt, creates a reservation, performs a size exchange and then calculates available stock. Ask the demonstrator to show both the style summary and individual variant quantities after every movement, including a damaged incoming return.
The EasyManageX catalogue is illustrative, so confirm the needed variant and reservation behaviour rather than inferring it from product names. Provide a real supplier pack and a sample garment tag. Their awkward details often expose whether staff can maintain the model without resorting to handwritten workarounds.
Your working checklist
- Define stable codes for size and colour combinations.
- Separate available, reserved and review quantities.
- Assign reservation review times and owners.
- Retain both variants on exchange records.
- Capture supplier pack composition.
- Test replenishment after a partial size exchange.
Common questions
Should we create separate products for every size?+
You need separately identifiable sellable variants, but they can belong to one style record. The important test is whether counts, reservations, returns and supplier receipts preserve the correct combination. Evaluate the staff workflow rather than insisting on a particular database or screen layout.
What should happen to an expired reservation?+
The responsible employee should review it using the shop’s agreed reservation policy. Record release, extension or another outcome, and preserve the customer reference. Automatically making the unit available without considering a recent customer conversation can create a promise the counter cannot fulfil.
Can sales totals tell us which sizes to buy?+
Sales totals provide one view, but unavailable sizes and unresolved reservations can hide customer requests. Review variant availability alongside recorded requests and exchanges. Keep the buyer’s reasoning visible and account for supplier packs, so a recommendation does not create unnecessary stock elsewhere.
Sources and further reading
These primary references explain relevant concepts. Our scenarios and working checklists are original, illustrative guidance.
- Microsoft Learn: Inventory on-hand list
Further reading on dimension-based inventory views; relevant to reviewing size and colour availability separately from style totals.
Published by EasyManageX as practical, AI-assisted guidance. Examples are illustrative. Confirm software capabilities, licence terms and project-specific requirements before committing. Read our editorial policy.
