Two penhold orders land on the same bench on the same morning. The first carries one word in the configuration field, penhold, plus a rubber name. The second names the build and says which faces carry rubber. One gets kicked back as an email asking what the buyer actually wanted. The other goes to assembly. Same blade family, same rubber brand, and only one of those two sheets can be executed without a phone call.
The configuration wording I use here comes from Butterfly's custom racket configurator page, a reference brand's ordering vocabulary and not a production promise from any factory. Nothing on that page tells you what a given OEM will quote, cut, or ship. Hold that line and the rest of this holds up.
One Rubber or Two Sets the Whole Order
The page names exactly two penhold builds. Chinese Penhold is the traditional configuration, with rubber on only one side. Reverse Penhold Backhand is the modern configuration, with rubber on both sides. Those parentheses carry the entire content of the decision, and the decision is binary. A face either has rubber on it or it doesn't.
That's why the configuration line outranks the blade name and the rubber name sitting next to it. Every line below inherits it: rubber gets picked per face, the sheet gets trimmed per face, edge tape follows whatever perimeter was actually covered, and assembly follows the same map. A correct configuration line gives the rest of the sheet something to attach to. A vague one hands the factory a word instead of a build.
Nothing here ranks the two builds on playing merit, and I'd push back on anyone who tries. One is labeled traditional, one modern, and those labels describe layout and the stroke the layout supports, not your buyer, your channel, or your price point. Settle the layout first, and argue about rubber second.
What the Configurator Page Fixes, and What It Doesn't
The assembly description runs one sentence long and reads like a bench sequence: rubbers assembled, cut to size, edge tape applied. Three actions, in the order they physically happen. Anyone who has watched a racket get built will find nothing surprising there, and that's the useful part. The sequence is standard enough that a supplier can confirm it or correct it in a single reply.
Special requests get thinner treatment. The page says they can be noted during checkout. Noted is where it stops: not specified, not approved, not costed, not scheduled. For a retail buyer that's fine. For a wholesale order it's the exact spot where a mismatch is born, because a comment field has no relationship to a work order until somebody on the supplier side turns it into one.
What the page does not settle is the commercial side and the capability side: what a factory charges, what volume it will take, how long it needs, how much customization it will accept per face, and what a first sample gets measured against. None of that lives on a configurator page, and none of it transfers from a reference brand to your supplier. Those are questions you send in writing and get back in writing.
One more thing the page can't do for you: it can't tell you whether the reference brand's assembly sequence matches your supplier's. Two factories can both glue, trim, and tape in that order and still differ in how they check the result. Ask your supplier to describe its own sequence and compare the two descriptions side by side; where they diverge is where your spec sheet has to be explicit.
What I Noticed Reading the Page Line by Line
I opened the saved copy of the page and read the configuration block twice. The two builds are named by different logic in the same breath, one by tradition and one by the stroke it enables, and the only operative detail in either name is the parenthetical about how many sides carry rubber. That parenthetical carries the whole decision. Two builds, two naming systems, one real detail.
Then I counted the actions in the assembly sentence and got three, all in bench order, which tells me coverage has to be settled before trimming starts rather than after. One line, three steps, nothing hidden in between. I looked at the special-requests line next and noticed where it sits in the sequence: at checkout, after every other choice has been made. There is nothing on the page defining what happens to a note once it is written down.
My read of the page, then, is that it's a good vocabulary source and a poor process source. It gives you the two names to put on a purchase order. It gives you the order in which rubber work happens. It does not tell you who signs off a special request, what a factory charges for a second glued face, or how a sample gets approved. I treat it as the first hundred words of a spec sheet, not the whole thing.
The Sample Check I Would Run First
I did not run a first-article check for this piece, and there are no measurements behind it. Treat what follows as a plan, not a result. Suppose a sample arrives from a supplier you've quoted and the sheet says reverse penhold backhand, rubber on both sides. Here is what I would put in front of me before signing anything.
Face by face, against the sheet. Forehand face carries rubber or it doesn't. Backhand face carries rubber or it doesn't. The cut line falls inside the covered area. Edge tape follows the covered perimeter and doesn't wander onto bare wood. The work order label uses one of the two configuration names or an unambiguous equivalent, not a shorthand somebody invented on the floor. If both faces agree with the spec sheet, the sample clears the check that matters most at this stage.
The finding that would overturn it is simple: a backhand face that disagrees with the order kills the assumption that a clear configuration line alone controls the build. The correction then belongs at the work order level, the document that travels with the parts, not in another comment field at checkout. A sample that passes everything except the face layout is a failed sample, however clean the gluing looks.
Writing Each Rubber Side as Its Own Line
On my own order template I don't give configuration a single free-text box. I give it two rows and a third for everything else. Forehand row: rubber yes or no, and if yes, which rubber. Backhand row: rubber yes or no, and if yes, which rubber. Third row: special requirements, kept separate from the layout rows so a request can't quietly overwrite a face.
I ran both named builds through that layout on paper to see where it breaks. Chinese penhold fills the forehand row and marks the backhand bare, clean. Reverse penhold backhand fills both rows, clean. Then I left the backhand row blank on the two-sided build and the sheet turned ambiguous in one second, because a blank row can mean bare or not yet decided. That is the failure mode this layout exposes, and it stays invisible on a sheet that only says penhold.
This is my purchasing-side format, not a supplier's form. A factory may hand you its own template and ask you to fill it in, and the names it uses may not match the ones quoted here. What survives that translation is the structure: one row per face, bare or covered stated explicitly, special requests on their own line. If the template you're handed has no per-face row, write the layout out in plain sentences in the cover note and ask for it to be confirmed back in writing before anything gets cut. That is a request, not a standard, and a supplier is free to answer it with its own form.
What Each Configuration Costs You at Order Time
Two-sided reverse penhold backhand buys you a modern layout with rubber on both faces. You pay for it in confirmation work: two faces to specify, two faces to check on the sample, more assembly steps per unit. Traditional one-sided penhold buys you a short order and simple assembly. You pay for it in flexibility, because the layout is locked to one covered face and a change of mind later means a new spec, not a note.
Both builds leave the same commercial answers outstanding: price, MOQ, lead time, capacity, and first-sample approval. No configuration wording answers any of them. They come back from your supplier in writing or they don't come back at all, and until they do, the neatest configuration line on your sheet is a well-organized question rather than an order.