A working layer on top of your dealer portal

Built for how a workshop actually searches: the right part for the right model and generation, without ringing to ask.

How does a workshop look for a spare part?

With the bike in front of them. The mechanic knows the model, roughly the model year and what is broken. What they do not know is your article number, and that is what your dealer portal asks for. The search becomes a guess, a phone call to your support or an order for the wrong part.

The working layer turns the order around. The workshop filters by model and model-year generation, sees which parts sit in that exact version and what is in stock. Same portal, same prices, same order; just sorted the way a workshop thinks.

What does the working layer show?

ViewWhat the workshop sees
Model overviewYour models with generation, number of versions, purchase price and recommended retail price
VersionsEach version on one row: generation, motor, frame, stock position, and ordering straight from the row
Spare partArticle number, prices, margin, stock status, and which versions the part sits in
Stock versus order itemWhat you have in now and what is ordered in, before the order is placed
Data qualityWhat is missing from the source, such as EAN or image, so it can be corrected

Which part sits in which version is otherwise a phone call. Here it is a click.

Where does the part go next?

Depending on what we agree, the same view can do two things. Either it puts the part in an order with you, through your existing order route, so the workshop orders without leaving the view. Or it pulls the product data into the shop's POS, so the part exists as an article with the right price and EAN when the customer pays.

Many shops want both: order from you and get the article into the till at the same time. It is the same data, delivered in two directions.

Order with you: the workshop orders from the row, and the order goes your usual way.
To the POS: the part is created as an article in the shop's system, with price, EAN and name.
No POS and no workshop system of our own; the view complements what the shop has.

What do we build it on?

On your own data. The model overview, the versions and the spare-part lists come from your source material, not from a sketch. If the link between part and version is missing from your portal, we build it from your exploded views or per-model parts lists, and show you where the material is thin.

The workshop sees only what you choose to show. Purchase prices and margins require the shop's login with you; what is public stays public.

Next step

Start at the small end

We suggest a pilot with one shop and one range, so that the whole chain proves itself in live use before anything is rolled out across your network.

A 20-minute call is enough to see whether there is something worth trying.

Frequently asked questions

Does it replace our dealer portal?
No. The working layer sits on top of the portal and uses your prices, your stock and your order route. It changes how the workshop finds the part, not where it is ordered.
Do we need a parts list per model?
It helps, but what you have is enough: exploded views, compatibility lists or a portal where the part can be found. We build the link between part and version and show you where it is missing.
Does it work for parts from other manufacturers?
Yes, if they are in your portal. The motor, display or battery fitted to your bike appears as a part in that version, with your article number.
How does the workshop get access?
With the shop's usual login with you. Prices and margins are shown only to logged-in retailers.