Marketplace Export
BrickLink XML Export for Custom Mosaic Parts
Generate your photo mosaic in a free preview before creating a buying inventory. Once the plan works, a paid digital blueprint unlock supplies complete personal PDF instructions and BrickLink XML. Physical parts are purchased separately; seller selection, stock checks, shipping, and checkout remain in BrickLink.
Direct Answer
After a free mosaic preview and paid blueprint unlock, BMBrick exports BrickLink XML with part IDs, color IDs, and quantities for the confirmed crop, size, material, and palette. Keep it with the matching PDF; XML is a sourcing inventory, not assembly instructions or a purchase.
Preview First
Generate the photo mosaic for free. Purchase the complete personal PDF and XML only after confirming the plan.
Still Needed
Seller selection, final availability, shipping decisions, and checkout happen outside BMBrick.
Use With
PDF instructions and a confirmed parts list so the build file and sourcing file describe the same mosaic.
How the workflow works
01 - Confirm the mosaic
Do not export XML while the crop, palette, or material style is still changing.
02 - Review route pressure
Check dropped colors, estimated totals, and part style before relying on any sourcing file.
03 - Export BrickLink XML
Use the XML output when a marketplace inventory workflow is the preferred sourcing path.
04 - Validate outside BMBrick
Review seller availability and shipping behavior in BrickLink before purchasing.
BrickLink XML workflow checks
The XML export is most useful when the project state is stable.
| Check | Good signal | Bad signal | Action |
|---|---|---|---|
| Crop | Subject is stable | Still experimenting | Return to editor |
| Material | 3024 or 98138 chosen | Switching styles | Compare square vs round first |
| Palette | Allowed colors reviewed | Many surprise drops | Tailor palette |
| Instruction path | PDF also exported | Only sourcing file exists | Keep build and sourcing outputs together |
Where XML helps most
XML is useful when a builder wants a structured inventory file instead of copying quantities by hand. For large mosaics, that can save time and reduce transcription mistakes.
It does not remove the need for sourcing judgment. BrickLink seller stock, lot condition, shipping cost, and regional availability are external variables that BMBrick cannot guarantee.
PAB CSV/JSON and Webrick files serve different supplier workflows. Do not upload BrickLink XML to those suppliers or assume their color IDs are interchangeable; choose the matching route and inspect its ordering notes.
- Use XML after the project state is locked.
- Keep a PDF instruction file with the same mosaic version.
- Expect to review seller availability before purchase.
Read the quantities before choosing sellers
A full 48×48 mosaic using one part per cell needs 2,304 pixel parts. Add all XML MINQTY values to confirm that total. If the plan skips background cells, compare against its active count instead of the full grid area.
ITEMID identifies the selected part, such as 3024 square plates or 98138 round tiles. COLOR uses BrickLink's color ID. These values are different from a LEGO element ID or another supplier's color code. The sample and detailed XML workflow let you inspect actual files before buying your own blueprint.
Estimate scope
Catalog scope: BMBrick's data was verified April 6, 2026 and generated April 15, 2026. Prices are USD planning estimates from that snapshot, not live supplier quotes or stock guarantees. Physical bricks, base/support hardware, display hardware, tax, and shipping are separate from the paid digital blueprint.
FAQ
Does BMBrick complete BrickLink checkout?
No. BMBrick exports XML inventory data; seller selection and purchasing happen in BrickLink.
Is the XML tied to the PDF?
Both outputs come from the selected mosaic state, so export them after the same crop, size, material, and palette are confirmed.
Can I use XML for square and round parts?
BMBrick supports separate material routes for 3024 square plates and 98138 round tiles.
Should I export XML before testing the image?
No. Test the image and route first so the XML reflects a build you actually want to source.
Where To Go Next
Next reads: