What Shopping Bag Sizes Should a Department Store Use?
A department store should not assign a shopping bag by department name alone. Cosmetics, folded apparel, a rigid gift box, and a mixed purchase fail in different ways even when they leave the same counter. The practical goal is a small, controlled size system: one core bag for repeat purchases, one larger exception where the evidence supports it, and clear routing for anything that needs another form of packaging.
Direct answer
Start by measuring completed purchases, including boxes, tissue, inserts, and protective packaging. Screen the smallest listed bag that accepts each purchase without forced insertion or blocked handle access. For this non-woven tote, the listed size labels are 30 × 25 × 11 cm, 35 × 30 × 11 cm, 45 × 40 × 14 cm, and 58 × 47 × 14 cm. Do not stock all four automatically. Approve a core row, document a larger exception, and verify that the exact Style, Size, and Pack combination is available in the live selector.
Build purchase profiles before choosing sizes
Separate departments by the geometry of the completed purchase, not by the product category printed on a stock report. A small accessory box may be rigid and depth-sensitive. Folded clothing may need more face area but can settle differently. A gift set may include a box, tissue, and card that change all three packed dimensions. A mixed basket may combine rigid and soft items that should not press against each other.
Create three or four master purchase profiles from real transactions. For each profile, record the finished width, height, and depth; the widest rigid zone; the orientation used at checkout; and the relevant packed-weight requirement. Bag dimensions do not establish carrying capacity, so weight and construction must be confirmed separately.
Screen the four listed size rows
Small — 30 × 25 × 11 cm
Use Small as a candidate for compact, already protected purchases. Reject it when a rigid corner catches at the opening, the contents crowd the handle area, or staff must rotate the item through a special angle that will not be repeatable during a busy shift.
Medium — 35 × 30 × 11 cm
Medium adds face width and height while retaining the same listed 11 cm depth. It can be a useful core candidate when everyday purchases need more front area but do not need a deeper base. Moving from Small to Medium will not solve a depth problem.
Large — 45 × 40 × 14 cm
Large adds face area and raises the listed depth to 14 cm. Test it for a defined apparel, boxed-gift, or mixed-purchase exception. Do not assume that the larger dimensions prove suitability for a particular load; confirm the packed-weight requirement and construction separately.
Extra Large — 58 × 47 × 14 cm
Extra Large adds substantial width and height but keeps the same listed 14 cm depth as Large. Retain it only for a recurring purchase that genuinely needs the added face area. A bulky item that exceeds 14 cm in finished depth may still need another stock structure or a separately specified custom bag.
Assign one core role and named exceptions
Do not place every size at every register. Start with a core row that covers the highest share of compatible completed purchases, then define a larger exception by rule. For example, an accessory counter might send ordinary protected purchases through the core row, while a boxed presentation purchase moves to the documented exception only after the finished pack passes.
Keep items that are sharp, leaking, unusually heavy, fragile without primary protection, or too large for the proven opening outside this routing system. The outer non-woven bag should not replace the packaging responsible for product protection.
Run a 10-bag counter pilot
The current product lists 10-Pack and 50-Pack options. Use a 10-Pack of one exact Style and Size as a ready-made operational test; it is not a verified custom MOQ or a substitute for a supplier-approved sample program.
- Freeze the purchase profile. Use the same completed items, inserts, and orientation for each rehearsal.
- Insert without force. Note catching corners, compressed tissue, or a blocked top area.
- Lift and hand off. Confirm that staff can reach the handles and the purchase remains controlled.
- Record exceptions. Write down why another bag was needed instead of relying on memory.
- Decide the role. Approve the row as core, exception-only, or rejected.
After the pilot, a 50-Pack can support ready-made replenishment for a proven row. Keep the exact style, size, pack quantity, current price, and observation date together so later comparisons remain auditable.
Factory control note: release a department routing card
A useful custom brief should replace labels such as “small department bag” with controlled fields. Record the department and purchase-profile name; finished packed W × H × D; rigid zones; insertion orientation; relevant packed-weight requirement; opening, gusset, handle, and closure requirements to confirm; exact finished dimensions and tolerances to confirm; material and construction; artwork revision; physical color reference; quantity; packing; destination; schedule; proof or sample basis; acceptance method; and one approval owner.
This prevents a color or artwork discussion from hiding an unresolved fit problem. It also separates the ready-made 10-Pack and 50-Pack options from a future custom quantity, printing method, timing, or performance claim. When the department routing data is stable, the buyer can Build a Custom Department-Store Bag Brief around confirmed requirements.
Approve the routing system, not all four sizes
The best department-store bag program is not the one with the most size labels. It is the smallest controlled set that staff can apply consistently to real purchases. Measure finished packs, prove one core row, keep only justified exceptions, and route incompatible merchandise elsewhere. That evidence makes the next 50-Pack purchase—or a separate custom inquiry—more precise.



