4 ms·
for the supplier problem, we just use a typeahead/combobox component. but for raw materials, we auto-generate the ids like this: https://x.com/barbinbrad/statu
by barbinbrad 1y ago
for the supplier problem, we just use a typeahead/combobox component.
but for raw materials, we auto-generate the ids like this: https://x.com/barbinbrad/status/1947682873416221184 https://x.com/barbinbrad/status/1947682873416221184
also working on some agents: https://x.com/barbinbrad/status/1903047303180464586 https://x.com/barbinbrad/status/1903047303180464586
would love to talk, i'm brad@carbon.ms
- mfrye0 1y agoNice! Yeah, a typeahead works to a degree. I imagine that's searching their own instance vs calling out to a standardized DB you manage? Raw materials is definitely a different animal, so auto-generating definitely works. I know a company where that's all they do - they manually pour over supplier specs to get all the model names. Agent approach looks super cool. I see the supplier search piece happening there. We've mapped out ~265M+ businesses globally. We're thinking about this as a data infra angle where products can tap into our system to access all the world's businesses. We're getting requests for processing millions of ERP records to clean/standardize, plus semantic supplier search across our full dataset. I'll shoot you an email to chat more.
- barbinbrad 1y agothanks! look forward to talking to you
- daedrdev 1y agoThis is interesting but what about non standard items? There are plenty of cases where the raw material might theoretically have the same name, but was made with a different process by each manufacturer or the resulting item from different manufacturers has slightly diverged for various reasons.
- barbinbrad 1y agofor that we use "batch" tracking with batch properties