Hello, I've seen this topic come up a number of times over the last year but none of the posts really seemed to address my specific issue or make it clear exactly what the processes is when order a panel of pcb's that will be assembled. My primary concern is with the displayed view JCL provides when uploading a pcb panel, I under stand the Gerber viewer isn't perfect but a similar image is also shown when attempting to order assembly of a panel.  When you look at the image above, you will notice that in each of the 4 corners the PCB does NOT have the stamp hole on the outside edge of the mouse bites. You will also notice that the top left pcb shows it would not have the notch in it cut out due to the incomplete hole stamping. Now I have tried all sorts of different things to fix the issues that you see here but nothing seems to work. So, how do I go about fixing this so that I don't loose several boards on every panel? <br> The next issues I'm running into is with how the panel should selected with JCL. I have highlighted the parts of the picture below that are in question...  So, when selecting "Panel By Customer" it then asks you to fill in the number of rows and columns. The issue here is the PCB already has the rows and columns as shows by the board size being displayed. The issue seems to be that EasyEDA and JCL are not on the same page here and they are both trying to do the same thing. Does JCl want me to upload a panel from EasyEDA and then select that its a Single PCB, or do they want me to export my gerber as a single PCB, then select Panel by customer and fill in these details? <br> It is very frustrating that there is so much contradiction between EasyEDA and JCL when trying to create a PCB panel and that the documentation from both company's fail to address how to go about doing this. As many others have said, it shouldn't be this hard to go about ordering something as simple as a panel. I understand that JCL is still growing and that EasyEDA is still developing it's software but this is an issue that seems to have been around for a couple of years now and it doesn't seem like either company has ever really addressed this issue.