What case-and-piece inventory means
Many Bangladesh grocery stores, wholesalers, dealers, and distributors buy products by case or carton but sell them in more than one quantity. A business might receive twenty cases, sell five complete cases to one customer, and sell twelve loose pieces at the counter. Case-and-piece inventory keeps one explicit relationship between those quantities. StockLedger products can store a pieces-per-case value, while relevant inventory quantities can be entered and displayed as cases and loose pieces. The basic formula is: total pieces = cases × pieces per case + loose pieces. If one case contains 24 pieces, 8 cases and 7 loose pieces equal 199 total pieces. The formula is simple, but every later case-based transaction depends on the pieces-per-case value being correct.
Why the case size must match the real packaging
If a product actually contains 24 pieces per case but is configured with 20, every case-level purchase, sale, issue, return, or damage entry represents the wrong underlying quantity. That error can survive even when staff enter later transactions carefully. Check the printed carton, supplier document, and a physical count before regular transactions begin. Products with different case sizes should not be treated as interchangeable merely because their names look similar. When a supplier changes packaging, verify whether the existing product setup should be updated or whether the new pack needs a separate product record and controlled opening quantity.
Record what was physically received from the supplier
Purchase receiving can record case or piece quantities. The entered quantity should match what physically arrived, not only what the invoice says. If an invoice lists 12 cases but the delivery contains 11 cases and 18 pieces, recording the expected invoice quantity creates a difference immediately. Count the delivery, verify the product and case size, record the actual quantity and cost, and resolve the supplier discrepancy through the appropriate purchase record. Purchase returns and supplier balances should remain traceable to the real receiving history instead of being corrected through an unexplained stock adjustment.
Use the quantity that actually leaves during sales and DSR issues
Sales and DSR morning issues can use case or piece quantities. A counter sale might be seven loose pieces, while a wholesale invoice or route issue might contain full cases plus loose pieces. Product barcode values can help staff match the correct product during sales search, but a barcode does not automatically decide whether the customer bought a case or a piece. Staff still need to enter the quantity that actually moved. Selling one case while recording one piece leaves too much stock in the system; recording one case for a single-piece sale reduces the balance too far.
Illustrative BDT example: receive by case and sell by case and piece
This fictional example explains the calculation and does not represent a customer or market price. A wholesaler carries FreshDay Mango Drink 250 ml with 24 pieces per case, an illustrative purchase price of ৳960 per case, and an illustrative selling price of ৳45 per piece. Receiving 10 cases adds 240 pieces. Selling 3 cases and 8 loose pieces removes 80 pieces because 3 × 24 + 8 = 80. The remaining 160 pieces display as 6 cases and 16 pieces. If the same product had incorrectly been configured with 20 pieces per case, the case entries would produce a different and inaccurate balance even though the staff selected the right number of cases.
Returns, damaged stock, and movements must not be skipped
Returns, damaged stock, and stock-movement workflows operate on recorded quantities. When five damaged pieces are physically removed but no damage entry is recorded, the software still includes those pieces in the recorded inventory. A customer return can create the opposite problem when goods come back physically but the return is omitted. The same principle applies when goods move between controlled stock locations or workflows: the recorded event must reflect the physical event. Software cannot infer a movement that nobody entered, so responsibility for returns, damage checks, and movement approval should be clear before rollout.
Common reasons software stock and shelf stock disagree
Start an investigation with the product's pieces-per-case value and opening quantity. Then review recent purchase receiving, sales, returns, damaged stock, and stock movements. Typical causes include entering an invoice quantity instead of the received quantity, recording a case as a piece, omitting a loose-piece sale, accepting a return without recording it, removing damaged goods without an entry, or postponing transactions until several physical movements have already happened. Low-stock results also depend on the same recorded history. Correct alerts cannot be expected from incomplete transactions or an incorrect starting balance.
Case-and-piece setup checklist
For every relevant product, confirm the real pieces in one case, enter the pieces-per-case value, verify the opening cases and loose pieces, and store the correct barcode where barcode search will be used. Make sure staff understand the difference between a case and a piece and know how purchases, sales, returns, damage, and movements should be entered. Review the first transactions against a physical count before processing a large volume. Correct setup mistakes early; repairing a long history of inconsistent quantities is harder than checking the packaging and opening balance at the start.
A practical demo test before rollout
Create a fictional sample product with 24 pieces per case. Receive 5 cases and 6 pieces, which should equal 126 pieces. Sell 9 loose pieces, leaving 117 pieces or 4 cases and 21 pieces. Then sell 1 full case, leaving 93 pieces or 3 cases and 21 pieces. Test a realistic return, record several damaged pieces, and confirm that the new balance matches the expected physical quantity. Store a barcode and verify that sales search finds the product, then ensure the cashier still enters the correct case or piece quantity. Ask the employee who will perform the real work to complete the test; a calculation that only the owner understands is not yet an operational process.
Frequently asked questions about case-and-piece stock
Can StockLedger record cases and loose pieces? Yes, products can store pieces per case and relevant inventory quantities can be entered and displayed in both forms. What is the conversion formula? Total pieces equal cases multiplied by pieces per case, plus loose pieces. Can purchases and sales use different quantities? Purchase receiving and sales can record case or piece quantities, using the product's configured case size. Why can physical stock differ? Check case size, opening stock, purchases, sales, returns, damage, movements, and late or missing entries. Does barcode matching choose case or piece automatically? No. It helps find the product; the user must still record the quantity actually sold.
Keep the setup, quantity, and transaction history consistent
Reliable case-and-piece inventory depends on three habits: set the real pieces-per-case value, enter the quantity that actually moved, and record every purchase, sale, return, damage event, and stock movement completely. StockLedger provides a consistent quantity structure across the verified workflows described here, but it cannot correct an inaccurate case size or discover an omitted physical movement. Use your own products and actual staff during evaluation, compare the first recorded balances with a physical count, and investigate differences while the source documents and events are still easy to trace.
