Weex connects to the Amazon Selling Partner API with the authorised seller's consent and uses only the capabilities listed below. Each item corresponds to a feature that is live in our panel.
We import the seller's Amazon orders and order items and list them on a single screen. We read FBA inventory summaries (fulfillable, reserved and inbound quantities) and the status of FBA shipments to present stock tracking.
Note: we read inventory data and create FBA inbound plans on the seller's instruction. We do not perform any operation that directly changes stock quantities on Amazon.
We search the Amazon catalogue by keyword or ASIN and display product title, brand, category and image data. For a given ASIN we retrieve competing offers and Amazon's estimated referral and FBA fees, helping the seller evaluate a product decision.
We use only Amazon's public catalogue and offer data; we do not access other sellers' private data.
We pull the seller's own account reports from Amazon and visualise them in our panel: sales and traffic, brand analytics search terms, account health, FBA inventory planning and ageing, stranded inventory, returns, storage fees and reimbursements.
Reports are shown only to the seller they belong to; we do not aggregate data across sellers or share it with third parties.
From the order screen we read the message types Amazon permits for that order (order detail confirmation, delivery details, unexpected problem) and send messages on the seller's behalf. Amazon returns only the permitted actions; no other message can be sent.
Note: SP-API does not allow reading incoming buyer messages; our integration is outbound only.
We read the Buy Box and lowest competing price for an ASIN and show them to the seller. If the seller approves, we update their own list price. Pricing decisions always rest with the seller; we do not run automation that changes prices on its own.
We apply a scheduled discount (sale price) with start and end dates to a seller's SKU, preserving the regular price. We also report redemption and cost performance for coupons the seller created on Amazon.
Our promotions consist solely of price reductions and coupons; we do not offer payment in return for purchases or any method that artificially inflates rankings.
Using Amazon's official Solicitations API we check whether an order is eligible for a review request and trigger Amazon's own standard "Request a Review" message. We do not author the text; Amazon sends it.
We do not provide incentivised, paid or directed review services.
We connect the seller's non-Amazon stores (e.g. Shopify) with their explicit consent and show orders from those channels in a single list alongside their Amazon orders, so the seller can follow every sales channel from one screen.
Sellers can fulfil an order received on a non-Amazon channel from their Amazon FBA inventory through our panel. We preview the fulfilment fee first, create the fulfilment order on Amazon once the seller approves, then track its status and carrier tracking number. Orders can be cancelled before they ship.
Every fulfilment is created on the seller's own instruction; we do not run automation that creates orders on its own.
The capabilities above are delivered through the APIs below. Every row listed here is in live use in our panel.
| API | What we use it for |
|---|---|
| Sellers | After authorisation we read which marketplaces the seller participates in, to verify the connection. |
| Orders | We import orders and order items; this is the source for our order list, revenue and returns screens. |
| FBA Inventory | We read fulfillable, reserved and inbound FBA stock quantities. Read-only; we do not write stock. |
| FBA Inbound | On the seller's instruction we create an FBA inbound plan and submit it to Amazon; we track the plan's operation status, its shipments and received quantities, and cancel the plan when required. |
| Fulfillment Outbound | Multi-Channel Fulfillment: fee preview, order creation on seller approval, status and carrier tracking, cancellation. |
| Catalog Items | Catalogue search by keyword or ASIN; we display product title, brand, category and images. |
| Product Pricing | We read the Buy Box and lowest competing offer for an ASIN and present them to the seller. |
| Product Fees | We calculate Amazon's estimated referral and FBA fees and show them on our product profitability screen. |
| Listings Items | We read listing health (issues, missing attributes, offer status); with the seller's approval we update the price field only. |
| A+ Content | We read whether a product has published A+ content and use it in our listing quality recommendations. |
| Reports | We pull sales and traffic, brand analytics, account health, inventory planning and ageing, stranded inventory, returns, storage fee and reimbursement reports. |
| Data Kiosk | We query sales and traffic by ASIN and seller economics data, and use it in our profitability analyses. |
| Finances | We read Amazon's fees, coupon costs and transaction line items for our profitability and VAT declaration screens. |
| Messaging | We read the message types Amazon permits for an order and send only those types on the seller's behalf. |
| Solicitations | We check order eligibility and trigger Amazon's own standard review request. Amazon writes the message. |
The following are also selected in our Appstore listing. Some run on SP-API, some on the Amazon Advertising API, and our logistics offering is an operational service of our own.
We read the seller's listings from Amazon and present their health: missing or invalid attributes, offer status, and whether A+ content is published. From this we generate listing quality recommendations.
SP-API (Listings Items, A+ Content). We do not author listing copy; through the API we update only the price field, and only with the seller's approval. Title and description improvements are applied by the seller as part of our consultancy service.
We pull and analyse performance reports for Sponsored Products, Sponsored Brands and Sponsored Display campaigns; on the seller's instruction we pause or resume campaigns and update their daily budgets. We also generate optimisation recommendations from search term and targeting data.
Amazon Advertising API — separate from SP-API and connected under a separate authorisation from the seller. Recommendations are presented to the seller; we do not change campaigns without approval.
We move the seller's goods to Amazon's warehouses: collecting quotes from contracted carriers, creating shipments and parcels, preparing packing lists and customs paperwork, plus intermediate warehouse and labelling services. The shipment is matched to the FBA inbound plan created in our panel.
This is our own operational service; transport is not performed through Amazon APIs. Its Amazon-side counterpart is limited to the FBA inbound plan and shipment tracking.
We read Amazon's fees and transaction line items to build the seller's profitability view and their VAT declaration screen. We provide European and UK VAT registration, EORI application and periodic VAT filing as advisory services.
SP-API (Finances). Filings are made on the seller's behalf by a licensed accountant; we do not execute any tax payment or funds transfer through Amazon.
We make no calls to the following SP-APIs: Feeds, Notifications, Merchant Fulfillment, Easy Ship, Shipping, Supply Sources, Replenishment, and all Vendor APIs. We do not offer credit or funding products to sellers and do not access Amazon funding data.
Our Amazon advertising management service runs on the Amazon Advertising API, which is separate from SP-API and connected under a separate authorisation granted by the seller.
We connect to the Amazon SP-API only with the seller's own authorisation and process the data solely to serve that seller. Sellers can revoke the connection at any time.
The data we retain is business data: order records, product and inventory information, fees and report output. We do not store buyers' names or e-mail addresses — our order sync never writes those fields. Address data needed for delivery is used only when a fulfilment order is created.
If buyer personal data arises through any path, a nightly automated purge removes it before it exceeds 30 days. This is the technical counterpart of the retention commitment in our Privacy Policy.