Planned Amazon SP-API data handling

Enreship plans an initial United States launch only after Amazon grants production access and Enreship completes implementation and validation. Canada and Mexico are staged future expansions that require localization, carrier, address, tax, privacy, and operational testing.

Amazon and Selling Partner API are trademarks of Amazon.com, Inc. or its affiliates. Their appearance identifies the planned platform connection and does not imply a partnership, certification, approval, or endorsement.

Enreship's application requests Product Listing, Inventory and Order Tracking, Amazon Logistics/Amazon Shipping, Direct-to-Consumer Shipping (Restricted), and Amazon Fulfillment/FBA capabilities.

Implemented workflows, gated from production use until Amazon approval, are:

• Seller-authorized order import.
• Product listing and inventory-quantity synchronization.
• Carrier rate retrieval and label creation.
• Shipment confirmation and tracking updates returned to Amazon.

FBA workflows are limited to inbound shipments to Amazon fulfillment centers and FBA inventory and shipment status. They remain disabled for production use until Amazon approval.

If production access is approved, each seller will authorize Enreship through Amazon's OAuth consent flow. Enreship will request only roles needed for the functions Amazon approves. Enreship never asks for or stores a seller's Amazon password.

A seller may revoke Enreship through applicable Amazon authorization controls or request disconnection through Enreship support. On revocation or termination, Enreship will stop new access, invalidate stored authorization credentials, and delete Amazon Information as required by applicable Amazon policy, subject only to a documented legal requirement.

Depending on the approved roles and seller-selected workflow, Enreship plans to process order identifiers and status, product and listing identifiers, SKUs and quantities, shipment and package details, carrier/service selections, label results, tracking identifiers and events, and FBA inbound/inventory/shipment status.

Restricted PII is limited to the shipping-required recipient name, delivery address, and phone number when available. It is used only to fulfill the seller-authorized order, obtain shipping services, create the label, confirm shipment, provide tracking, handle delivery exceptions, and meet documented legal obligations.

Amazon PII is not used for advertising, marketing, buyer profiling, unrelated analytics, or enrichment. Amazon Information is never sold or brokered.

Amazon Information will be disclosed only to the infrastructure provider that operates the service and to the carrier selected for the shipment. The named, repository-verified provider list, data categories, purposes, PII status, and restrictions are maintained in Privacy Policy section 4.

Amazon Shipping workflows are implemented but disabled until Amazon grants production approval. Transactional email, customer support, and telemetry systems are not authorized to receive Amazon Restricted PII.

Amazon Restricted PII will be deleted no later than 30 days after delivery, including through enforced backup lifecycle and expiration controls, unless a documented legal requirement applies. Data needed only transiently for a rate or label request will be removed sooner when it is no longer required.

After seller revocation, authorization termination, or application termination, Enreship will delete Amazon Information and credentials in accordance with applicable Amazon policy. Deleted data will not be restored from backup into active production use; backup copies will expire through the same maximum lifecycle.

AES-256/KMS-encrypted backups are replicated from the United States to a geographically separate European AWS Region. Quarterly restore tests validate recovery and the PII-deletion process. Recovery targets are a four-hour RPO and one-hour RTO, and PII-bearing backups expire within 30 days.

Each approved employee uses a unique SSO and IAM identity; shared accounts are prohibited and MFA is mandatory. Least-privilege role-based access limits Amazon Information to documented job duties. Production access is denied by default and requires approved, time-limited elevation. Access is reviewed quarterly and removed within 24 hours of termination or role change. AWS CloudTrail records user, role, API, and administrative activity for at least 12 months.

CloudTrail, VPC Flow Logs, RDS audit logs, CloudWatch, and sanitized Sentry events are centrally monitored, KMS-encrypted, tamper-protected, retained for at least 12 months, and reviewed manually at least every two weeks. Automated alerts notify the security team and investigations preserve evidence and track containment through closure.

Enreship conducts vulnerability scans at least every 30 days and an independent penetration test at least annually. SonarQube scans each pull request, and AWS Inspector, GuardDuty, Config, and Security Hub monitor runtime risks. Findings are risk-rated, tracked in Jira, remediated to defined deadlines, and closed only after documented rescanning or retesting.

Production Amazon PII is not copied to development or test environments. Testing uses synthetic or irreversibly anonymized data in isolated accounts with separate credentials, restricted access, encryption, and logging.

Enreship enforces the following credential controls for every account and system authorized to handle Amazon Information:

• Passwords of at least 12 characters containing uppercase and lowercase letters, a number, and a special character.
• Passwords that do not contain any part of the user's name.
• Password lifecycle settings enforce a minimum age of one day and Amazon's maximum expiration period of 365 days. Enreship applies a stricter 90-day expiration and prevents reuse of the previous 10 passwords.
• Multi-factor authentication and an account lockout that begins after five consecutive failed password attempts.
• Service and API credentials stored outside source code, rotated at least annually, and revoked and rotated immediately upon suspected compromise.

Amazon Cognito enforces password length and character-class requirements, password history, required MFA, and progressive lockout controls. Application controls enforce requirements Cognito does not provide natively, including exclusion of the user's name and minimum and maximum password-age checks.

Enreship maintains an incident-response plan with defined roles and reviews it at least every six months. The response team investigates suspected unauthorized access, contains confirmed incidents, preserves relevant evidence, rotates affected credentials, restores clean systems, and completes a post-incident review. Amazon is notified at security@amazon.com within 24 hours of detecting an incident involving Amazon Information.

Report a suspected issue to info@enreship.com.

Enreship LLC
933 Hylton Rd, Pennsauken, NJ 08110, United States

Email: info@enreship.com · Phone: 917-426-9625

Related pages: Privacy Policy, Security, Terms, and Data Processing.