Technical Product Data · BOM · Options · Configuration · Pricing · Publishing
One-Line Description
A structured product-information and configuration platform linking technical specifications, BOM, product options, development data, pricing, catalogs, and website publishing.
Core Purpose
Industrial products cannot be represented only by:
Name
Price
The platform therefore modeled products with technical depth.
Historical product screens show structured specifications such as:
- machine dimensions,
- spindle,
- tool-change capability,
- lubrication,
- remote control,
- technical options,
- images,
- detailed descriptions.
Product Master
The product record acted as the central product definition.
Conceptually:
Product
├── Identity
├── Technical Specifications
├── Images
├── Files
├── Options
├── BOM
├── Pricing
├── Design
├── Development
└── Production Definition
Bill of Materials
The BOM represented the components required for a product.
Product
↓
BOM
↓
Components
↓
Required Quantities
Historical screenshots show BOM lists and quantities.
BOM and Downstream Operations
The BOM was not isolated.
It affected:
- pricing,
- inventory requirements,
- procurement,
- custom configuration,
- production planning.
Product Configuration
The platform supported product-specific options.
A product for one customer could differ from the standard model.
Potential configurable dimensions included:
- dimensions,
- optional components,
- technical options,
- custom parts.
Customized BOM
Once a customer-specific configuration was finalized, the resulting BOM could differ from the standard BOM.
Conceptually:
Standard Product BOM
+
Customer Options
+
Custom Changes
=
Contract-Specific BOM
BOM Immutability After Contract
A strong business rule is:
Once a contract is finalized, the BOM attached to that contract should remain traceable and should not silently change when the master product changes.
Modern design:
Master BOM
↓
Contract Snapshot
↓
Production BOM
Pricing
The product module supported pricing logic rather than a single static price.
Historical development evidence indicates work around:
- price forms,
- online pricing,
- quotation-related pricing,
- configurable product values.
Price List
A price list can include:
- base price,
- options,
- custom development,
- currency,
- effective date.
Technical Media
The commercial team could access files used to introduce products.
Examples:
- images,
- catalogs,
- technical documents,
- presentation files,
- development drawings.
Web Publishing Integration
One of the strongest features was connection between internal product data and external websites.
Conceptually:
Internal Product Master
↓
Publishing / Sync Layer
┌─────────┴─────────┐
▼ ▼
Company Website Representative Websites
The objective was to avoid entering product data repeatedly.
WordPress Integration
The platform could be connected to WordPress-based company or representative sites.
Potential synchronized content included:
- products,
- articles,
- galleries,
- product information.
Single Source of Truth
This turns the product module into a PIM-like system.
Internal Product Record
↓
Single Source of Truth
↓
Web / Sales / Catalog / CRM
V2 Architecture
Recommended entities:
Product
ProductVersion
ProductSpecification
ProductOption
BOM
BOMItem
PriceList
PriceRule
MediaAsset
PublicationChannel
PublicationJob
Career Evidence
- product information management,
- BOM modeling,
- configuration,
- technical master data,
- pricing,
- product lifecycle integration,
- website publishing,
- single-source-of-truth architecture.
Suggested Slug
/projects/product-bom-pricing-platform
Cover Direction
Product Master, BOM & Pricing
Visual elements:
- industrial machine,
- BOM tree,
- option configuration,
- price calculator,
- technical drawings,
- website sync.