PLATFORM
Skuply for Magento
Connected through the REST API of Magento or Adobe Commerce, no extension inside your installation. And above all: we write values as attribute options, because only then does layered navigation do anything.
CONNECTING TAKES ABOUT HALF AN HOUR ON YOUR SIDE
THE PITFALL
The value is there, and navigation does not see it.
In Magento the attribute type decides whether a value is usable. A text field is invisible to layered navigation; only a dropdown or multiselect with real options does anything there.
Text attribute
Free text on the product. It sits on the page, but layered navigation cannot filter on it and the value cannot be normalised across the catalogue.
material = "full-grain leather" (text)
NO LAYERED NAVIGATION
Attribute with options
A dropdown or multiselect with fixed options, in the right attribute set and switched on for layered navigation. This is what filters.
material = option:1042 (select)
FILTERABLE AND FACETABLE
We create the missing options, attach the attribute to the right attribute sets and switch on use in layered navigation. Existing options we reuse, so no duplicate values appear.
THE CONNECTION
An integration token, not an extension.
You create an integration with read access to the catalogue and write access to products and attributes. We install nothing in app/code, so a Magento upgrade does not touch us.
What we read
Products, attributes, attribute sets, categories, media and the existing descriptions.
What we write
Attribute values and options, titles, descriptions, alt text and our own skuply fields.
What we cannot reach
Orders, customers, price rules and system settings. We do not request those permissions.
WHAT FILLS UP INSIDE MAGENTO
material
select, existing option
size
select, normalised
en_norm
select, newly created
name
title following the formula for this category
description
long description, assembled from the fields
media_gallery.label
alt text from image recognition
skuply_meta
source, timestamp, model version and confidence
Which attributes already exist and which attribute sets they hang in, we work out on day one.
QUESTIONS ABOUT MAGENTO
What Magento admins always ask.
Will it slow our site down?
No. No extension is added and we write in batches. After writing we trigger only the indexers that genuinely need it.
Will our theme keep working?
Yes. We touch no templates. Where your theme displays a custom attribute, we mirror the value there as well.
We have several store views.
Then we fill per store view. Values on global scope stay global, values on store scope get their own normalised term per view.
We have configurable products.
Attributes that serve as a configurable axis go on the exclusion list. We stay away from those, otherwise your variants break.
Does this work with Adobe Commerce?
Yes, and with Magento Open Source from 2.3 onwards. Below that the REST API is too limited and updating is the first step.