Add a signature when the cost of a disputed delivery is higher than the cost of the service, and declare a value when the loss of the parcel would be more than your business wants to absorb. Many B2B parcels may need neither, some need one, and some need both. The useful work is writing down the thresholds once, so the decision is made by a rule at the pack station and not by whoever happens to be printing labels that day.

What is the difference between a signature and a declared value?

They solve two different problems. A signature service is about proof: the carrier records that a person accepted the parcel, which gives you evidence when a customer says the box never arrived. A declared value is about money: you tell the carrier what the contents are worth, and that figure sets the ceiling on what you can claim if the parcel is lost or damaged, subject to the carrier's terms.

Neither one replaces the other. A signed-for parcel can still arrive crushed, and a parcel with a high declared value can still be left at an unattended dock. If you want the longer explanation of each, see signature confirmation explained and the shipping insurance decision guide.

One more distinction matters to finance teams. Coverage bought from a carrier and coverage bought from a third-party insurer are separate products with separate claim processes. This post uses "declared value" for the amount you state to the carrier at label purchase, and "insurance" loosely for any arrangement that pays you back after a loss.

How much coverage is already included?

It depends on the carrier and the service, so check before you pay for more. Per USPS, Priority Mail includes up to $100 of insurance with most shipments. That is the only included-coverage figure this post will state, because the others change with the service, the account, and the carrier's current terms.

For any other carrier or service, read the carrier's declared value and signature services in its current service guide. Look for four things:

The amount of liability included at no extra charge, if any.
How the charge for extra declared value is calculated.
Items that are excluded or capped regardless of the value you declare.
The claim window and the documents the carrier asks for.

Write the answers into a one-page reference for your shipping team and date it. Carrier terms are revised regularly, and a reference with no date on it is the one nobody trusts.

When should a B2B shipment require a signature?

Require a signature when a delivery dispute would be expensive or hard to resolve without proof. In B2B shipping the receiving location is often a staffed dock or front desk, which lowers the risk compared with a residential porch, but it does not remove it. Common cases where a signature earns its cost:

High-value, easily resold goods such as components, tools, or handheld devices.
Deliveries to shared buildings, job sites, or addresses without a receiving department.
Customers with a history of "not received" disputes.
Orders where the contract or the customer's purchasing policy asks for proof of receipt.
Replacement shipments, where a second loss would be especially costly to the relationship.

A signature also has a cost beyond the fee. If nobody is available to sign, the parcel is not delivered that day, and a missed delivery can hold up a production line or a field technician. For customers who receive daily and have never disputed a delivery, a signature may slow things down for no benefit. Teams that ship parts to both warehouses and job sites often set the rule by address type, commercial or residential, so the label step can apply it without a judgment call.

When is declaring a higher value worth the cost?

Declare a higher value when the loss would exceed what you have decided to self-insure. Every shipper self-insures to some degree: below a certain order value, you replace the goods and move on because the paperwork costs more than the claim. The question is where that line sits, and whether it is written down.

A simple way to set it is to compare the fee with the expected loss. Expected loss is the value of the parcel multiplied by how often a parcel like it is lost or damaged in your own history. If the fee for the extra coverage is far above that expected loss, you are paying for peace of mind, which may still be a reasonable choice for a parcel whose loss would hurt cash flow. If your history shows no pattern at all, start with a conservative threshold and revisit it after a quarter of data.

Also check what the declared value actually pays. A declared value is a ceiling, not a guaranteed payout. Carriers generally ask for proof of the item's value and evidence of adequate packaging, and some categories of goods are limited no matter what you declare. Read the exclusions for your product type before you rely on it.

What does a written policy look like? A worked example

A written policy is a short table that maps order value and destination type to an action. The numbers below are hypothetical and exist only to show the shape. Your thresholds should come from your own margins, loss history, and the carrier's current terms.

Example: a hypothetical distributor ships about 2,000 parcels a month with an average order value of $180.

Parcel value (example)	Destination	Signature	Declared value
Under $250	Any	No	No, rely on included coverage where it exists
$250 to $1,000	Staffed dock or front desk	No	Yes, to invoice value
$250 to $1,000	Job site, shared building, residence	Yes	Yes, to invoice value
Over $1,000	Any	Yes	Yes, to invoice value

In this example, suppose the distributor's records show 6 lost or damaged parcels in the last 12 months out of 24,000 shipped, with a combined value of $1,500. Absorbing those losses cost $1,500 for the year. If adding coverage to every parcel had cost even a hypothetical 50 cents each, the bill would have been $12,000. Covering only the parcels over $250, say 300 a month in this example, would cost far less and would still protect the shipments that matter. That is the reasoning the table encodes. The figures are invented, but the method works with your real ones.

To put a policy like this into practice:

Pull 12 months of loss and damage claims with order values.
Set the self-insure threshold and the signature threshold.
Add a column to your order export that flags which rule applies.
Record the rule applied in the shipment reference so finance can audit it later.
Review the thresholds once a year, or whenever the carrier's terms change.

Step 3 is where a policy can quietly fail. If the flag is not in the data that reaches the label step, the pack station falls back on habit. Teams exporting orders from an ERP can carry the flag as an extra column, as described in the guide to ERP shipping integration.

What should you document for a claim?

Document the value, the packaging, and the delivery event before anything goes wrong. A claim is far easier when the evidence already exists. Keep the commercial invoice or order record showing the value, a note or photo of the packaging method for high-value items, the tracking number tied to the order reference, and the date the customer reported the problem. Claim windows are set by the carrier, so file promptly and check the current deadline.

For serialized goods, record serial numbers per carton. Electronics distributors in particular tend to need that link between serial, carton, and tracking number, which is covered in more detail on the electronics distributor shipping software page.

Where GoatLabels fits

GoatLabels rate-shops USPS, UPS, FedEx, and DHL from one account and shows one all-in number per carrier, so you can compare services side by side when you buy a label. Every label debits a prepaid wallet and writes a dated ledger entry that carries your reference, which gives finance a place to record which rule was applied to each parcel.

The limits are worth stating plainly. This post does not claim that GoatLabels offers any particular signature option or sells insurance, so confirm what is available for your carrier and service before you build a policy around it. GoatLabels does not offer bring-your-own carrier accounts or negotiated rates, so any declared value terms in your own carrier contract do not carry over. It has no native ERP connector, so a policy flag arrives through a CSV column or the API, and nothing is written back into your ERP automatically. Claims are governed by the carrier's terms, and support is by email and the in-app assistant, not by phone.