Thirty days from the first conversation to a portal through which 300 shops order on their own
- Industry
- Wholesale of household goods and catering supplies
- Location
- Solin, Croatia
- ERP
- KISERP (Micronic)
- Duration
- 30 days to production
The brief
Three hundred business customers, from small shops to chains with twenty or more branches, each with its own price list and discount in KISERP. The portal had to show each customer exactly their prices and real stock, let them order themselves, and land the order in the ERP without anyone retyping it. On top of that, a warehouse that knows from those orders what gets packed tomorrow and in what sequence.
How we solved it
A connector to KISERP pulls per-customer prices and discounts and stock levels, and writes the order into the ERP in two phases, header then lines, with its own key, so even a resend cannot create a duplicate. A company with several branches picks which one it is ordering for with one click: each has its own price list, delivery address and e-mail addresses for confirmations. When a customer does call, the sales rep steps in as them, sees their cart and orders on their behalf, and the order remembers who entered it. The warehouse program prints pick lists for the day from the same orders each morning, with packing sequence, shipping status and a record of who packed what. The catalogue is laid out like an industrial catalogue: dense, with filters, no scrolling through pictures.
Numbers from the project
If you need something similar
- Timeline for a similar scope
- 4 to 6 weeks
Depends on what your ERP exposes through its API and how many business rules need mapping. What the base includes and what is added as needed is on the pricing page.
The price is set by your specific requirements. The real price is defined after a conversation and the technical documentation of the project, before you pay anything.
What the client had to prepare
- Access to the KISERP API and an hour with the person who knows it
- A customer list with e-mail addresses per branch
- Logo and colours
- One person who decides what goes into the first round
Technology
- WordPress
- WooCommerce
- React
- Node.js
- ERP REST API
- MariaDB
What is built in
- An order is sent to the ERP once. If the connection drops and it is sent again, no duplicate is created.
- When KISERP does not respond, the order waits with us and is sent as soon as it is back.
- A sales rep orders on the customer's behalf, and the order carries a mark of who entered it.
- Warehouse pick lists from webshop orders, with packing sequence and shipping status.
- Several e-mail addresses per branch, so confirmations reach both the warehouse and purchasing.
- Logs without personal data and a limited number of login attempts.
What we would tell you before you start
- Business customers do not want a redesign every six months. Once they know where things are, leave them alone.
- Business units are the most complex part, not the catalogue. Who orders for which address and who sees which price has to be settled before any code.
- Duplicate protection from day one is cheaper than cleaning up the ERP later.
Other projects
Tell us what you need. Within 24 hours you get a rough price and timeline.
A few sentences are enough: what you sell, which ERP you use and what costs you the most time today. If it is urgent, call.
Weekdays, 9 to 17. We reply within 24 hours.