Your BOM, turned into the Material Summary List your customer already uses.

Upload a Bill of Materials, confirm which column is which, and get back an MSL in your customer's own template — same layout, same merged cells, same look, just filled in correctly.

Try it now → See how it works

Right now, someone on your team retypes every part number, material, and TC number by hand into your customer's Excel template — column by column, job after job.

Four steps, no retyping.

Each BOM goes through the same short wizard — you check the machine's work before anything downloads.

  1. 01

    Upload

    Drop in the BOM as it came from your customer — Excel or PDF today, no reformatting first. Different format? We customize per request.

  2. 02

    Confirm columns

    Every column is matched to a field. Exact matches are pre-ticked; guesses are shown unticked, for you to approve.

  3. 03

    Pick the format

    Choose your product's MSL layout — already confirmed against real completed jobs.

  4. 04

    Download

    Get back the finished MSL, styled exactly like the one you'd have built by hand.

Already confirmed against real jobs.

Every layout below was built and checked against completed dossiers before it shipped — not a generic best guess.

Droplet Standard MSL layout.
Skid Bought-out items, read from the SO/FO list PDF — plus a separate raw-materials scope.
Roll Cooling Headers Two real layouts exist — SAP number or drawing number — you pick the one your customer uses.
Descaling Headers Handles multi-assembly BOMs without leaving stale rows behind.

Not a generic export.

Three things this does differently from a plain BOM-to-Excel converter.

01

Your exact template comes back

The output preserves your customer's real MSL file — its merges, styling, and layout — not a fresh sheet built from scratch.

02

You approve every guess

A guessed column mapping is shown unticked, never applied silently. You decide what feeds a traceability document.

03

No duplicate or stale rows

A smaller BOM than the last job won't leave old rows or leftover dividers behind in the output.

Where your BOM actually goes.

The question every QC lead asks before a real document goes anywhere — answered here, not buried in a policy PDF.

01

No AI ever reads your document

Column mapping and MSL generation run on fixed, auditable rules, not a language model. Your BOM is never sent to any third-party AI provider.

02

Nothing is kept after you download

Your file and the generated MSL exist only for your session. Nothing is written to a database, and nothing survives after you leave.

03

Never shared, never reused

Your BOM and template are used only to build your own MSL — never shown to another customer, never used to train anything.

Read the full privacy policy →

Built from the paperwork, not around it.

This came out of doing the job by hand — retyping the same Bill of Materials into a customer's fixed Material Summary List template, column by column, job after job, in a real fabrication shop's QC documentation.

It automates the retyping, not the judgment. Every column mapping is shown to you before anything downloads, and every output layout was checked against real completed jobs before it shipped.

This is an independent, early build — not a funded product — and it gets better with real BOMs from real jobs. If you try it, tell us what broke.

Contact.

Questions, a BOM that didn't map right, or a format/layout we don't support yet — write in. Output comes back in whatever format you need — same as what you uploaded, or a different one on request.

GET IN TOUCH

Try it with your own BOM.

This is an early build — if a column mapping looks wrong or a layout doesn't match your customer's MSL, tell us and we'll fix it.

Try it now → Send feedback