Our latest version of Price Checker 2 (3.0.0) uses Amazon’s all new Selling Partner API for the first time. They are forcing a hard switch from September 30th 2022, after which point the previous API will no longer function.
...
| Info |
|---|
That’s it! On returning to PC2 software you’ll now see green ticks for each market that you can access (inside Marketplace Setup in menu on left). Please don't forget to select “Refresh” if you had PC2 running while going through the above process. ** Repeat these steps for each separate selling region (North America or Europe) you require ** |
...
Some speed improvements may be seen with the new API, especially on short runs of up to around 1000 items and very short runs for single to 50 or so items, as the run start-up delay has been almost eliminated. There have also been several improvements so that historical data is no longer necessary for a number of relatively ‘basic’ data points (see below).
Hazmat and inbound eligibility checking is now accurate (matches Seller Central), but relatively slow - the maximum allowed by Amazon is 1 item per second (3600 per hour) - however, the check no longer produces obscure inventory entries.
We recommend the use of filtering so that as few items as possible need to pass through this stage, but in any case it can be avoided altogether by disabling and removing any Hazmat/Listing Shipment Restrictions related filters/columns/scoring, and doing so will increase overall speed.
In addition, when the columns/filters are in use, this Inbound Eligibility is cached (default up to 60 days, but user configurable), so that the check becomes obsolete when re-running the same items within that time frame. You can consider lengthening the retention period further using the new Cache Control screen.Amazon sets API speed per user. This means that you may exceed these guideline speeds.
Multi-machine users: If you are using PC2 on more than one device, please be aware that the Amazon-enforced API restrictions mean that you continue to be unlikely to see any advantage when running multiple jobs on multiple machines, as they will end up competing with each other. This could lead to slower running than if you’d just use a single device. The exception is browser runs where extraction time could be slower than actual runtime.
A suggested setup for such a situation is to run the browser extraction with only source columns on the one machine(s), then feed it to the other for actual analysis.Care has been taken to time all API calls to optimise throughput, nevertheless we do recommend using the Filters menu to discard unsuitable or irrelevant items. This will avoid PC2 making unnecessary API calls during the run and will lead to faster results.
...
Fees are specific to your selling account and provided directly by the Amazon API, which means that they will always be accurate as far as the reference offer is concerned, and they should always match the official Revenue Calculator.
However, unfortunately some inferred data points such as “Max cost to 0” or “AMZ price to BE” may no longer be 100% precise depending on the category, and changing the reference offer in Excel (post-run) may not be entirely accurate either.
Important: Amazon states that “The estimated fees returned by this API are not guaranteed. Actual fees may vary.”
As such, queries relating to actual fees not matching those returned by the API are best directed at Amazon directly.
...
Version | Notes |
|---|---|
3.0.0 (all) | Due to extensive remapping at Amazon’s end some of the Additional Attributes (column IDs 2000-2066) might not return a value. Please report issues with these columns with a particular ASIN so that they can be individually addressed. The best way to do so is to add the “All Attributes (JSON)” column. |
3.0.1 | Runs may cancel abruptly with an “error” on all markets except US and UK. Create a custom filter to mitigate:  This is fixed in 3.0.2 |
3.0.2 | Some runs are not finishing to completion. This is fixed in 3.0.3. |
3.0.3 | Some items may be skipped if the “Invalid IDs” warning popup is shown. Referral Fee column has been producing fixed values instead of formulas, preventing recalculation upon changing the reference price in Excel. Sales Estimates not being produced for some categories. Unnecessary data may be downloaded depending on column selection. Some data may be missing depending on column selection. Filters involving ASIN Score may discard items prematurely. The “Listing Restrictions” column is not available to be selected. All these issues are fixed in 3.0.4 |