Datadory notebook
How E-commerce Operators Use Drug Retail Data
E-commerce operators use drug retail data to anchor catalogs on NDC codes, generate compliant label copy, gate listings against recalls, and price against chain and coupon benchmarks. The working stack pairs two openFDA catalog APIs with three safety feeds, GoodRx cash prices and Walgreens shelf JSON - and all 16 primary drug-retail datasets Datadory catalogs are free.
1,744 datasets. Pick your catch.
Which dataset becomes your product master?
The openFDA NDC Directory API is the spine everything else keys to: 137,206 marketed finished drug products submitted under the Drug Listing Act of 1972, one row per product with nested rows per package and per active ingredient, refreshed daily and downloadable as a single ~26.8 MB zipped JSON partition. Documented fields cover product_ndc, package-level package_ndc, brand_name, generic_name, labeler_name, dosage_form, route and dea_schedule, alongside marketing_start_date and marketing_end_date reaching back decades.
How do you write compliant product pages without hiring a copywriter?
Copy in this category cannot be improvised, and the openFDA Drug Label API (Structured Product Labeling) removes the need: 261,996 SPL label records carrying section-level text arrays - indications_and_usage, dosage_and_administration, boxed_warning, adverse_reactions, drug_interactions, active_ingredient - keyed by NDC so they snap onto the catalog spine. Coverage runs mostly from June 2009 onward, refreshes weekly, and the full archive ships as 14 zipped JSON partitions totaling about 1.77 GB under commercial delivery terms.
Which safety checks gate a listing before it goes live?
The openFDA Drugs@FDA API confirms regulatory standing with 29,273 applications dating to 1939, carrying sponsors, submissions, marketing status and therapeutic equivalence codes, refreshed on weekdays from a one-file bulk export. After launch, the openFDA FAERS Adverse Event API closes the loop with 20,692,690 safety reports from 2004 Q1 onward across roughly 113.7 GB of quarterly partitions, lagging several months because FDA refreshes quarterly. Reports are voluntary and unvalidated, so they raise questions rather than settle them; the openFDA Drugs@FDA API vs FAERS Adverse Event API comparison separates the pre-listing and post-listing jobs.
Pick up where this leaves off
Every one of these ships with sample rows before you commit to anything.
GoodRx Drug Prices & Pharmacy Finder
Kaggle Pharmacy & Drug Retail Datasets
NLM Clinical Table Search Service
DISPLAY_NAME · DISPLAY_NAME_SYNONYM · STRENGTHS_AND_FORMS …+4 more
openFDA Drug Enforcement / Recall API
center_classification_date
openFDA Drug Label API (Structured Product Labeling)
openFDA Drugs@FDA API
Want rows instead of a pitch? Name the datasets.
API, files, or your warehouse. Daily, weekly, or hourly.
Get a sampleQuestions worth asking
Where can I get prescription drug price data for my store?
GoodRx is the richest open option: roughly 6,700 drug price pages comparing cash and coupon prices across more than 70,000 U.S. pharmacies, server-rendered as HTML with dosage-level tables and JSON-LD, refreshed daily through sitemaps. There is no official API, so access means crawling pages whose robots.txt disallows /coupon and /search paths.
How do I get NDC codes with package sizes?
Use the openFDA NDC Directory API: 137,206 marketed finished drug products submitted under the Drug Listing Act of 1972, one row per product with nested package and active-ingredient rows. It refreshes daily, ships as a ~26.8 MB zipped JSON bulk partition, and carries marketing start and end dates reaching back decades.