When multi-source inventory is already configured, the expected behavior is for the Relative URI in the Magento inventory import step to change from:
V1/products/{sku}/stockItems/{itemId}toV1/inventory/source-items
This is required for compatibility with multi-source inventory in Magento 2.
Confirm initial setup
Ensure you configure the multi-source inventory setting in both:
-
Magento 2
-
Magento 2 - NetSuite integration app (under General Settings)
Check NetSuite saved search:
-
Confirm that location_id (or locationb_id) is present in the Results tab
-
The saved search must return valid data for source mapping
Steps to troubleshoot
-
Toggle multi-source inventory setting:
-
Turn off the multi-source inventory setting in the integration app and save.
-
Re-configure the Multi Source Inventory setting and save.
-
Then, check if the Relative URI updates.
-
-
Disable and Re-enable inventory flow:
-
Disable the NetSuite Inventory to Magento Inventory Add/Update flow
-
Re-enable it and check if the URI updates in the import step.
-
-
Manually verify the URI:
-
Navigate to the import step of the flow.
-
Check if the HTTP method is POST and the Relative URI is V1/inventory/source-items.
-
-
Recheck multi-source inventory mapping:
-
Go to Settings > General > Multi Source inventory mapping and confirm the source mappings are correct.
-
Remove and re-add sources if needed.
-
-
Try using a cloning template (if you're migrating to a new tile):
-
Use Celigo’s cloning feature to carry over mappings from the old tile.
-
This avoids starting from scratch while testing in a new sandbox environment.
-
If the Issue Persists
-
The current install might be corrupted or partially failed due to a network interruption.
-
In this case, perform the following:
-
Provision a new Sandbox tile
-
Reinstall the integration app
-
Configure multi-source inventory in the new tile
-
Test if the correct Relative URI appears
-
The cloning template can be used to avoid remapping manually on the new tile.
Note
-
The relative URI cannot be edited manually through Postman or the UI.
-
This issue has occurred due to the inconsistent application of multi-source inventory settings in some environments.
If the new tile resolves the issue, the root cause is most likely a corrupted or incomplete configuration in the original instance