PLATFORM
Skuply for Shopware
Connected through the Admin API with an integration, no plugin. And above all: we fill properties, because that is what the filter in your storefront reads. Custom fields are quicker to fill and deliver nothing.
CONNECTING TAKES ABOUT HALF AN HOUR ON YOUR SIDE
THE PITFALL
Neatly filled, and the filter stays empty.
Shopware has two places to say something about a product that both look reasonable in the admin. The filter in your storefront reads only one of them.
Custom field
A free field on the product. Visible in the admin, usable in an export, and completely invisible to the filter in your storefront.
skuply_material = full-grain leather
DOES NOT FILTER
Property
A property group with options. This is what the filter panel in the storefront reads, and what a visitor ticks to find your product.
Material → full-grain leather
DOES FILTER
This costs us more work: a property only exists once both the group and the value are there, and we create them when they are missing. That comes with a promise. Whatever was already on a product goes back into the store unchanged, so we can never delete a property you set yourself.
THE CONNECTION
An integration, not a plugin.
You create an integration under Settings, System, Integrations that may edit products, and give us the Access key ID and the Secret access key. We install no plugin, so no code is added that can break on an update. Shopware has no public product list, so we can only measure once that key exists.
What we read
Products, variants, properties, media, categories and the existing descriptions.
What we write
Properties: the property group and the option, and the link to the product.
What we cannot reach
Orders, customers, prices and stock. We do not request those scopes.
WHAT FILLS UP INSIDE SHOPWARE
property_group
the property itself, created when missing
property_group_option
the value inside that property
product.properties
the link, with your own properties included
media.alt
read only, never written
productNumber
read only, to recognise products
ean
read only, to see what is missing
skuply provenance
source, timestamp and confidence, in our own log
We do not write alt text on Shopware. It sits on the media file rather than on the product, which would make a rollback half a job. We do read it, otherwise our report would put you at zero for no reason.
EXPLORE ALL CMS
Skuply runs on the other two as well.
WooCommerce
The difference between a global and a custom attribute, and why your filter stands or falls on it.
READ ON
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
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 SHOPWARE
What Shopware admins always ask.
Do you create new properties in our store?
Yes, when the property or the value does not exist yet. That is the only way a filter can come into being. We show you in advance which ones we would create.
Can you delete our existing properties?
No. We first read what is on a product and send that back unchanged. Even if Shopware were to replace the list rather than add to it, everything of yours stays.
Why not custom fields? They are faster.
Faster, yes, but a visitor cannot filter on them. Then you have a filled field nobody finds, and nobody pays for that.
We use variants with options.
Options are variant-defining and we stay away from those. We only write properties, which apply to the product as a whole.
Why can you only measure us after connecting?
Shopware has no public product list. We can read your product pages for a first impression, but the real catalogue arrives with your key.