Automation in wholesale trade. Effective improvements for heavy traffic.

The three mistakes we see most often when implementing automation

Before we get into what to implement, it's worth seeing where others get stuck. The following cases are scenarios based on real projects. The error mechanism is in each case identical to what wholesalers describe after a failed implementation.

Five things no one will tell you when selling your system

1. „Real-time” is not the same for every provider

You ask the supplier: „Is state synchronization real-time?” The answer is yes. The truth is that half of older ERP systems (Subiekt GT, Comarch Optima, part of the Symfonia configuration) do not offer a native API for reading inventory levels in push mode. They export an XML or CSV file every 5-15-60 minutes, which then „imports automatically”. This is not real-time. It is a batch with a short interval, which creates oversale windows in case of high traffic. Before implementation, ask directly: what protocol and with what delay does data get from ERP to the portal?

2. Cascading discount is math that the system needs to understand

Wholesalers typically have three overlapping levels of discounts: contract discount per customer (negotiated with the merchant), volume discount per order (the more, the cheaper) and product discount per category or manufacturer. In manual pricing, the salesperson „knows” that these discounts add up to a certain limit, because this is the company's tradition. None of these limits are saved in the system.

When you try to automate it, the first task is to put that knowledge into rules. If you don't do this, the system will either calculate incorrectly (too expensive or too cheap), or you will have to leave a quote „for salesperson approval” with each custom order, which defeats the purpose of automation.

3. Logistics units vs. sales units

The customer orders 17 pieces of the product packed in boxes of 12. The order goes through the system, the warehouse receives a picking order and the question arises: should I cut it out of an open box or send 2 full boxes (24 pieces)? If the system does not understand the concept of „logistic unit” and does not block orders below MOQ or forces multiples, you generate problems that manual order handling never had, because the salesperson solved them in conversation with the customer.

4. An „optional” B2B portal is a dead B2B portal

If a customer can choose between the new portal and an e-mail to their caregiver, most will choose e-mail. Not because the portal is bad. Because email works and change requires effort. Companies that implemented the portal and left the old channel „for customer comfort” have portals with 15-20% adoption after 6 months. Companies that have defined a date after which the old channel only handles exceptions have the 70-80% adopted at the same time.

5. Knowledge about prices is not in the system - it is in Mr. Marek's head

In every wholesaler there is a salesperson who „knows” that customer X receives -15% for category Y, because this was agreed 3 years ago when signing the contract. This contract is in the drawer. Its terms are not in CRM or ERP. Automating pricing without first cataloging all such arrangements will result in a wave of complaints from customers who received different prices than they expected. Digitizing pricing knowledge is the most difficult and most underestimated part of implementing a B2B portal.

What does it look like in practice? Before and after automation

The summary below concerns a specific stage: the ordering process in a wholesaler handling 80-200 orders a day. The differences are not academic, they are working hours and specific operational risk points.

Roadmap: where to start and in what order?

Warehouse automation is a multi-stage project. The key is the sequence: you start with the processes that bring the fastest return and do not require rebuilding the entire system. An important rule: each phase must be stable and measured before you start the next one. Phase 1 issues discovered during Phase 2 implementation are three times more expensive to fix.

What about ERP that „cannot be integrated”?

We often hear the argument „our ERP does not have an API”. This is rarely true. More often it means: „our ERP has an API, but it is poorly documented” or „our ERP provider wants more for the integration than the entire portal project.” In both cases there is a solution: middleware layer, which reads data from ERP (via the database, file export or legacy API), normalizes it and makes it available to the portal in REST format. It's not an elegant solution, but it works and is many times cheaper than replacing the ERP.

If you are stuck at the „our ERP doesn't work” stage, Describe your situation to us. We've probably seen this particular system before.

How much does it cost and when does it pay off?

For a wholesaler with a daily traffic of 100-300 orders, the cost of implementing a B2B portal with ERP integration and pricing automation is usually in the range 40-120 thousand PLN, depending on the complexity of the existing system and the number of integrations. ROI at this scale is 8-14 months.

For wholesalers with more than 500 orders a day, each minute saved on an order translates into several dozen thousand zlotys a year. Here, the ROI is sometimes shorter than 6 months, and the lack of automation becomes a competitive advantage of rivals who have implemented it.

Summary

Automation in wholesale trade is not an IT project. This is a business project in which IT is a tool. Companies that understand this start by mapping business processes and rules, and only then select tools. Companies that start by choosing a platform end up with a portal that no one uses or a sync that only works once every few hours.

If you run a B2B wholesaler and want to assess which processes are worth automating first and what budget is needed, please contact us. We will perform a free diagnosis and come back with a specific proposal within one business day.