For Amazon sellers
Amazon Fulfillment
FBA inventory, inbound shipment tracking and replenishment decisions.
Finance and Accounting
Transaction, fee, payment and settlement reconciliation.
Product Listing
Management of your own product listings, quantities and selling prices.
Selling Partner Insights
Japan marketplace participation, account status, order defect rate and late shipment rate for authorized seller accounts.
Orders and product sales use only basic data supported by these four roles. Restricted buyer PII, FBM shipping labels and purchaser invoicing are outside scope.
Employees and approved contractors located in Japan may access Amazon data for service operation, store-requested support, troubleshooting and security. Access is limited to authorization information, store operational data and sanitized logs necessary for the task, restricted by staff member, store and task using least privilege, and logged and supervised. Data is not used for our own advertising, external AI training or disclosure to other stores. Access, processing, disclosure and outsourcing outside Japan are prohibited.
For Yahoo! Shopping merchants
Order API
Order status and order operations within permitted processing scope, without retaining purchaser histories.
Product API
Read, register and update your store’s products, subject to the non-retention policy for API-supplied information.
Inventory API
Check and update inventory for each store without relying on saved API copies.
Inquiry API
Review and reply to inquiries within permitted scope, without retaining messages or purchaser information.
We do not retain any Yahoo! Shopping purchaser personal information, without exception. Order numbers, related identifiers, products, statuses and inquiry text that may identify a purchaser are subject to the same restriction. They are excluded from databases, files, logs, caches, backups and persistent sessions. Other information supplied by LY Corporation through the Shopping Store API or test API is also not retained unless LY Corporation separately instructs its storage. Such instructions apply only to other information and never to purchaser personal information. Any instructed storage is limited to specified fields, purposes and periods.
Features involving purchaser information follow lawful store instructions and the non-retention obligation in Article 10. Temporary memory processing is limited to what is necessary, and information is discarded when processing ends. It is never recorded in databases, logs, caches, queues, files or backups. Purchaser-data storage, file exports and saved shipping labels are outside the feature scope.
Yahoo! Shopping requires store reauthorization every four weeks. We notify the registered email before expiry and stop the affected store’s API processing when authorization expires. Processing resumes after reauthorization and verification of the store, permissions and connection.
Amazon feature and data-scope details
The initial release requests no restricted roles and does not obtain restricted buyer PII such as names, street addresses, emails and phone numbers. In Japan, Orders API can still return postal codes without restricted roles; DPP classifies postal codes as PII. Orders v2026-01-01 searchOrders/getOrder use basic datasets without includedData; BUYER, RECIPIENT and PAYMENT are not requested. FULFILLMENT is also not requested; individual order shipping and fulfillment status is outside the display scope. FBA inbound shipment status comes from the separately listed Fulfillment Inbound API. Postal codes and other unneeded non-restricted location fields are discarded in memory before logs or storage. Unexpected restricted fields stop processing. FBA/FBM responses, free text and field combinations are reviewed before enablement. Seller identity and telemetry PII require applicable safeguards before enablement.
Listings, inventory & pricing
SP-API: Listings Items / Catalog Items / Product Type Definitions / JSON_LISTINGS_FEEDReview listing details, SKU quantities and selling prices in one place. Manage updates to listings and prices.
Uses listing attributes, product identifiers, SKUs, the seller’s own listing prices, quantities and listing status. Competitive pricing queries and automated repricing are outside the initial scope. Updates run only within permissions granted by the seller.
FBA inventory & replenishment
SP-API: FBA Inventory / Fulfillment Inbound / ReportsSee available and inbound inventory alongside sales trends to make informed replenishment decisions.
Uses FBA available, reserved and inbound quantities. Inventory reports are limited to GET_FBA_MYI_ALL_INVENTORY_DATA. Tracks inbound shipment identifiers, quantities and status. Shipment booking and fulfillment services are outside scope.
Scope: FBA Inventory v1 getInventorySummaries and Fulfillment Inbound v2024-03-20 listInboundPlans, getInboundPlan, getShipment and listShipmentItems. Fields require review before enablement.
Sales & financial reports
SP-API: Sales / Finances / Settlement ReportsOrganize aggregate sales, fees and settlement information to understand each store’s performance.
Product-level sales summaries use Sales API getOrderMetrics. Reconciliation uses Finances v2024-06-19 listTransactions and GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2. Sales and Traffic reports are outside scope. Settlement reports are generated by Amazon and retrieved, not requested or scheduled.
A unified view of your stores
SP-API: Listings / Orders / FBA Inventory / Finances / SellersReview separately authorized selling accounts in one dashboard, with clear separation of each store’s data.
Organizes the authorized data above by store. Comparisons are limited to stores the user may view within the same subscription; independent customers’ data is never combined. Each selling account requires its owner’s authorization. Accounts without authorization are never accessed.
Connection & permissions
Connect through Amazon’s authorization flow without sharing your Seller Central password with us. We request only the roles needed for these functions and explain any additional permissions before they are requested. You can revoke authorization in Seller Central at any time. Data freshness and update timing depend on Amazon processing and API limits.
Orders and sales
SP-API: Orders v2026-01-01 / Sales v1Track order identifiers, creation dates, status, item identifiers and quantities, and product-level sales totals. Operations and fields are checked before collection. Restricted buyer PII, FBM shipping labels and personalized tax invoicing are outside scope.
Store status and performance
Role: Selling Partner Insights / SP-API: Sellers / GET_V2_SELLER_PERFORMANCE_REPORTWe display Japan marketplace participation from Sellers API getMarketplaceParticipations and account status (accountStatuses), order defect rate (orderDefectRate) and late shipment rate (lateShipmentRate) from the Seller Performance Report (GET_V2_SELLER_PERFORMANCE_REPORT). Metrics are limited to non-restricted aggregates and reporting periods returned for the authorized Japanese store; unavailable metrics are not displayed. We do not obtain buyer-level or free-text feedback reports or traffic reports requiring Brand Analytics.
Amazon: SP-API roles / Data scope
Amazon: Operation mappings / Amazon: Type mappings / Amazon: Settlement reports
Use across stores
Each store requires authorization and read/write permissions. Cross-store views are limited to authorized stores within one subscription; independent customers’ data is never pooled. Yahoo! Shopping purchaser or other API-supplied information cannot be retained under Amazon retention rules. Update timing depends on each API’s processing and limits.