How it works

Any feed in.
Only approved changes out.

Updated June 2026 · Ivan Stancich, STANCICH.AI

Skuvalence sits between your suppliers and Magento. It ingests any feed format, cross-validates every change against your own catalog and rules, lets routine updates through automatically, holds anomalies for your approval, and pushes only validated changes through the native Magento API, with a full record of what changed and why.

The flow

Four steps, one rule: nothing unverified ships.

01

Ingest anything

CSV, Excel, XML, JSON, API, or the supplier's website, with consent.

02

Cross-validate

Every change checked against your catalog, margins and attributes.

03

You approve

Routine changes auto-pass your rules. Anomalies wait for you.

04

Sync, with receipts

Pushed via the Magento API. Logged, traceable, reversible.

Trust & audit

No undesired change ever reaches production.

Built like infrastructure, not a plugin. Explore a change record:

change log · today

chg_88431

rejected · never pushed

€489.00

€302.90

SKU
OPT-4412
Field
price.retail
Source
optica-trade · CSV feed
Validation
Δ −38%: anomaly, exceeds band → held
Decision
you · 08:02

› every change traceable · every change reversible

Lineage per SKU

Every value traces to a source, a time, a rule.

Rules you define

Auto-approve bands, margin floors, attribute checks.

Reversible by design

Any change can be rolled back.

synced

Stock levels

qty, lead times, stockout fast-lane

synced

Prices

purchase & retail, margin-checked

synced

Product data

attributes, descriptions, media

synced

Lifecycle

new products in, discontinued out

FAQ

The mechanics, answered

01What does Skuvalence check before a change goes live?

Every incoming value is compared against your own catalog and the rules you set: your margins, your attributes, your expected ranges. Routine changes that fit pass automatically. Anything outside them is held.

02What happens when something looks wrong?

It's held out of production and queued for your review, with the before, the after, the source, and why it was flagged. You approve it or reject it. Nothing anomalous reaches your store on its own.

03What gets recorded for each change?

Every change keeps its lineage: the value before and after, the supplier and feed it came from, the time, the rule that decided it, and who approved it. Months later you can still answer why a price moved.

04Can a change be undone?

Yes. Every change that lands is reversible, so a bad sync is an inconvenience you roll back, not an emergency you clean up by hand.

Ivan Stancich is an engineer and the founder of STANCICH.AI. Before software he was an automotive quality engineer. The approval-and-audit model here is the same one he built a real ten-thousand-product Magento catalog on.

See it on your own feed.

Send one supplier feed. We map what's broken and send you the report. Free, a few days, yours either way.