Prescription capture
If you come from Shopify rather than from optics, start with the glossary. Setting this step up is far easier once you know what you are asking the customer for.
Glossary: what each value means
Section titled “Glossary: what each value means”A spectacle prescription is a list of numbers, one set per eye. Here is what they mean:
| Abbreviation | Name | What it does |
|---|---|---|
| OD | Right eye | From the Latin oculus dexter. It is the right eye in every country |
| OS / OI | Left eye | OS in English (oculus sinister); Spanish prescriptions write OI |
| SPH | Sphere | The main correction. Negative for short-sightedness (poor distance vision), positive for long-sightedness (poor near vision) |
| CYL | Cylinder | Corrects astigmatism: the cornea isn’t perfectly round, so the image comes out distorted. Usually negative, and can be 0 |
| AX | Axis | The angle that cylinder sits at, from 0 to 180 degrees. Only meaningful when there is a cylinder |
| ADD | Addition | Extra power for close-up vision. Appears on progressive and bifocal lenses, from the mid-forties onwards. Always positive |
| PD | Pupillary distance | The millimetres between the centre of one pupil and the other. Used to centre the lenses in front of the eyes. Adults are typically between 54 and 74 mm |
| Prism (Δ) | Prism | Shifts the image so both eyes see the same thing, for example with double vision. Written in prism dioptres (Δ) with its base: in (toward the nose), out (toward the ear), up or down. Few prescriptions carry it |
Dioptres are measured in steps of 0.25. That is why the dropdowns jump like this: -1.00, -1.25, -1.50…
The two step types
Section titled “The two step types”- Graduation (Rx) — a full prescription, with every value above. For genuine prescription eyewear.
- Reading Rx (grid) — just a magnification (
+1.00,+1.50…). For pre-made reading glasses, the ready-to-wear kind that carry no prescription.
Graduation (Rx) step
Section titled “Graduation (Rx) step”Captures the values for each eye: OD (right) and OS (left).
When you open the step in the editor, its settings sit in four sections you can fold and unfold. Folded, each one sums up on the right what it holds, so you don’t need to open them to see how the step is set up:
| Section | What it holds |
|---|---|
| What we ask the customer | Opens by default. Sphere, cylinder and axis are always asked; here you decide whether to also ask for the Addition (ADD), the Interpupillary distance (PD) and Prism, and whether the customer can upload a photo of the prescription instead of typing it |
| Values they can choose | A table with From, To and In steps of for each field |
| Help for the customer | The “?” on each field and the sample prescription, with their texts right below |
| Step texts | Everything the customer reads: the eyes, the field names, the PD, the tabs and the summary. Folded, it says “The store language’s own” or how many texts you changed |
What we ask the customer
Section titled “What we ask the customer”- Addition (ADD), for progressives and bifocals — turn it on only if you sell progressives or bifocals. On ordinary glasses it is noise.
- Interpupillary distance (PD) — see Pupillary distance, below.
- Prism — off by default. See Prism, below.
- Allow uploading a photo of the prescription instead of typing it — two tabs appear at the top of the step, “Enter manually” and “Upload photo”. Right below, you choose the file types and the maximum size. See Uploading the prescription.
Values they can choose
Section titled “Values they can choose”Each row of the table is a field: Sphere (SPH), Cylinder (CYL), Axis (AX) and, when they are enabled, Addition (ADD), PD in mm, PD per eye in mm and Prism (Δ). Set them to what your lab can actually make: if you don’t work below -8, put -8 in From and customers can’t order it.
The axis switches on with the cylinder
Section titled “The axis switches on with the cylinder”All three values for each eye — sphere, cylinder and axis — start empty. Not at 0.00: zero is a real clinical value, it means “no astigmatism”, and it can’t be confused with “I haven’t filled this in yet”.
The axis field also starts switched off, greyed out and untouchable. It only switches on once the customer enters a cylinder other than zero, because an axis with no cylinder means nothing — it is the angle of something that doesn’t exist. If the customer goes back and clears the cylinder, the axis empties and switches off again.
And the other way round: if there is a cylinder, the axis is required. The app won’t move past the step until it is filled in.
There is nothing to configure here: it works this way in every form, always.
Pupillary distance
Section titled “Pupillary distance”- Interpupillary distance (PD) — in What we ask the customer, adds pupillary distance capture.
- How they enter it — right below: Free text (they type the number), the historical behaviour, or Dropdown with the allowed values. The dropdown avoids typos and values your lab cannot make; free text is faster for someone who knows their PD. It starts at “—”: nobody has a default PD.
- The millimetres — in Values they can choose, the rows PD in mm (40 to 85 by default) and PD per eye in mm (20 to 45). The PD’s In steps of column only appears with the dropdown (0.5 by default). They are both what the dropdown offers and what the free text accepts: a customer who types 6 instead of 63 gets a warning, not an impossible order.
- Single or per-eye PD — one number (the usual case), or one per eye. The customer switches with a toggle.
- Messages if it is missing — what they are told if they leave it blank. They live in Step texts, with the rest of the PD texts.
- If they type a value out of range, the warning shows under the field as soon as they leave it, with the range (“Per eye, between 20 and 45 mm”) or with what probably happened: 65 in each eye is almost always the total PD typed twice (“This looks like your total PD: if your prescription has one number, switch off the two-values option”), and 32 as a single value is almost always a per-eye value. Once corrected, the warning goes away. If they press Next with the PD wrong or blank, the focus goes to the failing field. If you would rather they could not get it wrong at all, the dropdown with the allowed values above prevents it outright.
The customer gets help on every field
Section titled “The customer gets help on every field”Your customer is not an optician. They are holding their prescription and do not know what a cylinder is, whether the axis carries a sign, or which of the numbers is the pupillary distance. That is why every field in the step has a small “?” to the right of its label — SPH, CYL, AX, ADD and the PD title — which opens a short, plain-words explanation on hover, tap or keyboard: what the value is, which sign it takes and where to find it on the prescription.
It comes switched on in every form, with texts already written in your store’s language. There is nothing you need to do.
What you can do:
- Switch it off — in Help for the customer, untick Show a help icon next to each prescription field. All five “?” disappear at once.
- Rewrite the texts — right below that checkbox, in the same section. Each box shows up empty with the default text in grey, in your store’s language — the same text your customer reads. Type over it to say it your way — for instance, with the notation your lab uses — and if you empty the box, it goes back to the default (how it works, in Languages & wording). The ADD and PD texts only appear when those fields are enabled.
- Translate them — like every other label, from each language’s tab. See Languages & wording.
The “?” icons use the same colour, size and background settings as the ones on the form’s options. Change them under Design & cart, section Tooltips and help.
And a sample prescription
Section titled “And a sample prescription”At the top right of the step there is a link, “How to read your prescription”, which opens a sample prescription built with your own labels: two eyes with SPH, CYL and AX (and ADD if you have it enabled), and the PD underneath. The customer taps a column and the app highlights it and explains that value with the same help text as the matching “?”. It is what helps most someone holding a paper prescription: they see where each number sits in an example that looks like theirs.
It comes switched on. Turn it off in Help for the customer (Show a “How to read your prescription” link with a sample prescription); right below, you rewrite the link text, the caption above the sample and the hint under the sample. The explanations are the same as the “?” ones: change one and it changes in both places.
Some prescriptions carry prism: a value in prism dioptres (Δ) with its base, which shifts the image so both eyes see the same thing. They are few, but a customer who needs it cannot buy if the form doesn’t ask for it.
In What we ask the customer, the Prism dropdown has three options:
- Off — the default. The step stays as it always was.
- The customer says whether their prescription has prism — a switch appears under both eyes, “My prescription includes prism”. Off, nothing changes; switched on, the prism fields open.
- Always shown — the prism fields show open, with no switch, and at least one value must be filled in to move on. Use it only on a step reached by someone who already said their prescription has prism (see charging for it, below).
For each eye, the customer copies from their prescription the horizontal prism with its base, In (BI) or Out (BO), and the vertical one, Up (BU) or Down (BD). The base unlocks once an amount is chosen, and the step won’t move on with an amount and no base, or with the switch on and everything empty.
In Values they can choose, the Prism (Δ) row sets the maximum value (5 by default, 10 at most) and whether it goes in steps of 0.25 or 0.50.
The prism “?” already warns the customer about two things that are often mixed up: that on Spanish prescriptions “BI” usually means base down (base inferior), not base in, and that with prism the lab needs the PD for each eye.
Changing the texts
Section titled “Changing the texts”Everything the customer reads in this step is rewritten in Step texts, without touching code: the eye titles, the field names, the PD texts, the “Enter manually” and “Upload photo” tabs and the summary. Those of a feature that is off (ADD, PD, the tabs) don’t show. Before you change them, read Languages & wording — the boxes come pre-filled in English and there is a catch.
Graduation summary step
Section titled “Graduation summary step”Shows the customer the prescription they just entered before adding to cart: a table with your labels as headers (SPH, CYL, AX and ADD if present), one row per eye and the PD underneath — the same layout as the sample prescription in the previous step, so they never have to guess which number is which.
Add it whenever you capture full prescriptions. It is the last chance for the customer to spot their own mistake, and it saves you returns.
If the customer uploaded a photo of their prescription instead of typing it, the summary shows them the image, not just the file name. That is the difference between confirming prescription.png and confirming the numbers that are about to be manufactured: a wrong file — a gym receipt, a screenshot of something else — is obvious at a glance. If they uploaded a PDF, which can’t be drawn, a document icon appears with the name and the size.
Reading Rx (grid) step
Section titled “Reading Rx (grid) step”For pre-made reading glasses, where the customer only picks a magnification.
- Powers it offers — From, To, In steps of and Columns of the grid, the same names as the prescription table, with a live preview of the values it generates.
- Value prefix — usually
+, so it reads+1.50.
How the prescription reaches the order
Section titled “How the prescription reaches the order”When the customer adds to cart, the prescription travels inside the Shopify order, alongside the product. You see it on the order detail in your usual admin, and it carries through to whatever you send your lab.
It is written one line per eye, each value preceded by its field’s label — yours, in the customer’s language — so anyone can read it without knowing the order of the numbers:
Frame type: Prescription glassesLens type: Standard thin lensesOD: SPH -2.50 · CYL -1.25 · AX 90° · ADD +1.50OS: SPH -3.00 · CYL 0.00 · AX — · ADD +2.00PD: 63An eye without a cylinder has no axis: it prints AX —, just like the addition when only one eye has it — never a made-up 0° an optician would read as a real axis. It is the same line the customer sees in the cart, at checkout and in the confirmation email.
If the customer entered prism, each eye carries one more value at the end, with the amount and base of each component joined by +, and — on the eye without it:
OD: SPH -2.50 · CYL -1.25 · AX 90° · PRISM 2.00 BI + 1.00 BUOS: SPH -3.00 · CYL 0.00 · AX — · PRISM —In Spanish it comes out in words: PRISMA 2.00 nasal + 1.00 superior. If nobody enters prism, the line is exactly the usual one.
If you have an integration with your practice software, the same prescription also travels in the hidden property you agreed with it, in the format that software expects (there an empty axis does go as 0, because that is what its contract asks for). See Integration.
If the customer uploads a photo of their prescription instead of typing it, the order shows the file name. See Uploading the prescription.
Tagging the orders that include configured glasses
Section titled “Tagging the orders that include configured glasses”If you want to tell at a glance which orders go to the lab — to filter them in your orders list or alert your team — Shopify Flow can tag them automatically. You set it up once:
- In your admin, open the Flow app and create a new workflow (Create workflow). If you don’t see Flow, install it from the Shopify App Store: it’s called Shopify Flow.
- Choose the trigger Order created.
- Add a condition. Choose At least one of order / line items and, inside it, At least one of custom attributes. There:
- Key · Equal to ·
_ofd_type - click the Add criteria that says for customAttributes_item list item and add Value · Equal to ·
main, joined with AND.
- Key · Equal to ·
- If you have an integration with your practice software, add the same block with
_p_productTypeinstead of_ofd_type, joined to the first one with OR. - On the True branch, add the action Add order tags with the tag
Prescription Order, or whichever tag your store uses. - Turn the workflow on.
Under each field Flow shows its path (order.lineItems.customAttributes.key and order.lineItems.customAttributes.value), so you can find them even if your admin is in another language.
From then on, every new order that includes a bundle configured with Optical Form gets the tag. Ordinary orders and add-ons bought on their own are left alone.
The workflow doesn’t read the prescription: it looks for the hidden property the app puts on the frame of each bundle (_ofd_type = main, or _p_productType = main if you have an integration with your practice software). That’s why it works the same in any language and whatever you call your fields.