Ok, not it's more clear. To discuss it, let's number the rows of the grid on the screenshot from 0 to 11. I'll try to describe how I understand what I see on the picture. Confirm it, please, so we all will know that we are talking about the same things.
Well, if we get the task right, the general idea of this grid is to have a 2-level grid, i.e. parent-child relationship without deep row hierarchy. Row #1 looks like usual column headers for the parent rows (row ## 2, 9-11).
However, if we look at rows ## 3-7, we see that they have a different column set. What is important for iGrid, it's different from the parent row structure. Unfortunately, this grid structure is also called "nested gird", isn't supported by iGrid. In iGrid, you can create a so called tree-grid (or multi-column treeview) enough easily, but it implies you have the same column structure in rows of all hierarchy levels.
Another option could be to use the iGrid group rows for your parent rows if you need just to display fields in them. As I can judge from the screenshot, there should be no way to resize the fields in rows 2 or 9 interactively, and their contents can be drawn without any problems using standard GDI+ methods. If we go this way, we could use the iGrid column headers for the child rows.
As I understand from the picture, the fields in gray rectangles should be editable. My idea with using group rows for your parent rows will work in this case too. The only problem in this case would be the Qty Received field I see in the group rows. It seems, we will need to implement a special interface solution (an additional button, hyperlink, etc) to edit it in a separate dialog.
The only row we have not talked about is row #8. To "build in" two buttons inside such a row (most likely, we will need to use a group row for that too), we will need custom draw code + code that processes mouse clicks on this buttons.
In general, something similar to the grid you need can be eventually implemented with iGrid.NET. But as I see, this may require a big amount of development from our side (building a prototype, adjusting them, polishing the functionality, etc) and we can discuss the possibility of doing that on contract basis in private correspondence.