Purchasing may order cartons while warehouse staff count pieces and sales teams sell packs. A quantity without its unit is incomplete. Agree the conversion model before importing products or connecting an order channel to stock.
Related service: CRM, ERP and web application development- 01Identify the item and base unit.
- 02Define allowed packs and conversions.
- 03Record entered and converted quantities.
- 04Check rounding and partial units.
- 05Reconcile transactions in the same unit.
SECTION 01
Distinguish a physical unit from a product pack
Kilograms and grams have a standard relationship; a carton can contain different quantities for different products. Define whether the conversion is universal, item-specific or variant-specific. Microsoft's unit documentation illustrates these distinctions as a reference, not a recommendation that you adopt a particular ERP or a claim of platform partnership.
Ask how partial quantities behave. Can staff receive half a carton, or must they enter individual units? Which precision is allowed for measurement-based stock? Do not fix a rounding difference by quietly changing the requested quantity. Give users the original amount, converted amount and reason for rejection when a combination is not permitted.
SECTION 02
Illustrative example: a supplier changes its carton size
Imagine an item previously arrived in cartons of twelve, but the supplier begins shipping cartons of ten. An open purchase order still refers to the old pack. Updating a single global conversion would change the apparent meaning of that order. This is a hypothetical stock-modeling example.
Create an effective new packaging definition and preserve the old order's conversion. Staff receiving the shipment confirm which pack actually arrived. Any difference becomes a receiving exception for review. An inventory report can still show a consistent piece count while purchasing sees the original carton quantities and the conversion applied to each receipt.
SECTION 03
Test the interfaces where units change
Begin with a small item family and the units genuinely used today. Existing inventory software may already support these conversions; configure and test it before building a substitute. Custom screens should make the units clearer, not hide an inconsistent stock model behind a convenient number field.
Ask the agency to demonstrate a changed pack, a partial receipt, a return, an invalid fractional unit and repeated conversions. Reconcile both the entered quantities and the base-unit movements. Database constraints can reject invalid references or values, while business tests establish whether a permitted conversion is correct. Include unit labels in exports and APIs so the next system does not mistake cartons for pieces.
SECTION 04
Frequently asked questions
Can every item use the same carton conversion?
Only if the physical contents truly match. Most pack quantities need an item-specific definition rather than a universal carton multiplier.
Should old orders use a new conversion?
Not silently. Preserve the conversion tied to the original transaction and review any real change through the receiving or order-change process.
Why include units in API data?
A quantity alone is ambiguous. Send the item, unit and agreed conversion context so the destination can interpret and reconcile it.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Units of measure and conversionsMicrosoft Learn
- Database constraintsPostgreSQL
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy