Gene Synthesis Orders: A Review Checklist Before You Submit

A pre-order review checklist for a gene-synthesis submission is a cart gate, not a second design-review seminar. Stop the order if a second person cannot restate the protein, the recoding policy, the sites you still need, and the backbone the vendor will return. A pretty viewer that hides a frameshift is not ready.

What Must Be True Before the Cart

The outcome is a frozen DNA file that still encodes the protein you think it does, under a recoding policy you can name, in a return vector you can clone. Inputs are the amino-acid sequence or the intended ORF, the expression host, any restriction sites you must keep or forbid, and the destination backbone. This is not a rewrite of the construct design-review workflow. That page owns junctions before bench work. This page owns the vendor cart. If those four objects live only in chat, the order is still a draft, even if the viewer looks finished.

Steps: Freeze the Protein and the DNA

1. Translate the exact DNA you are about to submit and match it to the intended protein, including linkers and tags. Twist’s gene-design note tells the user to confirm the translation is in frame before ordering. Treat that as a dated vendor reminder, not a unique Twist ritual.
2. Confirm a start and a stop, and that no extra base in a linker created a frameshift.
3. Name the recoding policy in writing: native sequence, max-CAI / host-preferred optimization, or codon harmonization. Angov et al. (2008) defined harmonization as frequency matching, not max-CAI. The definition lives on the harmonization page. This checklist only asks which policy you intended.
4. Scan reserved restriction sites and any internal sites the assembly method cannot tolerate. A silent optimization that removes a needed site is a failed gate.
5. Read GC, repeat, and homopolymer warnings as manufacturing risk for that vendor’s class system. They are not a quality score of your biology.

Expected Result and Verification

Expected result: a second person can open the file and restate protein, recoding policy, reserved sites, and return backbone without asking you. Verification: the translation view matches the protein; reserved sites are present or absent as planned; the vendor vector is named, not “whatever MCS.” If any of those four objects is unsigned, the cart is early.

Common Failures That Still Pass a Pretty Viewer

An extra base in a fusion linker shifts the tag and still looks like an open reading frame in a zoomed window. Optimization domesticates a Type II site you needed for the next clone. The form said “harmonize” and the returned file is max-CAI. The return vector’s MCS was never opened. Assembly chemistry — restriction, Gibson, or homology — was chosen on the method page and then ignored when the vendor offered a stock backbone. Each of those failures can pass a pretty viewer. None of them should pass a second-person restatement of the four objects.

This Gate Is Not the Design-Review SOP

The design-review sibling owns frame, junctions, and unique sites before wet work. This page owns the synthesis cart. After the sequence is frozen, a map such as ZettaGene is one place to inspect the ORF and restriction-site annotations. Official copy documents visualization, editing, and those annotations. It does not replace the four written objects. The takeaway is the gate, not a faster order.

Frequently Asked Questions

What has to be written down before a gene synthesis order is submitted?

The protein, the recoding policy, reserved sites, and the return backbone. If a second person cannot restate those four, the cart is early.

Is codon optimization the same check as codon harmonization?

No. Optimization usually pushes host-preferred codons. Harmonization matches the native frequency ramp. The definition lives on the sibling page; this checklist only asks which policy you intended.