ALL PLATFORMS
Skuply runs on the shop you already have.
One API key, no plugin, no app and no extension. What differs per platform is not whether it can be done but which kind of field actually filters there. That is where each platform goes wrong, and that is what every page below is about.
WORKS ON
Three platforms, three pitfalls.
WooCommerce
A global attribute is a taxonomy the filter runs on; a custom attribute is text on the page. Fill the wrong one and the filter stays empty.
READ ON
Shopify
Without a definition a metafield does nothing: invisible in the admin, unusable in channels. We create it before the value exists.
READ ON
Magento
Only a dropdown or multiselect with real options ever reaches layered navigation. A text field does not filter.
READ ON
AND OTHERWISE
What we can fill today, and what we cannot.
We can measure any shop, whatever it runs on: our scan reads your product pages the way any visitor can. We can fill five, and on each one we fill something different. We do not hide that difference, because it decides what actually changes in your shop.
WooCommerce
Global attributes and alt text.
Shopify
Metafields in a skuply namespace of our own, and alt text.
Magento
Alt text only. Attributes there go by attribute code, set up differently in every shop; guessing puts a value in the wrong field. Magento fills alt with the file name by default, so that is where the real emptiness sits.
BigCommerce
Custom fields. These shops have no open product list, so connecting comes before measuring.
Shopware
Properties, because that is what the filter runs on. Custom fields are easier to fill but do not filter, and then you have a filled field nobody finds. Alt text lives on the media file, not on the product; we leave it alone.
Does your shop run on something else? Then we can show you what is missing, but not fill it. Shops without a writable product api, like most website builders, we cannot help. We say so before you pay, not after.