How to get LegitScript certified
You apply as the entity that operates the program. The application documents who owns the business, where the providers are licensed, which pharmacy dispenses, and how the site sells the offer. Most of the work is assembling accurate detail rather than writing anything persuasive.
Who does the application belong to?
The certification attaches to the business behind the offer, not to a brand name and not to a platform. A med spa adding prescription programs applies as the med spa.
That matters because the review examines ownership and control. A submission that describes the patient-facing brand without describing the entity behind it cannot be reviewed.
What does the application ask for?
- the entity that owns and operates the program
- where each provider is licensed, and the states you serve
- the pharmacy that dispenses, and how it is licensed
- the site itself, including how the offer is presented and priced
- how complaints, refunds and chargebacks are handled
What order do the steps run in?
- Confirm the entity and ownership detail, because everything else references it.
- Collect provider licensing and the states you will actually serve.
- Confirm the pharmacy arrangement and its licensing.
- Align the site so what it advertises matches what you are submitting.
- Submit, then answer questions in one pass rather than several.
What gets an application sent back?
Mismatches cause it. Three show up most often:
- the site advertises states you are not licensed in
- the pharmacy is not named
- the brand does not plainly belong to the entity applying
The review is reading for consistency between the business, the paperwork and the storefront. Where those three disagree, the reviewer has to ask, and each round trip costs time.
Where does a platform help?
A platform that already holds certification, or already files regularly, removes the assembly work and keeps the storefront consistent with the submission. That is the part most owners underestimate, because the site and the application drift apart easily when two different people build them.
What does each step produce?
| Step | What you end up with |
|---|---|
| Eligibility check | A decision to proceed, or a reason to change the model first. |
| Documentation | Ownership records, licences, pharmacy details, complaint process. |
| Submission | A complete file, or a request for more information. |
| Review | Questions about anything the site and the file describe differently. |
| Decision | Certification, or a list of items to resolve and resubmit. |
The documentation step decides the others. Files that arrive complete move. Files that arrive in pieces get questions, and questions cost weeks.
What should you gather before you start?
About the business
- Which entity operates the site, and who owns it.
- Registration documents for that entity.
- Who is authorised to sign on its behalf.
About the clinical side
- Which providers prescribe, and the states each is licensed in.
- How a patient is assessed before a prescription is written.
- What happens when a patient reports a side effect.
About the pharmacy and the site
- The dispensing pharmacy, and what it is licensed to dispense.
- The pages that describe and sell the offer.
- How a patient raises a complaint, and who answers.
Collect all three groups before you open the application. The reviewer is comparing these against each other, so an answer that is missing in one group becomes a question about another.
Who should actually file it?
Whoever can answer follow-up questions about the business, which usually means the owner rather than an agency.
A filing service can upload documents. It cannot explain why your site sells into a state your provider list does not cover, and that explanation is the thing the review wants. Where a platform files on your behalf, it should be able to answer those questions from its own records rather than forwarding them to you.