sourcing · Source researched
How to read a robotics parts estimate before buying
Treat a robot subtotal as the price of its stated scope. Check configuration, exact parts, availability, missing requirements and the equipment you already own before treating it as your budget.
For: Builders planning a first source-documented robot configuration
Scope: Source research only; pinned configuration and recorded cost inputs. Current seller prices, electrical validation and physical reproduction are outside this guide.
By Open Source Robotics editorial team · Sources checked 2026-10-07 · Updated 2026-10-07
Start with the task and configuration
A parts estimate answers a narrower question than “What will this robot cost me?” Identify the hardware revision, first task, region and currency before using a subtotal. A follower-only arm and a leader–follower setup require different quantities; the SO-101 cost sheet therefore keeps them as separate configurations. SO-101 configuration cost sheet
Read the scope before the number
For each required item, record the exact variant, quantity, seller, offer date and whether you already own it. Then separate parts, tools, host equipment, delivery and tax. A useful estimate shows missing costs explicitly. An unpriced requirement is not a free requirement.
The existing cost sheets provide these concrete examples:
| Question | Example from the recorded research | Consequence for your budget |
|---|---|---|
| Does the BOM cover assembly hardware? | SO-101's reviewed list leaves M2×6 and M3×6 screw sourcing unresolved | Check the assembly steps as well as the BOM |
| Is the computer part of the robot or an external tool? | LeKiwi lists an onboard Raspberry Pi separately from host equipment | Owning a laptop does not remove the onboard-computer line |
| Does a similar replacement have established fit? | LeKiwi's alternative omni wheel has unverified printed-hub fit | Keep the substitution out of a confirmed total |
| Are all required parts priced? | Microban's reviewed battery wiring is not fully itemized and several parts lack an identified US offer | Treat the subtotal as partial |
SO-101 coverage notes LeKiwi sourcing notes Microban coverage notes
Keep a dated offer distinct from a purchase price
The SO-101 sheet records inputs dated October 4, 2026. Its scope notes say unavailable listings should be excluded from counted totals. A past listing can explain an earlier estimate without establishing something you can buy now. This guide uses the stored cost sheets as examples and has not refreshed their seller offers. SO-101 offer history
Before ordering, revisit each seller, confirm the exact variant and quantity, and include the destination-dependent charges shown at checkout. Record unavailable items as gaps. Do not replace them silently with a cheaper product whose compatibility is unverified.
Printing and ownership change the answer
When estimating printing costs, distinguish buying a spool from the material used by one build. Record the slicing settings and assumptions behind a material estimate; failed prints and labor are separate concerns. This is budgeting advice, rather than a verified material-consumption estimate for SO-101. A downloadable model also does not establish a successful print or mechanical fit. SO-101 build scope
Use two budget views: the requirements for the configuration, and the new purchases needed after subtracting the things you already own. Keep the first view intact so a reader without your tools can understand the same build. Check that an owned item actually meets the requirement before removing its purchase cost.
A practical order checklist
- Name the robot revision, configuration and first task.
- Match each required item to an exact variant and quantity.
- Recheck availability, offer dates and seller conditions.
- Reconcile the assembly steps with the BOM, including fasteners and wiring.
- Identify tools, host equipment, printing and other omitted requirements.
- Add delivery and tax when known; retain gaps when they are unknown.
- Separate documented compatibility from proposed substitutions.
Start with SO-101, LeKiwi or Microban and audit one configuration line by line. The resulting list is a sourcing plan; reproduction still requires an actual build and test.
Sources
- SO-101 cost and sourcing record — Open Source Robotics. Approved catalog export at source 863bad7a; cost sheet as of 2026-10-04; local retained copy inspected October 7. Accessed 2026-10-04.
- LeKiwi cost and sourcing record — Open Source Robotics. Approved catalog export at source 863bad7a; cost sheet as of 2026-10-04; local retained copy inspected October 7. Accessed 2026-10-04.
- Microban cost and sourcing record — Open Source Robotics. Approved catalog export at source 863bad7a; cost sheet as of 2026-10-04; local retained copy inspected October 7. Accessed 2026-10-04.