Customer pick-up (CPU) relationships seem like an amazing idea at first glance. After all, with CPU, your customer handles picking up their order entirely. Wouldn’t it be a huge relief to pass off coordinating shipping and everything that comes with it?
Not quite. We’ve seen first hand that surrendering control of logistics operations can ruin retail relationships and tank brands’ gross profit.
Why CPU Relationships Don’t Benefit CPG Brands
As part of a contract with your organization, distributors will offer to pick up your product from your warehouse and store it in theirs before transporting it into a retailer’s supply chain.
But letting a distributor manage your transportation can cause service failures. Distributors schedule pick-up when it makes the most sense for their network, not necessarily yours. Without scheduling the appointment yourself, you lose the ability to set and monitor when a truck will arrive to grab your order.
This can throw off having enough lead time needed to prepare a smooth delivery. If that happens, the scheduled carrier will likely leave your product and require you to reschedule, which can result in missed appointment times. These appointment misfires are always the vendor’s responsibility when working with a distributor, even in CPU arrangements. Your organization will be fined by the distributor as well as tasked with finding a delivery alternative.
Consistently missing appointments, even if they are due to poorly coordinated customer pick-ups, can also jeopardize your space on store shelves. On top of that, your brand will need to pay for warehousing space while waiting for a new pick-up. This can sometimes take weeks and even months before a new pick-up is arranged, which can throw your production facilities and parts of your supply chain into misalignment.
Zipline Clients Hurt by CPU Relationships
Unfortunately, we’ve seen some of our customers get burned by CPU relationships. One of our clients – let’s call them Client A – recently shared their negative experience with CPU.
A retail buyer in Client A’s network was fed up with constant shipment delays and missed pick-ups. Not knowing they were in a CPU arrangement, the buyer believed it was Client A that was falling short. In turn, they warned Client A that they would no longer be extending their delivery due date or be understanding about missed pick-ups. This means Client A will be more likely to get late fees. If the issue continued much longer, they risked losing their relationship with the buyer altogether. The buyer also went to the warehouse to complain, but the warehouse informed them that the CPU orders had been ready. They just weren’t getting picked up by the customer. The warehouse was also charging Client A for having to hold their freight for additional days.
Even though none of this was Client A’s fault, they are now ones enduring the consequences. Fees are piling up and their relationship with the person who gets their product on the shelf is tanking.
Another issue is that Client A’s only way to reach their customer was through the retail buyer, who we’ve already established is not going to be flexible with them any longer. Client A is now scrambling to keep their relationship by preparing a defense, enlisting the warehouse’s help to get documentation on…
- When orders have been scheduled
- How often they’ve been missed
- Additional charges they are incurring
- What needs to be re-scheduled
All of this extra, unnecessary work and stress for Client A could be avoided by not being in a CPU relationship in the first place.
We also had a different customer – Client B – recently switch a large lane from CPU Pricing to a Delivery model, due to nuances in their inventory process. Client B was in a CPU relationship in which several truckloads were not picked up or re-scheduled for weeks on end. After looking into it, Client B realized they were getting orders with multiple SKUs and if one order was short, it would automatically be cut.
Client B’s customer was routing with a mix of carriers and would simply not pick up if a shipment was under a full truckload amount. Orders would be delayed for weeks or cancelled entirely, only getting corrected in end-of-month audits and ultimately equating to lost sales. By getting out of the CPU relationship, Client B is now able to combine loads together, have greater insight into when product will be available, and give approval to ship short if needed.
Work with a Retail-Specialized Logistics Provider
These stories are two of MANY we’ve heard about why CPG brands should avoid relying on CPU relationships.
To set your brand up for success, consider working with a specialized logistics provider that understands what is at stake. Zipline Logistics‘ retail experts know how to control the controllables and eliminate fines, lost shelf space, and headaches.
What Zipline Logistics brings to the table:
- 95% on-time in-full average for appointments
- World-class customer satisfaction score ranking 5 times the industry average
- National network of 38,000+ hand-picked carriers vetted to haul retail goods specifically
- Consultative retail logistics solutions
The post Client Testimonials: CPU Relationships Hurt More Than Help appeared first on Zipline Logistics.