The customer rejected a delivery because the pallet labels were wrong. How do we prevent it?
Why do customers reject deliveries over pallet labels?
It is Thursday morning at a distributor of cleaning supplies. A truckload of 22 pallets arrives at a retail customer's distribution center for a 7:00 a.m. appointment. The receiving clerk scans the first pallet label and gets an error: the label carries the purchase order number from a cancelled order that was replaced on Monday. The clerk checks two more pallets, finds the same problem and refuses the load. The driver calls the carrier's dispatch, dispatch emails the distributor's customer service inbox, and by the time the logistics coordinator sees it, the truck is on its way back to the terminal with a redelivery fee and a new appointment two days out.
Customers reject deliveries over pallet labels because their receiving process depends on the label: the receiver scans it to match the pallet to a purchase order, a ship-to location and an expected quantity, and when the label does not match, the freight cannot be received without manual work the receiver will not do. The way to prevent it is to know each customer's label rules, build the labels from the same up-to-date order data as the packing slip and bill of lading, and check the labeled pallets before the truck leaves.
Large receivers, such as retail and grocery distribution centers, often publish their requirements in a routing guide or vendor compliance manual. Smaller customers may have a few simple rules shared by email. In both cases the rules are the customer's, and a delivery that breaks them can be refused, delayed or accepted with a chargeback.
What the label does at the receiving dock
At a busy distribution center, the receiving clerk does not open every pallet. The label tells the clerk what is on it and which order it belongs to. A scan connects the pallet to the order in the receiver's warehouse system, sets the putaway location and confirms the quantity. If the label is wrong, the clerk would have to stop, check the contents by hand, call the buyer and fix the record. Many receivers simply refuse the freight instead, because their dock schedule has no time for it.
The most common label errors
The errors that cause rejections are usually simple:
- Wrong or old PO number. The order was changed, split or replaced and the labels were printed from the old version.
- Wrong ship-to location. The label names a different distribution center or store number from the one receiving the freight.
- Pallet count mismatch. Labels say "1 of 20" when 22 pallets shipped, or the BOL shows a different count from the labels.
- Missing required fields. A lot number, a product code, a carton count or a "mixed pallet" marking the customer requires is not on the label.
- Wrong placement or number of labels. The customer wants labels on two adjacent sides, and the pallet has one label on the side facing the wall of the trailer.
- Unreadable barcodes. The barcode is smudged, covered by stretch wrap, torn in transit or printed too small to scan.
Most of these are data errors. Only the last two are mainly physical, and even those come from rules nobody wrote down for the dock.
What a rejection costs
A rejected load usually brings a redelivery fee or return freight, possible storage at the carrier's terminal and a new appointment that may be days away. The customer may apply a chargeback under its compliance terms. The order may miss a promotion or a store shelf date. And the team spends a day on calls instead of other loads. For how chargebacks work more broadly, see how to avoid retailer chargebacks for late or non-compliant shipments.
Let's review your customers' labeling requirements. You don't need to prepare anything: Cartage maps the workflow with you on the call.
See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.
Book a demo →How do you build a process that gets pallet labels right?
Write each customer's label rules down, make labels from the current order data, keep the labels, packing slip and BOL in step, and check the pallets before loading. Each step closes a different gap.
Step 1: Collect each customer's rules
For every customer with labeling requirements, collect the source document: the routing guide, the vendor compliance manual or the email with the instructions. Pull the label rules into a one-page sheet:
- Required fields on each pallet label, in the customer's terms.
- Barcode type and size if the customer specifies one.
- Number of labels per pallet and where they go.
- Rules for mixed pallets, partial pallets and single-item pallets.
- What the packing slip must show and where it goes on the load.
- What the BOL must show, such as the PO number, the pallet count or the customer's location number.
- Any advance notice the customer requires before shipment, and who sends it.
Keep the source document with the sheet, and note the date of the version you used. Customers update their manuals, and an old version is a common cause of rejections that "never happened before".
Step 2: Make the order data complete before printing
A label is only as good as the order behind it. Before labels are printed, the order should have every field the customer's sheet requires. If the customer requires a lot number on each pallet and the order does not have one, the order is not ready to ship. Do not guess the value, and do not print a label with the field blank and hope the receiver does not notice. Ask for the detail and hold the order until it arrives.
Step 3: Generate the labels, packing slip and BOL together
The three documents describe the same load, so they should come from the same record. When the PO number, ship-to location or pallet count is entered once and used for all three documents, they cannot disagree with each other. When the labels come from one system, the packing slip from another and the BOL from a template someone fills in by hand, every change is a chance for one of them to fall behind.
The same applies when the order changes. A cancelled and replaced PO, a split shipment or an added pallet should trigger new labels, a new packing slip and a revised BOL at the same time. For more on the documents themselves, see how AI produces freight documents, from rate confirmations to pallet labels.
Step 4: Check the pallets on the dock
Some errors only show up on the physical freight. Before the truck is loaded, the dock should check:
- The number of labeled pallets matches the BOL and the packing slip.
- Each pallet has the required number of labels in the required places.
- The labels are on the outside of the stretch wrap, or under clear wrap, if the customer's rules require it.
- A sample of barcodes scans.
- The label on each pallet matches the products on that pallet.
A photo of each labeled pallet takes a minute and gives the shipper evidence if the receiver later says the labels were wrong.
Step 5: Handle changes at the dock
When the pallet count changes at the dock, because freight was consolidated or a pallet was split, the labels, the packing slip and the BOL all have to change together. A driver may also write a different count on the BOL at pickup. Both cases need the load owner to decide and the documents to be corrected before the truck leaves. What happens when the driver changes the pallet count on the BOL covers that case.
Which label details matter most to the receiver?
The receiver cares most about the fields it scans or matches: the PO number, its own location number, the item and quantity on the pallet, and the pallet's place in the shipment. Getting these right covers most of the risk. The exact list always comes from the customer's own rules.
The PO number
The PO number connects the pallet to the order in the receiver's system. It must be the current PO, not the original one if the order was replaced or revised. When one truck carries several POs, keep each PO on its own pallets unless the customer allows mixed POs, and label each pallet with the PO it carries. A pallet with two POs and one label is a common reason for a refusal.
The receiver's location number
Retail and grocery customers often use their own numbers for distribution centers and stores. The label, the packing slip and the BOL should all carry the number of the location that is receiving this load. When a customer moves a PO from one distribution center to another, the location number changes too, and every document has to follow.
Item, quantity and lot
The label should show what is on the pallet in the customer's terms: its item code if it uses one, the carton count and, where required, the lot or date code. On a mixed pallet, the customer may want a "mixed" marking and a contents list instead of a single item. Quantities on the labels should add up to the quantity on the packing slip.
The pallet's place in the shipment
Labels such as "pallet 3 of 22" let the receiver check that the whole shipment arrived. If one PO ships on two trucks, decide with the customer how to number the pallets, and make sure the BOL for each truck shows only the pallets on that truck. A count that does not add up is often treated as a short or over shipment.
Advance notice and appointments
Some customers require a notice before the freight ships, listing the pallets and their contents, and some require a delivery appointment that quotes the PO. Whatever the customer receives in advance should match the labels exactly. A notice for 20 pallets followed by 22 labeled pallets is a mismatch, even if every label is correct.
What should you do on the day a delivery is rejected?
Get the reason in writing, decide between re-labeling and redelivering, returning or rerouting the freight, and tell the customer what will happen and when. Speed matters, because every day at the carrier's terminal adds cost and pushes the new appointment further out.
Get the reason in writing
Ask the carrier for the receiver's reason for refusing the freight, the time of the refusal and any notes on the delivery receipt. If possible, get photos of the labels the receiver objected to. Ask the customer's receiving or compliance contact to confirm the reason too. "Labels wrong" is not enough: you need to know which field, on which pallets.
Decide what happens to the freight
The options depend on the error and the customer:
- Re-label and redeliver. If the freight is right and only the labels are wrong, new labels can solve it. The question is where the re-labeling happens. Some carriers can arrange it at their terminal for a fee; often the shipper sends someone or the freight comes back to the warehouse. Ask the carrier what it can do before deciding.
- Return to the shipper. If the error is bigger, such as the wrong products or the wrong order, the freight usually comes back, and the order ships again correctly.
- Reroute. If the PO was moved to a different distribution center, the freight may need to go to a new address, which usually means a reconsignment charge and a new rate.
Whatever the choice, confirm it in writing with the carrier, request a new delivery appointment and update the expected delivery date on the shipment. For refusals that are not about labels, the broader steps in what to do when a customer refuses a delivery apply.
Tell the customer and sales
The customer's buyer needs a new delivery date and to know the problem has been understood. The sales team needs to know before the buyer calls them. Send one short message with the reason, the fix and the new date.
Check the extra charges
When the carrier invoice arrives, it may include a redelivery fee, storage, return freight or a reconsignment charge. Compare each charge with what happened and with what the carrier confirmed in writing. Charges that match the decision are fair. Charges for services that were not provided, or above what was agreed, should be raised with the carrier before payment.
Fix the cause the same week
The most important step is the one most teams skip. Find out which part of the process let the error through: the rule sheet, the order data, the document generation or the dock check. Fix that part, not just the load. If the PO was replaced and the labels were not reprinted, the fix is a rule that a PO change always regenerates the documents.
Common mistakes
- Treating every rejection as a one-off. Repeated rejections from one customer point to a missing or outdated rule.
- Printing labels before the order is final. Early printing saves time until the order changes.
- Keeping label rules in one person's head. When that person is out, the rules go with them.
- Fixing the labels but not the BOL. A receiver that sees 22 labeled pallets and a BOL for 20 still has a mismatch.
- Skipping the photo. Without evidence of how the pallets left, it is hard to dispute a chargeback.
- Paying redelivery and storage charges without checking them. Some charges match the decision; some do not.
Which checklist keeps pallet labels right on every load?
Use a customer rule sheet, a pre-pickup checklist and a rejection log. The tables below are generic. Fill them in from each customer's own requirements.
Customer label rule sheet
| Field | What to record | Example entry (hypothetical) |
|---|---|---|
| Source document | Routing guide or manual, with version date | Vendor manual, March 2026 version |
| Required label fields | Every field the customer requires | PO number, DC number, item code, carton count |
| Labels per pallet | How many and where | Two, on adjacent sides |
| Mixed pallets | How to mark them | "Mixed" marking plus a contents list |
| Packing slip | Content and placement | One per load, in a pouch on the lead pallet |
| BOL requirements | What must appear on the BOL | PO number and pallet count |
| Advance notice | Whether a notice is required before shipping, and who sends it | Sent by the customer service team |
| Appointment | How delivery appointments are made | Customer scheduling contact by email |
| Contacts | Receiving and compliance contacts | Receiving lead, compliance desk |
Pre-pickup checklist
| Check | Who | Done when |
|---|---|---|
| Order has every required field | Customer service or logistics | No blank required fields |
| Labels, packing slip and BOL generated from the current order | Logistics | All three show the same PO, location and count |
| Pallet count matches documents | Dock | Count confirmed |
| Labels placed per the rule sheet | Dock | Placement checked on every pallet |
| Sample barcodes scan | Dock | Scans recorded |
| Photo of each labeled pallet | Dock | Photos attached to the load |
| Changes at the dock reflected in all documents | Load owner | New documents issued if anything changed |
Rejection log
| Field | Why it matters |
|---|---|
| Date, customer and receiving location | Shows which customers and sites reject most |
| Reason in the receiver's words | Points to the exact field or rule |
| Root cause: rule, data, documents or dock | Shows which part of the process failed |
| Decision: re-label, return or reroute | Builds a playbook for the next one |
| Extra charges and chargebacks | Shows the real cost per rejection |
| Fix made | Proves the cause was closed |
A hypothetical review
Consider a hypothetical distributor with four label rejections in a quarter. The log shows two from a PO replaced after labels were printed, one from a missing lot number and one from labels hidden under opaque stretch wrap. Three of the four were data errors that a "documents follow the order" rule and a required-field check would have caught. The fourth needed one line on the dock checklist. The example shows the method, not a measured result.
How does Wilson, by Cartage, help prevent label rejections?
Wilson, by Cartage, is an AI logistics agent that generates pallet labels, packing slips and bills of lading from the same shipment record, holds orders that are missing a required detail and handles the carrier, the team and the next steps when a delivery is rejected. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. Think of it as a free logistics department: what big shippers build over years, Wilson does from day one, in four parts.
The labor. Wilson does the work from the first quote to the final POD: quotes, bookings, paperwork, tracking and carrier follow-ups. Orders reach Wilson by email, an ERP connection or CSV and XLSX files. When an order is missing a detail the customer's documents require, such as a lot number, Wilson does not book it. It holds the order as pending, asks the customer for the missing detail and tells the team. It never invents the missing value.
Wilson generates the bill of lading, packing slips and pallet labels and attaches them to the shipment, with an activity log of who wrote what and when. It can request, chase, file and attach any document configured in the workflow, so a loading photo can be a required document that Wilson asks the warehouse for before pickup. Wilson does not see the pallets: the physical check of placement and scanning stays with the dock. Wilson also does not upload documents to customer portals.
When a BOL change touches the address, freight class, carrier or price, it goes to the load owner. When a delivery is rejected, Wilson contacts the carrier, tells the team, tells the customer if that is configured and follows up with the carrier by phone and email until it gets an answer. Once the team decides between redelivery, return or a new address, Wilson works with the carrier on the new plan and updates the expected delivery date.
The data. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. A customer's label and document requirements can be kept as rules the team can see and edit, such as "this customer needs the PO and DC number on every pallet label". When the team changes something on one load, Wilson treats it as a change to that load; if it looks like it should become a rule, Wilson asks the team whether to make it one. Every message, document and change is kept in the shipment's change history.
Wilson replaces the TMS for freight execution and connects to the company's ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope.
The network. Wilson gets better freight rates on every lane because the shipper's volume counts with every other Wilson customer's. The network includes carriers and brokers, and the company still approves who hauls its freight.
The payments. Wilson audits every carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Redelivery, storage or return charges that fall outside the rules are held and flagged for a person, along with any invoice over the agreed rate.
Control stays with the company. Wilson starts with assisted execution, the company sets approval limits, and routine actions can run automatically within those rules as the workflow is proven.
Pricing
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.
FAQs
Can Wilson make our pallet labels and packing slips?
Yes. Wilson, by Cartage, an AI logistics agent, generates pallet labels, packing slips and bills of lading and attaches them to the shipment. Because all three come from the same shipment record, they show the same order details. If a required detail is missing from the order, Wilson holds the order and asks for it instead of guessing.
Why do distribution centers reject freight over labels?
Their receiving process depends on scanning the label to match the pallet to a purchase order, a location and a quantity. When the label does not match, receiving the freight would take manual work the dock has no time for, so many receivers refuse it or accept it with a chargeback.
What are the most common pallet label errors?
An old or wrong PO number, the wrong ship-to location, a pallet count that does not match the BOL, missing required fields, labels in the wrong place and barcodes that will not scan. Most are data errors made before the labels were printed.
Where do we find a customer's label requirements?
Large customers usually publish them in a routing guide or vendor compliance manual. Smaller customers may send instructions by email. Ask the customer for the current version and record its date. If you need rules for your own carriers and suppliers, write your own routing guide in the same format.
Can a carrier fix wrong labels at its terminal?
Some carriers can arrange re-labeling at a terminal for a fee, and some cannot. Ask the carrier before deciding. If it cannot, the freight usually comes back to the warehouse or the shipper sends someone to re-label it.
Who pays when a load is rejected for wrong labels?
The shipper usually pays the redelivery, storage or return charges, because the error was on its side. The customer may also apply a chargeback under its compliance terms. Check each carrier charge against what was agreed before paying.
Does Wilson check the labels on the physical pallets?
No. Wilson does not see the pallets, so the dock checks placement and scans. Wilson can request a loading photo as a required document, chase it before pickup and attach it to the load.
What should happen when the order changes after labels are printed?
The labels, packing slip and BOL should all be regenerated from the updated order before the truck is loaded. Old labels should be removed from the pallets. A written rule that any PO change regenerates the documents prevents the most common rejection.
Can Wilson upload labels or documents to a customer's portal?
No. Wilson does not upload documents to customer portals. Those uploads stay with the team. Wilson generates, files and attaches the documents to the shipment record.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
Let's review your customers' labeling requirements. You don't need to prepare anything: Cartage maps the workflow with you on the call.
