Specialized webshop for professional tools

Industry
Professional tools (masons, builders, restorers)
Location
Croatia
ERP
KIS (Micronic), bridge toward existing importer
Duration
2 to 5 weeks
Live in productioncom-adria.hr
Challenge

What needed solving.

The client has many items in the ERP, but most are variants of the same product. The previous setup treated every variant as a separate product, and the catalog exploded. Grouping was needed, without breaking the existing ERP importer and without manually mapping thousands of items.

Solution

What we built.

We group several ERP items into one logical product. The customer picks an option through a simple interface, the system pulls the exact SKU from the ERP. All orders return to the ERP with the correct item code. Custom theme, online payments, R1 invoice and fiscalization. Five languages in one catalog, eleven international brands presented as authority in the vertical.

Production outcomes
2k→300
ERP variants grouped into clean products
5
languages in production (HR, EN, DE, SL, IT)
11
partner brands featured
100%
orders returned to the ERP with the correct SKU
Technology
  • WordPress
  • WooCommerce
  • Tailwind CSS
  • Vite
  • ERP bridge
  • Online payments
  • Multilingual setup
Technical highlights
  • Stable variant grouping that survives sync
  • Bridge that doesn't break the existing ERP importer
  • Accurate orders feed with the correct item code
  • Online payments, COD, R1 invoice and fiscalization
  • Brand section that's easy to extend

The catalog dropped from two thousand listings to 300 clean products. The multilingual setup opened up EU customers.

Selected example · operations

What we learned

Lessons that feed the next project.

  1. 01

    Variant grouping is 80% business decision, 20% technical

  2. 02

    A bridge to the existing importer is cheaper than a full fork

  3. 03

    Multilingual makes sense only when a consistent content workflow exists

Other work

Ready to talk?Send an enquiry

A short conversation about your business. After the conversation we agree on the documentation phase and an initial proposal, before any code is written.

Email us