Data usage, security and compliance
Catalogr is a supplier catalog screening tool for Amazon sellers, designed to operate within Amazon SP-API usage rules. It uses Amazon SP-API to match supplier barcodes to ASINs, retrieve sales rank, package dimensions, Buy Box and offer data, and estimate Amazon fees for sourcing review.
Amazon SP-API usage
Catalogr uses official Amazon SP-API endpoints to process supplier catalog files.
- Catalog Items is used to resolve EAN, UPC and GTIN values to Amazon ASINs, retrieve sales rank data and retrieve product dimensions when available.
- Product Pricing is used to retrieve Buy Box, pricing and offer data.
- Catalogr estimates referral fees and FBA fees for screening purposes.
- Catalogr does not access buyer personal information, seller orders, advertising data, inventory data, Brand Analytics data or account health data.
Data scope
Catalogr processes supplier files uploaded by the user and Amazon SP-API data required for supplier catalog screening.
Catalogr may process:
- Uploaded supplier XLSX files
- Barcode identifiers such as EAN, UPC and GTIN
- Supplier prices detected from uploaded files
- Amazon ASIN matches, sales rank data and product dimensions when available
- Buy Box, pricing and offer signals from Product Pricing
- Estimated referral fees, estimated FBA fees, estimated profit and estimated ROI
- Generated CSV outputs for the user who launched the job
Catalogr does not access:
- Buyer personal information
- Buyer addresses or buyer messages
- Seller order data
- Advertising data
- Inventory data
- Finance data
- Account health data
- Brand Analytics data
File isolation and access control
- Each user only accesses their own uploaded files and generated outputs.
- No uploaded supplier file is shared across users.
- No resale or sharing of uploaded supplier files is performed by the service.
Technical cache
Catalogr maintains technical caches to reduce redundant Amazon SP-API calls and improve processing speed.
The cache may store:
- Catalogr maintains a technical cache of GTIN to ASIN mappings, rank data and product dimensions to reduce repeated SP-API calls.
- Pricing cache may be used to reduce repeated Product Pricing calls for recently seen ASINs.
- FBA fees are not stored as fixed values. They are estimated from dimensions and fee tables when outputs are generated.
- The cache exists only to improve processing speed and reduce redundant API calls.
Pricing snapshots expire automatically. Uploaded supplier files are not shared across users. The technical cache is used only to reduce redundant Amazon SP-API calls and improve processing speed.
Security and retention
- Passwordless authentication by magic link.
- Rate limiting and abuse prevention.
- Uploaded files and generated outputs are retained for up to 30 days, then permanently deleted.