# Prepack Optimization > Site directory and reading guidance: [llms.txt](https://wiki.skusavvy.com/llms.txt). Canonical URL: https://wiki.skusavvy.com/article/prepack-optimization Published: 2026-11-07T00:03:13.146Z Last updated: 2026-11-07T00:31:17.877Z Category: Fulfillment > This article is AI-assisted reference material. Verify important or time-sensitive claims against the cited sources; AI review does not establish independent factual verification. ## Overview **Prepack optimization** is the process of deciding which products or variants to combine in a predefined pack, how many packs to produce or buy, and where to send them. It is especially relevant in apparel and footwear, where a single style may be distributed in a fixed assortment of sizes, and in retail replenishment, where mixed-product cases can reduce handling. The aim is to match demand as closely as possible without losing the operational advantages of standardized packs. A plan may draw on [SKU-level inventory information](https://www.skusavvy.com/sku-based-inventory) and broader [inventory optimization practices](https://www.skusavvy.com/inventory-optimization-software), but a warehouse management system does not necessarily calculate the pack mix itself. Intact prepacks may later move through [cross-docking workflows](https://www.skusavvy.com/docs/guides/warehouse/cross-docking) or be stored and allocated as bulk inventory; neither method is required in every network. ## Etymology and Origins *Prepack* is a shortened form of *prepackaged*: goods are packaged before the point at which they are distributed or sold. In logistics, the term can refer to a fixed assortment of variants assembled before shipment. [Prepackaged](https://www.merriam-webster.com/dictionary/prepackaged) is a broader term and does not by itself imply that a pack contains multiple SKUs. [Optimization](https://www.merriam-webster.com/dictionary/optimization) describes selecting a desirable solution subject to constraints. In this context, it distinguishes a deliberate choice of pack ratios and allocations from simply using a customary case quantity. The approach can use [mathematical optimization](https://developers.google.com/optimization), including [mixed-integer programming](https://developers.google.com/optimization/mip), although spreadsheets and business rules can also support prepack decisions. A definitive first use of the combined term *prepack optimization* is not established here. ## Historical Development Prepack optimization applies several older practices rather than an invention attributable to one person. Manufacturers and merchants have long used standardized packages to make products easier to handle and distribute. The specific origin of mixed-variant retail prepacks is not established in the sources cited here. A mathematical foundation for a related inventory decision appeared in **1913**, when Ford W. Harris published “How Many Parts to Make at Once.” The [1990 republication of the Harris paper](https://doi.org/10.1287/opre.38.6.947) presents that economic-order-quantity work. It addresses order sizing, not modern apparel prepack optimization, but illustrates the longstanding trade-off between ordering and holding costs. In the **1970s**, barcode-based identification made item-level data capture more practical at retail scale. Accounts of the [history of the barcode](https://www.nist.gov/history/barcode) and the [Universal Product Code](https://en.wikipedia.org/wiki/Universal_Product_Code) place the first commercial UPC scan in **1974**. Later computerized inventory, enterprise-planning, and warehouse systems made it easier to maintain sales and stock records by variant and location. Those developments are not evidence of a particular date when prepack optimization was first practiced. Published operations-research work has since formulated prepack configuration and allocation with mixed-integer programming and heuristics. One cited example is research on [prepack optimization for retail distribution](https://doi.org/10.1016/j.ejor.2008.07.037). That literature examines how fixed pack ratios interact with location-level demand. It does not by itself establish when merchants first used prepacks, nor does it prove that a particular decade originated the practice. Planning tools can combine variant-level records with forecasts and [integer optimization methods](https://developers.google.com/optimization/mip). ## Core Concepts and Calculation A **pack profile** specifies the number of units of each SKU or variant in one pack. A size pack of small, medium, and large garments might have a **1:2:1** profile, for four units per pack. A purchase of ten such packs contains 10 small, 20 medium, and 10 large units. The profile can be fixed by a supplier or chosen from an approved set. A typical model considers: - **Demand:** expected sales or replenishment needs by SKU, store, and period. - **Pack choices:** permitted profiles, case sizes, and the number of packs assigned to each destination. - **Constraints:** supplier minimums, available stock, warehouse capacity, delivery schedules, and whether cases may be broken. - **Costs and service:** shortages, excess inventory, markdowns, handling, transport, and transfers. For destination *s* and variant *i*, supplied quantity can be expressed as the sum, over pack types, of the number of packs of each type assigned to that destination multiplied by that pack’s quantity of variant *i*, plus any loose units supplied. An objective can minimize the weighted costs of shortage and excess alongside pack, handling, and transport costs. Pack counts are normally nonnegative integers, so [mixed-integer programming](https://developers.google.com/optimization/mip) is a useful modeling approach when the decisions and constraints are complex. Reliable [SKU-based inventory records](https://www.skusavvy.com/sku-based-inventory) are needed to turn a calculated allocation into executable movements; replenishment tools such as [reorder monitoring](https://www.skusavvy.com/docs/guides/warehouse/reorder-radar) can support that execution but do not themselves define the optimization model. ### Illustrative example Suppose a store needs **3 small, 4 medium, and 1 large** unit. Two packs with a 1:2:1 profile supply **2 small, 4 medium, and 2 large**. Compared with demand, the shipment is one small unit short and has one excess large unit. Although the shipment and demand both total eight units, only seven units match the requested variants. Supplying the missing small unit separately can improve service, but the extra handling and remaining large-unit excess must be considered. ## Types and Applications **Single-profile prepacks** use one fixed ratio across destinations. They are easy to procure and handle but may fit individual stores poorly. **Multiple-profile prepacks** offer several approved ratios, allowing stores with different size curves to receive better-fitting assortments at the cost of more planning complexity. **Mixed-case prepacks** combine different products, such as several flavors or cosmetics, rather than sizes of one style. **Store-ready packs** are assembled for a particular destination, while a distribution center may break bulk cases and build custom assortments closer to the point of demand. These operations overlap with [warehouse kitting](https://www.skusavvy.com/docs/guides/warehouse/kitting), although a prepack may be a distribution unit rather than a kit sold to a consumer. Pack definitions must also distinguish the case from its contents. [GS1 GTIN guidance](https://www.gs1.org/standards/id-keys/gtin) provides a framework for identifying trade items. A case and each unit inside it may require different identifiers, depending on how the items are ordered and traded; organizations should apply the relevant identification rules rather than assume that they share one identifier. ## Benefits, Challenges, and Trade-offs Standard packs can reduce individual picking, simplify receiving, and make supplier production and shipment planning more repeatable. They are most attractive when destinations have similar demand patterns and case quantities align with replenishment needs. [Pick-and-pack workflows](https://www.skusavvy.com/pick-pack-ship-software) illustrate the handling activity that can be reduced or reorganized when goods arrive preassembled. The principal drawback is **ratio mismatch**: excess units of one variant can coexist with shortages of another. Forecast errors, seasonal shifts, minimum order quantities, and changing store demographics can worsen that mismatch. A plan that minimizes case handling alone may therefore increase markdowns or missed sales. [Inventory optimization](https://www.skusavvy.com/inventory-optimization-software) provides the broader context for evaluating availability against inventory investment. A hybrid approach can limit risk: send common profiles for the predictable base requirement, then use loose units or transfers for exceptions. Whether this is economical depends on the cost of breaking packs, shipping additional units, and managing the remaining inventory. ## Implementation and Measurement 1. **Prepare data.** Validate variant identifiers, pack contents, store inventory, sales history, lead times, and supplier constraints. Record the relationship between cases and individual units using consistent [units of measure](https://www.skusavvy.com/docs/guides/products/unit-of-measure) and establish [unit-of-measure conversions](https://www.skusavvy.com/docs/workflows/unit-of-measure-conversion) between case packs and eaches. 2. **Estimate demand.** Develop forecasts by destination and variant; adjust for promotions, seasonality, and known stockouts that may have suppressed observed sales. 3. **Generate and test profiles.** Compare the current assortment with candidate ratios, loose-unit fulfillment, and hybrid alternatives. Model operational constraints before treating a calculated solution as feasible. 4. **Pilot and reconcile.** Test with a limited product group or store cluster. Check physical case contents against system records and use [inventory reconciliation](https://www.skusavvy.com/docs/guides/warehouse/inventory-reconciliation) to investigate discrepancies. 5. **Review outcomes.** Track variant-level fill rate, stockouts, excess units, markdowns, handling time, and cost per unit delivered. Re-estimate profiles as demand or supplier terms change. A useful diagnostic is **variant match rate**: units supplied that correspond to demand for the same variant, divided by total units demanded. In the illustrative example, the match rate is 7 ÷ 8, or **87.5%**. This is a planning measure, not a substitute for actual sales or service results. ## Source links - [GS1 Global Trade Item Number]() - [SKU-Based Inventory]() - [Inventory Optimization Software]() - [Prepackaged Definition]() - [Mixed-Integer Optimization]() - [How Many Parts to Make at Once]() - [The History of the Barcode]() - [Warehouse Kitting Guide]() - [Pick, Pack, Ship Software]() - [Unit of Measure Guide]() - [Inventory Reconciliation Guide]() - [Cross-Docking Guide]() - [Optimizing pre-packs for retail distribution]() - [Reorder Radar]() - [Unit of Measure Conversion Workflow]() - [Universal Product Code]() - [Optimization]() - [Google OR-Tools: Optimization]()