Draw an ERD for a database that should track baluster designs, balusters sold, and customer orders for a company that sells various wood balusters. Details follow:

There are various baluster designs to choose from. Each wood baluster design can be offered in various wood species, such as oak, maple, and hickory. However, not all wood species are available to all designs. (Some only come in oak, others come in both oak and maple, still others may have wider wood species selection.) A unique design id is used to denote each design. Not all designs are available to ship to all states. The database needs to store all baluster designs and what wood species are available for each design. In addition, for each design, the database needs to store which states it can't be shipped to.

Each design comes in 5 different lengths: 31", 34", 39", 41", and 44". For each design in each length, an image of the baluster should be stored to give customers more visual information.

Price can vary depending on the design, the wood species, and the length. The database needs to store pricing information for each type of balusters.

Each baluster of a particular design, wood species, and length is assigned a unique baluster id.
When a customer orders balusters, she chooses the design, the wood species, and the length. The database should store all balusters ordered, as well as the quantity and the unit price for each baluster. The database also stores customer's first name, last name, address, phone, and email.

Hint: Since there is a unique design id and a unique baluster id, it's a dead giveaway that you'll need two entities, one for baluster design and the other for baluster. There are of course other entities as well.