YARDPUMP · Buying Guide

Should Every Branch Stock the Same Pump Service Kit?

Compare real transfer time, compatibility and simultaneous demand before pooling slow-moving pump service kits across dealer branches.

Imagine a distributor with three branches. Each holds one rarely used repair kit, while one location urgently needs a different kit to finish a job. Inventory is spread across shelves that cannot help within the customer’s deadline. Pool a compatible part only if the central location can deliver within the required service time and can cope with overlapping demand. Keep local stock where the consequence of delay or an unreliable route makes central supply unsuitable. A shared spreadsheet balance is not the same as an available kit.

Make the part truly poolable

Start with the full approved kit number and the pump serial or configuration ranges it serves. A kit described as “fits this family” may contain an old seal, different fasteners or instructions for another revision. Confirm both the applicability and any direction of substitution; a newer service kit does not necessarily work on all older units. Physically separate incompatible versions and keep any special storage conditions. Pooling several similar items into one bin does not reduce inventory risk if none can be issued confidently.

Set the response time from the moment the branch confirms the requirement to the time the technician has a correct, released kit. Count order cutoffs, picking, route times, weekends, holidays and inspection at receipt where required. If shipping takes one day but the next van leaves in two days, the promised service time is longer. Establish which stock is reserved, quarantined or already moving. The same kit cannot be promised to a second branch after the first has requested it.

Compare same-day overlap, not just average usage

For illustration, imagine three branches holding one kit each and a proposed center stocking two. In a review window there are five single requests on separate days and one day with two simultaneous requests. If both central kits are available and transfer meets the service deadline, the central arrangement could cover that pattern with one fewer unit on hand. If three requests arrive together after a storm, two kits do not cover all three. Neither illustration predicts real failure or demand. Review local peak timing and how quickly the center is replenished before reducing stock.

Measure past requests from ticket and order data, including jobs delayed during shortages. Use actual service deadlines rather than assuming every request can wait. Record if one event affects several branches at once. Pooling is most useful when stock can reach the work and demand is not always concentrated at the same time. Critical repairs with short deadlines may justify a local minimum alongside the central supply.

Prove the handoff before moving inventory

Run a small trial for a defined kit and branch pair. Put the central stock on an actual reservation, verify the compatibility record, pick it, and check when the branch can release it to the technician. Record wrong issues and cutoffs as well as successful transfers. Define the owner for emergency requests, replenishment triggers and what to do if the shipment fails. A kit removed from a shelf must become unavailable to the other locations immediately. On receipt, preserve part and lot identity; repacking or forwarding must not break traceability.

A central pool is a service promise only when its movement and compatibility are proven. Ask how many correctly identified kits will be available within the promised time on a busy day. If that answer cannot be tested, retain the local reserve until the transfer process is established.

Frequently asked questions

Can the center stock an older kit that has the same dimensions?

Only if the approved compatibility record covers the exact application. Matching dimensions alone do not make the kit poolable.

Does a stock transfer always count as an extra sale?

No. It moves an existing unit between locations. Track customer demand separately so the same request is not counted twice.

When should a branch keep a local minimum?

When the required response is faster than a dependable transfer, demand overlaps often, or the consequence of an unavailable part justifies a local reserve.

Related reading