There is a moment in every digital builder's journey that changes everything. You have spent hours — maybe days, maybe weeks — designing a MOC in Stud.io. The model is finished. It renders beautifully. The colors are right, the geometry is tight, and you have already imagined where it will sit on your shelf. But it exists only as data. Pixels on a screen. And the gap between a finished digital model and a pile of real bricks in your hands feels enormous.
It does not have to be. The pipeline from Stud.io to a delivered box of parts is well-established, surprisingly efficient, and — once you understand the steps — repeatable for every MOC you ever design. The core pathway runs through BrickLink, the world's largest marketplace for LEGO parts, and the integration between the two platforms is no accident. BrickLink owns Stud.io. The export tools were built specifically for this workflow. If you have not already read the BrickLink beginner's guide, now is the time. This article assumes you know what BrickLink is and have an account. What you may not know is how seamless the ordering process can be when you follow the right steps.
This guide walks through every stage of that pipeline: exporting your parts list from Stud.io, uploading it to a BrickLink Wanted List, using the auto-match feature to find sellers, dealing with parts or colors that are not available, making smart substitutions, consolidating orders across multiple stores, estimating your total cost, and finally placing your order. By the end, you will have a repeatable system for turning any digital design into a real, physical build.
The export process begins inside Stud.io itself, and it is one of the most streamlined features in the entire application. With your model open, navigate to File > Export As and select BrickLink Wanted List XML. This generates an XML file that contains every part in your model — element ID, color, and quantity — formatted exactly the way BrickLink expects to receive it. One click. One file. Every part accounted for.
Before you export, though, there are a few things worth checking. First, run the Model Info panel (View > Model Info) and review the total part count and unique element count. This gives you a realistic preview of what you are about to order. A 500-piece MOC with 80 unique elements is a very different ordering challenge than a 500-piece MOC with 300 unique elements. The more unique parts, the more stores you will likely need to buy from, and the higher your shipping costs will be.
Second, check for any parts flagged with warnings. Stud.io marks elements that do not exist in the specific color you have chosen with a small alert icon. These are parts that exist in the LEGO system but have never been produced in that particular color. You can still use them in your digital model — Stud.io does not restrict you — but you cannot buy them because they were never manufactured. Catching these before export saves you from confusion later when BrickLink cannot find matches. If you need a refresher on how Stud.io handles color and part databases, the import and export formats guide covers the technical details.
Third, consider whether you need the entire model or just a portion. If you are building in phases or already own some of the parts, you can select specific elements in Stud.io before exporting and choose to export only the selection. This is enormously useful for large MOCs where you want to order one section at a time, or when you are updating an existing build and only need the new parts.
With your XML file exported, the next step happens on BrickLink. Log in, navigate to Want > Upload, and paste the contents of your XML file or upload the file directly. BrickLink parses the XML and creates a Wanted List — a saved shopping list that the platform uses to match your needs against available inventory across thousands of stores worldwide.
You can name the Wanted List anything you like, but I strongly recommend naming it after the MOC it corresponds to. If you are building a custom castle, name it "Custom Castle v2" or whatever version you are on. Over time, you will accumulate multiple Wanted Lists for different projects, and clear naming prevents the confusion of staring at a list called "Untitled" and having no idea what it is for. You can also add notes to each list for future reference.
Once uploaded, BrickLink displays your complete parts list with each element shown alongside its current marketplace availability. Green indicators mean the part is widely available in the color you need. Yellow means limited availability. Red means trouble — the part either does not exist in that color, is extremely rare, or has been retired so long that remaining stock is nearly gone. This color-coded overview is your first real reality check. A list that is mostly green means your MOC is practical to build from available parts. A list with significant red means you have design work ahead of you.
One important detail: BrickLink's part numbering system does not always match Stud.io's system perfectly. Stud.io uses a combination of LDraw part numbers and BrickLink part numbers, and occasionally a part will fail to match on upload. When this happens, BrickLink flags the unmatched items. You will need to manually search for the correct BrickLink part number and add it to your Wanted List. This is uncommon — the integration handles the vast majority of parts correctly — but it happens often enough that you should check for unmatched items after every upload.
BrickLink's auto-match is the engine that turns your Wanted List into actionable orders. Navigate to your Wanted List and click Buy All. The platform searches its entire marketplace — every store, every inventory listing — and attempts to find the combination of stores that can fulfill your list at the lowest total cost, including shipping. It is essentially solving an optimization problem: minimize total spend across N stores while ensuring every part is covered.
The results page shows you a ranked list of store combinations. The top result is usually the cheapest option, but it is worth scrolling through the alternatives. Sometimes the second or third option costs slightly more but uses fewer stores, which means fewer packages to track, fewer shipping charges, and fewer chances for something to go wrong in transit. A solution that costs two or three extra dollars but consolidates your order from six stores down to three is almost always worth it.
You can also set parameters before running the auto-match. Maximum number of stores is the most useful constraint. Setting it to five or six forces the algorithm to prioritize consolidation over absolute minimum cost. You can also set a minimum order value per store — some stores have minimum purchase requirements, and filtering them out in advance avoids wasted time. Geographic filters are useful too. If you are in the United States, limiting results to US-based stores eliminates international shipping times and customs uncertainty.
One thing auto-match cannot do is think creatively. It matches parts exactly as specified. If your Wanted List asks for a 1x4 plate in dark azure and only three stores worldwide carry it, the algorithm will route you to one of those three stores regardless of cost. It will not suggest that dark blue is a close visual match that is available everywhere. That kind of judgment requires a human, and it is the subject of the next two sections.
Every MOC designer eventually runs into the wall: the part exists but not in the color you want, or the color exists but not on the part you need. This is the fundamental constraint of building with real LEGO. The digital palette in Stud.io is larger than the physical palette in reality. Not every part has been produced in every color, and some color-part combinations were only available in a single set from 2003 that now commands collector prices.
The first step when you hit an unavailable part-color combination is to check whether the part was ever produced in that color. BrickLink's catalog pages show the complete production history of every element — which sets included it, in which colors, and during which years. If the part was produced but is rare, you have two options: pay the premium and source it from the handful of stores that carry it, or redesign. If the part was never produced in that color, redesign is your only option.
Stud.io actually helps with this. The Part Palette panel shows you which colors are available for any selected part. If you click on a part in your model, you can see a grid of every color it has been manufactured in. Switch to a color that exists, and the problem disappears. The visual impact of swapping dark azure for dark blue in a single structural part buried inside your model is exactly zero. Nobody will see it. Nobody will know. The build will hold together exactly the same way. Save your energy for the parts that are actually visible.
For parts that simply do not exist in any acceptable color, you need to rethink the design. Can you achieve the same structural connection with a different part? Can two smaller parts replace one larger part? Can you use a different building technique entirely? This is where the MOC building fundamentals matter — understanding how parts connect gives you the flexibility to improvise when your first choice is not available. The best MOC designers treat unavailable parts not as problems but as creative constraints that push them toward better solutions.
Part substitution is both an art and a science. The science is knowing which parts are dimensionally compatible — which elements occupy the same space, connect the same way, and provide the same structural integrity. The art is knowing which substitutions are invisible and which ones compromise the design. Mastering both transforms you from a builder who is limited by availability into one who can adapt any design to reality.
The most common substitution categories are straightforward. Plate equivalents: a 1x4 plate can almost always be replaced by two 1x2 plates side by side. A 2x6 plate can become a 2x4 and a 2x2. The connection points are identical and the visual difference is a single seam line that disappears under other elements. Color adjacents: dark bluish gray and dark stone gray are functionally identical to anyone who is not holding them side by side. Medium azure and dark azure are close enough for most applications. These micro-swaps solve ninety percent of availability problems without touching the design.
More creative substitutions require structural thinking. A headlight brick (modified 1x1 with stud on side) can be replaced by a 1x1 brick plus a 1x1 bracket in many applications. A 1x2 jumper plate can be replaced by a 1x2 plate if the half-stud offset is not critical. Slopes come in enough varieties that a 33-degree slope can often fill the role of a 45-degree slope with minor visual differences. The Parts Lab is your reference for these kinds of dimensional relationships between elements.
The golden rule of substitution: make changes in Stud.io first, then re-export. Never substitute parts mentally and order the substitutes directly. Update your digital model so it reflects exactly what you are ordering. This keeps your model accurate, lets you verify that the substitutions actually work structurally, and ensures your Wanted List matches your final design. A model that does not match the parts you ordered is a model that will surprise you during assembly — and not in a good way.
Unless your MOC uses exclusively common parts in common colors, you will be ordering from multiple BrickLink stores. This is normal. No single store carries everything, and the marketplace model means your order will typically span three to ten different sellers. The challenge is managing this complexity without losing track of what you have ordered, what has shipped, and what is still missing.
Start with the auto-match results and review each store's portion of your order. Check seller ratings — anything above 99% positive feedback with more than 100 transactions is reliable. Check shipping costs — some stores offer flat-rate shipping while others charge by weight, and the difference on a large order can be significant. Check processing times — a store with a stated 5-business-day processing time will delay your entire build if it is the one holding a critical part. For a deeper comparison of sourcing strategies, the BrickLink vs. Pick a Brick vs. Amazon guide breaks down the pros and cons of each platform.
The consolidation strategy that works best is the anchor store method. Identify the one or two stores that carry the largest portion of your Wanted List and place those orders first. These are your anchor stores — the orders that cover the bulk of your parts. Then use smaller stores to fill in the gaps. This minimizes the number of transactions and concentrates your spending where it has the most impact. Many BrickLink stores offer volume discounts or reduced shipping on larger orders, so consolidating spend into fewer stores often saves money beyond just reducing shipping charges.
Keep a simple tracking spreadsheet or use BrickLink's built-in order management to monitor the status of each order. Mark each store as ordered, shipped, or received. When all orders arrive, cross-reference the physical parts against your Stud.io model before you start building. Missing a single critical part after you have assembled half the model is frustrating. Catching it before you start is a minor inconvenience. This is also where the bulk brick sourcing guide becomes relevant — if you find yourself repeatedly ordering the same common elements, buying in bulk from dedicated suppliers is more cost-effective than sourcing them one MOC at a time.
Before you commit to ordering, you need a realistic estimate of what your MOC will cost to build in real parts. The part count alone is a poor predictor. A 1,000-piece MOC built from common 1x2 and 2x4 bricks in standard colors might cost a fraction of what a 300-piece MOC built from rare elements in unusual colors costs. What matters is not how many parts you need but which parts you need and how available they are.
BrickLink's auto-match results give you the most accurate cost estimate because they include actual asking prices from real stores plus shipping. But before you reach that step, you can get a rough estimate by looking at the Wanted List and noting the average availability and average lot price for each element. Common parts — basic bricks, standard plates, common slopes in primary colors — typically run a few cents each. Specialized parts — printed elements, rare colors, retired molds — can range from fifty cents to several dollars each. Minifigure parts, if your MOC includes them, add up quickly.
Shipping is the cost that surprises most first-time BrickLink buyers. Each store charges its own shipping rate, and when you are ordering from five or six stores, shipping can add thirty to fifty percent to your total parts cost. This is where consolidation pays for itself. Cutting your order from eight stores to four stores does not halve your shipping costs — it usually does better than that, because each remaining store now has a larger, heavier order that amortizes the fixed shipping cost more efficiently.
The other hidden cost is what I call the last-five-parts problem. Auto-match will find great deals on ninety-five percent of your list, but the last few rare or unusual parts often come from stores that only carry one or two items you need. You end up paying full shipping for a handful of parts. When this happens, consider whether those parts are worth a design revision. Swapping one rare element for a common one can save you an entire separate order. Design flexibility is a financial asset in MOC building.
With your Wanted List reviewed, substitutions made, and stores selected, it is time to place the order. BrickLink's checkout process works store by store — each seller is an independent transaction with its own cart, payment, and shipping. Work through your auto-match results methodically. Open each store, review the items in your cart, verify quantities and colors, and submit. Most stores accept PayPal, which adds a layer of buyer protection that is worth using.
Before finalizing each store order, read the store's terms. Some require minimum order values. Some do not ship on certain days. Some offer combined shipping if you order again within a window. A few stores allow you to add a note with your order — use this to mention that you are building a MOC and would appreciate careful color sorting if possible. Most sellers are fellow LEGO enthusiasts and appreciate knowing their parts are going toward a creative project rather than resale.
After placing all orders, resist the urge to start building with whatever arrives first. Wait until everything is in hand. The reason is practical: if a store is out of stock on something you thought they had (inventory updates lag occasionally), you need to know before you are mid-build with a structural gap. Once all packages have arrived, open everything, sort by type or by model section, and verify against your Stud.io parts list. Use the Model Info panel in Stud.io as your checklist. Only when every element is accounted for should you start assembly.
There is nothing quite like the moment you connect the first two bricks of a MOC you designed yourself. Digital building is satisfying in its own way — the clean precision of Stud.io, the ability to undo mistakes, the unlimited parts bin. But it is a simulation of building. The real thing has weight and texture and the sound of bricks clicking together. It has the occasional piece that does not quite sit right and needs to be pressed harder. It has the accumulated evidence of hours of creative work taking physical form on your desk.
The pipeline from Stud.io to BrickLink is what makes that moment possible. It is the bridge between imagination and reality, and once you have crossed it a few times, it becomes second nature. Export, upload, match, order, verify, build. Six steps from screen to shelf. The Builds hub is full of MOCs that followed exactly this path, and the Reviews section covers official sets that might inspire your next digital design. If you are working on your first MOC and the ordering process feels overwhelming, start small. A 200-piece model with common parts is the perfect test run. You will learn the workflow, build your confidence, and end up with something real on your desk — proof that the bricks on your screen can become bricks in your hands.
The best MOC is not the one that renders the prettiest. It is the one you can actually build. Design with availability in mind, and reality will meet you halfway.