UnitPriceSpecification

schema:Thing > schema:Intangible > schema:StructuredValue > schema:PriceSpecification > schema:UnitPriceSpecification

The price asked for a given offer by the respective organization or person.
PropertyExpected TypeDescription
Properties from schema:UnitPriceSpecification
schema:billingIncrement schema:Number This property specifies the minimal quantity and rounding increment that will be the basis for the billing. The unit of measurement is specified by the unitCode property.
schema:priceType schema:Text A short text or acronym indicating multiple price specifications for the same offer, e.g. SRP for the suggested retail price or INVOICE for the invoice price, mostly used in the car industry.
schema:unitCode schema:Text The unit of measurement given using the UN/CEFACT Common Code (3 characters).
Properties from schema:PriceSpecification
schema:eligibleQuantity schema:QuantitativeValue The interval and unit of measurement of ordering quantities for which the offer or price specification is valid. This allows e.g. specifying that a certain freight charge is valid only for a certain quantity.
schema:eligibleTransactionVolume schema:PriceSpecification The transaction volume, in a monetary unit, for which the offer or price specification is valid, e.g. for indicating a minimal purchasing volume, to express free shipping above a certain order volume, or to limit the acceptance of credit cards to purchases to a certain minimal amount.
schema:maxPrice schema:Number The highest price if the price is a range.
schema:minPrice schema:Number The lowest price if the price is a range.
schema:price schema:Text  or
schema:Number 
The offer price of a product, or of a price component when attached to PriceSpecification and its subtypes.

Usage guidelines:
  • Use the priceCurrency property (with ISO 4217 codes e.g. "USD") instead of including ambiguous symbols such as '$' in the value.
  • Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
  • Note that both RDFa and Microdata syntax allow the use of a "content=" attribute for publishing simple machine-readable values alongside more human-friendly formatting.
  • Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similiar Unicode symbols.
schema:priceCurrency schema:Text The currency (in 3-letter ISO 4217 format) of the price or a price component, when attached to PriceSpecification and its subtypes.
schema:validFrom schema:DateTime The date when the item becomes valid.
schema:validThrough schema:DateTime The end of the validity of offer, price specification, or opening hours data.
schema:valueAddedTaxIncluded schema:Boolean Specifies whether the applicable value-added tax (VAT) is included in the price specification or not.
Properties from schema:Thing
schema:additionalType schema:URL An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally.
schema:alternateName schema:Text An alias for the item.
schema:description schema:Text A short description of the item.
schema:image schema:URL  or
schema:ImageObject 
An image of the item. This can be a URL or a fully described ImageObject.
schema:name schema:Text The name of the item.
schema:potentialAction schema:Action Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
schema:sameAs schema:URL URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Freebase page, or official website.
schema:url schema:URL URL of the item.

Prefixes used:

  • schema: http://schema.org/
  • Acknowledgements

    This class is derived from the GoodRelations Vocabulary for E-Commerce, created by Martin Hepp. GoodRelations is a data model for sharing e-commerce data on the Web that can be expressed in a variety of syntaxes, including RDFa and HTML5 Microdata. More information about GoodRelations can be found at http://purl.org/goodrelations/.

    Schema.org Version 1.93
    BiblioGraph.net Version 1.1
    Code Version 1.1