Villeroy wrote:
How often do you get new slut bunnies?
How often do you get new export files?
Ideally I need to update daily to keep them synced.
The slutbunny file (Discogs/45,000 rows) changes by approx 50-150 rows per day. New items are listed. Old items are changed from "For Sale" to "Sold". Prices change on old rows.
The export file (woocommerce/7000 rows) changes daily everytime I use the API to update the data from discogs. It creates a new ID any time there is a new listing_id on discogs and removes an ID if the listing_id is no longer "for sale" on discogs.
export.ID is the page number for the woocommerce site. Each new product listing gets a new unique ID. It is possible to have a stock quantity of any amount on woocommerce.
listing_id is the unique sales page number for the discogs site. It is also the SKU on the woocommerce site. It is NOT possible to have a stock quantity of anything other than 1 on discogs.
release_id is the unique product ID on discogs for the item that is being sold. It is also rel_id on the woocommerce site.
Discogs built a 3rd party app 6 months ago to deal with the quantity=1 issue. This 3rd party app lists the stock quantity data in the [q=n] field within the external_id field. When a listing_id with external_id [q=3] changes from "For Sale" to "Sold" it creates a new listing_id with the same release_id (and price, condition, comments etc etc) but external_id [q=2].
There are multiple instances of the same release_id appearing on multiple listing_id (different condition/price of same item or simply listing errors). I would be willing to remove these instances if it would make things run more smoothly.
I have experimented with using the release_id for the SKU on woocommerce and would be willing to change it again if it would help.
Hopefully that summary helps. There are other issues, but this is the fundamental part I think.