POS Case-Break Guide 2026: Keep Unit Stock Accurate

A case of 24 drinks arrives at your store. You sell one sealed six-pack and two single cans. Your stock should now represent 16 cans, but it should also tell staff which sealed packs remain. A POS that merely creates separate products called “case,” “six-pack,” and “single” may not connect those quantities at all.

This 2026 buying guide explains how to compare case-break POS inventory: the controls that connect purchasing units, packaging changes, sales, and counts. The objective is not to make every system use the same method. It is to choose a method your staff can execute without inventing stock or promising sealed packaging you no longer have.

POSadvice.com helps you compare POS systems. The examples below are illustrative acceptance tests, not results from a hands-on product trial. Vendor-specific statements are limited to the official documentation linked in this guide; confirm the exact edition, plan, and integrations in your quote.

Start with the packaging you actually sell

Write down three facts for each product family: the unit your supplier invoices, the units customers buy, and whether intact packaging matters. A store buying cases but selling only singles has a simpler requirement than a store selling cases, packs, and singles simultaneously. An unopened gift box is not necessarily interchangeable with the same number of loose products.

A case-break workflow changes how identical goods are packaged or counted. A mixed gift basket combines different goods and is a different inventory problem. See our POS bundle inventory guide if your offer includes multiple products rather than different quantities of one product.

Ask a supplier to demonstrate the precise hierarchy you use: for example, one case contains four six-packs, and each six-pack contains six singles. Bring actual barcode labels. A polished demonstration of one case becoming singles does not prove support for the intermediate pack size your cashiers scan.

Compare three case-break inventory approaches

Do not buy a system simply because the vendor says it supports variants. A color variant and a case-size variant can both appear in a catalog, but only the latter needs a mathematical packaging relationship. Get the relationship, the stock movement, and the effect on reporting demonstrated together.

What the official documentation actually distinguishes

Lightspeed Retail R-Series documentation on boxes describes linking cases to packs and singles, automatic breakdown or buildup at checkout, and manual box management. It also documents building boxes from singles. Its box type must contain the same item; mixed-item creations use assemblies instead.

Lightspeed Retail X-Series documentation on packaging relationships describes independent SKUs for pack sizes and explicitly assigned breakdown relationships. It says each variant or standard product can divide into one smaller product, so a hierarchy may be required to reach both packs and singles. It also states that the documented division cannot be reversed to rebuild a pack from singles.

The X-Series article places conditions on breaking products down during a sale; more complex packaging relationships may need catalog-based breakdown. These are material buying differences within one vendor’s product families. Do not let a quote substitute the broad brand name for the edition being demonstrated.

Neither documentation page establishes your full subscription price, every ecommerce connector’s behavior, or compatibility with your existing hardware. Put those unresolved items into the proposal. Treat documentation as a starting point for a specific demonstration, not a blanket endorsement.

Use a quantity test that exposes double counting

Create a test product with a case size of 24 and a pack size of six. Receive two cases. The starting quantity is 48 single-unit equivalents, regardless of how the software displays packaging. Preserve one case unopened and break the other into four packs. Then open one pack into six singles.

At that point, a packaging-aware record should describe one case, three packs, and six singles: 24 + 18 + 6 = 48. Sell one pack and two singles. The remaining equivalent quantity is 40, represented by one case, two packs, and four singles. Ask the demonstrator to show that result in the stock screen and inventory export.

Now request one sealed case. The unopened case can fulfill it. After selling that case, 16 single-unit equivalents remain, but those leftovers cannot satisfy another sealed-case order. This second test separates quantity availability from package availability, a distinction that can matter for online orders and customer promises.

Record exactly what the cashier had to do. A technically correct result that requires a manager to edit inventory during every rush may be the wrong operational fit. Measure the number of actions during your own demo instead of relying on an unverified speed claim.

Check cost conversion separately from selling price

For an illustrative costing test, assume one case costs $36 and contains 24 identical units, with no freight or other adjustments. The starting cost is $1.50 per single, or $9 for a six-pack. A conversion should not create an extra $36 of stock or erase the original cost merely because additional product records appear.

Your six-pack selling price does not have to equal six times the single selling price. Selling price and inventory cost answer different questions. Ask where the system stores each value, how price changes affect linked sizes, and whether an employee can accidentally edit the conversion factor while changing a promotion.

Then receive a second shipment at a different cost. Have the provider explain its supported costing method and show the resulting valuation. The R-Series documentation describes allocating box cost to singles when breaking boxes and summing component cost when building them. That does not mean every POS or accounting integration follows the same method.

Include receiving and invoice matching in the trial. Our POS purchase orders guide covers the wider purchasing workflow. Here, the critical requirement is that “two cases received” does not become “two singles received” because the purchase order and catalog use different units.

Test returns, damage, and counts before signing

Return an unopened six-pack against its receipt, then repeat with a damaged pack containing only five sellable units. The second case needs a clear decision about return policy, quarantine, and salvage; staff should not silently restock a sealed six-pack that does not physically exist. Ask how the original sale, refund, and stock correction remain connected.

For damage, remove one single from an opened pack and record the reason. Check whether the adjustment affects only that location and whether it preserves the correct cost basis. A generic negative adjustment may be workable, but the person reviewing shrink should still understand what happened.

During a count, deliberately enter one unopened case, two packs, and four singles. The software should not count the case once as a case and again as 24 freely available singles. Ask how the count sheet labels units and whether inactive purchasing-only SKUs are included when needed.

Finally, transfer a case to another location and break it down after receipt. Confirm which location owns the stock during transit and who may record the breakdown. A correct one-store demonstration does not establish the behavior of a multi-location rollout.

Pros and cons of buying deeper packaging controls

Pros

• Clearer stock explanations: staff can distinguish a sealed case from loose units instead of relying on a total alone.
• More structured receiving: supplier packaging can be recorded without manually translating every line into selling units.
• Reviewable conversions: a documented breakdown can explain why one SKU fell while another increased.

Cons

• More catalog setup: package ratios, barcodes, prices, and relationships require careful maintenance.
• More training: physical repacking and software events must stay aligned.
• Possible channel differences: the register, ecommerce store, and inventory connector may not share identical conversion behavior.

These are reasons to scope the implementation, not promises of financial savings. A shop that opens every case immediately might be better served by straightforward receiving into singles. A shop selling sealed cases all day should put packaging visibility higher on its evaluation sheet.

Request a quote with an acceptance checklist

Send each finalist the same small catalog sample and packaging diagram. Request separate prices for software, registers, scanners, catalog setup, migration, ecommerce integration, training, and ongoing support. Ask whether the quoted plan includes the demonstrated packaging feature and whether additional outlets change the price.

Require five acceptance results: correct receiving units, correct pack conversion, correct sales availability, correct return behavior, and a reconciled count export. Save the demonstration date and product edition. If an integration is needed, identify who supports it when the register quantity and online quantity disagree.

Agree on a pilot using a handful of high-volume packaged products before converting the whole catalog. Count the physical stock at the start, record every breakdown, and compare the ending stock with the system. Expand only after the staff member who will actually handle replenishment can explain the result.

A strong buying decision is not “this POS has case breaks.” It is “this quoted configuration preserves our quantities, packaging, and costs through the transactions we perform.” Use that standard when comparing proposals.

Frequently asked questions

What is case-break inventory in a POS system?

Case-break inventory connects larger packaging quantities to smaller selling quantities, such as one case of 24 cans becoming four six-packs. The system must record the quantity movement without counting the same goods twice.

Are product variants enough to track cases and singles?

Not necessarily. Separate variants can have unrelated inventory quantities. Ask the provider to demonstrate an explicit packaging relationship or another supported method that preserves total units when stock is received, divided, sold, and returned.

Can every case-break POS rebuild packs from singles?

No. Support depends on the product and workflow. Lightspeed R-Series documents building boxes from singles, while the cited X-Series packaging documentation says its division cannot be undone. Confirm the exact edition and physical packaging requirements.

What should a case-break POS quote include?

Request the exact product edition and plan, required registers and scanners, catalog conversion, migration, ecommerce connectors, training, and support. Include acceptance tests for receiving, packaging conversion, sales, returns, and inventory counts.