Amazon SP-API Integration
Public architectural specification detailing authorization flows, scoped API roles, data handling practices, and zero-PII data minimization for Amazon Selling Partner APIs.
Amazon Selling Partner API (SP-API) Application
Our application connects programmatically with Amazon Selling Partner APIs to manage Ledermode GbR's catalog and logistics synchronization across Amazon European marketplaces.
What the Application Does
The software functions as an operational integration engine. It enables bidirectional data exchange between local warehouse databases and Amazon Seller Central:
- • Stock Management: Synchronizes physical SKU counts with active Amazon listings.
- • Order Manifests: Pulls pending orders to generate packaging slips and carrier dispatch labels.
- • Tracking Dispatch: Back-syncs carrier tracking codes (e.g., DHL, Deutsche Post) upon shipment.
- • Price Synchronization: Maintains competitive pricing within predefined safety margins.
Who Uses It & How It Differs from Retail
The application is deployed for operational use by Ledermode GbR's internal fulfillment and catalog management staff in Hattersheim, Germany:
Seller Authorization & Token Handling
All API operations are guarded by Amazon's official OAuth 2.0 Selling Partner workflow. Master credentials and login details are never requested, stored, or exposed.
OAuth 2.0 Consent
The seller initiates access through the official Amazon Seller Central consent screen. Amazon authenticates the seller and issues a temporary authorization code directly to our registered redirect URI.
Token Exchange & Encryption
Our backend exchanges the authorization code for an Amazon Refresh Token over TLS 1.3. The refresh token is stored in an encrypted database with restricted access keys, and short-lived access tokens are rotated hourly.
Immediate Revocation
If authorization is removed in Amazon Seller Central (Manage Your Apps), subsequent API calls fail immediately. Our system invalidates the cached session and securely deletes associated temporary tokens.
SP-API Roles Required & Data Justification
In compliance with Amazon's Principle of Least Privilege, our application requests only the specific SP-API roles required for active operations.
| SP-API Role | Data Accessed | Business Justification | PII Accessed? |
|---|---|---|---|
| Inventory and Order Tracking | SKU, FNSKU, ASIN, Quantity Available, Inbound Status | Required to synchronize real-time warehouse stock and prevent overselling on Amazon. | No PII |
| Orders (Restricted) | Order ID, Item SKU, Qty, Shipping Address (for label print only) | Strictly required for generating postal shipping labels and transmitting tracking IDs back to Amazon. | Temporary Only (Purged Post-Dispatch) |
| Pricing | Seller SKU, Current Listing Price, Shipping Fee, Currency | Maintains competitive pricing within hard-coded margin floors to avoid unintended pricing anomalies. | No PII |
| Product Listing | Item Attributes, EAN/UPC, Title, Brand, Bullet Points | Permits submitting corrected product titles and catalog attributes for smoking accessories and incense lines. | No PII |
Customer Personally Identifiable Information (PII) Statement
Ledermode GbR treats customer privacy with utmost seriousness. Our policy on customer Personally Identifiable Information (PII) adheres strictly to Amazon's Data Protection Policy (DPP):
- • Purpose Limitation: Customer name and delivery address are accessed solely for generating compliant carrier shipping labels.
- • Zero Marketing Use: Customer PII is never used for advertising, marketing campaigns, newsletters, or third-party profiling.
- • No Cold Storage: Customer address records are held in active memory during the fulfillment run and securely purged once dispatch is confirmed.
- • Cryptographic Safeguards: In-flight transit uses TLS 1.3, and any transient operational cache uses industry-standard encryption at rest.
Auditable Policies & Compliance Standards
Inspect our full regulatory documentation governing data security, access control, and incident resolution.
Data Handling & Protection →
Classification of marketplace data, network controls, and separate PII isolation measures.
Information Security Policy →
Key management, credential safeguards, network firewalls, and least-privilege employee access.
Data Retention & Deletion →
Specific retention schedules, automated purge jobs, and disposal upon seller request.
Technical Verification & Developer Inquiry
For inquiries regarding our Amazon SP-API registration, developer profile, or security architecture, contact our security officer.