BRICKPULSE

Collecting

Prepare a LEGO set-inventory CSV that is ready to review

A small, normalized CSV can save retyping when you have several set copies to add. Use the exact two-column format, preview the whole batch, fix every problem, and confirm only when the resulting set copies look right.

01 · prepare the source

Use two columns and keep their names exact.

Brick Pulse's normalized set import expects a header named set_number,quantity. Each following row has a catalog set number and a positive whole-number quantity. This is the collector set-copy format, not a parts list and not a vendor or marketplace export.

Exact headerset_number,quantityKeep the comma between the two column names. Do not add a third column.

The current intake screen displays its applicable row and file-size limits beside the CSV input. Use those limits as the source of truth for the version you are using; this guide does not prescribe an encoding or a universal file-size number.

  • Use a set number that the current catalog can resolve.
  • Use a positive whole number for copies; leave blank, fractional, and zero quantities out.
  • Keep notes, prices, part numbers, condition, and locations in their own workflows.
  • Remove names, account data, order data, and other private fields before preparing a file.

02 · working example

Download a two-row file you can inspect before importing.

This synthetic example uses the locally verified catalog fixture 75192-1 and synthetic quantities. The repeated number is intentional: the preview should combine the two lines into one normalized row for three copies and show which source line was combined.

Download the working CSV example

set_number,quantity
75192-1,1
75192-1,2

If you want one row per set number in your own source file, combine those quantities before saving it. Keeping the duplicate rows is also useful for learning how the preview reports normalization.

03 · repeated set numbers

Read duplicates as a normalization result, not a second copy of the batch.

When the same valid set number appears more than once, Brick Pulse combines the quantities in the preview and shows the original line numbers. In the example above, lines 2 and 3 become one row for three copies. Check that total before confirming; do not assume repeated lines will create separate set records.

Source lines75192-1,1
75192-1,2
Preview row75192-1 · 3 copies
Review clueCombined duplicate lines 2, 3

A repeated number with an invalid quantity does not become a valid copy count by proximity. Fix the source row, save it, and build a fresh preview.

04 · validate before changing anything

Preview the whole file before you decide.

  1. Open Add set instances and choose Normalized CSV.
  2. Choose the CSV file or paste its contents, then select Preview batch.
  3. Read every row, including the catalog name or the problem shown for that line.
  4. Correct the source file and preview again if any row is unclear or invalid.

The preview can identify a wrong header, wrong column count, malformed CSV, blank row, invalid set number, invalid quantity, an unknown catalog set, or a row-limit problem. Treat those as source-file issues to resolve rather than evidence that a partial import succeeded.

Whole-batch boundaryIf any row is invalid, confirmation stays disabled and no partial batch is created. Fix the file and preview the complete batch again.

05 · check the cap

Review current usage and the batch overage together.

The preview reports current set-list usage, the applicable cap, and any amount by which this batch would exceed it. A cap refusal is whole-batch: nothing from that preview is confirmed. Remove or reduce rows, or use the account's current capacity path, then build a new preview.

A list cap counts set instances, not the number of LEGO parts inside each set. Adding three copies creates three set-copy records. It does not automatically create loose physical parts, part lots, or a parts inventory from the set contents.

Barcode lookup and source-native vendor schemas are not part of this normalized CSV workflow. Do not rename another tool's columns and assume they have been approved or mapped.

06 · confirm deliberately

Confirm only the batch you just reviewed.

Before selecting the confirmation action, compare the normalized rows, copy totals, catalog names, duplicate notes, errors, and capacity message with your source file. Confirmation creates the complete local set-copy batch or none of it. It does not contact a marketplace, change a listing, or claim that the physical boxes or loose parts have been counted.

  1. Keep the preview open while you check the resulting copy count.
  2. Confirm only after every row is valid and the cap message is acceptable.
  3. Inspect the created set copies and their chosen defaults after confirmation.
  4. If a response is interrupted, retry the same unchanged confirmation rather than changing the file mid-retry.

The local flow uses a preview digest and repeat-safe confirmation. That is a workflow safety boundary, not a promise of automatic reconciliation, marketplace synchronization, or guaranteed catalog completeness.

07 · related reading

Keep set copies and loose inventory in their proper records.

Collector records explain the set-copy context. Organize parts and keep an inventory covers physical lots and locations. The inventory featuredescribes loose-part records separately. These routes are private-preview descriptions; they do not promise public availability or live provider writes.