How shipping and tax attributes work
A Merchant Center product feed carries more than a title, a price and an image. It also has to tell Google what a shopper will actually be charged at checkout. The shipping attribute declares the delivery cost — either a flat value stated in the feed itself, or a service name that points at a shipping setting configured in the Merchant Center account. The tax attribute does the same for sales tax, in markets where tax is expected to be shown separately from the price.
Which of the two you need depends entirely on the country you are selling into. Some markets require a shipping value on every item before a product can serve at all. Others treat tax as included in the displayed price, so a separate tax attribute is either unnecessary or actively wrong. Google publishes the requirement per country, and it is the country of sale that decides, not the country your business is registered in.
Where the same product ships differently by region, weight or order value, the account-level shipping settings usually carry the rule and the feed simply names the service. That keeps the logic in one place instead of repeating it on every row of the catalogue.
Why shipping and tax attributes matter
They are the difference between a listing that serves and one that sits blocked. A missing required shipping value is a routine reason an otherwise healthy product stops appearing, and it surfaces as an item-level issue in Merchant Center rather than as an obvious campaign problem — so it is easy to miss while you are staring at the ads.
They also shape what shoppers do after the click. Shopping surfaces show delivery cost beside the price, so an inflated placeholder value makes your listing look dearer than it is and quietly loses clicks. An understated one wins the click and loses the sale at checkout, which is worse: you paid for the visit and taught the shopper not to trust the listing.
Where shipping and tax attributes go wrong
The commonest fault is a single flat rate applied to a catalogue of wildly different parcel sizes. The bulky items are then advertised below their real delivery cost and the small ones above it. The second is stale data: courier rates change, the feed does not, and nobody notices because nothing errors.
Cross-border sellers get caught a third way. A feed built for one country is copied to another with the tax treatment left exactly as it was, so tax is either declared twice or not at all. Currency belongs to this problem too — the shipping value has to be in the currency of the destination market, not of your accounts.
What to do about it
Start from the destination country’s requirement rather than from the feed you already have, and set shipping in the account settings wherever the rule is more complicated than a single number. Match every value to what your checkout genuinely charges, and put a recurring reminder in the calendar to re-check them whenever courier pricing moves. If the feed is throwing blocks you cannot trace back to a row, a structured review of the whole file through Merchant Center feed management will usually find the pattern faster than editing products one at a time.
