Order Schema Generator and Guide

Order

Schema.org Type

An order is a confirmation of a transaction (a receipt), which can contain multiple line items, each represented by an Offer that has been accepted by the customer.

Generate this schema

We Can Help

Order schema is a sub type of:

This schema has no sub types

Order Schema Generator in JSON-LD

Create Knowledge Graph

Order schema code:

This Schema can take the following complex properties:


How to Create a Order Schema

Step 1: Fill out the form above as much as possible.

Note:Use this Schema.org based structured data generator tool to easily create Order schema.
The properties are the description of your entity. You don't have to fill in all the properties on this page. Provide what is available and leave what is not. To learn more about each property in your schema type please check Order schema properties


Step 2: When complete click the Copy Code button to get your JSON-LD code

Notes:To check if your code is eligible for featured snippets (rich snippets or rich results) test your code with the Rich Results Test tool to learn more about which schema are qualified for rich results check out Google’s search gallery.
To validate your markup code, check your JSON-LD code with the Schema Markup Validator


Step 3: To add a sub-schema, click on the Create Knowledge Graph button

Important Notes: to describe the relationship between your entities you must design a custom schema, this is where the 'creation of knowledge graph' is needed.
For example: if you have a local business and you want to add a service catalogue, or if you have a recipe schema and you want to add a HowTo steps, or if you have a product and you want to add a FAQ about it, to learn more watch this semantic SEO workshop




Generate this schema

Hire Us


Order Schema Properties

Order has 34 properties:

  • acceptedOffer The offer(s) -- e.g., product, quantity and price combinations -- included in the order.
  • additionalType 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.
  • alternateName An alias for the item.
  • billingAddress The billing address for the order.
  • broker An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred.
  • confirmationNumber A number that confirms the given order or payment has been received.
  • customer Party placing the order or paying the invoice.
  • description A description of the item.
  • disambiguatingDescription A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.
  • discount Any discount applied (to an Order).
  • discountCode Code used to redeem a discount.
  • discountCurrency The currency of the discount.

    Use standard formats: ISO 4217 currency format e.g. "USD"; Ticker symbol for cryptocurrencies e.g. "BTC"; well known names for Local Exchange Tradings Systems (LETS) and other currency types e.g. "Ithaca HOUR".
  • identifier The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.
  • image An image of the item. This can be a URL or a fully described ImageObject.
  • isGift Was the offer accepted as a gift for someone other than the buyer.
  • merchant 'merchant' is an out-dated term for 'seller'.
  • mainEntityOfPage Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details.
  • name The name of the item.
  • orderDate Date order was placed.
  • orderDelivery The delivery of the parcel related to this order or order item.
  • orderNumber The identifier of the transaction.
  • orderStatus The current status of the order.
  • orderedItem The item ordered.
  • partOfInvoice The order is being paid as part of the referenced Invoice.
  • paymentDue The date that payment is due.
  • paymentDueDate The date that payment is due.
  • paymentMethod The name of the credit card or other method of payment for the order.
  • paymentMethodId An identifier for the method of payment used (e.g. the last 4 digits of the credit card).
  • paymentUrl The URL for sending a payment.
  • potentialAction Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
  • sameAs URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.
  • seller An entity which offers (sells / leases / lends / loans) the services / goods. A seller may also be a provider.
  • subjectOf A CreativeWork or Event about this Thing.
  • url URL of the item.