Channels · Amazon

Not a feed. A catalog with its own schema for every product type — and Scout reads that schema live.

Amazon doesn't take your product data as-is. It asks what type of thing you're selling, then requires the attributes that type demands — which differ by type and change over time. Scout resolves the type, reads the current requirements, validates against them, and only then submits.

TypeMarketplace

Connects viaSeller Central authorization (SP-API)

Who sells hereMerchants listing on Amazon who are tired of rejections that don't say which of thirty attributes was wrong.

A feed channel takes your catalog as you send it. A marketplace makes you conform to its own. That difference is why this page — and Scout's work here — looks different from the feed channels. How Scout handles marketplaces →

Catalog requirementsLive schema

BackpacksFootwearHome

Example productCanvas backpackTypeBackpackASINB0EXAMPLECategoryLuggage & Bags

Current requirementsBrandText (1–100 chars)MaterialText (1–50 chars)ColorText (1–30 chars)CapacityText (1–20 chars)Requirements vary by type and change over time.

Resolve typeBackpackRead schemaLive schemaValidateAll required fields4SubmitReady

Meerkat ScoutCurrent schema loadedBackpack · Live schema

How Scout connects

3 steps, in the app.

Scout holds only the credential the channel issues for this connection, encrypted at rest. Disconnecting the channel deletes it.

01Authorize in Seller CentralScout is authorized as a Selling Partner application against your seller account; you approve it from Seller Central.
02Choose the marketplaceAmazon.com, Amazon.co.uk, Amazon.de — each is a separate marketplace with its own requirements.
03Confirm GTIN policyScout reads whether your brand has a GTIN exemption and validates identifiers accordingly.

What makes Amazon different

One product type. Its live required attributes. Your product checked against them, before submission.

Resolved product type

SHOES

High confidence

Because: product_type "Footwear" and a Size (US) option match SHOES; the GTIN resolves to an existing ASIN in this type.

MarketplaceAmazon.comGTIN exemptionNone on fileSchema read2 h ago

AcceptChoose another…

Required for SHOES · Amazon.com15 required · 13 present

✓item_namefrom title

✓brandfrom vendor

✓external_product_idfrom barcode · UPC

✕footwear_size_systemSet to "US" for this feed →

✕footwear_age_groupSet to "adult" when tag ≠ kids →

✓colorfrom option1

✓target_genderfrom tag "men"

✓country_of_originfrom metafield

+ 7 more present

2 attributes block submission.0 submissions spent

What Scout does for Amazon

Resolves each product to an Amazon Product Type Definition with a confidence level and a stated reason, and lets you accept or override before anything is submitted.

Reads the required attributes for that type from Amazon's live schema and validates every one before spending a submission.

Translates processing-report errors into Scout's vocabulary and names the attribute, so a rejection becomes a field.

What Amazon requires that others don't

A product type per item, from Amazon's own definitions — "Shoes" is not a type; SHOES is.
Per-type required attributes that can run to dozens, and that differ between Amazon.com and Amazon.de.
A GTIN on every item unless the brand holds a GTIN exemption, which Amazon tracks and Scout reads.
Existing-ASIN matching: if the GTIN already exists on Amazon, you're contributing to that listing, not creating one.

Scout's starter template for Amazon pre-maps these from Shopify where a mapping exists, and its diagnostics name the field when one is missing.

Not a feed. A catalog with its own schema for every product type — and Scout reads that schema live.

3 steps, in the app.

One product type. Its live required attributes. Your product checked against them, before submission.

Ready to put Scout on watch?