Hi JLCPCB Support Team,

When designing PCBs to be ordered via JLCPCB, I (like many users) often create a documentation text field somewhere in the PCB layout that describes all required PCB ordering options, such as number of layers, thickness, stackup config, and other important project-specific requirements, such as material types, copper weights, tolerances etc.

Obviously, manually entering all these options for each order in the web order form is error prone.

It would be a great enhancement to have a simple input/output string interface for all these settings. That is, when creating an order, the user can read the currently selected configuration settings in a readonly text field (plain text with variable assignments, see below, or JSON, or whatever you like) generated by your web services.

For example, that string could look like this:

base_mat=fr4;layers=6;thick=0.8;color=blue;mat=s1000h;fin=enig;w_out=2;w_in=1;via_cov=epx_fil_cap;...

Then, when ordering the same type of PCB again in the future, you can simply paste that same configuration string into an input field on the order page (after uploading the Gerbers) and all the settings are automatically preset as specified in the pasted text string. Newly introduced settings, or generally speaking, settings that are not specified in the pasted string could be highlighted as "still to be selected manually". And settings that have become obsolete, but which are specified in the pasted string, would result in an import error message that tells the user where they should check their options again.

The user could put this string somewhere in their project documentation and simply use that string, instead of long human-readable configuration descriptions, for new PCB orders of that same project in the future.

This would help sharing designs between coworkers, or even when published on the internet. Users would simply post that string along with their open-source Gerber files and users could immediately order the right configuration from your (and only your ;) website.

Thanks for your consideration.

Mark