PLATFORM
Skuply for WooCommerce
Connected through the REST API, no plugin inside your installation. And above all: we fill the kind of attribute your filter actually runs on, because that is where WooCommerce goes wrong.
CONNECTING TAKES ABOUT HALF AN HOUR ON YOUR SIDE
THE PITFALL
Neatly filled in, and the filter stays empty.
WooCommerce has two kinds of attributes that look almost identical in the admin. The difference decides whether a visitor ever finds your product.
Custom attribute
Plain text on the product. It sits neatly on the page, but it is not a taxonomy. A filter cannot use it, a feed usually will not read it, and search does not work.
material = full-grain leather
INVISIBLE TO THE FILTER
Global attribute
A real taxonomy with the pa_ prefix. Filterable, searchable, and it travels with the product feed. This is the one you need.
pa_material = full-grain leather
FILTERABLE AND READABLE
We first check which of the two your shop uses, per attribute, including the fields a plugin or the theme created. Then we write to the field that works, and mirror it to the field your theme displays.
THE CONNECTION
One key, no plugin.
You create a REST key in WooCommerce with read access to products and write access to product fields. We install nothing, so no code is added that could slow your site down or break on an update.
What we read
Products, variants, categories, attributes, media and the existing descriptions.
What we write
Attributes, titles, descriptions, alt text and our own skuply fields.
What we cannot reach
Orders, customers, coupons and settings. We do not request those permissions.
WHAT FILLS UP INSIDE WOOCOMMERCE
pa_material
global attribute
pa_size
read only, we do not fill size
pa_en-norm
read only, we do not create new attributes
post_title
read only, never written
post_content
read only, never written
_wp_attachment_image_alt
alt text from the product title and the colour
skuply_meta
source, timestamp and confidence
Which fields these are exactly depends on your theme and plugins. We work that out on day one.
EXPLORE ALL CMS
Skuply runs on the other two as well.
Shopify
Without a definition a metafield does nothing. We create it before the value exists.
READ ON
Magento
Only an attribute with real options ever reaches layered navigation.
READ ON
BigCommerce
No open product list, so the key comes first. And custom fields named differently on every product never become one field.
READ ON
Shopware
The filter runs on properties, not on custom fields. We fill the first, even though the second is easier.
READ ON
Another platform
If your shop runs on something else with an API, that is a conversation and not a no. Tell us what it is.
PUT IT TO US
QUESTIONS ABOUT WOOCOMMERCE
What WooCommerce admins always ask.
Will it slow our site down?
No. No plugin is added and we write in batches outside peak hours. On large catalogues we spread the writes across the night.
Will our theme keep working?
Yes. We create no new templates. If your theme displays a custom field, we mirror the value there as well so the page stays correct.
We use WPML or Polylang.
Then we fill per language. Attributes with their own taxonomy per language each get their own normalised value.
We have variable products.
Attributes that serve as a variation axis go on the exclusion list. We stay away from those, otherwise your variants break.
We are still on an old version.
The REST API exists from WooCommerce 3.5 onwards. Below that, updating is the first step and we do not do that for you.