Working with a 3PL: the communication that matters

You have outsourced the work, not the responsibility

The pitch for a third-party logistics provider is that fulfilment stops being your problem. In practice what changes is the shape of the problem, not whether you have one. You stop picking and packing. You start managing a relationship with an organisation that holds your stock, does work you cannot watch, and communicates with you through a portal and an email address.

Stores that are happy with their 3PL and stores that are miserable with theirs are often using the same provider. The difference is usually not service quality. It is whether the store set up a working communication arrangement or assumed one would emerge.

The three things you can no longer see

When fulfilment moves out of your building, three kinds of information stop being ambient and start needing to be requested.

Whether an order has actually been picked. Your system says fulfilled when a label is generated. A label is not a parcel. The gap between those two states is where a surprising number of "lost" orders live.

What your real stock position is. Not the number in Shopify, the number on the shelf. These drift, and the drift is invisible until a count.

Whether something has gone wrong that nobody has told you about. A damaged pallet, a mis-slotted SKU, a receiving discrepancy. Warehouses generally do report these. Whether the report reaches a person who acts on it is a different question.

Each of these needs a deliberate answer. None of them answers itself.

What has to flow to the 3PL

The information you owe them is mostly about exceptions and changes, and the most common failure is telling them late.

• Inbound shipments before they arrive. What is coming, when, how many cartons, on what reference. A pallet that arrives unannounced sits.
• Promotions and expected volume. A warehouse staffs to a forecast. A flash sale they hear about on the day is a bad day for both of you.
• New SKUs with their real dimensions. Wrong dimensions produce wrong shipping quotes and wrong cartonisation.
• Special handling. Fragile, batch-tracked, anything requiring an insert or a gift note.
• Order changes and cancellations, fast. There is a cut-off after which a change costs money. Know what yours is.

Most of these are predictable, which means most of them can be scheduled rather than remembered. That is the important part: a communication arrangement that depends on somebody remembering will fail in a busy week, which is exactly the week it matters.

What has to flow back

The return direction is where stores under-specify. It is worth writing down explicitly what you expect to be told without asking, and how fast.

• Receiving discrepancies. They counted 480 and the paperwork said 500. You want this within a day, not at month end.
• Damage. Inbound and outbound, with photographs.
• Orders they cannot fill. Before the SLA expires, not after.
• Stock that has gone below a threshold you set. If they can do this, take it.
• Anything that changes their capacity. A site move, a system change, a peak cut-off date.

Ask for these during onboarding, in writing. Asking after a problem reads as blame; asking before reads as competence, and account managers generally respond well to a client who has thought about it.

The cadence that actually works

Two rhythms cover most of it, and both should be short.

A daily exception check. Not a report of everything, a list of what did not go to plan: orders not shipped within SLA, receiving discrepancies, anything on hold. Five minutes for one person. If nothing is on the list, the check took thirty seconds and you have learned something.

A monthly account call. Volume, accuracy, cost per order, anything recurring. This is the meeting where structural problems get fixed, and skipping it for three quiet months is how you arrive at peak with an unaddressed issue.

The weekly middle ground tends to collapse, because there is rarely a week's worth of new material and the meeting stops feeling worth attending. Daily and monthly, both short, holds up better.

When the portal and reality disagree

Every 3PL relationship eventually produces a moment where the portal says one thing and a customer says another. How you handle these determines how much they cost.

The mistake is to resolve them one at a time and move on. A single mismatch is an incident. A pattern of mismatches is a process problem at the warehouse, and it will keep costing you until somebody names it.

So log them. Not elaborately: date, order, what the portal said, what actually happened. After a month you either have a handful of unrelated one-offs, which is normal, or you have a shape, which is a conversation to have on the monthly call with evidence rather than a feeling.

One mismatch is bad luck. Five with the same cause is a process, and processes get fixed when somebody can point at them.

Who on your side owns the relationship

This should be one person, and it should not automatically be the owner.

A 3PL account manager who receives messages from four different people at your store, none of whom knows what the others asked, will be slower and less useful than one who has a single counterpart. This is not a warehouse quirk. It is true of any relationship where context accumulates.

Name the counterpart, tell the 3PL who it is, and make sure everything that goes to them goes through or past that person. The point is not gatekeeping, it is that somebody holds the history.

Inside your own team, keep that history somewhere the rest of the team can read, which is the thing a shared inbox does badly and a room does well. If the person who owns the relationship is off for a week, their replacement should be able to read what happened rather than start from nothing.

Peak, and the conversation to have in September

Warehouses plan peak months ahead. The stores that get looked after during peak are the ones that gave a forecast early and were roughly right.

Ask for their cut-off dates, their receiving cut-off for inbound stock, and what happens to SLA during the busiest fortnight. Give them your promotional calendar, even in rough form, and a volume estimate you are prepared to be held to.

Being slightly wrong with an early forecast is much better than being exactly right with a late one. A warehouse can staff to a number they were given in September. They cannot staff to a number you knew in September and told them in November. Our BFCM preparation checklist covers the store-side half of the same planning.

The onboarding questions worth asking

If you are choosing or changing provider, a handful of questions separate providers quickly, and all of them are about communication rather than price.

• Who is my named contact, and who covers them when they are away?
• What do you tell me without being asked, and how fast?
• What is your cut-off for an order change, and what happens after it?
• How do I raise something urgent outside the portal?
• What does your reporting show me about accuracy, not just volume?

The answers matter, but so does the manner. A provider who has clearly been asked these before, and has a ready answer, is telling you something useful about how they run.

What this looks like in Store Huddle

The practical shape is a room for the 3PL relationship with the people who need it in it: whoever owns the relationship, whoever covers them, and whoever handles the daily exception list. Portal mismatches get logged there as they happen, so the monthly call has evidence attached rather than recollection.

Attaching the actual order to the conversation removes the most common friction, which is four messages spent establishing which order everybody is talking about. Exceptions that need somebody to act become tasks with an owner and a date rather than messages that may or may not have been read.

The 3PL itself does not need to be in your workspace for this to help. The value is on your side of the relationship: one place where the history lives, so the person covering next week can read it.

Common questions