How to track product costs from multiple seasonal suppliers
Sourcing the same item from different seasonal suppliers causes product costs to fluctuate constantly. These continuous shifts disrupt unit economics month to month, which can ultimately force founders to pull the plug on their products entirely.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Tracking each vendor's cost separately or using an average costDid this help you?
- 2moving to usage-based or credit pricing instead of flat monthly feesDid this help you?
- 3routing the majority of requests to cheaper models and only calling expensive ones when necessaryDid this help you?
- 4hosting open-source models locally with caching and optimization layers in frontDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Worked on an AI product where the co-founder pulled the plug because token costs and API changes kept shifting the unit economics every month.”source ↗
“How do you guys handle product costs when you're sourcing the same item from different suppliers and the price changes seasonally?”source ↗
Where this came up
People with this problem also raised
- 11How to stay competitive when wholesale food suppliers merge
- 5How to follow up with a client who picked a cheaper vendor
- 16Why can't I just see the price of software without a sales call?
- 3How do you handle constant tariff changes messing up your supply chain?
- 62How to handle unexpected software subscription price hikes and slow support
- 3Why did my competitor change their prices?