To purge Amazon, the task is relatively simple. The time constraint is dependent on the total number of vendors. The more vendors, the more exports you will need to run, as well as SKU unmaps and mapping you will need to operate. To make everything as simple as possible, follow the steps below. To save time regarding purging, ask yourself which vendors you delete products related to your Amazon store. Importantly, while purging, your products will become unsynced and unmapped, meaning for any live site processing orders, this can have a temporary impact while awaiting each step to be complete, tasked below. You will want to make sure this is noted, and you may need to process orders temporarily while manually purging your amazon.
An example is that we have three vendors connected to our Amazon store. Let's say those three vendors are named "vendor1", "vendor2", and "vendor3." If we only deleted products in our Amazon site that involves "vendor1." it would not make sense in this case to export vendor2 or vendor3. This is something to consider and would save you a lot of time overall. However, if you deleted products from all vendors, running a full purge on all connected vendors is recommended to remove any leftover data within Spark completely.
1. Export all vendor data. We will use these exports to unmap and send all products to the default vendor.
2. Unmap using the exported vendor's data. This will send your data to your default vendor.
3. Request a deletion of all products in your default vendor with support firstname.lastname@example.org
. Make the subject Amazon Purge - Request
4. We will delete your default vendor, and from this point forward, you can use the same mapping files to run SKU mapping, which will bring back all products from default into the perspective vendors.
Repeat this operation for all connected vendors that you deleted products in Amazon and wish for that to reflect within SparkShipping. You only need to export both PRODUCT SKU AND VENDOR SKU.
Step 2: We take the exported file and run that with the perspective vendor. We do not need to run this for all files, only the ones that correspond to the vendor. Make sure that when you are on the SKU mapping page, you are unmapping (it should be grey as depicted in the image below.)
For each unmapping, you should see this as a redirect in your browser as confirmation that it's running. You can refresh and see more information over time, confirming that SKUs are being unmapped.
Step 4: We take the exported file and run that with the perspective vendor. We do not need to run this for all files, only those corresponding to the vendor. Please make sure that when you are on the SKU mapping page, you are Mapping now (it should be mapping by default, as depicted in the image below.) This is how to pull everything back from default into your perspective vendors. You'll want to repeat this process on each vendor you unmapped with their perspective exported files.
How do I know the unmapping is complete?
Check for the total product counts in the tables of each vendor. You should start to see that the total value go down considerably, and at the end of an unmapping, it should be 0.