Nutid at the counter, Abicart on the web

The setup we run in our own bike shop, with everything we have learned from it.

The combination we use ourselves

Hermodex grew out of a bike shop that sells both over the counter and online. The till runs Nutid, the web shop runs Abicart, and the link between them was built so that nobody would have to key in the same article twice.

That means we know Abicart's quirks in detail: how variants behave, what happens to categories when a template is switched, and where prices are actually read from. Those things only surface once you have run a shop through a season.

So when we build the same connection for you, it is not a new construction. It is the same flow, fitted to your article register and your range.

What is synchronised between Nutid and Abicart

The flows are the same ones we run in our own shop, and you choose which of them are active.

Articles created in Nutid are published in Abicart with images and descriptions.
Prices follow the POS, so the shelf price in the shop matches the price on the web.
Stock levels are mirrored, with a margin on articles you want to keep back for the workshop.
Web orders land in the flow so you handle them in one place.

How you get started

Abicart wants the structure settled before the range is loaded in, otherwise the web inherits whatever disorder sits in the POS. So we begin with the register.

We go through categories and variants so they can take being filled automatically.
We set up the connection to your Abicart shop and test it against one limited category.
We scale up category by category until the range is live.

From your side we need a login to the Abicart admin and access to Nutid. After that you keep working at the counter, and the web keeps itself current.

A connection we run in production in our own shop.
Abicart's pitfalls are already mapped.
One register at the counter, one shop window on the web.

We do not build anything for you that we do not run ourselves.