Corporate apparel feels simple until a program asks people for sizes. A useful process must give each recipient enough information to choose a garment, keep unnecessary body details out of employer systems, reserve a realistic exchange pool, and close every exception without turning the size field into a permanent employee profile. The operating question is not “Which sizes do we need?” It is “What is the smallest, clearest decision record that lets a person receive or exchange the right item?”
Start with the recipient decision, not the inventory forecast
A size curve and an individual size choice solve different problems. A size curve estimates how many units to stock before everyone has responded. An individual choice records which specific garment a specific person wants. Mixing the two creates false certainty: a planning estimate becomes a personal assignment, while a personal preference is retained longer than the shipment needs it.
Use the branded apparel size-curve calculator for aggregate inventory scenarios. Use the workflow in this guide for recipient-facing collection, choice changes, exchange authorization, and deletion. The two records can reconcile at totals, but they should not be the same table.
Begin by defining the decision unit. “Medium” is rarely sufficient. A useful choice binds a supplier, product code, cut or fit, color, size label, size-chart version, destination, and choice timestamp. It does not require weight, medical history, body shape, pregnancy status, or a narrative about why a standard cut does not work. If the garment is optional, an equivalent non-apparel choice or an opt-out should be visible before collection begins.
ISO 8559-3 describes a methodology for body-measurement tables and intervals used in ready-to-wear garment development. That is useful context, but it does not make a supplier’s letter size universal. The operational source of truth remains the exact supplier chart and sample for the exact garment version. Publish measurements as product information; do not ask recipients to submit more measurements than the choice requires.
Before opening a form, write four statements in plain language: why the selection is needed, who can see it, when it will be deleted or de-identified, and what happens if the person does not want to provide it. If the team cannot state a deletion event, the form is not ready.
Design a minimal field map with clear owners
Treat every field as a cost and risk. The program owner should be able to point to the decision each field changes. “Helpful later” is not a decision. The NIST Privacy Framework is a voluntary risk-management tool, not an employment-law ruling, but its lifecycle view is practical here: collection, use, sharing, retention, and disposal all belong in the design, not only the form screen.
| Field or evidence | Operational purpose | Owner | Retention event |
|---|---|---|---|
| Program recipient key | Match an eligible recipient without exposing payroll details | Program operations | Case closure plus approved audit window |
| Product and size choice | Reserve, fulfill, or exchange one garment | Merchandise operations | Exchange window closes and reconciliation passes |
| Supplier chart version | Prove what measurements the recipient saw | Procurement | Retain as product evidence, not a person profile |
| Delivery destination token | Route fulfillment without copying an address into every system | Fulfillment owner | Delivery and exception period ends |
| Exchange reason code | Distinguish fit, damage, wrong item, or preference | Recipient support | Aggregate after case closure |
Do not default to free-text fields. A structured reason such as “too small,” “too large,” “wrong product,” or “damaged” is usually enough. Free text invites health, disability, family, or workplace information that the exchange team neither needs nor should interpret. If support needs a note, make it optional, warn users not to include sensitive information, restrict access, and define a short deletion rule.
Separate roles. Human resources may confirm eligibility without seeing size. Procurement may see aggregate demand and the supplier chart without seeing employee identity. Fulfillment may receive the shipping token and item code without receiving an employment record. Recipient support may open an exchange case without editing the source eligibility list. Security or privacy staff should review the data flow; they should not become day-to-day size approvers.
For United States programs, accessibility and employment decisions need specialist review when the process touches accommodation or disability. Do not ask a recipient to explain a medical reason merely to select another fit. Route an accommodation request to the authorized people process, and keep the merchandise record limited to the approved operational outcome. This guide is a workflow design, not legal advice.
Give people information that supports an honest choice
The quality of a size selection depends on the evidence shown before the click. Display the supplier’s current measurements, the measurement method, garment cut, stretch or layering notes, sample availability, personalization implications, exchange deadline, and stock limits. Add the chart’s effective date or version. A screenshot without a product code is weak evidence because it cannot prove which garment it described.
Avoid presenting a letter size as a body judgment. Say “choose the size you want for this garment,” not “enter your body size.” Explain that supplier labels vary. If employees can try a sample, use a private process: a shared try-on set or appointment may inform the person’s choice without recording measurements or comments. Sanitize and retire samples according to the program’s product and hygiene rules.
Offer meaningful alternatives. A recipient might choose a unisex cut, a different garment, a non-apparel item, a voucher within policy, or no item. An alternative is meaningful only when it is not visibly punitive and does not require a public explanation. Where local employment, equality, tax, or benefit rules could change the design, the local employer and specialist own that decision.
The collection interface should confirm three things before submission: the exact item, the exact supplier size, and whether personalization makes exchange harder. After submission, show a receipt that does not expose the choice in a public channel. Give a change deadline and a clear path for correction. A hidden support email is not a self-service change path.
-
Freeze the product code, fit, material, decoration, and supplier chart version.
-
Test the chart against physical samples before inviting recipients.
-
Remove fields that do not alter eligibility, fulfillment, or exchange.
-
Publish the choice deadline, exchange window, and personalization boundary.
-
Offer an opt-out or suitable alternative where program policy permits.
-
Restrict exports and prohibit copying size choices into general HR notes.
-
Test deletion, correction, and access revocation before launch.
Exception: the employee needs an accommodation
Do not turn recipient support into a medical inquiry. Record that the standard catalog did not meet the approved need, transfer the decision to the authorized employer process, and return only the minimum fulfillment instruction. The merchandise team should receive the approved product, size or alternative, delivery instruction, and case boundary—not the underlying diagnosis or narrative.
Reserve exchange inventory as a controlled service level
Exchange stock is not a random percentage added to every size. It is a service-level decision based on garment uncertainty, supplier lead time, personalization, event timing, regional return routes, and the cost of unused units. Keep it separate from the uncertainty buffer used for recipients who have not answered.
Define the exchange pool by product, size, location, and release rule. Stock reserved for exchanges should not silently satisfy new demand before the exchange window closes. Conversely, a huge locked pool creates waste. The owner needs a dated release decision: when open cases and remaining days fall below a threshold, excess units can return to normal stock or another approved use.
Decide whether the exchange is simultaneous, advance, or return-first. Simultaneous exchange reduces recipient delay but requires inventory and fraud controls. Advance exchange ships the replacement before return and may need an authorization hold or manager exception. Return-first protects inventory but can miss an event date. The policy should select the default and name the conditions for an exception.
Use the broader corporate gift returns and exchanges guide for financial treatment, cross-border movement, refunds, and damaged goods. This page narrows the question to apparel fit choice and its data trail.
An exchange ledger should record the original item, requested item, reason code, authorization, outbound and inbound state, stock movements, costs, deadlines, recipient notice, and closure proof. It should not require a body measurement. When a returned item is personalized, worn, damaged, or otherwise unsuitable for restocking, record disposition separately from the recipient’s eligibility for a replacement.
Prove the workflow with a small launch test
Do not make the first complete test the production launch. Build a compact test population that represents the real decision paths: a standard choice, a changed choice before decoration, an opt-out, an alternative item, an exchange with stock available, an exchange with stock unavailable, a delivery correction, and an approved accommodation path. Use test identities and safe destinations where possible. The goal is not to predict a response rate; it is to prove that every state has an owner, evidence, and reversible correction.
Write the state model before testing. A recipient might move from eligible to invited, selected, locked, allocated, decorated, shipped, delivered, exchange requested, exchange authorized, replacement shipped, closed, and retention expired. Not every program needs every state, but the owner must know which transitions are reversible. A change from selected to locked should require a documented cutoff. A move from exchange requested to closed should require the promised outcome, not merely an internal note.
Test permissions separately from functionality. Confirm that an eligibility administrator cannot browse size choices, a warehouse operator cannot open HR attributes, a support agent cannot export the full population, and a former contractor loses access. Attempt a correction after the deadline and confirm that the exception reaches the named approver instead of disappearing. Attempt to paste sensitive free text and confirm that the interface warns the user or the operating procedure removes it safely.
Rehearse inventory failure. Set one popular size to zero and confirm that the workflow shows real alternatives rather than accepting an impossible choice. Test whether a substitute requires new recipient consent when the cut, color, value, or decoration changes. If an exchange crosses a border, stop and obtain the applicable logistics and customs decision instead of treating it as a domestic return.
Finally, test closure. Close a successful case, a denied case, and an abandoned case. Confirm that the recipient received the final status, inventory posted correctly, costs reached the right owner, and the retention clock started. Run the deletion job against test records, inspect backups and exports covered by the process, and document exceptions. A launch passes only when the team can demonstrate both fulfillment and controlled disposal.
Hypothetical decision one: a 250-person jacket program
This is an illustrative case, not a Giftpack customer result. A company plans a 250-person jacket program across three offices. Procurement has an aggregate size curve, but only sixty percent of recipients have selected a size. The jacket has a supplier-specific athletic cut, and decoration begins ten days after the choice deadline.
The owner first separates confirmed demand from forecast demand. Confirmed choices reserve exact units. The remaining quantity uses the aggregate curve only for procurement planning; it does not assign sizes to people. Recipients see the supplier chart, a sample-fit schedule, the decoration deadline, a non-apparel alternative, and a notice that the program retains the choice through the exchange window and reconciliation.
The field map includes recipient key, product code, size choice, office, chart version, timestamp, and delivery token. It excludes height, weight, chest measurement, health information, and free-text explanation. Human resources supplies an eligibility token and never receives the size export. Procurement sees totals. Fulfillment receives the item and routing records. Recipient support can amend a choice until decoration begins.
The team reserves exchange stock by size using the known fit risk and supplier replenishment lead time. It keeps the reserve distinct from units purchased for nonrespondents. Before launch, five volunteers test physical samples and report product-level fit observations without creating named body profiles. Procurement records that the sleeves run differently from the prior jacket and updates the public fit note.
Failure appears after the first office receives samples: recipients interpreted the supplier’s medium as equivalent to another brand’s medium. The program pauses the invitation, corrects the guide with garment measurements, extends the choice deadline, and sends a neutral correction message. It does not ask recipients to justify changed choices.
Acceptance requires: the correct chart version attached to the product; all confirmed choices mapped to available units; zero unapproved body-measurement fields; an accessible alternative path; exchange reserve by size and location; successful correction and deletion tests; and a reconciliation showing confirmed, forecast, exchanged, released, and remaining units. A high response rate alone is not acceptance if recipients lacked a safe alternative or if stale choices remain in exports.
Hypothetical decision two: a size-out after peak shipment
This second case is also illustrative. A recipient receives a personalized polo during a peak shipment and reports that it is too small. The preferred replacement size is unavailable locally, the event is in twelve days, and an undecorated substitute is available from another region.
Support validates the recipient and original order using the case key, not by asking for body details. The reason code is “fit—too small.” The original item cannot return to general stock because it is personalized. Operations compares four outcomes: wait for the exact replacement, move the substitute across regions, offer a different approved garment, or issue the program’s allowed non-apparel alternative. A cash refund to the recipient would be wrong if the employer paid for the item, unless the program’s legal and financial owners define otherwise.
The decision owner chooses the different approved garment because it can arrive before the event and the recipient accepts it. The ledger preserves the original promise, the recipient’s new selection, stock decrement, disposition of the personalized item, freight, approval, and delivery proof. The recipient receives one message explaining the options and one closure message after delivery.
If the alternate shipment misses its carrier handoff, the case does not close merely because a label exists. Support reopens the remedy decision, confirms the event date, and offers the remaining alternatives. The failure path has an owner and a clock; it is not a vague promise to “follow up.”
Acceptance requires the recipient’s explicit selection among available outcomes, correct inventory movements, no duplicate shipment, a documented disposition for the personalized item, delivery or alternative completion evidence, and deletion or aggregation of the individual size record after the approved window. The organization may retain product-level exchange rates for planning without retaining named choices indefinitely.
Measure the system without profiling people
Program reporting should answer whether the process works, not rank bodies or teams. Useful measures include selection completion by deadline, change rate before decoration, fit-exchange rate by product and chart version, exchange cycle time, stockout frequency, duplicate shipments, unused exchange units, alternative-choice rate, deletion-test success, and recipient support reopen rate.
Use thresholds as investigation triggers, not proof of cause. A high exchange rate may indicate an inaccurate chart, a changed supplier cut, confusing instructions, or inventory substitution. It does not prove that recipients chose carelessly. Break product performance down by garment version and destination only when the segment is large enough for a legitimate operational decision and privacy review permits it.
Reconcile four ledgers: eligibility, recipient choice, inventory movement, and support cases. Counts should connect without forcing one unrestricted master file. Investigate mismatches such as a choice with no eligible recipient token, a shipment without a choice, an exchange without stock movement, or a closed case without delivery evidence.
Set a deletion job and prove it ran. The program owner should receive an exception report, not a copy of every deleted choice. Backups, exports, email attachments, and supplier portals belong in the retention map. Deleting the main form while leaving spreadsheets in shared folders is not closure.
At the end of the cycle, preserve the supplier chart, product specification, aggregate demand, aggregate exchange outcomes, policy version, and reconciliation. Remove or de-identify recipient-level size choices when the approved purpose and dispute window end, unless a documented obligation requires longer retention. The responsible employer and local specialists determine that rule; the merchandise platform does not.
Conclusion: make a size choice temporary and an exchange provable
A strong corporate apparel program does not try to predict every person’s body or eliminate all exchanges. It gives recipients a supplier-specific choice, provides a dignified alternative, limits who can see the record, reserves exchange stock deliberately, and preserves enough evidence to correct mistakes. The durable asset is the operating method: a field map, chart version, choice receipt, inventory reserve, exchange ledger, failure path, and tested deletion rule.
If your team is evaluating Giftpack for choice and fulfillment workflows, use this control set in the pilot: verify what data enters each system, who owns eligibility and privacy decisions, how alternatives are offered, and what evidence closes an exchange. Giftpack can support gifting execution; it does not decide employment, accessibility, privacy, tax, or legal obligations for the organization.