Notes: BoM, Combos, Variations #374

New Issue

2026-06-29T08:37:58Z

rob commented

2026-06-29 08:37:58 +00:00

This is a just a Tim-brain-dump, and can be safely ignored by anyone who isn't Tim, at least for now.

We have several similar, but possibly different concepts, that we should try to harmonize:

Combos
- A basket of items sold for a single price.
- Can be constructed at pick-time.
- How to attribute revenue to individual component SKUs?
  - Pricing might vary by channel
  - Percentages?
- Can have virtual stock.
BoM (Bill of Materials)
- Similar to combos, but requires manufacturing
  - Inputs are consumed resulting in finished goods
  - Informs CoGS for finished product, based on actual consumption at factory (#140)
  - Unlike Combos, no virtual stock
- Revenue is attributed directly to the finished good.
- Possible tie-in to suppliers (factories) to track things
  - Capabilities (which suppliers can produce the finished good)
  - Performance
    - On-time delivery
    - Waste
    - Quality score?
  - Possible need to model a manufacturing job/run?
  - While not particularly relevant to Zeneroe, what about in-house manufacturing?
    - Build-to-Stock vs. Build-to-Order?
      - Is BtO just combos? Maybe, but consider complications from build-time, labor, etc.

It's tempting to share some code between BoM and Combos, but this should be thought about carefully.

Variations
- Less related, but similar to the others.
- Things come in different sizes/colors/etc.
- Ability to use existing SKU as a template for a new one. (#135)
- VariationSet entity should ideally support unlimited, and arbitrary, dimensions (ex: baseball-shirt with body color + sleeve color + size + number printed on back + size is 4 dimensions)

This is a just a Tim-brain-dump, and can be safely ignored by anyone who isn't Tim, at least for now. We have several similar, but possibly different concepts, that we should try to harmonize: * Combos * A basket of items sold for a single price. * Can be constructed at pick-time. * How to attribute revenue to individual component SKUs? * Pricing might vary by channel * Percentages? * Can have virtual stock. * BoM (Bill of Materials) * Similar to combos, but requires manufacturing * Inputs are consumed resulting in finished goods * Informs CoGS for finished product, based on actual consumption at factory (#140) * Unlike Combos, no virtual stock * Revenue is attributed directly to the finished good. * Possible tie-in to suppliers (factories) to track things * Capabilities (which suppliers can produce the finished good) * Performance * On-time delivery * Waste * Quality score? * Possible need to model a manufacturing job/run? * While not particularly relevant to Zeneroe, what about in-house manufacturing? * Build-to-Stock vs. Build-to-Order? * Is BtO just combos? Maybe, but consider complications from build-time, labor, etc. It's tempting to share some code between BoM and Combos, but this should be thought about carefully. --- * Variations * Less related, but similar to the others. * Things come in different sizes/colors/etc. * Ability to use existing SKU as a template for a new one. (#135) * VariationSet entity should ideally support unlimited, and arbitrary, dimensions (ex: baseball-shirt with body color + sleeve color + size + number printed on back + size is 4 dimensions)

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#374