We'eve just pushed an update to our EZ Inventory app to provide an option for case-insensitive matching when perofroming variant lookups by SKU, barcode, product title, or a custom variant metafield value.

We've seen a few cases in the past where the supplier's feed may use all uppercase for the SKU while the rmerchant may use all lowercase in Shopify (or vice versa).  We already have an option for manipulating the supplier feed data before doing a lookup via our …

EZ Inventory has been successfully migrated to use the new Shopify GraphQL Product APIs which provide support for up to 2048 (aka 2K) variants per product.

This new limit is a big improvement from the 100 variants per product limit with the old APIs.

All the changes are on the backend, so users of our app don't need to do anything.  Our app will automatically pick up the new variants created that go over the previous limit of 100 after …

There may be cases where your supplier uses a different SKU or barcode from what you use in your Shopify store.  Using Shopify Variant Metafields is a good way to track these. With this EZ Inventory update, you now have the option to map product variants in your Shopify store to products in your suppliers' feeds based on a custom variant metafield's value.

In the Data Feed settings, you can find this option under Field Mapping > Shopify Variant Field.  Select the …

JSON data feed format is now supported in EZ Inventory!

This allows you to upload a JSON file or use a web feed/REST API endpoint that returns JSON data as a data source when updating the inventory quantity of products/variants in your Shopify store.

The JSON data just needs to have a list of products and you can specify the specific key that contains this data in the app.  If the data structure has a variants subfield, our app can …

We've recently pushed an update to our EZ Inventory Shopify app which allows our users to specify additional HTTP headers when pulling their product/inventory feeds.

A use case that came up was when one of our customer's supplier feed recently made a change to their website to require a 'User-Agent' header before the web request is accepted.  So having this option took care of the issue.

There are other use cases where being able to specify a custom header could come …