Skip to content
Procurement & supply chainTextiles

Collection BOM straight into purchasing

The fabrics, yarns, trims and colours of a collection as demand per supplier, with minimum quantities and lead times checked.

Today

Collection BOMs live in spreadsheets, with many colour and size variants. Purchasing copies them over by hand, line by line. Minimum quantities get lost along the way, and material with long lead times only shows up when production is waiting.

An example

Fibrana is planning a collection of 38 fabrics for tarpaulins and sun protection, each in 4 colourways, made from PES dtex 1100 with a PU coating, 1,600 mm wide. The agent totals the demand for yarn and coating compound per supplier and rounds it to the spinning mills' minimum quantities. It flags two colourants whose lead time misses the February production start.
Fictional company, typical workflow.

Your data, wherever it lives

Collection BOMs sit today in product development's spreadsheets, with many colour and size variants, items and orders in the ERP, and suppliers' minimum quantities, terms and lead times in e-mails and PDF price lists. demi reads, understands and links them per material, colour and supplier, with your rights. Demand per supplier, with checked minimum quantities, is ready in hours instead of after days of retyping, long lead times stand out at once, and the buyer approves every order.

Where the data lives today

  • Office files
  • ERP
  • E-mails
  • PDFs
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from spreadsheets, ERP and e-mail. demi replaces nothing and links collection BOMs, colourways and sizes with articles, supplier conditions, minimum quantities and lead times; every material has one record. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Product development sees the collection, purchasing sees the conditions. Orders go into the ERP only once the buyer has approved them, and this is recorded.

  3. 3 · ActIntelligence Layer

    The agent explodes the BOM into material demand per colour and size by fixed rules, rounds to minimum quantities and pack sizes and groups the demand per supplier. It flags items that would miss the production start, with lead time and date.

How it runs

  1. 1

    Product development releases the collection BOM, in the spreadsheet as it is today.

  2. 2

    The agent matches every material to an ERP article and reports unknown ones.

  3. 3

    It calculates demand per colour and size and rounds to minimum quantities.

  4. 4

    It groups the demand per supplier and flags items with too long a lead time.

  5. 5

    The buyer reviews the order proposals, and demi writes back only after approval.

What changes

  • Complete orders, placed faster

  • Minimum quantities respected

  • Late items visible early

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+144 hfreed per year

Assumptions and calculation

demi turns the collection into demand per supplier with checked minimum quantities; you order.

30 min → 18 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

60 styles × 30 min × 40% × 1.0 (manual) × 12 months = 8,640 min = 144 h

Value per year, before demi costs

Freed per year+144 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€9,360

gained per year

144 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Can demi handle colour and size variants?

Yes. The agent breaks every article down into its colourways and sizes and calculates material demand per variant, using the consumption and allowance from the BOM. It combines the same material from different articles into one demand.

Does it take minimum quantities and pack sizes into account?

Yes, as they are recorded in the ERP or in the supplier conditions. The agent rounds up by fixed rules and shows how much surplus that creates. If the surplus is too large, the buyer decides whether to group differently, swap a material or drop the item.

Does the agent write orders back without approval?

Only after approval. The agent creates order proposals per supplier and the buyer reviews and approves them. demi writes back only after approval. Who approved what is recorded.

Do we have to rebuild our BOM spreadsheets?

No. demi reads the spreadsheets in the form your product development uses today. The agent asks once about unclear columns or materials without an article number and remembers the answer.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases