Integrations
It fits around your storefront, not the other way round.
ExactHue Core is one REST call and an optional widget. Nothing about your platform, theme or checkout has to change to accommodate it, and nothing about it is difficult to remove.
Supported platforms
Four ways in.
Three managed integrations and a direct one. Whichever you use, the engine behind it is identical — the difference is only in how the shade finder reaches your product page.
App-embed block
Install the app, drag the block into your product template, and point it at the metafield holding your shade codes. Merchandisers can move or disable it from the theme editor without an engineer, and no Liquid is overwritten — so a theme update never clobbers it.
// cartridge path
int_exacthue:app_storefront_base
// controller hook
Product-Show → append
exacthue.shadeFinder
// template
<isinclude template=
"product/exacthueFinder"/>SFRA cartridge
A cartridge you add to the path, with an SFRA controller hook and one ISML include. It appends rather than overrides, so your existing product controller keeps working and an upgrade does not fork your codebase.
// API extension
trigger: "product.published"
enrich(projection) {
attributes.measuredColour
= "lab(62.1 12.4 18.9)";
attributes.undertone
= "neutral";
}API extension
An extension that enriches product projections with measured colour when a product is published, so your catalogue carries the colour data natively and any front end you build on top of it can read the shade attributes directly.
Custom storefronts
If you built your own front end, integrate against the REST API directly. There is an optional web component if you want the interface handled for you, and it is framework-agnostic — it will sit inside React, Vue, Svelte or plain server-rendered HTML without complaint.
Everything else
In-store tablets, clienteling apps, marketplaces with their own listing pipeline — all of these are just the REST API with a different interface on top. If you can make an HTTPS request and show an image, you can run the engine.
Tell us what you are working with and we will say honestly whether it fits: get in touch.
What actually lands on your site
Small, and easy to audit.
Your security and performance teams will ask. Here are the answers before they do.
Getting your catalogue in
The long pole is measurement, not code.
The technical integration is usually an afternoon. What takes longer is turning your range into measured colour, because that is the part that determines whether any of it works.
There are three ways to do it, and you can mix them:
- You already have spectrophotometer readings. Send them and we validate the format, flag anything out of gamut, and ingest. Fastest route — often a couple of days.
- You have Pantone references but no measurements. We work from those and tell you plainly where the reference is too coarse to trust.
- You have neither. Ship physical samples to the laboratory and we measure the range for you. Two weeks is typical, longer for very large assortments.
Once a range is in, seasonal re-measurement is included on Growth and Enterprise. A catalogue that drifts out of date quietly degrades every match made against it, and we would rather carry that cost than watch accuracy decay.
What we need from you on day one
- A SKU list for the complexion range, with your own shade codes
- Whichever colour data you hold, in any format
- A sandbox storefront or staging environment to point at
- One engineering contact and one merchandising contact
What you get back
- Scoped credentials for sandbox and production
- Your measured catalogue, exportable in an open format at any time
- Per-band accuracy figures for your specific range
- A named engineer in a shared channel through launch
Typical timeline
Four weeks from first call to live traffic.
Assuming a single brand and a complexion range under sixty shades. Bigger assortments take longer, and we will say so up front rather than discover it halfway.
Week one — baseline and samples
We take twelve months of return data and classify it by reason, shade and tonal band. You ship samples, or send readings if you have them. This week usually surfaces a pattern the team had never quantified.
Weeks two and three — measurement
Your range is measured and ingested, with out-of-gamut and unmeasurable finishes flagged before anything goes live. Meanwhile your engineers have sandbox credentials and can build against real responses.
Week four — controlled rollout
The shade finder goes live for a share of traffic, with the rest held as a control. Both cohorts are measured on the same definitions so the read-out means something.
After — the read-out
Mismatch return rate, single-shade order share and per-band accuracy against control. If the effect is not there, that is what the report will say.
Tell us what you are running.
Platform, range size, and where the returns pressure sits. We will tell you what integration fits and roughly how long it takes.