Answers.Body: <p>This doesn't have anything to do with database limitations or anything like that. Brickset scrapes their inventories from the replacement parts list on LEGO.com:</p>
  
  <p><a href="https://www.lego.com/en-us/service/replacementparts" rel="noreferrer">https://www.lego.com/en-us/service/replacementparts</a></p>
  
  <p>Normally, you are able to request as many replacement parts as there are parts in the set, so this is the number that Brickset uses for it's inventory count. Unfortunately, the max you can request is 200, so Brickset doesn't list more than 200 of the same part being found in a set.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-19T17:37:08.123Z
Answers.Text: That's a fun bug.  Can we fix those quantities after they scrape it?
Answers.UserDisplayName: chicks
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-19T23:40:55.557Z
Answers.Text: I believe that they intentionally keep this data synced directly with what is found on lego.com. They do also link to curated inventories (Bricklink, Rebrickable, etc). From their contact page: "Information about parts and set inventories comes from LEGO customer services we are unable to make changes to it." I'll ping their staff about this just in case.
Answers.UserDisplayName: jncraton
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-20T07:06:43.667Z
Answers.Text: Thank you -- that is exactly why. We don't modify inventories once obtained, we prefer to keep them verbatim, errors and all. -- Huw, Brickset.com
Answers.UserDisplayName: Huw Millington
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-20T23:41:13.993Z
Answers.Text: @HuwMillington Makes sense. Thanks for the info!
Answers.UserDisplayName: jncraton
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-18T16:59:19.793Z
Answers.LastActivityDate: 2017-09-18T16:59:19.793Z
Answers.UserDisplayName: jncraton
Body: <p>One example of this issue would be a set like <a href="https://brickset.com/sets/42056-1/Porsche-911-GT3-RS" rel="noreferrer">42056</a> that has 516 black Technic pins with friction. Brickset lists it as only having 200. Is this a technical limitation of some kind? What causes this?</p>
  
Tags: <inventory>
Title: Why does the Brickset inventory page incorrectly list a set as including 200 of a part when it actually includes more?
UserDisplayName: jncraton
ThreadText: # Why does the Brickset inventory page incorrectly list a set as including 200 of a part when it actually includes more?
  
  (Asked by: username_0 on 2017-09-18)
  
  One example of this issue would be a set like [42056](https://brickset.com/sets/42056-1/Porsche-911-GT3-RS) that has 516 black Technic pins with friction. Brickset lists it as only having 200. Is this a technical limitation of some kind? What causes this?
  
  **Tags:** inventory
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-09-18. Score: 10 | Accepted answer
  
  This doesn't have anything to do with database limitations or anything like that. Brickset scrapes their inventories from the replacement parts list on LEGO.com:
  
  <https://www.lego.com/en-us/service/replacementparts>
  
  Normally, you are able to request as many replacement parts as there are parts in the set, so this is the number that Brickset uses for it's inventory count. Unfortunately, the max you can request is 200, so Brickset doesn't list more than 200 of the same part being found in a set.
  
  > **Comments:**
  > **username_1**: That's a fun bug.  Can we fix those quantities after they scrape it?  
  > **username_0**: I believe that they intentionally keep this data synced directly with what is found on lego.com. They do also link to curated inventories (Bricklink, Rebrickable, etc). From their contact page: "Information about parts and set inventories comes from LEGO customer services we are unable to make changes to it." I'll ping their staff about this just in case.  
  > **username_2**: Thank you -- that is exactly why. We don't modify inventories once obtained, we prefer to keep them verbatim, errors and all. -- Huw, Brickset.com  
  > **username_0**: @HuwMillington Makes sense. Thanks for the info!  
  
  ---
  
  