[GH-ISSUE #452] [Feature]: Add per-filament cost tracking #282

Closed
opened 2026-05-06 12:27:53 +02:00 by BreizhHardware · 2 comments

Originally created by @Keybored02 on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/452

Originally assigned to: @Keybored02 on GitHub.

Problem or Use Case

The current cost analysis for filament is limited to a single global value. Since usage is already logged, it is not excessively complex to add cost tracking. This would benefit in case of multi-material and varying material costs.

Proposed Solution

This feature would:

  1. Add a Cost Field to Each Spool
  2. Link Filament Usage to Cost: When tracking filament usage (already implemented), fetch the associated spool’s cost field. Calculate the cost for each print/job by multiplying the used amount by the spool’s cost.
  3. Store and Collect Usage Costs: Store each usage event with its calculated cost, either in a dedicated usage log table/model or as part of the print/job record. Ensure this data is accessible for later aggregation.
  4. Display Cost Data: Add API endpoints to fetch cost summaries, per-spool costs, or usage history.
    Update frontend components to display cost information, e.g., pre-print card/job history, statistics dashboards.

This feature is for the internal spool tracker only. How to actually display the data is not definitive yet.

I can contribute this. Please let me know if you would like me to wait for this.

Alternatives Considered

No response

Feature Category

Monitoring & Stats

Priority

Would improve my workflow

Mockups or Examples

No response

Contribution

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
Originally created by @Keybored02 on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/452 Originally assigned to: @Keybored02 on GitHub. ### Problem or Use Case The current cost analysis for filament is limited to a single global value. Since usage is already logged, it is not excessively complex to add cost tracking. This would benefit in case of multi-material and varying material costs. ### Proposed Solution This feature would: 1. **Add a Cost Field to Each Spool** 2. **Link Filament Usage to Cost**: When tracking filament usage (already implemented), fetch the associated spool’s cost field. Calculate the cost for each print/job by multiplying the used amount by the spool’s cost. 3. **Store and Collect Usage Costs**: Store each usage event with its calculated cost, either in a dedicated usage log table/model or as part of the print/job record. Ensure this data is accessible for later aggregation. 4. **Display Cost Data**: Add API endpoints to fetch cost summaries, per-spool costs, or usage history. Update frontend components to display cost information, e.g., pre-print card/job history, statistics dashboards. This feature is for the internal spool tracker only. How to actually display the data is not definitive yet. I can contribute this. Please let me know if you would like me to wait for this. ### Alternatives Considered _No response_ ### Feature Category Monitoring & Stats ### Priority Would improve my workflow ### Mockups or Examples _No response_ ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-06 12:27:53 +02:00
Author
Owner

@maziggy commented on GitHub (Feb 19, 2026):

https://github.com/maziggy/bambuddy/pull/454

<!-- gh-comment-id:3928092500 --> @maziggy commented on GitHub (Feb 19, 2026): https://github.com/maziggy/bambuddy/pull/454
Author
Owner

@Keybored02 commented on GitHub (Feb 20, 2026):

Merged

<!-- gh-comment-id:3936225291 --> @Keybored02 commented on GitHub (Feb 20, 2026): Merged
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#282
No description provided.