What is a unit?
A way of selling the same underlying product quantity, such as carton, pack, or piece.
Units and product intelligence
Sell cartons, packs, pieces, sizes, and colours without mixing up what you actually have.
“We buy in cartons and sell in pieces.” The hard part starts when some sizes can use one pack, other colours cannot, prices differ, and stock is spread across locations. IGFirstERP keeps units, variants, and repacking as separate operating concepts.
A carton is not a colour. A pack is not a size. Repacking one product into another is not the same as selling the same product in a larger or smaller unit.
Published 2026-07-11 · Verified 2026-07-11 · Editorial policy
Decision points before a demo
What the owner needs to know
What is a variant?
A distinct option such as size or colour that may have its own SKU, stock, unit availability, and prices.
What is repacking?
A controlled conversion where source stock becomes a different saleable product, with a mapping and movement trail.
Best fit
- Wholesalers and retailers buying large units and selling smaller units.
- Fashion, beauty, health-product, food, and distribution businesses with variant-specific rules.
- Multi-location teams that need the product list to show only the detail relevant to their setup.
Probably not fit yet
- An operator who has not defined conversion quantities or product identities.
- Using unit conversion to hide wastage created during repacking.
- Treating sizes or colours as interchangeable stock when they are not.
Why it returns
One flat unit field cannot describe a real wholesale or variant operation
When cartons, packs, pieces, sizes, and colours are placed in the same field, staff improvise. The system may show a number while the business cannot explain what the number means.
- Define conversion relationships once.
- Keep variation stock and price rules distinct.
- Apply the correct unit rules at the right location.
What IGFirstERP controls
Separate conversion from variation and product transformation
IGFirstERP supports product-level and variation-level unit rules, separate unit prices, conversion controls, location stock, and repack mappings when source stock becomes another product.
- A variation can allow only the units that make sense for it.
- Prices can follow the relevant product, variation, and unit.
- Repacking retains a source-to-output mapping instead of pretending it was a sale.
Operator clarity
The product list adapts to the complexity that actually exists
A one-location simple product does not need the same explanation as a multi-location product with many variants and units. The list surface prioritises the stock, location, unit, and variation detail relevant to the record.
- Reduce noise for simpler products.
- Expose location and variation distribution when complexity exists.
- Keep unit summaries close to the stock people act on.
Demonstration workflow · not customer data
Set up one wholesale product correctly
Demonstration data: a beverage sold as carton, pack, and piece with two variants across two locations.
Define the product
Create the product, variants, SKUs, and trusted base unit.
Add unit rules
Set carton, pack, and piece conversions and the variants allowed to use them.
Set prices and locations
Assign supported unit prices and review where each variant is stocked.
Test a sale or repack
Confirm conversion integrity and use a repack mapping only when product identity changes.
What the owner can verify
- Unit conversion values are defined and consistent.
- Variant-specific units and prices do not leak into unrelated variants.
- Location stock and repack movements remain traceable.
When the happy path fails
- Invalid or stale unit selections are normalised or removed from the supported configuration.
- A product correction path protects SKU and product-name integrity.
- Repack exceptions remain reviewable rather than silently changing source stock.
Explicit limitations
What this page does not promise
- The system cannot decide undefined commercial conversion rules for the business.
- Physical wastage and yield still require honest operator records.
- Unit support depends on correct setup, permissions, and adoption.
Operational proof, not vanity claims
These proof assets show what became visible, traceable, faster, or easier to review after IGFirstERP was implemented. Named customer metrics are used only where permission has been granted. Results vary by operating discipline, data quality, implementation scope, and adoption.
Proof library
Named customer evidence
Review what became traceable, visible, or easier to control, with limitations stated.
Methodology
How claims are governed
See the evidence, permission, review-date, and limitation rules behind public claims.
Product
Walk through the operating system
See how stock, sales, staff, storefronts, and reporting connect.
Pain-answer hub
Start from the problem
Find the repeated stock-control problem your team is still rebuilding by hand.
Academy
Operator education
Use practical lessons to strengthen the process around the system.
Documentation
Product guides and SOPs
Review the current operating instructions for IGFirstERP workflows.
Questions serious buyers ask
Is a carton a product variation?
Usually no. A carton is a selling or purchasing unit of the same product. Size or colour is a variation that can have its own stock and SKU.
Can different variants allow different units and prices?
Yes. Supported unit availability and prices can be scoped so a variation only presents the units that make sense for it.
When should I use repacking instead of unit conversion?
Use repacking when source stock becomes a different saleable product. Use unit conversion when it remains the same product expressed in a larger or smaller unit.
Operations Fit Call
Choose the path that fits your operation
Use Find my plan when the workflow is clear. Book an Operations Fit Call when branches, warehouses, integrations, migration, permissions, or reporting need to be mapped first.
Book an Operations Fit Call