Guides

Amazon Seller Central (ASC) — One-Time Import Guide

Overview

This guide outlines how to extract Amazon Seller Central (ASC) data for a one-time historical import into Prescient.

Requirements

The following fields are required for ingestion:

  • amazon-order-id
  • purchase-date
  • order-status
  • order total amount (derived from item-level pricing)
  • buyer-email (Amazon marketplace email — if available)

Available Report Options

There are two primary report options in Amazon Seller Central:

  1. All Orders Report (Recommended starting point)
  2. Fulfilled Shipments Report (Alternative with additional fields)

Option 1: All Orders Report

Location

Key Characteristics

  • ✅ Can export up to 2 years of historical data
  • ⚠️ Limited to 30 days per report pull
  • ⚠️ Output format: .txt only
  • ⏱️ Faster generation time (~10 minutes)

Included Fields

  • ✅ amazon-order-id
  • ✅ purchase-date
  • ✅ order-status
  • ✅ item-price (used to calculate order total)
  • ❌ buyer-email (not included)

Considerations

  • Revenue is provided at the line-item (ASIN) level
    • Requires aggregation to order-level totals
  • Revenue appears to be gross (pre-discounts)
    • Discounts may be provided separately
  • Missing buyer-email field
  • Requires transformation:
    • Group by amazon-order-id
    • Sum item-level values to calculate total revenue

Option 2: Fulfilled Shipments Report

Location

Key Characteristics

  • ✅ Includes buyer email
  • ✅ More detailed dataset
  • ⚠️ Limited to ~18 months of historical data
  • ⚠️ Limited to 30 days per report pull
  • 📁 Available as .txt or .xls

Included Fields

  • ✅ amazon-order-id (SKU-level, requires aggregation)
  • ✅ purchase-date
  • ❌ order-status
  • ✅ buyer-email
  • ✅ item-price (used for revenue calculation)

Additional Available Fields

This report includes a wide set of additional fields such as:

  • Order & shipment IDs
  • Buyer information (email, name, phone)
  • Product details (SKU, product name, quantity)
  • Pricing fields:
    • item-price
    • item-tax
    • shipping-price
    • promotion discounts
  • Fulfillment details:
    • carrier
    • tracking-number
    • fulfillment-channel
    • sales-channel

Considerations

  • Data is at the SKU level
    • Must be aggregated to the order level
  • Does not include order-status
  • More complete dataset than All Orders Report, but slightly shorter history window

Data Transformation Requirements

For both report types:

Required Transformations

  • Aggregate data to:
    • One row per order (amazon-order-id)
  • Compute:
    • Total revenue per order (sum of item-level prices)
  • Ensure:
    • One row per date × order

Known Limitations

  • Reports must be pulled in 30-day increments
  • Full historical backfill requires multiple exports
  • Large file sizes (especially .txt)
  • Some required fields may be missing depending on report type:
    • buyer-email missing in All Orders Report
    • order-status missing in Fulfilled Shipments Report

Recommendations

  • Use All Orders Report for:

    • Faster pulls
    • Longer history (up to 2 years)

  • Use Fulfilled Shipments Report if:

    • buyer-email is required
    • More granular shipment-level detail is needed

  • Plan for:

    • Manual or programmatic aggregation
    • Multiple report pulls for full history

Notes

  • Amazon data is typically:
    • Line-item based
    • Requires transformation for modeling
  • Confirm internally:
    • Whether to model gross vs net revenue

Amazon Ads (Reference)

Separate from Seller Central data, Amazon Ads data should be pulled via:

  • Amazon Advertising Console
  • Campaign reporting templates

(See Amazon Ads documentation for full instructions.)


Updated about 22 hours ago