Real-time order sync for manual fulfillment with event-driven SP-API

Overview

Event-driven SP-API integration built for speed, scale, and secure PII access.

Amazon Guy implemented an event-driven Amazon SP-API integration using Amazon Notifications, Amazon SQS, the Orders API, the Order Items API, and Restricted Data Tokens (RDT) to synchronize merchant-fulfilled orders in near real time.

Instead of repeatedly polling Amazon for new and updated orders, the platform listens for ORDER_CHANGE notifications delivered through SQS. That shift eliminated fulfillment delays caused by batch downloads, reduced unnecessary API consumption, and gave warehouse teams timely visibility into order lifecycle changes across Unshipped, Shipped, and Canceled statuses.

Business challenges

Four operational barriers stood between manual workflows and scalable fulfillment.

The client's fulfillment team depended on manual order downloads from Seller Central—a process that introduced lag between when Amazon received an order and when the warehouse could act on it. Peak periods amplified the problem, and status changes were easy to miss without constant monitoring.

• Delayed order synchronization due to a polling-based architecture
• Secure access to Amazon customer PII required for shipping and fulfillment
• Managing order lifecycle status changes across Unshipped, Shipped, and Canceled states
• High API consumption and scalability limitations from frequent polling cycles

Solution

Amazon ORDER_CHANGE notifications drive a status-aware fulfillment pipeline.

The integration subscribes to Amazon ORDER_CHANGE notifications routed through Amazon SQS. Each message triggers a targeted workflow based on the current order status—creating new fulfillment records when orders arrive and updating existing records when Amazon marks them Shipped or Canceled.

When OrderStatus = Unshipped: the platform retrieves a Restricted Data Token, calls the GetOrder and GetOrderItems APIs to collect order and line-item detail—including customer shipping information—and creates the order in the internal fulfillment platform.

1. Receive ORDER_CHANGE notification via Amazon SQS
2. Retrieve Restricted Data Token (RDT) for PII access
3. Call GetOrder API for order-level details
4. Call GetOrderItems API for line-item and shipping data
5. Create order in the fulfillment platform

When OrderStatus = Shipped or Canceled: the platform updates the existing order record in the fulfillment system to reflect the latest Amazon status, keeping warehouse and operations teams aligned without re-fetching full order payloads.

• Match notification to an existing fulfillment record
• Update order status to Shipped or Canceled
• Avoid redundant API calls for unchanged order data

Customer PII is handled using Amazon-recommended security controls—Restricted Data Tokens issued only when shipping information is required, OAuth authorization, IAM security controls, and comprehensive audit logging across every restricted data access.

Technical components

Purpose-built services for notifications, order data, and secure access.

The architecture combines Amazon's event notification layer with SP-API order endpoints and enterprise security controls. Each component plays a defined role in delivering reliable, compliant order synchronization at scale.

• Amazon Notifications API
• Amazon SQS
• Amazon Orders API
• Amazon Order Items API
• Amazon Tokens API (RDT)
• OAuth Authorization
• IAM Security Controls
• Audit Logging

Notifications and SQS form the event backbone, triggering processing only when Amazon reports a meaningful order change. The Orders and Order Items APIs supply fulfillment data, while the Tokens API issues short-lived RDT credentials for restricted customer fields. OAuth and IAM enforce least-privilege access, and audit logging provides a complete trail of restricted data requests and order state transitions.