What case-and-piece inventory means
Many grocery stores, wholesalers, dealers, and distributors in Bangladesh buy products by case or carton but sell them in both full cases and loose pieces. For example, a business may receive 20 cases, sell 5 complete cases to a wholesale customer, and sell another 12 loose pieces at the counter. Case-and-piece inventory keeps one conversion 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 pieces because 8 × 24 + 7 = 199. The arithmetic is simple, but every later case-based purchase, sale, issue, return, or stock count depends on the pieces-per-case value being correct.
Set the correct pieces-per-case value before regular transactions begin
The most important setup decision is the real number of pieces inside one case. If a product physically contains 24 pieces per case but the system is configured with 20, every full-case transaction represents the wrong underlying quantity. Staff may enter the correct number of cases and still end up with incorrect stock. Verify the packaging before regular transactions begin. Check the printed carton, supplier document, and a physical count where necessary. Products with similar names should not automatically share one case size. For example, a supplier may sell different pack sizes or change packaging later. When packaging changes, decide carefully whether the existing product setup should be changed or whether the new pack should use a separate product record and controlled opening quantity. Correcting the case size at the beginning is much easier than repairing months of quantity history later.
Record the quantity that physically arrived from the supplier
Purchase receiving should reflect the quantity actually received, not simply the quantity expected from the supplier invoice. StockLedger purchase receiving can record case or piece quantities. Suppose an invoice says 12 cases, but the delivery physically contains 11 cases and 18 loose pieces. If one case contains 24 pieces, the received quantity is 11 × 24 + 18 = 282 pieces. Recording 12 complete cases would instead add 288 pieces and create a 6-piece difference before anything has even been sold. Count the delivery, confirm the product and case size, and record the actual received quantity and relevant cost. Then resolve any supplier discrepancy through the appropriate purchase process. Purchase returns and supplier balances are easier to investigate when they remain connected to what was genuinely received instead of being repaired later with an unexplained stock adjustment.
Record what actually leaves during sales and DSR issues
The same rule applies when products leave the business. Sales and DSR morning issues can use case or piece quantities. A retail counter may sell seven loose pieces, while a wholesale invoice or route issue may contain three full cases plus several individual pieces. Product barcode values can help staff find the correct product during sales search, but the barcode does not automatically decide whether the customer bought a case or a single piece. The user still needs to enter the quantity that physically moved. If one full case leaves the shop but only one piece is recorded, the software will show too much remaining stock. If one loose piece is sold but one case is entered, the recorded balance will fall too far. The quantity entry should describe the physical movement, not merely the packaging label staff happen to remember.
Worked example: receive by case, then sell by case and piece
Example only: a wholesaler carries a fictional product called FreshDay Mango Drink 250 ml. One case contains 24 pieces. For illustration, assume a purchase price of ৳960 per case and a selling price of ৳45 per piece. Receiving 10 cases adds 10 × 24 = 240 pieces. The wholesaler then sells 3 full cases and 8 loose pieces. That sale removes 3 × 24 + 8 = 80 pieces. The expected remaining stock is therefore 240 - 80 = 160 pieces. Converting 160 pieces back into case-and-piece form gives 6 complete cases and 16 loose pieces because 6 × 24 + 16 = 160. Now imagine the same product had mistakenly been configured with 20 pieces per case. The staff could enter exactly the same '3 cases and 8 pieces' transaction, but the underlying quantity calculation would be wrong. This is why case size is a master-data control, not just a display preference.
Returns, damaged stock, and stock movements must use the same quantity logic
Case-and-piece control does not stop after purchases and sales. Returns, damaged stock, and stock movements also change the recorded quantity. Suppose five loose pieces are damaged and physically removed from normal stock. If no damage transaction is recorded, the software continues to include those five pieces in inventory. A customer return creates the opposite problem when goods physically come back but no return is entered. The same principle applies when stock moves between controlled locations or workflows: the recorded movement should match what physically happened. Keep good returns and damaged goods distinguishable where the business process requires different treatment. Software cannot discover a physical movement that nobody recorded. Clear responsibility for purchase receiving, customer returns, damaged-stock entry, and stock movement therefore matters as much as the case-and-piece conversion itself.
Why software stock and physical stock may disagree
When the software balance and shelf quantity do not agree, start with the basic conversion setup before making a manual adjustment. Check the product's pieces-per-case value and opening stock first. Then review recent purchase receiving, sales, DSR issues where relevant, customer returns, purchase returns, damaged stock, and stock movements. Common causes include entering the supplier invoice quantity instead of the physically received quantity, recording a case as a piece, recording a piece as a case, missing a loose-piece sale, accepting a customer return without entering it, removing damaged goods without a damage record, or entering transactions long after the physical movement happened. Low-stock information also depends on this transaction history. A system cannot produce a reliable stock warning from an incorrect opening balance, wrong case size, or incomplete movements.
Use a case-and-piece setup checklist for every relevant product
A short setup checklist can prevent many later stock problems. 1) Confirm the real number of pieces in one case. 2) Enter the correct pieces-per-case value. 3) Verify the opening quantity in cases and loose pieces. 4) Store the correct barcode where barcode search will be used. 5) Confirm how staff should enter purchases received in mixed case-and-piece quantities. 6) Confirm how full-case and loose-piece sales should be recorded. 7) Explain how customer returns, purchase returns, damage, and stock movements affect quantities. 8) Test the first few transactions against a physical count. 9) Investigate any difference before processing a large volume of transactions. 10) When packaging changes, review the product setup before using the new case size. The goal is to make the conversion rule part of the operating process rather than something only the owner understands.
Run a practical case-and-piece test before rollout
A simple test can reveal setup and staff-entry problems before they affect real stock. Create a sample product with 24 pieces per case. Receive 5 cases and 6 pieces. The expected total is 5 × 24 + 6 = 126 pieces. Sell 9 loose pieces, leaving 117 pieces, which converts to 4 cases and 21 pieces. Then sell 1 full case, reducing stock by another 24 pieces and leaving 93 pieces, or 3 cases and 21 pieces. Next, record a realistic customer return and several damaged pieces, then calculate the expected balance again and compare it with the recorded quantity. Store a barcode and verify that the cashier can find the correct product, then confirm that the cashier still chooses the correct case or piece quantity. Ask the employees who will perform the real work to complete the test themselves. A workflow that works only when the owner operates it is not yet ready for everyday use.
Frequently asked questions about case-and-piece inventory
Can StockLedger record cases and loose pieces? Yes. Products can store pieces per case, and relevant inventory quantities can be entered and displayed in case-and-piece form. What is the conversion formula? Total pieces = cases × pieces per case + loose pieces. Can purchases and sales use case or piece quantities? Purchase receiving and sales can record case or piece quantities using the configured case size. Why can physical stock differ from software stock? Check the case size, opening quantity, purchase receiving, sales, returns, damaged stock, stock movements, and any late or missing entries. Does scanning a barcode automatically decide case or piece quantity? No. Barcode values help staff find the product; the user still needs to record the quantity that was actually sold or moved. Should a packaging change be ignored? No. Review the product setup whenever the real number of pieces per case changes.
Where StockLedger fits in case-and-piece stock control
Case-and-piece inventory becomes difficult when purchases are counted in cartons, counter sales are remembered in pieces, wholesale sales use mixed quantities, damaged goods are tracked separately, and physical counts are compared with another spreadsheet later. StockLedger provides a consistent quantity structure across the relevant purchase, inventory, sales, return, damage, and stock-movement workflows described above. The practical benefit is that one pieces-per-case relationship can be used when staff record different physical quantities during normal operations. Software still depends on correct product setup and complete transaction entry. It cannot repair an incorrect case size or automatically discover a movement that was never recorded. Before wider rollout, use your own products, real pack sizes, and actual staff to reproduce several normal transactions, then compare the recorded closing quantity with a physical count while the source documents are still easy to trace.
