Seven feed checks for Birmingham wholesalers selling on Amazon UK

What to take away

Check one: VAT-inclusive prices in wholesale catalogues

Birmingham wholesale catalogues usually hold trade prices ex VAT. Amazon UK shows consumers VAT-inclusive prices, so the feed must carry the gross figure. If your catalogue exports the net price, every listing undercharges by 20 per cent and your margin disappears on the first sale.

HMRC sets the rules on how VAT is charged and displayed, and the feed is the display. Read the VAT detailed information before you map price fields. For a Birmingham distributor selling to consumers through Amazon UK, the price on the detail page is the VAT-inclusive price.

Check the rounding rule too. A trade price of 8.33 ex VAT becomes 10.00 gross, not 9.99. Small rounding errors across a 4,000 line catalogue become a real cost at month end.

The referral fee catches people out. Amazon UK charges its commission on the total price the buyer pays, VAT included, so a catalogue built on net prices understates both your revenue and the fee you owe.

If you sell to trade buyers as well, keep a separate price column rather than trying to serve both audiences from one field. Trade buyers expect to see the net figure and the rate quoted separately.

Check two: stock sync between warehouse and Amazon UK

Stock sync is the gap between what your Birmingham warehouse holds and what Amazon UK believes you hold. Overnight batch updates are too slow for fast movers. A line that sells out at 11am and still shows as in stock at 3pm produces a cancellation, and cancellations count against your account health.

Use the availability attribute properly. The availability attribute guidance explains how in stock, out of stock and backorder states should be declared, and the same discipline applies to Amazon UK Seller Central inventory feeds.

Aim for an update cycle measured in minutes for your top 200 lines, and hours for the tail. Map warehouse locations to a single sellable quantity so two pick faces do not double count.

Keep a small buffer on lines that sell in bursts. If a Birmingham trade counter can sell the same stock at 9am, the feed should not promise the last unit to an online buyer at 9.05am.

Distributors running two sites, say a Birmingham depot and a Midlands overflow unit, need the feed to add both before it publishes. Publishing each site separately is how phantom stock appears.

If you run the same discipline across marketplaces, a shopping feeds operating workflow stops the firefighting.

Check three: category mapping and browse nodes

Category mapping is the difference between a listing that appears in the right Amazon UK browse node and one that sits in a generic catch-all. Birmingham wholesalers often carry ranges that span several nodes, such as kitchen textiles, cleaning chemicals and catering disposables. Each needs its own mapping.

Map from your own category tree to the marketplace taxonomy, not the other way round. Keep the mapping in a table with a named owner. When Amazon UK changes a node, the table shows what moved and which lines are affected.

Ambiguous lines cause most of the trouble. A wholesale case of mixed cleaning items might sit under household supplies or under business and industrial, and the choice affects who sees it and what fee band applies.

A shopping feeds selection checklist helps when you choose tooling that can hold these mappings without manual rework.

Check four: returns data and cancellation rights

Returns data feeds are the least glamorous check and the one that protects your account. Amazon UK expects a returns policy that matches consumer law, and your feed should carry the policy text, the return window and the condition rules.

The Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 set the cancellation rights consumers have when they buy at a distance. The Consumer Contracts Regulations 2013 cover the information you must give before purchase and the cancellation period.

Track returns by SKU in the feed, not just in the warehouse system. A line with a high return rate because the description overstated size or quantity is a feed problem, not a customer problem. Fix the description and the returns fall.

Returns also carry a data protection angle. Customer details held for return handling sit under Information Commissioner's Office rules, so keep returns records in systems you can account for rather than in a spreadsheet on a shared drive.

Check five: product identifiers and GTIN accuracy

GTIN accuracy decides whether Amazon UK can match your offer to an existing product page. A wrong digit sends the offer to a new page with no reviews and no sales history. For a Birmingham wholesaler adding hundreds of lines a month, identifier errors compound quickly.

Follow the product data specification for identifiers. The product data specification sets out the identifier requirements, and Amazon UK applies similar matching logic. Check the check digit, not just the length.

Where you are the brand owner and no GTIN exists, apply for an exemption rather than inventing a number. Never reuse a GTIN across variants.

Variants are the usual weak point. A six colour range shares a base product code but needs a distinct GTIN for each colour, and copy and paste in the catalogue build is how duplicates slip in.

Check six: shipping and fulfilment promises

The delivery promise in the feed must match what your Birmingham operation can actually do. A two day promise on a line picked from a Birmingham warehouse is credible. The same promise on a container due from Felixstowe is not.

Split your catalogue by fulfilment method: stock held locally, stock held at Amazon, and stock on order. Each needs its own handling time and delivery estimate. Mixing them produces late deliveries and negative feedback.

Check carrier cut off times against your pick and pack schedule. A 4pm cut off with a 5pm pick is a promise you cannot keep.

Birmingham sits on the M6 and M5 with next day coverage across most of the UK, which is a genuine advantage. Use it in your delivery messaging, but only on the lines your own vans or carriers genuinely reach.

Check seven: reporting and error review

Error review is a weekly habit, not a quarterly project. Amazon UK Seller Central surfaces feed problems in its reports, and the Merchant Centre issue handling guidance shows how issues are grouped and prioritised.

Review in this order: disapprovals, missing attributes, price mismatches, image problems, then warnings. Fix the top category first, because a single missing attribute can suppress thousands of lines.

Keep a log of what changed and when. A shopping feeds quality checklist gives you a repeatable format for the review, so the same error does not return next month.

Set a fixed slot each week for the review, and give one person the authority to hold a feed back from publishing until the top errors clear. That single decision prevents most of the account health problems.

Common questions

Do Birmingham wholesalers need VAT-inclusive prices in the feed?

Yes, if the catalogue feeds a consumer marketplace such as Amazon UK. The price shown to the consumer must include VAT, even though your trade catalogue holds net prices.

How often should stock sync run?

For fast moving lines, every few minutes. For slow movers, hourly is usually enough. Overnight batches are too slow for anything that sells out during the day.

What happens if category mapping is wrong?

The listing appears in the wrong browse node or in a catch-all, so buyers browsing the correct category never see it. Sales fall without any error message.

Which law covers returns information in the feed?

The Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 set the cancellation rights and the information you must give before purchase.

Where do I fix feed errors on Amazon UK?

In Amazon UK Seller Central, under the inventory and feed reports. Review disapprovals first, then missing attributes, then warnings.