Amazon

ParcelPilot currently supports direct Amazon Seller Central integration for MFN order pulling only.

Implemented

• Pulling merchant-fulfilled (MFN) Amazon orders into ParcelPilot
• Manual backfill via Client Integrations → Pull Orders
• Scheduled order pulling via the normal ecommerce sync jobs
• Reimporting an Amazon order from upstream
• Normalizing Amazon orders into the existing ecommerce importer shape used by ParcelPilot
• Test connection from the Client Integration edit screen
• Configurable default order pulling based on Amazon order statuses

Credentials needed

Enter these under Integrations → Client Integrations → Amazon:

• LWA Client ID
• LWA Client Secret
• Refresh Token
• Marketplace IDs
• SP-API endpoint
• AWS signing region
• AWS Access Key ID
• AWS Secret Access Key
• AWS Session Token (optional, if your AWS setup uses one)

Still to do

• FBA / AFN order handling
• Product import from Amazon
• Inventory sync with Amazon
• Pushing shipment confirmations back to Amazon
• Broader real-world testing across multiple marketplaces / accounts
• Decide whether Amazon-specific docs/help should include setup steps for restricted data token requirements and SP-API role assignment screenshots

Notes

• Marketplace IDs are required because Amazon order APIs are marketplace-scoped.
• The default endpoint/signing region in ParcelPilot is the EU pair:
  • Endpoint: https://sellingpartnerapi-eu.amazon.com
  • Signing region: eu-west-1
• To import UK Amazon orders, the marketplace ID is commonly A1F83G8C2ARO7P.
• ParcelPilot requests shipping address data for imported MFN orders, so the connected SP-API app and roles must allow that access.
• Current Amazon implementation is intentionally isolated from other ecommerce integrations so existing integrations are not affected.