Our product In production, not a prototype

Customers find the right part. First time.

Which means fewer returns, fewer phone calls and a new supplier live in a day instead of three weeks. It is a PIM for parts merchants on Shopify: supplier files in whatever state they arrive, one catalogue that agrees with itself, pushed live. ACES and PIES native, not an add-on.

ACES PIES PDM Automotive Matrixify Shopify Admin API
A heap of paper spreadsheets beside one lit grid of clean product records

We are not consultants describing this from the outside. We run three businesses of our own and do every one of these jobs in them, every week.

WYBBPlateSellerDrehwerks
64,000+
Products managed
250+
Supplier brands normalised
1
Catalogue that agrees with itself
0
Spreadsheets in the loop
Why it exists

Every supplier sends their catalogue a different way, and all of them are confident theirs is the sensible one.

One sends a 40,000 row spreadsheet with fitment in a free-text column. One sends proper ACES and PIES. One sends a PDF. Brand names arrive as BOSCH, Bosch and Bosch Ltd in the same file. Half the images are 400 pixels wide and the other half are named IMG_0043.

We looked at the PIMs on the market. They are built for brands with a few thousand SKUs they control, not for a merchant reselling 250 brands they do not. Nothing handled fitment properly, which in this trade is the entire point. So we built one.

×The same part listed four times under four names
×Filters that return nothing, or everything
×A new brand taking three weeks to go live
×Returns because it did not fit after all
The pipeline

Supplier file in. Live product out.

Five stages, each one inspectable. When something looks wrong on the storefront you can trace it back to the row it came from.

Ingest

Take it as it comes

ACES and PIES, PDM Automotive exports, supplier spreadsheets in whatever shape. No "please reformat and resend".

Normalise

Make them agree

Brands, attributes and units mapped to one vocabulary. BOSCH, Bosch and Bosch Ltd become one brand, once.

Enrich

Fill the gaps

Titles, descriptions and attributes generated where the supplier left them blank, then held for review rather than published blind.

Score

Know what is weak

Every product gets a quality score. You can see at a glance which 400 products are letting the catalogue down.

Publish

Push it live

Matrixify for bulk, the Shopify Admin API for everything else. Metafields structured so filters actually work.

A wall of catalogue tiles, one filtered set lit
What makes it different

Fitment is the product, not a field on it.

In this trade a customer does not search for a part. They search for their car and expect you to know what fits it. Every generic PIM treats compatibility as another attribute. Ours treats it as the spine.

Year, make, model, engine and sub-model relationships come through from ACES intact and land in Shopify as structured metafields, which is what makes a year-make-model filter possible at all. Most of the ones you see on Shopify stores are faked with tags and break quietly.

Means
Filters that return the right parts, and nothing else
And
Fewer returns, because it fitted
Built for you if
  • › You sell parts on Shopify and your catalogue is past about 5,000 SKUs
  • › You resell brands rather than manufacture, so you do not control the data
  • › Somebody on your team spends their week in spreadsheets, and it is not their job title
  • › Adding a supplier feels like a project rather than a Tuesday
Probably not if
  • × You have a few hundred products you wrote yourself. Shopify alone is fine
  • × You manufacture your own range and own the data end to end
  • × Fitment is not a thing in your category
  • × You want software you install yourself and never speak to anyone about
Where it was proved

Software like this does not come out of a workshop. It comes out of a catalogue that has to work on Monday morning.

It was built against 60,000 SKUs of real supplier data, arriving in every format going, for a business whose revenue depended on customers finding the right part. Nothing in it is theoretical. Every rule exists because that catalogue broke without it.

That is what you inherit. Not a system that will learn your edge cases at your expense over the next six months, but one that already knows them, running in production across 64,000 products and 250 supplier brands.

Status

Built, running and available now. We are taking on a small number of catalogues at a time, because setting one up properly needs us in it with you rather than a signup form.

Start with your own file

Send us a supplier file and we will show you what comes out.

Not a demo environment with sample data in it. Your actual file, run through the actual pipeline, so you can see what your catalogue looks like on the other side.

We do not charge for this, because showing you beats describing it. If the answer is that you do not need us, you will hear that too.