Auto-generated inventoryItemGroupKey is always the same by using bulkMigrateListing.

[ikkaz-60]

I'm trying to migrate multiple-variation listing which was used with trading api for revising data to inventory api format.
And with the migration, I want to be possible to revise data with maintaining ItemID(listingId) if possible.
(I will call bulkUpdatePriceQuantity for the revising.)

But as the title says, auto-generated inventoryItemGroupKey is always the same by using bulkMigrateListing.
This makes one inventoryItemGroupKey includes multiple sku and offers of multiple item group(i.e. data of multiple ItemID).
After some attempts, offers excluding the first migrated ItemID seems to be UNPUBLISHED and can't revise data, but web page of the item can be viewed(i.e. it seems to be published actually).

I know that makes the items to be revisable by creating new inventoryItemGroupKey(createOrReplaceInventoryItemGroup) and to publish the group key(publishOfferByInventoryItemGroup), but this method delete existing ItemID(listingId) and issue new listingId.
Is it possible to migrate ItemID to revisable without changing ItemID?

[bernie6547]

---

@ikkaz-60 Read Morewrote:

I'm trying to migrate multiple-variation listing which was used with trading api for revising data to inventory api format.
And with the migration, I want to be possible to revise data with maintaining ItemID(listingId) if possible.
(I will call bulkUpdatePriceQuantity for the revising.)

But as the title says, auto-generated inventoryItemGroupKey is always the same by using bulkMigrateListing.
This makes one inventoryItemGroupKey includes multiple sku and offers of multiple item group(i.e. data of multiple ItemID).
After some attempts, offers excluding the first migrated ItemID seems to be UNPUBLISHED and can't revise data, but web page of the item can be viewed(i.e. it seems to be published actually).

I know that makes the items to be revisable by creating new inventoryItemGroupKey(createOrReplaceInventoryItemGroup) and to publish the group key(publishOfferByInventoryItemGroup), but this method delete existing ItemID(listingId) and issue new listingId.
Is it possible to migrate ItemID to revisable without changing ItemID?

---

Migrating multiple-variation listings from Trading API to Inventory API while preserving the original ItemID (listingId) using bulkMigrateListing and bulkUpdatePriceQuantity can be challenging. bulkMigrateListing often assigns a single inventoryItemGroupKey to multiple variations, hindering data revision for variations beyond the first. Consider manual item creation or explore alternative migration tools.