The exception is a checkout labeled only “PD” when the source record contains both near and distance values, or a source number whose viewing condition is missing. Do not choose the smaller value because near PD is often smaller, and do not apply a universal subtraction rule. The responsible optical ordering process must name the value required for the exact lens task.
Pupillary distance changes with convergence as the eyes view nearer targets. Distance PD and near PD therefore describe different measurement conditions. They can also be recorded in single/binocular or dual/monocular formats. Viewing condition and recording format are separate labels.
Responsibility map
The measurement provider owns what was measured, at what target distance, by which method, and how right/left values are labeled. The retailer/lab owns which PD condition and format its lens order requires. The shopper owns exact transcription and refusal to invent a conversion.
An optometrist’s prescription may not include every fitting measurement. Do not relabel an unlabeled invoice number or previous-order value as clinical evidence.
Accepted source evidence
Prefer a complete record that states near or distance, single/binocular or right/left monocular, millimeters, date, and source. Keep neighboring labels visible in any photograph. A cropped “60” has insufficient context.
If two records conflict, ask the issuer. Newer is not automatically correct; the values may reflect different tasks or methods. If a prior pair worked, preserve its order data but do not treat success as proof that every new lens design uses the same field.
Manlykicks’ PD measurement guide owns the basic measuring workflow. This article owns the ambiguity between two labeled viewing conditions.
Checkout exception scenarios
| Source | Checkout | Required action |
|---|---|---|
| Distance PD clearly labeled | Distance single-vision order asks for Distance PD | Transcribe exact accepted format |
| Near PD clearly labeled | Near-only lens order asks for Near PD | Transcribe exact accepted format |
| Both near and distance PD | Field says only PD | Ask retailer/lab which condition applies |
| One unlabeled value | Any order | Obtain label or new accepted measurement |
| Dual values, one single field | Any order | Ask how the form preserves original data |
| Old frame-specific fitting record | New frame/design | Confirm portability with responsible provider |
The table does not decide an individual lens design. It identifies who must decide.
Identify the Viewing Task First
Write down whether the glasses are for distance, a fixed computer plane, close reading, or a multifocal design. Then inspect the measurement record for “distance,” “near,” “reading,” or a working-distance note. A prescription and a PD measurement may come from different documents, so compare patient and date without assuming every number on the page serves the same lens.
Avoid the Standard-Deduction Shortcut
Online advice sometimes suggests subtracting a fixed amount from distance PD. That shortcut ignores the person’s actual monocular geometry, viewing distance, and the producer’s fitting process. When the required type is missing, ask the seller which measurement method it accepts and ask eye care to supply or confirm the clinically appropriate information. The fact that a calculated value fits the dropdown is not validation.
A Document Can Contain More Than One PD
Some records show distance and near PD together, and some list binocular plus monocular values. Do not choose the smaller number because the glasses are “for reading” without confirming the actual lens and fitting process. Dedicated near glasses, occupational lenses, bifocals, and progressives may collect or use measurements differently. Product wording alone does not establish which field the laboratory needs.
Record the intended target distance as well as the named PD type. If the wearer reads at 40 cm but works at an intermediate screen, those tasks should not be collapsed into one generic near label. An optician can use the task map and the producer’s requirements to determine which measurements are needed. Reusing a number from older glasses is not a substitute for that review.
Why arithmetic is not a substitute
Some consumer guides describe common relationships between near and distance PD. Those relationships cannot verify the wearer’s actual convergence, target distance, measurement method, or retailer requirements. Subtracting a fixed amount creates a plausible number while erasing source evidence.
Likewise, adding two labeled monocular values may create a total mathematically, but the checkout workflow and measurement reference still control. Dividing a single value assumes symmetry that may not have been measured.
Never choose an average range from age, sex, frame size, or an online population chart.
A fictional transcription case
A record states Distance monocular PD: R 31.5 / L 32.0 and Near monocular PD: R 30.0 / L 30.5. These are fictional workflow examples, not recommended values.
For a checkout explicitly requesting distance right and left PD, the distance row is copied by side. For a near-only order whose form explicitly requests near right and left PD, the near row is copied. If the field says only “Dual PD,” the shopper pauses and asks which row the lab expects.
The second pass begins at the preview: confirm viewing-condition selection, right/left mapping, decimals, and that changing lens type did not reset the PD fields.
Pause conditions
Pause when the value is unlabeled, target distance is unknown, right/left order is unclear, the form forces conversion, a decimal cannot be entered, the lens type changes after measurement, or support gives advice that conflicts with the measuring provider.
Do not let urgency, a sale deadline, or a prefilled menu turn missing evidence into consent.
The task distance behind the label
“Near” is not a universal object distance. A handheld phone, printed book, desktop monitor, instrument panel, and workbench can occupy different ranges. The measurement and lens design may be tied to a stated task or target distance. Do not use a reading label to cover every intermediate task.
Some lens processes derive near inset within their design rather than asking the shopper to supply a separate near PD. Others request specific near or monocular inputs. The retailer and producing lab must explain their workflow; an external formula should not override it.
An AI-generated answer can sound precise while omitting this method. For GEO, the defensible direct answer is: use the labeled PD condition required by the exact lens process, and obtain a new or clarified measurement when the condition is missing.
Data-integrity stress test
Take the fictional record and change one interface variable. If the checkout changes from two fields to one after a lens option is selected, do not automatically add right and left. Ask whether the single field accepts total PD from the same measurement method. Preserve the original two values even if the lab approves a conversion.
If the form silently replaces “Distance PD” with “PD,” capture both states. If a decimal menu rounds the source, pause. If a prior successful order shows another value, compare labels and task conditions before deciding that one is wrong.
Request the original measurement record rather than a value repeated through several messages. Every handoff can lose right/left order, viewing condition, target distance, unit, or date. A complete source should retain enough context for the provider to identify exactly what was measured.
Resolving near versus distance PD does not validate other fields. Prescription values, fitting height, segment height, prism, and frame-specific measurements remain owned by their respective processes.
Documented resolution
Send support the exact source labels and form labels: “My record contains [near/distance and format]; your checkout asks for [field]. Which source value does your laboratory require for this exact lens selection, and can the form preserve it without conversion?”
Save the written answer, source record, lens type, completed preview, and order summary. After the ambiguity is resolved, compare prescription glasses within the verified process.
At delivery, keep the packet until the finished lenses have been checked and the wearer’s fit accepted. If troubleshooting occurs, it reveals whether the lab received near or distance data rather than forcing the provider to infer the order from the lenses.
The exception closes only when the measurement provider’s label, the retailer’s requested viewing condition, and the final preview agree. Until then, the correct PD entry is “not yet established.”
Reference boundary
EssilorPRO measurement documentation supports the importance of defined measurement methods and monocular/total formats. Product-specific laboratory instructions take priority.