Overview

On March 21 2023 Amazon will drop the StandardPricePointsPercent and SalePricePointsPercent fields from its inventory flat‑file schema and the matching XSD definition. The removal is part of a larger effort to simplify the way sellers configure Amazon Points, the loyalty credit shoppers can earn on eligible purchases. Sellers who still include these columns after the deadline will see their feeds rejected, so they must adjust their upload process or shift to the Promotions API to keep point‑based offers alive.

Key Points

• Removal date — Effective March 21 2023 the two points‑related columns disappear from every inventory flat‑file template and from the XSD used for validation.
• Who is affected — Any seller who currently submits StandardPricePointsPercent or SalePricePointsPercent in their inventory feeds will experience validation failures once the change goes live.
• Why Amazon is acting — The company is consolidating points management to a single, API‑driven workflow, reducing the number of attributes sellers must maintain in flat files.
• No automatic migration — Existing point percentages are not converted automatically; sellers must recreate each offer using the new promotion tools.
• Reporting stays intact — Sales reports will continue to show points earned, but the source of those points must now come from approved promotion configurations rather than flat‑file data.
• Compliance consequence — Feeds that still contain the removed attributes after the cut‑off will be rejected with an XSD validation error, halting inventory updates for those SKUs.

How the Points Removal Works

1. Schema revision — Amazon publishes an updated XSD that omits the two points fields. For example, a file that previously contained a header named StandardPricePointsPercent will now trigger a “field not recognized” error during the upload process.
2. Flat‑file validation — When a seller submits an inventory file, Amazon’s ingestion engine cross‑checks every column against the new XSD. If the deprecated column remains, the system returns a 400‑level error such as “Invalid element: SalePricePointsPercent.”