✓ TestedWorks with CSV, Excel, Google Sheets → JSON-LD Schema
By dataclean.to team · 2026-02-05
B2B offer data converts into Schema.org Offer markup for products and services. Structured pricing, availability, and terms help search engines understand commercial offerings. This process transforms spreadsheet data into valid JSON-LD that meets schema requirements.
The Problem
B2B companies maintain offer data across multiple systems with inconsistent formatting. Pricing fields mix currencies, availability states vary, and valid-through dates use different formats. Manual schema creation for hundreds of offers takes excessive time and introduces errors. Automated conversion ensures consistent structured data while maintaining offer details like seller information, item conditions, and warranty terms. Schema.org Offer Specification
How to Fix It
1
Upload B2B Offer Data
Import CSV or Excel files containing offer information including SKU, price, currency, availability, and valid dates. System identifies offer-specific columns.
2
Map Offer Properties
Match spreadsheet columns to Schema.org Offer properties like price, priceCurrency, availability, validFrom, validThrough, seller, and itemOffered.
3
Normalize Pricing Data
Standardize currency codes to ISO 4217 format, validate price formats, and ensure availability values match schema enumeration like InStock or OutOfStock.
4
Generate Offer Schema
Create JSON-LD structured data for each offer with proper nesting of seller Organization and itemOffered Product or Service entities.
5
Export Schema Files
Download individual JSON-LD files or bulk export all offer schemas with validated structure ready for website implementation.
Frequently Asked Questions
What offer properties are required?
Required properties include price and priceCurrency. Recommended properties include availability, itemOffered (Product or Service), seller (Organization), validFrom, and validThrough dates.
How are currency codes standardized?
The tool converts common currency symbols and names to ISO 4217 three-letter codes like USD, EUR, GBP that Schema.org requires for priceCurrency.
Can I include warranty information?
Yes, warranty details map to the warranty property using WarrantyPromise type with duration, scope, and warrantyScope fields defined in schema specifications.
Example: Input → Output
name
email
phone
city
status
Alice Johnson
alice@example.com
+1-555-0101
New York
active
alice johnson
ALICE@EXAMPLE.COM
5550101
new york
Active
Red rows show common data quality issues. dataclean.to normalizes and generates JSON-LD automatically.