Retailers that run drop ship vendor programs usually require three things around every parcel: a prompt order acknowledgment, a tracking number sent back against the order line, and paperwork in the box that looks like it came from the retailer. Which carrier account pays for the label, and which label format is allowed, is not universal. Each program's own rules decide that, so the first job is to read the program documents and ask the retailer direct questions before you choose how to print labels.

What does a retailer expect from a drop ship vendor?

A retailer expects the vendor to behave like an extension of its own fulfillment operation. The shopper bought from the retailer, so the retailer wants to know quickly that you accepted the order, when it shipped, and how to track it.

Walmart's program is a useful public example. Per Walmart's developer documentation, the DSV Order Management API lets suppliers acknowledge, ship, or cancel order lines. The same documentation says orders must be acknowledged before shipping, preferably within four hours, and that lines ship with tracking information.

That sequence is a reasonable mental model for most programs, even though the details differ:

The retailer sends you an order.
You acknowledge it, or cancel the lines you cannot fill.
You pack and label the parcel.
You send a ship confirmation with the carrier and tracking number for each line.
The retailer tells its customer, and later pays you under the program terms.

A label is only step three. The steps on either side of it are where most compliance problems start.

Who buys the label: you or the retailer?

It depends on the program, and you should not assume either answer. Some programs expect the vendor to ship on a carrier account the retailer provides or designates, some let the vendor ship on its own account and build freight into the cost, and some offer both under different terms.

This post cannot tell you which model a specific retailer uses, because the rule lives in that retailer's supplier agreement and routing documents, and it can change. What matters is the practical consequence:

Program rule	What it means for labels
Retailer supplies or designates the carrier account	Labels must be generated through the retailer's portal or on that account. A separate label tool with its own rates does not fit.
Vendor ships on its own account	You choose how to buy the label, within any carrier and service limits the retailer sets.
Either, by order or by service level	You need a rule in your order flow that sorts orders into the two paths before anyone prints.

If the second or third row applies to you, the label cost is yours to manage, and the choice of carrier becomes an ordinary rate decision inside whatever limits the program sets. The drop ship vendor shipping labels page covers that case in more detail.

Why do packing slips matter so much?

Packing slips matter because the customer should see the retailer's name in the box, not yours. SPS Commerce says retailer-branded packing slips are a common drop ship requirement.

The operational point is that the packing slip is a separate document from the shipping label, and often comes from a separate system. The slip template, the logo, the return instructions, and the fields printed on it are set by the retailer. A team that solves labels but prints its own generic slip can still fail the program's requirements.

Before you ship the first order, confirm three things at the pack station: where the slip prints from, whether it prints in the same step as the label, and how a packer matches the right slip to the right carton when an order splits into several cartons.

What should you ask the retailer before the first shipment?

Ask the questions below in writing, and keep the answers with your supplier agreement. They are ordered roughly the way an order moves through your building.

How do orders arrive: portal, API, or EDI, and which of those is required rather than optional?
How quickly must an order be acknowledged, and is that measured in clock hours or business hours?
What is the ship-by deadline, and how are weekends and holidays counted?
Whose carrier account pays for the label: ours, yours, or either?
If ours, which carriers and service levels are allowed for each promised delivery speed?
If yours, where do we generate the label, and can it be done in bulk?
Does the shipping label need specific content, such as a return address, a reference field, or the retailer's name as shipper?
Is a retailer-branded packing slip required, and where do we get the template?
How do we send tracking: per line, per carton, or per order, and by what deadline after the label is created?
What happens when an order ships in more than one carton?
How do cancellations and short ships get reported, and do they count against a scorecard?
Who handles returns, and to what address?
Are there penalties or chargebacks for late acknowledgment, late shipment, or missing tracking, and where are they published?
Who is our contact when an order is stuck?

The answers to questions 4 through 7 decide whether you have any freedom in how labels are bought. The rest decide how much work surrounds each label. If the program runs on EDI documents, EDI shipping labels explains where a label tool sits next to an EDI provider.

How does this look on an ordinary day?

Here is an example with hypothetical numbers, made up to show the flow rather than to describe any real retailer or supplier.

Suppose a housewares manufacturer receives 40 drop ship orders from one retailer on a Tuesday morning. The program, in this example, lets the vendor ship on its own account and asks for acknowledgment within four hours.

8:15: orders arrive. A coordinator checks stock and finds 38 fillable and 2 out of stock.
9:00: the 38 are acknowledged and the 2 are cancelled through the retailer's system, well inside the window.
9:30: the 38 orders are exported to a file with one row per carton. Five orders need two cartons, so the file has 43 rows, each carrying the retailer's PO number as the reference.
10:00: 43 labels are bought. In this example the average works out to $9.20 per label, or $395.60 for the batch, all tagged with PO numbers.
10:00 to 13:00: packers print the retailer-branded slip from the retailer's portal, pack, and apply labels.
14:00: tracking numbers are sent back per line through the retailer's system.

Two things stand out. The label purchase took minutes, while the acknowledgment, slips, and tracking confirmations took most of the coordinator's attention. And because every label carried the PO number, finance can later compare $395.60 of freight against what the retailer paid on those 38 orders without guessing which parcel belonged to which order.

What goes wrong most often?

Failures tend to come from the handoffs, not from the label itself. Common ones:

Shipping before acknowledging. If the program requires acknowledgment first, a fast packer can create a violation.
Tracking sent late or not at all. The parcel moved, but the retailer's system still shows the line as open.
Wrong paperwork in the box. Your own invoice or slip went in instead of the retailer's.
Multi-carton orders confirmed with one tracking number. Find out how the program wants the others reported.
Mixing marketplace and vendor orders. Selling on a retailer's marketplace as a third-party seller is a different relationship from supplying it as a drop ship vendor, with different rules. If you do both with Walmart, the Walmart Marketplace shipping software page covers the marketplace side.

A short written procedure for each handoff, taped up at the pack station, helps prevent these.

Where GoatLabels fits

GoatLabels fits only the programs that let the supplier buy its own carrier label. If the retailer requires labels from its portal or on its carrier account, GoatLabels is not the right tool for those orders, and there is no way to add your own or a retailer's carrier account to it.

Where the program does leave the label to you, the fit is straightforward. You can import up to 500 rows per CSV file, with errors that name the row and field, or create labels through the REST API with an Idempotency-Key and signed webhooks. USPS, UPS, FedEx, and DHL are rate-shopped on every parcel from one account. Each label debits a prepaid wallet as a dated ledger entry that carries your reference, so a retailer PO number follows the cost, and a multi-carton order produces several ledger lines with the same reference. The Free plan covers 50 shipments a month at $0, and Pro is a flat $40 a month with unlimited shipments; see pricing.

The limits matter here. GoatLabels does not print retailer packing slips or retailer compliance labels such as GS1-128, does not send acknowledgments, ship confirmations, or any EDI document, and has no native EDI or ERP connector. The Walmart connector is one of 13 store connectors for sellers; it is not a drop ship vendor integration. Acknowledging orders and returning tracking to the retailer remain your process, through the retailer's portal, API, or your EDI provider. For the wider picture of how a label tool sits in a wholesale operation, see B2B shipping software.