Global BOM Import: How to Update Pricing Across Hundreds of Jewelry SKUs in One CSV

The problem with pricing one project at a time

If you've ever had to update gem rates across a whole collection, you know the drill. Open a project, open its pricing panel, re-enter the metal weight, re-enter every stone spec, save, close, repeat. Do that fifty or a hundred times and you've burned an entire afternoon on data entry instead of design work.

It gets worse when the change isn't really about one project at all. Your gold rate moves. Your diamond supplier updates a price list. Suddenly every SKU with 14k gold or a certain diamond clarity needs a new number, and there's no fast way to touch all of them at once without opening each one individually.

Studio just shipped a fix for exactly this, and it's called Global BOM Import.

What Global BOM Import actually does

Instead of importing a Bill of Materials CSV into a single project (which you could already do), Global BOM Import lets you upload one CSV that contains pricing rows for many SKUs at once. Studio reads the file, groups the rows by SKU, matches each group to the right project in your library, and applies all the pricing updates in a single submission.

You're not clicking into each project anymore. You're not re-typing metal weights or stone specs project by project. You upload one file, and the BOM import does the matching and the writing for you.

When it's done, you get a summary: how many projects were updated, and which SKUs (if any) didn't find a match in your library. That last part matters more than it sounds like it should: it means you're never left wondering whether a row silently failed to apply. If a SKU in your CSV doesn't correspond to an existing project, Studio tells you so you can go fix the typo or create the missing project, instead of assuming everything went through.

Getting your BOM import CSV right

The importer expects the same kind of data as a single-project BOM import: metal rows, stone rows, and extra-charge rows, just grouped under a SKU column so Studio knows which project each row belongs to.

There's a downloadable CSV template built for this specifically, and it's worth actually using it rather than building your own from scratch. Column order and naming matter for the parser, and starting from the template means you skip the round of trial and error that comes from guessing at header names.

A few things that make the import go smoothly:

• Keep one SKU per group of rows, with metal, stone, and extra-charge lines clearly attached to it
• Double check that the SKU in your CSV matches the SKU on the project exactly, including case and any leading zeros
• Run a smaller batch first if you're touching hundreds of SKUs for the first time, just to confirm the format is doing what you expect

Where this saves the most time

This isn't a feature you'll use every day, but when you need it, you really need it. A few situations where bulk BOM import earns its keep:

Gem rate changes that ripple across a catalog. Your Price Book updates for a stone category, and instead of manually revisiting every affected project, you export current data, adjust the relevant column, and re-import.

Onboarding a wholesale catalog. If you're bringing an existing collection of designs into Studio and you already have pricing data in a spreadsheet from your old system, you don't have to type it in one project at a time. Format it to match the template and bring it in as one batch.

Correcting a pricing mistake at scale. If a metal weight was entered wrong across a whole product line, fixing it project by project multiplies a small mistake into a big time cost. One corrected CSV fixes all of them together.

A few things worth knowing

Global BOM Import updates pricing fields, not the design images or descriptions themselves, so it's safe to run without touching anything else about your projects. It also respects the same manually-confirmed pricing logic as the rest of Studio: once you've verified pricing on a project, that confirmed data carries forward as context for future AI generations on it, the same way it would if you'd entered it by hand.

If you manage pricing for more than a handful of SKUs, this is worth trying the next time a rate changes. Pull the template from the Global BOM Import page, fill in your current data, and see how much of that manual re-entry disappears in one upload.