Baker Taylor Data Requirements For Title Submissions and Reference File Download Link
https://eu2.contabostorage.com/00f3241116844f24b628f46d81abb929:st1/folder6/6606/1656118802_new_title_requirements_04_10_2009_-_Standar_Format.xls
2026-05-30 07:12:04 - Admin
<style> body { font-family: Arial, Helvetica, sans-serif; margin: 0; padding: 0; background-color: #f9f9f9; color: #333; line-height: 1.6; } .container { max-width: 960px; margin: 30px auto; background: #fff; padding: 30px 40px; box-shadow: 0 2px 8px rgba(0,0,0,.1); } h1, h2, h3 { color: #2a5d9f; } h1 { margin-top: 0; font-size: 2.2em; } h2 { margin-top: 1.8em; font-size: 1.8em; } h3 { margin-top: 1.4em; font-size: 1.4em; } ul, ol { margin-left: 1.5em; } table { width: 100%; border-collapse: collapse; margin-top: 1em; } th, td { border: 1px solid #ddd; padding: 8px; text-align: left; } th { background-color: #eaeff7; } a { color: #2a5d9f; text-decoration: none; } a:hover { text-decoration: underline; } </style><div class="container"> <h1>BakerTaylor Data Requirements for Title Submissions</h1> <p>When submitting titles to BakerTaylor, the accuracy and completeness of the data you provide are critical for timely processing, proper cataloguing, and downstream distribution. This guide outlines the core data elements, formatting rules, and bestpractice tips that will help you prepare a clean, compliant submission package.</p> <h2>1. Core Data Elements</h2> <p>Every title record must contain the following mandatory fields:</p> <ul> <li><strong>Title Name</strong> Full, official title as it appears on the product packaging.</li> <li><strong>UPC/EAN</strong> 12digit UPC or 13digit EAN barcode. Must be numeric, no dashes.</li> <li><strong>Release Date</strong> YYYYMMDD format. Use UTC time zone for dateonly values.</li> <li><strong>Format</strong> One of: DVD, BluRay, Digital, 4K Ultra HD, etc.</li> <li><strong>Genre(s)</strong> Select from BakerTaylor's approved genre list (e.g., Action, Comedy, Documentary).</li> <li><strong>Studio / Distributor</strong> Legal name of the entity that holds the distribution rights.</li> <li><strong>Running Time</strong> Total runtime in minutes (integer only).</li> <li><strong>MPAA Rating</strong> G, PG, PG13, R, NC17, Unrated.</li> </ul> <h2>2. Optional but Recommended Fields</h2> <p>Providing the following optional fields improves discoverability and reduces manual followups:</p> <ul> <li>Original Language</li> <li>Country of Production</li> <li>Synopsis (max 1000 characters)</li> <li>Cast & Crew (up to 10 principal members each)</li> <li>Keywords (pipedelimited, up to 10 per title)</li> <li>Cover Art URL (HTTPS, PNG/JPEG, 300450px minimum)</li> <li>Trailer URL (YouTube or Vimeo, HTTPS, embedfriendly)</li> </ul> <h2>3. File Formats & Submission Methods</h2> <h3>3.1 CSV (CommaSeparated Values)</h3> <p>Most distributors use a CSV file for bulk uploads. Follow these rules:</p> <ul> <li>UTF8 encoding without BOM.</li> <li>First row must contain column headers exactly matching the field names listed above.</li> <li>Enclose text fields containing commas or quotes in double quotes.</li> <li>Use TRUE/FALSE for boolean values (e.g., IsExclusive).</li> </ul> <h3>3.2 XML</h3> <p>For APIdriven or automated pipelines, XML is accepted. The root node must be <code><Titles></code>, with each title wrapped in a <code><Title></code> element. An example snippet:</p> <pre><Titles> <Title> <TitleName>The Great Adventure</TitleName> <UPC>012345678912</UPC> <ReleaseDate>2024-11-01</ReleaseDate> <Format>BluRay</Format> <Genre>Adventure</Genre> <Studio>Epic Studios</Studio> <RunningTime>124</RunningTime> <Rating>PG13</Rating> </Title></Titles> </pre> <h3>3.3 API (REST)</h3> <p>The preferred method for frequent updates is the <a href="https://developer.bakertaylor.com/api-docs">BakerTaylor Title API</a>. Submissions must be JSONencoded and sent via HTTPS POST to <code>/v1/titles</code>. Required headers:</p> <ul> <li><code>Content-Type: application/json</code></li> <li><code>Authorization: Bearer <youraccesstoken></code></li> </ul> <h2>4. Data Validation Rules</h2> <p>Before you upload, run your data through these checks:</p> <ol> <li><strong>UPC/EAN checksum</strong> Must pass standard Mod10 validation.</li> <li><strong>Date consistency</strong> Release date cannot be in the future unless flagged as PreRelease.</li> <li><strong>Running time range</strong> Must be between 1 and 600 minutes.</li> <li><strong>Genre mapping</strong> Use the exact spelling from the master list; SciFi should be Science Fiction.</li> <li><strong>URL format</strong> Must start with <code>https://</code> and be reachable (status 200) at submission time.</li> </ol> <h2>5. Common Errors & How to Fix Them</h2> <table> <thead> <tr> <th>Error Code</th> <th>Description</th> <th>Resolution</th> </tr> </thead> <tbody> <tr> <td>ERR001</td> <td>Invalid UPC checksum</td> <td>Recalculate the check digit or request a new barcode from GS1.</td> </tr> <tr> <td>ERR002</td> <td>Missing mandatory field</td> <td>Populate every required column; the system will list which field(s) are absent.</td> </tr> <tr> <td>ERR003</td> <td>Unsupported genre</td> <td>Choose a genre from the current <a href="https://www.bakertaylor.com/genre-list">BakerTaylor genre list</a>.</td> </tr> <tr> <td>ERR004</td> <td>Cover art resolution too low</td> <td>Upload an image (PNG/JPEG) of at least 300450px.</td> </tr> <tr> <td>ERR005</td> <td>Release date in the future without PreRelease flag</td> <td>Either set the flag or adjust the date to a past/present value.</td> </tr> </tbody> </table> <h2>6. BestPractice Tips</h2> <ul> <li><strong>Keep a master reference file.</strong> Maintain a single source of truth for titles, then generate CSV/XML/JSON from it.</li> <li><strong>Validate programmatically.</strong> Use a small script (Python, Node, etc.) to run checksum, date, and URL tests before each submission.</li> <li><strong>Version control.</strong> Commit every data file to a repository so you can track changes and revert if needed.</li> <li><strong>Batch size.</strong> Submit no more than 2,000 titles per file to avoid timeouts; larger catalogs should be split.</li> <li><strong>Monitor acknowledgments.</strong> After upload, the system returns a processing receipt store it for audit purposes.</li> </ul> <h2>7. Submission Workflow Overview</h2> <ol> <li>Collect title information from internal systems.</li> <li>Map data to BakerTaylors required field names.</li> <li>Run validation scripts (UPC, dates, URLs).</li> <li>Generate CSV, XML, or JSON payload.</li> <li>Upload via FTP/SFTP (CSV/XML) or POST to the REST API.</li> <li>Receive processing receipt and error report.</li> <li>Correct any errors and resubmit.</li> <li>Confirm that titles appear in the BakerTaylor catalog within 48hours.</li> </ol> <h2>8. Contacts & Support</h2> <p>If you encounter issues that are not covered by the error codes above, reach out to the BakerTaylor Technical Support team:</p> <ul> <li>Email: <a href="mailto:titlesupport@bakertaylor.com">titlesupport@bakertaylor.com</a></li> <li>Phone: +18005550123 (MonFri, 8am6pm EST)</li> <li>Support portal: <a href="https://support.bakertaylor.com">https://support.bakertaylor.com</a></li> </ul> <p>Adhering to these guidelines will help you avoid delays, reduce rework, and ensure your titles reach retailers quickly and accurately.</p></div>