Unmapping takes a vendor's SKU off your products, so Spark Shipping stops ordering those products from that vendor and stops using its stock and cost for them. You do it with the same two-column file you'd use to map, uploaded to the same vendor.
How to unmap
- Go to Vendors, click the vendor, then click SKU Mapping in the left menu.
- Under What's in this file?, choose Basic SKUs.
- Click Unmap.
- Choose a CSV with a ProductSku and VendorSku for each product you want to unmap. It's the same format as the Basic SKUs template.
- Check the Preflight check, then click Unmap Basic SKUs.
The job starts right away and the page links you to its job log.
What happens to the products
Spark Shipping removes this vendor's SKU from each product in the file. If a product is also mapped to other vendors, it stays with them and nothing else changes.
If this vendor was the only one, the product moves to Default Vendor with stock 0. The page warns you about this before you upload. With nothing in stock and no vendor behind it, the product won't sell until you map it again.
If you're moving products from one vendor to another, map them to the new vendor first and unmap the old one second. They never land on Default Vendor at 0 that way.
Bundles and Super Bundles
To take a component out of a bundle, choose Bundles instead and use the three-column file. Creating Product Bundles walks through it.
Super Bundles work differently. Unmapping a Super Bundles file breaks the Super Bundle apart: its items become regular bundles and the parent becomes a simple product. Spark Shipping asks you to tick a box confirming that before it will run. If you only meant to drop one vendor from a kit, stop and contact support first.