Buy by the carton, sell by the item: prepare product units for ERP
Matching product names can hide different stock quantities
Businesses buying by the carton and selling individual items must agree on what quantities mean before connecting data to ERP. If a quantity field sends only 2 without a unit, the recipient cannot tell whether it means two cartons or two items. This differs from a duplicate transaction: even one successful submission can record the wrong quantity. Establish shared product definitions before testing purchasing, sales and warehouse operations.
Identify the product before defining its units
List product codes, names, separately sold models or sizes, and the units each team actually uses. Do not merge products into one code simply because their names resemble each other. Microsoft describes product information as including identifiers, descriptions, attributes, units and conversions. This helps frame questions about the chosen system; it does not mean all software has the same structure or that the business must use a particular product.
Make the conversion a rule for the actual product
In a hypothetical example, one carton of product A contains 12 items. Receiving two cartons means 24 items; selling 5 with no other movements leaves 19. This calculation applies only if that pack size is correct. Another product or a new pack version may contain a different quantity per carton. Do not define carton as 12 items for every product. Have the product owner confirm the actual conversion and always show units on documents.
Assign change ownership and check historical effects
Agree on who requests a code, checks units, approves conversions and maintains the authoritative source system. If pack size changes, ask how a new code or version will be used and whether historical transactions will retain their original meaning. Do not overwrite a conversion simply to reconcile today's stock without checking past effects. Products with fractional units also need rounding rules and a check that operations support them. Microsoft's guide identifies conversion rules and decimal precision as settings requiring definition.
Test movements from receipt through returns
Use sample data to test receipt by carton, sale by item, partial returns and a different pack size. Have sales, warehouse and accounting staff compare the same quantities with their units, rather than only report totals that may use different units. In the example above, if 2 of the sold items are returned and fully accepted back into stock, the balance becomes 21 items. Record expected and actual outcomes, including the system's return-approval process.
Start with a small table that can be checked
Choose representative products with unit problems and prepare a table of codes, purchase units, sales units, stock units, conversions and approving owners. Use it to discuss accounting, ERP and business-system services with Chawinnix. Real customer databases are not necessary for an initial discussion. Ask acceptance criteria to cover unit display, conversion and change history. Complete product codes do not replace checking that quantities mean the same thing in every process.
