Receiving boxes should add the right number of units

An inventory receipt needs a quantity and a unit. If staff buy products by the box but sell them individually, the software should make that conversion visible before the receipt changes stock.

Consider a hypothetical item with twelve units in each supplier box. Receiving two full boxes adds twenty-four individual units, not two. Starting from zero, with no other movements, selling five leaves nineteen. A receipt that records only "2" cannot explain that sequence.

Define the conversion for each product

Microsoft's Business Central documentation separates an item's base inventory unit from alternate purchase, production and sales units. The alternate unit specifies how much of the base unit it contains.[1]

Odoo 19 documents a similar distinction: a purchase quantity can use one unit while the warehouse receipt shows the converted inventory quantity.[2]

For your own system, agree which unit staff count, how the supplier packs the product and which conversion applies. Avoid one blanket rule for "box." Odoo's packaging guidance makes its pack definitions product-specific, rather than generic.[4]

Show what the scan will add

A barcode can identify a configured pack, not just the product. Odoo describes receiving with a packaging barcode that adds the pack's unit quantity to the internal product count.[4]

Ask your developer to demonstrate what a product scan means and what a pack scan means. Before posting, the receiver should see the entered quantity, its unit and the resulting stock quantity. In the example, that means "2 boxes," "12 units per box" and "24 units."

If a label is unknown or the pack size has not been agreed, route the receipt for review rather than silently applying a default. A readable number on a scanner screen is not enough if nobody knows what it counts.

Keep partial packs and changes explicit

Microsoft also documents rounding problems when a receipt uses a fraction of an alternate unit. Its quantity-rounding setting addresses that issue in Business Central.[1]

For a custom system, agree how staff record loose units or a short box. An item sold as a whole piece should not acquire an unexplained fractional balance through conversion. Products measured by weight or length need their own precision rules.

If a supplier changes the pack size, decide how to identify the new pack and retain the conversion used on earlier receipts. Ask for a demonstration that updating today's product setup does not recalculate yesterday's posted quantity.

Test the receipt before sign-off

Use a small agreed example:

• Receive two boxes of twelve. The posted movement adds twenty-four units.
• Sell five individual units. With no other movements, the balance is nineteen.
• Receive a short box. Record the actual units received and keep the discrepancy visible.
• Change a pack definition. Earlier posted receipts retain their recorded quantities.

Rootscratch's Inventory & Warehouse Management Systems service covers purchase receiving and stock-movement records. Barcode hardware and accounting integration need explicit scope.[3]

Bring a supplier label, a receiving form and one example of how your team counts the item. Those details belong in the brief before anyone designs the stock dashboard.

Sources

[1] https://learn.microsoft.com/en-us/dynamics365/business-central/inventory-how-setup-units-of-measure [2] https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/product_management/configure/uom.html [3] https://rootscratch.com/services/inventory-warehouse-management [4] https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/product_management/configure/packaging.html