Two part questions

I have a product aggregate that has;

Prices PackagingOptions ProductDescriptions ProductImages etc

I have modeled one product repository and did not create individual repositories for any of the child classes. All db operations are handled through product repository.

Am I understanding the DDD concept correctly so far? Sometimes the question comes to my mind that having a repository for lets say packaging options could make my life easier by directly fetching a the packaging option from the DB by using its ID instead of asking the product repository to find it in its PackagingOptions collection and give it to me..

Second part is managing the edit create operations using ASP.MVC frame work

I am currently trying to manage all add edit remove of these child collections of product through product controller(sound right?).

One challenge I am now facing is;

If I edit a specific packaging option of product through

mydomain/product/editpackagingoption/10

I have access to the id of the packaging option

But I don't have the ID of the product it self and this forces me to write a query to first find the product that has this specific packaging option then edit that product and the revelant packaging option. I can do this as all packaging option have their unique ID but this would fail if I have collections that don't have unique ID.

That feels very wrong..

The next option I thought of is sending both the product and packaging option IDs on the url like;

mydomain/product/editpackagingoption/3/10

But I am not sure if that is a good design either.

So I am at a point that I am a bit confused. might be having fundamental misunderstandings around all of this...

I would appreciate if you bear with the long question and help me put this together. thanks!