Why it is a separate MicroERP
A product-information product serves multiple inventory and commerce systems; it owns descriptive identities, not their stock balances.
InventoryReviewed functional scope
Product Information MicroERP
Approved, consistent item/variant/compatibility catalogue
Who it helpsCatalogue / merchandising master-data steward
FROM A REAL REQUEST TO A USEFUL RESULT
The working flow.
New sellable/operating item, variant or catalogue change
- 01
Capture canonical item/attributes
- 02
verify variants/compatibility/units
- 03
approve assortment
- 04
publish identifiers/reference changes
The useful outcome
Approved, consistent item/variant/compatibility catalogue
ALL FEATURES IN THEIR OWNING PRODUCT10 feature modules.
10 feature modules.
One product scope.
Open each module to review its purpose and actions. These features belong inside Product Information MicroERP.
01Part Supersession & Interchange3 scoped actions
Handle replacement part numbers without losing compatibility evidence.
- Maintain manufacturer supersession chains
- Distinguish confirmed from proposed interchange
- Preserve original order and supplied part references
02Vehicle-to-Part Fitment3 scoped actions
Identify compatible parts for a specific vehicle configuration.
- Match vehicle variant to approved catalogue data
- Compare OE and aftermarket references
- Record fitment exceptions and selected alternatives
03Electronics Compatibility Catalogue3 scoped actions
Avoid selling accessories incompatible with the selected device.
- Model compatibility
- Connector and specification attributes
- Approved accessory bundles
04Operating Item Catalogue4 scoped actions
Identify purchased inputs, spare parts and consumables used in business operations.
- Item identifiers categories and specifications
- Approved-use and blocked-item states
- Supplier item references and handling requirements
- Lot expiry or serial-tracking designation
05Parts Catalogue & Attribute Normalization3 scoped actions
Make supplier parts identifiable and comparable.
- Maintain brand, part number and specifications
- Normalize units and cross-references
- Resolve duplicate or conflicting catalogue records
06Pack & Unit Breakup3 scoped actions
Sell and stock parts in approved packaging units.
- Define piece, pack and carton conversions
- Track opened-pack balances
- Prevent quantity and price conversion errors
07Store Assortment3 scoped actions
Control which products a store or channel carries.
- Range inclusion rules
- New-item launch dates
- Delisting and runout plans
08Product Variants3 scoped actions
Distinguish stock and prices for actual product combinations.
- Attribute combinations
- Variant-specific identifiers
- Variant availability rules
09SKU Catalogue3 scoped actions
Maintain the sellable item reference used by stock and orders.
- Item identifiers and categories
- Sellable and blocked states
- Product attributes and images
10Units & Pack Conversion3 scoped actions
Reconcile purchasing, storage and selling quantities.
- Base and alternate units
- Case-to-unit conversion
- Conversion rounding checks
CLEAR OWNERSHIP. CONNECTED FUNCTIONS.
How the scope fits together.
Dependencies to plan
- Shared organization/reference data
- Publication/integration primitive
Outside this scope
- Vehicle/parts compatibility assertions retain confirmed/proposed evidence; catalogue changes do not edit accepted order lines.
REUSE THE SAME PRODUCT
Mapped to your industry.
Industry compositions select relevant products and modules. Some options apply only under particular operating conditions; review the industry page before choosing.
Start with this scope.
Confirm your workflows, required integrations, team access, migration and acceptance checks in one implementation brief.