Choosing between sanger sequencing services and short read platforms by what the answer has to survive: what ngs vs sanger sequencing and the blunter sanger vs ngs comparison actually trade in cost, turnaround and confidence, why sanger vs next generation sequencing is a question about read length and sample count rather than about accuracy, how ngs platforms and the ngs sequencing platforms behind a quotation change the crossover point, what a sequencing service should return besides a consensus, how to read a trace properly before believing a variant, and where verification of a construct is still cheaper and faster one read at a time

Choosing and using the service

1. Count the samples and the regions. A few regions across a few samples is single read territory: cheap per reaction, fast, and the trace is inspectable. Many regions or many samples crosses over to a short read platform quickly, and the crossover is lower than most people assume.
2. Ask whether you need a consensus or the evidence. A service returning only a called sequence has thrown away the information that lets you judge it. Ask for the trace files as well, because ambiguous positions, mixed peaks and poor early bases are visible there and nowhere else.
3. Design the primers for the read, not for amplification. Read quality is poor for the first stretch after the primer and degrades at the far end. Place primers so the region of interest sits in the reliable middle, and sequence both strands where a single base matters.
4. Sequence whole constructs rather than junctions. For plasmids, whole construct sequencing now costs little and catches rearrangements and unintended changes that junction reads miss. Reserve single reads for confirming a known edit at a known position.
5. Record the read with the sample, not in an inbox. Traces and consensus sequences belong in the construct or sample record under an identifier. Sequencing results filed as email attachments are results that will be paid for twice.

Turnaround is the real advantage

The reason this chemistry survives is that a sample submitted in the afternoon can be answered the next morning, one construct at a time, without batching. For a laboratory building constructs continuously that responsiveness is worth more than a lower per base cost.

Short read platforms win the moment the work batches naturally, because the fixed cost of a run is shared. The decision is therefore about workflow rhythm as much as about price.

Reading a trace honestly

Look at peak shape and spacing, not just the called bases. Broad, overlapping or shifted peaks indicate a template or chemistry problem, and a caller will happily assign bases through all of it.

Sequence both strands whenever a single base carries the conclusion. Agreement between independent reads is the cheapest confidence available in this technique.

Common questions

Is short read sequencing more accurate?

Per base in a deep dataset, yes, because coverage provides consensus. For a single amplicon read by an experienced eye, single read chemistry gives a long, contiguous, inspectable trace that is entirely adequate and far faster.

How long a read should I expect?

Several hundred usable bases after the primer, with quality falling at both ends. Design around the reliable middle rather than the theoretical maximum, and cover long regions with overlapping reads.

What causes a mixed peak?

A genuine heterozygous position, a mixed template such as an unpurified colony pool, or contamination from another amplicon. Distinguishing them requires the trace and often a re read from a clean template.

Should plasmids still be verified this way?

For confirming a known point change, yes. For accepting a newly built construct, whole plasmid sequencing is now the better economy because it catches the failures that a targeted read cannot see.

Browse by service class

• Compare Gene synthesis on advertised prices