This topic describes different ways partners can group their content into packages of special interest for customers.
Season offers
A season offer allows customers to buy or rent an entire season of a TV show in a single transaction. By purchasing a season offer, customers receive access to all of the season’s content immediately. A full season offer may also be available to customers at a lower price, compared to their purchasing individual episodes.
Delivery requirements:
- Season-level requirements: Avails, assets, metadata
- Episodic-level requirements: All episodes in the season have been delivered with the same start date, or all start dates are in the past.
Marketplace: Season offers are available in Global and Classic territories.
Season passes
A season pass allows customers to buy or rent an entire season of TV episodes in a single transaction. Customers receive access to each episode on a progressive basis until all episodes are live. This often aligns with the show’s broadcast schedule.
Delivery requirements:
- Season-level requirements: Avail, assets, metadata
- Episodic-level requirements:
- At least one episode is delivered with all requirements met.
- At least one episode in the season is availed with a start date in the future; metadata and assets are not required.
- For Sports Data Platform (SDP) content, it is recommended for partners to deliver metadata at least 24 hours before the season pass is scheduled to launch.
Marketplace: Available in Classic territories.
TV box sets
This section describes how to deliver TV box sets as “bundles” of content.
TV box sets are purchasable bundles that include all completed seasons within a series. They allow customers to purchase an entire series at a discounted price. Customers who already own some seasons of a series will see a “Complete your series” option to purchase the rest of the seasons at a discounted price. Each of the individual titles within the TV box set will be available to customers at the highest resolution available. For example, if Season 1 of a series has been delivered in SD and HD and Season 2 has been delivered in SD, HD, and UHD, the customer receives Season 1 in HD and Season 2 in UHD. Customers will see information about the exact resolution they will receive on the confirmation page.
Each TV box set delivery requires:
- A unique identifier/SKU (use the existing identifier/SKU if the series has already been delivered to Prime Video)
- Avails (EMA)
Dedicated metadata (MEC), manifest (MMC), and artwork are not required.
Storefront experience
Customers with the option to purchase a complete TV box set will see a screen similar to the following example.
Customers who click the option to buy a TV box set will see a list of the included seasons, with their respective resolution quality, on the confirmation screen.
Customers who already own some seasons of a TV series will see an option to complete their collection, similar to the following example.
Content rights (EMA avails)
Avail delivery is required to publish TV box sets.
Notes:
- For WorkType = series, since there will be no option for quality-specific TV box sets, Prime Video has launched a new FormatProfile value, Max. This is the recommended value. However, Prime Video still accepts the usual values of HD, SD, or UHD . These values will be converted internally to Max, which partners will be able to see in Slate.
- Partners must submit a single avail with a FormatProfile value of HD, SD, UHD, or Max. If avails are submitted across different FormatProfile values, the avails will be rejected.
TV box set policies for Transactional Video on Demand (TVOD) content are governed by two policy types:
- Downloads: Whether downloading is enabled (On) or disabled (Off).
- AssetRestriction: Controls for language availability (either LanguageHoldbacks or IncludedLanguages).
Important: All policies for TV box sets are inherited from their constituent episode-level policies. You cannot configure policies directly at the TV box set level. If you submit policy values for TV box sets via EMA, these values will be recorded in the system, but they won’t affect actual content behavior. Similar to other optional field validations, any avail submission with values that don’t conform to the expected format for policies will lead to EMA rejections.
The following table lists fields in the EMA avail that are relevant for TV box sets. Please reference the samples available on this page for more information.
Field name |
Definition and notes |
Accepted values |
Prime Video usage |
WorkType |
Type of the work. |
Series |
Required |
SeriesTitleInternal Alias |
The title of the TV box set. |
Required |
|
SeasonCount |
The number of seasons in the series. |
Integer |
Required |
ALID |
Logical Asset ID that references the fulfillment/content package. |
Required |
|
LicenseType |
The type of license being granted. |
EST |
Required |
FormatProfile |
Indicates the resolution of the video covered by the terms. For TV box sets and movie collections, resolution should be specified as Max. Note that other values such as SD, HD, or UHD will be accepted; however, customers will always receive the highest quality available, regardless of FormatProfile input. |
Max (recommended), SD, HD, UHD |
Required |
PriceType |
The type of cost-terms applied to TVOD rights. Please provide WSP and/or SRP pricing inputs. Avails without either of these inputs will be rejected. |
WSP, SRP |
Required |
PriceValue |
Content-specific cost-terms. For WSP and SRP PriceType, PriceValue must be a monetary value. Non-numeric values aren’t accepted. Invalid characters will be rejected. |
Monetary values (for example, 10.49, 13.99). |
Required |
SRP |
Suggested local retail price. Use SRP field if also providing WSP in PriceType field. |
Monetary values (for example, 10.49, 13.99) |
Optional |
SeriesContentID |
Series identifier for metadata. |
Required |
|
RetailerSpare1 |
Percentage discount that will apply to Complete your series purchases. |
Numeric value from 0 to 100 |
Strongly encouraged |
The following table lists the most common reasons a TV box set avail might be rejected, and provides steps to correct each issue.
Rejection reason |
Mitigation steps |
Multiple avail submissions with differing FormatProfile values (HD or SD or UHD or Max), partially or fully overlapping avail windows, and the same pricing values. |
Please specify a single FormatProfile for WorkType = series. |
Multiple avail submissions with the same FormatProfile values (HD or SD or UHD or Max), partially or fully overlapping avail windows, and different pricing values. |
Please enter non-overlapping avail start and end date/time for WorkType = series. |
Multiple avail submissions with the same FormatProfile values (HD or SD or UHD or Max), partially or fully overlapping avail windows, and the same pricing values. |
Please enter non-overlapping avail start and end date/time for WorkType = series. |
Multiple avail submissions with differing FormatProfile values (HD or SD or UHD or Max), partially or fully overlapping avail windows, and different pricing values. |
Please enter non-overlapping avail start and end date/time for WorkType = series and specify a single FormatProfile for WorkType = series. |
A non-numeric value appears in the RetailerSpare1 field. |
Enter a numeric value from 0 to 100 without an decimals or fractions |
Avail submission for WorkType = series is made using EMA 1.6. |
Please upgrade to EMA 1.7. |
Avail submission does not include either a SRP or WSP for WorkType = series |
For wholesale-cost terms, please specify the PriceType as WSP and PriceValue as a monetary value. For revenue-share terms, please specify SuggestedRetailPrice as a monetary value. |
A non-numeric or zero value appears in the SeasonCount field, or the field is blank. |
Enter a non-zero numeric value. |
Avail entries for SeriesAltID, ALID, and SeriesContentID do not match or are missing. |
SeriesAltID, ALID, and SeriesContentID in EMA 1.7 must be identical for WorkType = series. |
Avail submission for WorkType = series has a value other than HD, SD, UHD, 4K, or Max in the FormatProfile field. |
Enter one of the following values: SD, HD, 4K, UHD, or Max. |
Avail submission for WorkType = season, episode, or supplemental has a value other than HD, SD, UHD, or 4K in the FormatProfile field. |
Enter one of the following values: SD, HD, 4K, or UHD. |
Exclude seasons from a “Complete your series” discount
Customers who have already purchased some seasons of a series will be offered remaining seasons via a “Complete your series” Buy Box. The percentage discount that applies to the remaining seasons is defined by the numeric value (for example, 30 = 30% discount) in the RetailerSpare1 field of the TV box set (series-level) avail.
If you do not want to provide a “Complete your series” discount on a particular season, you have 2 options to exclude it from the “Complete your series” discount via the season-level avails for that season.
Note: Prime Video will not apply a “double discount” in the event that you have Temporary Price Reductions (TPRs) or Prime Member Deals (PMDs) running on titles that are part of a TV box set. If a particular season is on TPR or PMD, that season will be automatically excluded from “Complete your series” discounts without further action required from you.
Option 1: New release scenario
If your season just completed, and you want to exclude it from the “Complete your series” discount, use the LicenseRightsDescription field in the season-level EMA avail to designate it as “New Release”. Keep in mind that this value does not automatically turn off. Once time has passed and the season is no longer considered a new release, you will need to deliver an updated season-level EMA avail that removes the “New Release” value from the field.Field name
Definition and notes
Accepted values
Prime Video usage
WorkType
Type of the work.
Season
Required
LicenseRightsDescription
Content type. Specify as New Release to exclude title from Complete Your Series discount. If the property is left blank, the title will be considered as Library. If you already use this field to tag content SDP (Same Day Production) or SWP (Same Week Production), you can use Option 2 below.
Note: Any input in this field will be applied across all quality types during that time period.
New Release
Required
Option 2: All other scenarios
If for any other reason you want to exclude a season from the “Complete your series” discount, use the OtherTerms field in the season-level EMA avail to designate it as “Excluded from bundle discount”. Keep in mind that this value does not automatically turn off. Once you no longer want to exclude the season from the “Complete your series” discount, you will need to deliver an updated season-level EMA avail that removes the “Excluded from bundle discount” value from the field.Field name
Definition and notes
Accepted values
Prime Video usage
WorkType
Type of the work.
Season
Required
OtherTerms
Excluded from bundle discount
Required
Validation rules
For TV box sets, these validation rules must be satisfied:
- Season avail start dates ≤ series avail start date
- Season avail end dates ≥ series avail end date
- Series avail SeasonCount = number of completely aired seasons within the series
- All seasons must meet publishing requirements
- Series offer price < sum of season prices
- Season avail must have the right SeriesAltID in 1.6v+ or SeriesContentID in 1.7v+
- Episode avail must have the right SeasonAltID in 1.6v+ or SeasonContentID in 1.7v+
Samples
The following sample file provides examples that you can edit to reflect your own information. Right-click the link and select Save link as to save the file to your computer. You can then make changes in Excel.
Sample_Amazon_EMA_Avails_Movies-TV_Bundles.xlsx
FAQs for TV box set bundles
Movie collections
This section describes how to deliver movie collections as “bundles” of content. (For information about delivering TV box sets instead, see TV box sets earlier in this page.)
A movie collection is a purchasable bundle of related movie titles (for example, every James Bond movie ever). They allow customers to purchase all of the movies in the collection at a discounted price. Customers who already own some of the movies in the collection will see a “Complete your bundle” option to purchase the rest of the movies at a discounted price. Each of the individual titles within a movie collection will be at the highest resolution available. For example, if Movie A in a collection is available in SD and HD and Movie B is available in SD, HD, and UHD, the customer receives Movie A in HD and Movie B in UHD.
Each movie collection delivery requires:
- A unique identifier/SKU
- Avails (EMA)
- Dedicated metadata (MEC)
- Artwork
- Dedicated manifest (MMC) only if used for delivery of artwork
Note: Movie collections are not compatible with Classic spec offers. All individual movie titles in a collection need to be in the Global spec.
Storefront experience
Customers with the option to purchase a complete movie collection will see a screen similar to the following example.
Customers who click the option to buy a movie collection will see a list of the included titles, with their respective resolution quality, on the confirmation screen.
Customers who already own some titles in a movie collection will see an option to complete their collection,
Content rights (EMA avails)
Avail delivery is required to publish movie collections. The following table lists fields in the EMA avail that are relevant for movie collections. Please reference the samples available on this page for more information.
Notes:
- For WorkType = collection, since there will be no option for quality-specific movie collections, Prime Video has launched a new FormatProfile value, Max. This is the recommended value. However, Prime Video still accepts the usual values of HD, SD, or UHD . These values will be converted internally to Max, which partners will be able to see in Slate.
- Partners must submit a single avail with a FormatProfile value of HD, SD, UHD, or Max. If avails are submitted across different FormatProfile values, the avails will be rejected.
Movie collection policies for Transactional Video on Demand (TVOD) content are governed by two policy types:
- Downloads: Whether downloading is enabled (On) or disabled (Off).
- AssetRestriction: Controls for language availability (either LanguageHoldbacks or IncludedLanguages).
Important: All policies for movie collections are inherited from their constituent movie-level policies. You cannot configure policies directly at the collection level. If you submit policy values for collections via EMA, these values will be recorded in the system, but they won’t affect actual content behavior. Similar to other optional field validations, any avail submission with values that don’t conform to the expected format for policies will lead to EMA rejections.
The following table lists fields in the EMA avail that are relevant for movie collections. Please reference the samples available on this page for more information.
Field name |
Definition and notes |
Accepted values |
Prime Video usage |
WorkType |
Type of the work. |
collection |
Required |
TitleInternalAlias |
The title of the movie collection. |
Required |
|
LicenseType |
The type of license being granted. |
EST |
Required |
PriceType |
The type of cost-terms applied to TVOD rights. Please provide WSP and/or SRP pricing inputs. Avails without either of these inputs will be rejected. |
WSP, SRP |
Required |
PriceValue |
Content-specific cost-terms. For WSP and SRP PriceType, PriceValue must be a monetary value. Non-numeric values aren’t accepted. Invalid characters will be rejected. |
Monetary values (for example, 10.49, 13.99) |
Required |
SRP |
Suggested local retail price. Use SRP field if also providing WSP in the PriceType field. |
Monetary values (for example, 10.49, 13.99) |
Optional |
ContentID |
Feature identifier for metadata. |
Required |
|
ALID |
Logical Asset ID that references the fulfillment/content package. |
Required |
|
FormatProfile |
Indicates the resolution of the video covered by the terms. For TV box sets and movie collections, resolution should be specified as “Max”. Note that other values such as SD, HD, or UHD will be accepted; however, customers will always receive the highest quality available, regardless of FormatProfile input. |
Max (recommended), SD, HD, UHD |
Required |
BundleALIDs |
List of titles to be included in the movie collection. Specified as a list of identifiers/SKUs separate by a semicolon (;) without spaces. |
UTF-8 numbers/EN letters/ underscore/hyphen |
Required |
RetailerSpare1 |
Percentage discount that will apply to Complete Your Bundle purchases. |
Numeric value from 0 to 100 |
Strongly encouraged |
The following table lists the most common reasons a movie collection avail might be rejected, and provides steps to correct each issue.
Rejection reason |
Mitigation steps |
Multiple avail submissions with differing FormatProfile values (HD or SD or UHD or Max), partially or fully overlapping avail windows, and the same pricing values. |
Please specify a single FormatProfile for WorkType = collection. |
Multiple avail submissions with the same FormatProfile values (HD or SD or UHD or Max), partially or fully overlapping avail windows, and different pricing values. |
Please enter non-overlapping avail start and end date/time for WorkType = collection. |
Multiple avail submissions with the same FormatProfile values (HD or SD or UHD or Max), partially or fully overlapping avail windows, and the same pricing values. |
Please enter non-overlapping avail start and end date/time for WorkType= collection. |
Multiple avail submissions with differing FormatProfile values (HD or SD or UHD or Max), partially or fully overlapping avail windows, and different pricing values. |
Please enter non-overlapping avail start and end date/time for WorkType = collection and specify a single FormatProfile for WorkType = collection |
A non-numeric value appears in the RetailerSpare1 field. |
Enter a numeric value from 0 to 100. |
Avail submission for WorkType = collection is made using EMA 1.6. |
Please upgrade to EMA 1.7 |
Avail submission does not include either a SRP or WSP for WorkType = collection. |
For wholesale-cost terms, please specify the PriceType as WSP and PriceValue as a monetary value. For revenue-share terms, please specify SuggestedRetailPrice as a monetary value. |
A non-numeric or zero value appears in the SeasonCount field, or the field is blank. |
Enter a non-zero numeric value. |
The BundleALIDs field is <blank> for WorkType = collection. |
BundleALIDs is a required field for WorkType = collection. Please specify movie SKUs separated by semicolons. |
Avail sumission specifies only a single BundleALID value for WorkType = collection. |
BundleALIDs field should include at least two movie SKUs. Please specify at least two identifiers that are separated by semicolons without spaces. |
Avail submission specifies different BundleALIDs list for an existing collection. |
The relationship between the collection and BundleALIDs cannot be modified. This collection already exists and the BundleALIDs specified in the avail do not match the mapping relationship. Please submit the avail against a new collection SKU, or update the BundleALIDs to match the current relationship. |
Avail submission for WorkType = collection has a value other than HD, SD, UHD, 4K, or Max in the FormatProfile field. |
Enter one of the following values: SD, HD, 4K, UHD, Max |
Exclude movies from a “Complete your bundle” discount
Customers who already own some of the movie titles in a collection will be offered remaining movie titles via a “Complete your bundle” Buy Box. The percentage discount that applies to the remaining titles is defined by the numeric value (for example, 30 = 30% discount) in the RetailerSpare1 field of the collection avail.
We understand you may not wish to provide a “Complete your bundle” discount on a particular movie, so you have 2 options to exclude it from the discount via the EMA avail for that movie.
Note: Prime Video will not apply a “double discount” in the event that you have Temporary Price Reductions (TPRs) or Prime Member Deals (PMDs) running on titles that are part of a movie collection. If a particular movie is on TPR or PMD, that movie will be automatically excluded from “Complete your bundle” discounts without further action required from you.
Option 1: New release scenario
If your movie is a new release, and you want to exclude it from the “Complete your bundle” discount, you may use the LicenseRightsDescription field in the movie EMA avail to designate it as a “New Release”. Keep in mind that this value does not automatically turn off. Once time has passed and the movie is no longer considered a new release, you will have to deliver an updated movie EMA avail that removes the “New Release” value in the field. Also, if a New Release value is specified across either one of the FormatProfiles, it will be considered across all other resolution qualities.
Field name
Definition and notes
Accepted values
Prime Video usage
WorkType
Type of the work.
Movie
Required
LicenseRightsDescription
Content type. Specify as New Release to exclude title from Compleste your bundle discount. If the property is left blank, the title will be considered as Library. If you already use this field to tag content SDP (Same Day Production) or SWP (Same Week Production), you can use Option 2 below.
Note: Any input in this field will be applied across all quality types during that time period.
New Release
Required
Option 2: All other scenarios
If for any other reason you want to exclude a movie from the “Complete your bundle” discount, use the OtherTerms field in the movie EMA avail to designate it as “Excluded from bundle discount”. Keep in mind that this value does not automatically turn off. Once you no longer want to exclude the movie from the “Complete your bundle” discount, you will have to deliver an updated movie EMA avail that removes the “Excluded from bundle discount” value in the field.
Field name |
Definition and note |
Accepted values |
Prime Video usage |
WorkType |
Type of the work. |
Movie |
Required |
OtherTerms |
Excluded from bundle discount |
Required |
Validation rules
For movie collections, these validation rules must be satisfied:
- BundleALID SKUs must have WorkType = movie
- Movie avail start dates ≤ collection avail start date
- Movie avail end dates ≥ collection avail end date
- All movies must meet publishing requirements
Metadata (MEC) references
The following table lists fields in MEC title metadata that are relevant for movie collections.
Field name |
Definition and notes |
Accepted values |
Prime Video usage |
@ContentID |
ID of the metadata provided. Should follow the MovieLabs ID best practices. Updates to previously-submitted metadata must include the same ContentID. |
Required |
|
UpdateNum |
Amazon will use the most recently received file as the latest update, as determined by delivery timestamp. |
Integer |
Not supported |
LocalizedInfo |
This block includes elements that may be localized. At least one is required. |
Required |
|
@Language |
Must be a value from the list of Prime Video allowed languages. |
Required |
|
@Default |
Must be included for one instance of LocalizedInfo for the language of original production. |
Boolean |
Not supported |
TitleDisplay19 |
19-character limit. |
Optional |
|
TitleDisplay60 |
35-character limit. This is the title field used by Amazon to display custom season names on the detail page. This field SHOULD NOT include the series name. This field should be localized in the same language as the associated synopsis. If the contribution for TitleDisplay60 does not honor the guidelines (including character limit), Amazon will fall back to the AlternateNumber field. If AlternateNumber is not available, we will fall back to Number. For example: If multi-part seasons or specials are intended, then TitleDisplay60 would have Season 1, Season 2 Part 1, Season 2 Part 2, Season 3, Holiday Special, Season 4, and so on. If you supply TitleDisplay60 with a particular language-LOCALE on a season, you must provide TitleDisplay60 with the same language-LOCALE on all seasons within the same series. |
||
TitleDisplayUnlimited |
250-character limit. This is the title field used by Amazon. The words “episode” and “season,” if used, should be localized in the same language as the associated synopsis. If this is for season level, then the series name should be included in the season title. A number should also be used to indicate a season. |
String |
Required |
TitleSort |
Title sort is required by the MEC XSD, but isn’t used by Amazon. It’s permissible to provide empty tags to satisfy the XSD: <md:TitleSort></md:TitleSort> |
Not used |
|
ArtReference |
This is used by Amazon. Artwork must be associated with a title via the art reference section in the MEC file. |
Required |
|
@Resolution |
This is the resolution of the image being delivered. |
Required |
|
@Purpose |
This is the purpose of the image being delivered. |
Required |
|
Summary190 |
150-character limit. Note that although MEC specification supports 190 characters in Summary190, Prime Video only accepts up to 150 characters. |
Required |
|
Summary400 |
400-character limit. |
Required |
|
Summary4000 |
4,000-character limit. |
Optional |
|
DisplayIndicators |
Intended to capture information that may affect customer UI. Examples include CC (Closed Captions), DVS (Descriptive Video Service), Premiere (season premiere), and so on. |
Not supported |
|
Genre |
Genre will be internally rolled up from child movies to satisfy Search requirements. Up to three Prime Video genre entries are allowed for each LocalizedInfo section. |
Optional |
|
@source |
URL that identifies the source of the genre list. If you’re providing genres from multiple lists, distinguish the genre list for each entry using this attribute. |
Optional |
|
@ID |
ID code for genre. Required for Amazon genres. See genre list for genre values and codes. |
Optional |
|
@level |
“0" indicates parent level. “1" indicates sub-genre. Indication of levels isn’t required for Amazon genres. |
Optional |
|
Keyword |
Keywords are often culturally specific, so different keywords may exist for different regions. At this time, no keywords are defined. |
Not supported |
|
VersionNotes |
A descriptive statement about why this cut was created, or what its content represents with reference to other versions of this work. Don’t include information about the language of the title in this field. |
Optional |
|
Region |
The region(s) where the work is intended to be broadcast or shown. |
Optional |
|
Country |
The country where the work is intended to be broadcast or shown. |
ISO 3166-1 |
Optional |
CountryRegion |
The country-region where the work is intended to be broadcast or shown. |
Not supported |
|
OriginalTitle |
Original title of the content. |
Optional |
|
CopyrightLine |
Displayable copyright line. |
Optional |
|
PeopleLocal |
Individuals involved in a localized production of the work (typically voice actors for dubbing). Don’t use for localized versions of cast names. Note: See the People field in this list for the full list of attributes available in the People type. |
Not supported |
|
AlternateTitle |
Used to communicate commonly known alternate titles for content. |
Not supported |
|
@type |
Various types should be used for the type attribute describing an AlternateTitle element. |
Not supported |
|
@language |
Alternate titles may include a language attribute to indicate a language different from the language attribute in the parent element. |
Not supported |
|
RunLength |
Specify to at least seconds. Zero is recommended for seasons and series. |
Optional |
|
ReleaseYear |
The first year the work was released in any territory. Enter the Collection creation year. |
Required |
|
ReleaseDate |
The date of a movie’s original theatrical release, or the original television debut/premiere of a TV series. Format is YYYY-MM-DD. For a movie, this is the first theatrical release date in the specified territory. For TV episodes, this is the original air date (not the most recent broadcast date). For bundles, use the bundle creation date as the release date. For trilogies, use the theatrical release of the first movie. Collection detail page will not display ReleaseDate. |
Optional |
|
ReleaseHistory |
Information about releases of the content. |
Optional |
|
ReleaseType |
The type of release of the content (Original, Broadcast, DVD, Blu-ray, PayTV, InternetBuy, InternetRent, Theatrical, SVOD). |
Enumerated |
Optional |
@wide |
Indicates a wide release, particularly for theatrical. |
Boolean |
Not supported |
DistrTerritory |
Country code for distribution territory. |
ISO 3166-1 |
Optional |
Date |
May include year, full date, or date and time. Provide as much specificity as available. |
Optional |
|
@scheduled |
Indicates date is scheduled. |
Boolean |
Not supported |
Description |
Description of the release. |
Optional |
|
ReleaseOrg |
Organization involved with the release for the ReleaseHistory. |
Optional |
|
@organizationID |
Organization’s unique ID |
Optional |
|
@idType |
ID scheme used for organizationID. |
Optional |
|
@role |
Role of the associated organization. |
Optional |
|
DisplayName |
A string that will be displayed when referring to this group. |
Optional |
|
SortName |
Sortable version of name. If the display name and the sort name are the same, the SortName element may be excluded. |
Optional |
|
AlternateName |
Other names for this organization. |
Optional |
|
WorkType |
Type of the work. Enter collection. |
collection |
Required |
WorkTypeDetail |
More specific definition of WorkType to allow a more detailed description. |
Not supported |
|
PictureColorType |
Color type of asset. |
Not supported |
|
PictureFormat |
A textual description of the aspect ratio format type. This field doesn’t contain the actual aspect ratio. |
Not supported |
|
Aspect Ratio |
Aspect ratio of active pixels. |
Not supported |
|
AltIdentifier |
The ID used in the avail must also be included here with the appropriate namespace (EIDR or ORG). |
Required |
|
Namespace |
Accepted values: EIDR, ISAN, IMDB, or ORG. Exactly one ID of either EIDR or ORG must be included, and its Identifier value must correspond to the ALID from the MMC and the AltID from the avail. |
EIDR, ISAN, IMDB, or ORG |
Required |
Identifier |
This value must be the ID string only and not a MovieLabs ID URN. For example, provide “manchester” instead of “md:contentid:org:amazon: |
Required |
|
Location |
Provide URI to look up the ID (such as an EIDR or IMDB link). |
Optional |
|
RatingSet |
Rating is optional. Collection detail page will not display ratings if submitted. |
Optional |
|
Rating |
Content rating. |
Not used |
|
Region |
The region(s) where rating applies. |
Required if providing a rating |
|
Country |
ISO country code of applicable country where rating applies |
ISO 3166-1 |
Required if providing a rating |
System |
The values provided in the System and Value fields should conform to the common metadata ratings provided by MovieLabs. |
Required if providing a rating |
|
Value |
The values provided in the System and Value fields should conform to the common metadata ratings provided by MovieLabs. |
Required if providing a rating |
|
Reason |
Reasons for the rating (for example, violence). |
Optional |
|
NotRated |
If content hasn’t received a rating in any territory, a NotRated field must be included per the following example: <md:RatingSet> Please note that true is case sensitive. |
Boolean |
Optional |
@condition |
Indicates why the content isn’t rated. |
Optional |
|
IsAdult |
Indicates adult content. There is no standard definition of this flag, and it’s used at the discretion of the licensor. |
Boolean |
Optional |
People |
People inputs will be internally calculated from child movies to satisfy Search requirements. Collection detail page will not display information provided in People fields. Include Actor, Director, and Producer entries, as applicable. Maximum 100 entriesl. |
Optional |
|
Job |
Description of job. |
Optional |
|
JobFunction |
Role in production of media. Prime Video accepts Director, Producer, Actor, Writer and Creator. |
Optional |
|
JobDisplay |
Displayable version of role. |
Optional |
|
@language |
Language of JobDisplay. |
Optional |
|
BillingBlockOrder |
Order of listing, starting with 1. If missing, implies infinity and may be listed in any order. |
Integer |
Optional |
Character |
For Actor entries, what role(s) they are playing. |
Optional |
|
Guest |
Whether this is a guest role. |
Boolean |
Optional |
Name |
Defines person identification for the purposes of metadata. |
Optional |
|
DisplayName |
Name of the person identified. May provide multiple entries with the language attribute to provide localizations of the name where appropriate. |
Optional |
|
@language |
If a language attribute isn’t supplied for DisplayName, the language identified in OriginalLanguage will be assumed. Also, if you supply a language that doesn’t match any language provided in the LocalizedInfo section, the People DisplayName won’t be displayed. |
Optional |
|
SortName |
Name used to sort. May be excluded if identical to DisplayName. |
Optional |
|
@language |
Language of SortName. |
Optional |
|
FirstGivenName |
First name. |
Optional |
|
SecondGivenName |
Second name. |
Optional |
|
FamilyName |
Family name. |
Optional |
|
Suffix |
Suffix. |
Optional |
|
Moniker |
Alternative name |
Optional |
|
Identifier |
Assuming there is an identifier associated with the person, this section holds information about that identifier. |
Optional |
|
Namespace |
Namespace for Identifier. |
Optional |
|
ReferenceLocation |
Location associated for the identifier within the namespace. This is expected to be an online reference to information about the individual. |
Optional |
|
Gender |
Gender of the individual. |
Optional |
|
CountryOfOrigin |
Defined as the “generally accepted country of reference.” |
Optional |
|
country |
The country from where the title originates. |
ISO 3166-1 |
Optional |
countryRegion |
The country-region from where the title originates. |
Not supported |
|
PrimarySpokenLanguage |
Language spoken throughout the work. May have more than one. |
Optional |
|
OriginalLanguage |
Language identified as the original production of the work (the “OV” language). This is generally the language used for the title treatment and/or credits of the work. Only one value allowed. |
Optional |
|
VersionLanguage |
Used only if the title described is edited for a particular language release. Not common. |
Optional |
|
AssociatedOrg |
One entry with organizationalID = Prime Video Partner Alias and role value = “licensor” is required. |
Required |
|
@organizationalID |
Unique ID for the organization. Prime Video-provided Partner Alias should be included here. |
Required |
|
@idType |
ID scheme used for the organizationalID. Not required if @role = “licensor”. Acceptable for other entries. |
Optional |
|
@role |
One entry with the value of “licensor” is required. “LSP” is also accepted to identify an LSP delivery. |
Required |
|
DisplayName |
Organization name (human-readable). This is required by the XSD but not Prime Video. |
Optional |
|
SortName |
Sortable version of organization name. |
Optional |
|
AlternateName |
Alternative name of organization. |
Optional |
|
SequenceInfo |
Sequence information for seasons and episodes. |
Not supported |
|
Number |
The sequence number that Amazon uses to order episodes within seasons and seasons within series. Do not use zero (0); start at 1. |
Integer |
Not supported |
DistributionNumber |
A flexible, but mainly numeric, representation of the sequence of release within a set or season as used in distribution. |
Not supported |
|
@domain |
The namespace domain for the element. |
Not supported |
|
AlternateNumber |
This number is optional and will only be used by Amazon to generate a fallback display for season name (Season+AlternateNumber) IF TitleDisplay60 is not provided/compliant AND the value in Number is not desired for display. For example: If AlternateNumber values are 1, 2, 301, 302, 4, then the display fallback will be Season 1, Season 2, Season 4, Season 301, Season 302. |
Integer |
Not supported |
@domain |
The namespace domain for the element. |
Not supported |
|
Parent |
The parent metadata object. |
Not supported |
|
@relationshipType |
isepisodeof = Episode of a season |
Enumerated |
Not supported |
ParentContentID |
ContentID of the parent. For example, for an episode, this would be the ContentID of the season metadata. |
Not supported |
|
[Parent metadata] |
Nested parent metadata information. This is accepted by Prime Video. |
Not supported |
|
mdmec:CompanyDisplayCredit |
At least one entry for CompanyDisplayCredit is required. This provides the customer-facing studio credit line. May be optionally localized by language and by territory. A single line limited to 250 characters is supported for any given language or territory. |
Required |
|
DisplayString |
Customer-facing company credit line. |
Required |
|
@language |
Language of DisplayString. If blank, then all languages. |
Optional |
|
Region |
Region for which credit applies. |
Optional |
|
Country |
Country for which credit applies. |
ISO 3166-1 |
Optional |
Countryregion |
Not supported |
||
DisplaySequence |
Order of display. Lower-numbered entries are displayed before higher-numbered entries. |
Integer |
Optional |
Manifest (MMC) references
MMC delivery for movie collections is only required if used for artwork delivery. If you use the MEC to deliver your artwork, you do not need to provide the MMC.
For details on how to deliver artwork via MMC, see MMC partial image delivery.
Artwork requirements
Artwork requirements for movie collections are identical to movie-level artwork specifications. See Artwork for full details about artwork specifications and requirements. We encourage using artwork that clearly signals to customers that the title is a movie collection, to help distinguish these from standard movie titles on the storefront.
Artwork type |
Movie collection requirement |
Box art (3:4) |
Required |
Cover art (16:9) |
Required |
Poster art (2:3) |
Required |
Hero art (16:9) |
Required |
Title art |
Encouraged |
Samples
The following sample files provide commented code and field examples that you can edit to reflect your own information. Right-click a link and select Save link as to save the file to your computer. You can then make changes in Excel and/or XML editors.
Avail sample file: Sample_Amazon_EMA_Avails_Movies-TV_Bundles.xlsx
MEC sample file: Amazon_MEC_Template-Collection v1.4.xml
FAQs for movie collections
Troubleshoot errors
The following table lists rules for proper publishing of season offers, season passes, and bundles. It also shows the corresponding error messages you may encounter in Slate or reporting, and provides paths to resolution.
# |
Rule |
Applicable to |
Error Message |
Details and Resolution Steps |
1 |
Publishing: In-Sequence Publishing |
Season |
The following episodes are missing: ##, ##, ##. The episode number is sourced from the metadata Eg: The sequence in the episode metadata deliveries is missing [ep3] |
All the episodes must be present in sequence without gaps for a season to be published. This means that the partner has either entered the wrong sequnece in the episode metadata deliveries or have entirely missed delivering episode avails and metadata. Example : For Season A, - Partner has submitted Episode 1 Avail and mentioned Sequence #1 in the metadata - Partner has submitted Episode 2 Avail and mentioned Sequence #4 in the metadata -Partner has submitted Episode 3 Avail and mentioned Sequence #3 in the metadata In the above example, the partner will receive an error as missing sequence #2. The partner has two options (1) correct the sequence number in the metadata for episode 2 or (2) deliver avail and metadata for episode 2, re-deliver the avail as Episode 4 avail Partner Action: (1) Correct the sequence in the metadata or (2) correct the avail to signal the right episode number and deliver avail and metadata for the episode |
2 |
Publishing: In-Sequence Publishing |
Series |
The following seasons are missing: ##, ##, ##. The season number is sourced from the metadata |
All the seasons must be present in sequence without gaps for a season to be published. Similar to the ruleprohibiting gaps in episodes but for seasons. Partner Action : (1) Correct the sequence in the season metadata or (2) correct the avail to signal the right season number and deliver avail and metadata for the season |
3 |
Avail: Bundle Component Avail Validity |
Collection |
<SKU1, SKU2> child SKUs belonging to this bundle do not have backing avails delivered to Prime Video |
All child entities must have avails before the parent bundle entity can be published. This means that Partner has not delivered avails for the underlying items in the bundle. Partner Action : Deliver the avails for the missing movie avails |
4 |
Avail: Bundle Component Avail Conflict |
Season, Series, Collection |
The following <childentity (movie,episode,season)> have conflicting avails: [ChildSKU1(startDate, end date), ChildSKU2(startDate, end date)], [ChildSKU3(startDate, end date), childSKU4(startDate, end date)] |
All child entities must have avails delivered without any conflicting avail windows. This means that underlying items in the bundle have conflicting avails by the same partner. Ex: (1) partner submits SD/HD avails on primary sku and (2) Partner submits SD/HD/4K avails on the secondary sku. (3) Partner submits (1) after (2), so (1) gets selected which is unfavourable to the partner. Partner Action: Re-deliver the avail that is intended for the partner so the conflict automatically gets resolved. |
5 |
Avail: Bundle Component Offer Conflict |
Season, Series, Collection |
The following <childentity (movie,episode,season)> have conflicting offers: [ChildSKU1(startDate, end date), ChildSKU2(startDate, end date)], [ChildSKU3(startDate, end date), childSKU4(startDate, end date)] |
All child entities must have offers created without any conflicting offer windows. This means that underlying items in the bundle have conflicting offers by different partners Ex: Fox and WB have delivered avails with conflicting windows for Movie POM Action: Resolve the conflict by performing takedowns/ end-dating avails. |
6 |
Avail: Bundle Component Takedown State |
Season, Series, Collection |
The following <childentitytypes> have been takendown <childsku1>, <childsku2> |
All child entities must be in an untakedown state for the bundle to be published. This means that the underlying items in the bundle have been takendown. POM Action : Untakedown offers as necessasy for the bundle to go live |
7 |
Pre-requisite: Bundle Components Publish-Ready |
Season, Series, Collection |
The following <childentitytype> don’t meet one or more publishing requirements: {{childSku}}: <number of rules failing>, {{childSku2}}: <number of rules failing> Ex: The following episodes don’t meet one or more publishing requirements: EP1 (1), EP2(3) |
All child entities within the parent bundle must satisfy publishing requirements before the bundle can be published. This means that one or more underlying items in the bundle has not fulfilled a publishing requirement Partner Action : Fulfill the publishing requirements for the impacted Skus |
8 |
Pre-requisite: Bundle Components Live On Storefront Check |
Season, Series, Collection |
{{childSku}} meets all the publishing requirements but is not live on the storefront |
All child entities within the parent bundle must be live on the storefront before the bundle can be published. This means that the underlying items have met all the publishing requirements but are still not live to customers. POM Action: Resolution is internal to PV. Reach out to the Bundle Tech support team to resolve |
9 |
Publishing : System Requirement Check |
Season, Series |
Internal error |
Prime Video System Error. This is a Gen3/Gen4 underlying issue. We are actively working on removing this error code through Gen4 migration Partner/POM Action: Ignore this error code |
10 |
Publishing : System Requirement Check |
Season, Series |
Internal error |
Prime Video System Error (#2). This is a Gen3/Gen4 underlying issue. We are actively working on removing this error code through Gen4 migration Partner/POM Action: Ignore this error code |
11 |
Avail: Bundle End Date |
Season, Series, Collection |
The following SKUs have an earlier end date than <parentEntityType> end date (<parent end date>): SKU1(endDate1), SKU2(endDate2) |
End dates of the child entities must be later or equal to the parent bundle end date. This means that one or more underlying items in the bundle have an end date earlier than the bundle end date Partner Action: Check the collection avail as well as the max quality avail for each child movie to ensure that the dates and times are compliant. If not, resubmit avails to ensure date compliance. If all dates are compliant but the error still persists, POM Action: Reach out to Bundle Support Team for resolution |
12 |
Avail: Bundle Price |
Season, Series, Collection |
The Parent Bundle Price is <xx>. This is higher than the combined price of the child entities xxx |
The price of the parent bundle must be less than or equal to the combined price of all child entities. This means that the bundle price is greater than sum of prices of the underlying items. POM Action: Reach out to Pricing Managers for resolution |
13 |
Avail: Bundle Start Date |
Season, Series, Collection |
The following SKUs have a later start date than <parentEntityType> start date (<parent start date>): SKU1(start Date1), SKU2(start date 2)... |
Start dates of the child entities must be earlier or equal to the parent bundle start date. This means that one or more underling items in the bundle have an start date later than the bundle start date Partner/POM Action: Check the collection avail as well as the max quality avail for each child movie to ensure that the dates and times are compliant. If not, resubmit avails to ensure date compliance. If all dates are compliant but the error still persists, POM Action: Reach out to Bundle Support Team for resolution |
14 |
Avail: Continuous Bundle Component Availability |
Season, Series, Collection |
The following <child entity type> have a gap in availability windows as per their avails: <childsku1> (gapStart, gapEnd), <child sku2> (gapStart, gapEnd) |
All child entities must maintain continuous availability throughout the parent bundle’s entire availability window. This means that one or more underlying items in the bundle have multiple avail windows with an availability gap more than a second. Partner Action: Re-avail the impacted skus with availability windows without the gap |
15 |
Avail: Bundle License Type Eligibility |
Series, Collection, Season |
LicenseType for this bundle has not been enabled |
Bundle can only be created for eligible license types. This means that the license type for this bundle has not been enabled. Partner Action: None, Ignore |
16 |
Publishing: Bundle Component Global Catalog Presence |
Collection |
The following SKUs are not in the global catalog: <childsku1>,<childsku2> |
All underlying entities must be available in the Global catalog. This means that (1) either the movie sku mentioned in the BundleAlid column in the bundle has not been migrated to global or (2) The sku mentioned in the BundleAlid column is in global, but the movie has been delivered under a different sku in classic and needs to be migrated to global POM Action: Reach out to the 1C Support team to understand how/when the Movie will be migrated to Global. |
17 |
Avail: Excess Seasons |
Series |
The Series Avail record states xx as the Expected number of seasons, but yy Seasons are linked to this parent bundle exceeding the expected count. The Seasons that are currently linked to the Series are <childsku1>, childsku2, childsku3 |
Expected count of seasons specified in the Series Avail must not exceed the number of actual seasons linked to the bundle. There is a heirarchy missing/incorrect in the underlying season avails POM Action: In CRMS, either Find the underlying season avail that has a missing/incorrect Series ID Partner Action: Re-deliver the avails with the correction. |
18 |
Avail: Excess Episodes |
Season |
The Season Avail record states xx as the Expected number of Episodes, but yy Episodes are linked to this parent bundle exceeding the expected count. The Episodes that are currently linked to the Season are <childsku1>, childsku2, childsku3 |
Expected count of episodes specified in the Season Avail must not exceed the number of actual episodes linked to the bundle. There is a heirarchy missing/incorrect in the underlying episode avails POM Action: In CRMS, either Find the underlying episode avail that has a missing/incorrect Season ID Partner Action: Re-deliver the avails with the correction. |
19 |
Publishing: Consistent Bundle Hierarchy Check |
Season, Series |
The folowing Child SKUs are linked to different parent bundles in Avail versus Metadata systems.: Child SKU1 points to ParentBundleSKU1> in Metadata while it points to parentbundlesKU2 in Avail,Child SKU2 points to ParentBundleSKU2> in Metadata while it points to parentbundleSKU3 in Avail |
The bundle-to-child entity relationship differ between Avail and Metadata systems. Both systems must reflect identical parent-child relationships before the bundle can be published. This means that the avail delivery for the season points to Series A while Metadata delivery for season points to Series B or The avail delivery for the episode points to the Season A but the metadata for the episode points to Season B Partner Action : Re-submit either the metadata or the avail to point to the right parent SKU |
20 |
Avail: Missing Season |
Series |
The Series Avail record states xx as the Expected number of seasons, but only yy Seasons are actually linked to this parent bundle in the catalog. The Seasons that are currently linked to the Series are <childsku1>, childsku2, childsku3 |
Expected count of seasons specified in the Series Avail must not be less than the number of actual seasons linked to the bundle. This means that the underlying Seasons do not have backing avails Partner Action : Deliver the missing avails for the Seasons |
21 |
Avail: Missing Episode |
Season |
The Season Avail record states xx as the Expected number of Episodes, but only yy Episodes are actually linked to this parent bundle in the catalog. The Episodes that are currently linked to the Season are <childsku1>, childsku2, childsku3 |
Expected count of episodes specified in the Series Avail must not be less than the number of actual episodes linked to the bundle. This means that the underlying Episodes do not have backing avails Partner Action : Deliver the missing avails for the Episodes |
22 |
Publishing: Movie SKU Validity |
Collection |
The following movie SKUs have been removed: <childSkus> |
All movies in the collection must be valid in the catalog. This means that the Secondary SKU referenced in the bundle avail has been removed internally by an operator/POM. POM Action: POMs should investigate why the secondary SKU was removed in the first place and can do the following: (1) If secondary SKU was removed in error, re-add the secondary SKU (2)If the secondary SKU is no longer in use and needs to be removed but the movie is still expected to be live under a different sku, Partner Action: submit a new collection avail using the desired movie SKU |
23 |
Publishing: Bundles with Pre-orders Feature |
Collection |
Collection contains pre-order movies: <childSkuList> |
Collection must not contain movies that have preorders. This means that the collection has Pre-order movies, and this feature has not been enabled yet. Partner Action : None. |
24 |
Avail: Bundle Pre-order Date Eligibility |
Collection |
The following Pre-order movies have invalid EST end dates that start before POEST offer end dates child SKU: <childSkuList> |
Movies with POEST must have an end date before EST start date when in a Collection. N/A |
25 |
Publishing: Bundles with Season Pass |
Series |
The following child SKUs have season pass offer: <childSkuList> |
Series must not contain seasons that have season pass. This means that the Series contains seasons that are Season Passes, and this feature has not been enabled yet. Partner Action : None. |
26 |
Publishing: Bundles with valid season pass territory |
Season |
The following season SKUs have season pass offers in non-eligible territory: <childSkuList> |
Season Pass is only applicable in eligible territories. Season pass offer is not allowed in ROW territories. There is no partner action required here Partner Action : None. Once the Season Passes convert to Season Offers in these territories, the bundle will go live automatically |
27 |
Publishing: Bundle Pre-order Single Title Requirement |
Collection |
The following Pre-order movies have multiple POEST offers for the same partner: <childSkuList> |
All Movies with pre-order offers must not have multiple POEST offers for the same PVID and offer tier when in a Collection. This means that the collection has Pre-order movies for the same title Partner Action : Re-avail the impacted SKUs |
