Supplier New Line Form Template

The average supplier new line form has grown to around two hundred columns and comes back roughly twelve per cent complete. Nobody designed it that way. It grew one range review at a time, because adding a column is easier than deciding a column is not needed, and nobody has ever been blamed for asking for too much.

This supplier new line form template has eighteen fields. Not because eighteen is a target, but because that is what is left once you remove everything the supplier can send you in the form they already hold it.

Why eighteen fields and not two hundred

Split the two hundred into two piles.

The first pile is what only the supplier knows: their part number, the barcode, the cost price, the pack quantity, the unit of measure, the lead time, the country of origin, the commodity code. Nobody else can supply these. Nothing can derive them. That pile comes to about eighteen fields.

The second pile is everything else: long descriptions, feature bullets, category mapping, channel attributes, technical values, image alt text. All of it already exists somewhere in the supplier's world, in a spec sheet, a price list, a website, a PDF. Asking them to retype it into your columns is asking them to do a data entry job on your behalf, unpaid, in a format they will never use again. The twelve per cent completion rate is not the supplier being difficult. It is the rational response.

So this form asks for the first pile and asks them to attach the second pile in whatever form they already have. The last two columns are for a spec sheet filename and an image filename. A PDF is a perfectly good answer.

What is in the supplier new line form template

Two tabs. A How to use this tab written to the supplier, not about them, and a New lines tab with eighteen columns.

Eight are required and filled red: supplier part number, product name, brand, GTIN or EAN, pack quantity, unit of measure, cost price and currency. Unit of measure and currency carry dropdown validation, because free text in those two columns is where most reconciliation problems start.

The remaining ten cover RRP, lead time, country of origin, commodity code, supplier category, the three variant columns, and the two attachment columns.

What each required field is actually for

Supplier part number. The only stable key between their system and yours. It has to be their code, unedited. Tidying it up, stripping a prefix or adding the size on the end breaks the link the first time they send a price update.

Product name. Used for matching and for spotting duplicates before they are created. It should read like something a person would say.

Brand. The manufacturer, not the supplier. A distributor filling their own name in here is the most common cause of duplicate product records, and it is worth saying so explicitly on the form.

GTIN or EAN. How marketplaces and your customers' systems identify the product. A missing barcode blocks marketplace listing outright, so it is far cheaper to chase at submission than to discover during a launch. Digits only.

Pack quantity and unit of measure. Without both, the price means nothing. Twelve pounds per what. This pair causes more margin errors than any other field on the form.

Cost price and currency. Two columns, never one. A cell reading 12.50 GBP is a string, and a column of strings cannot be summed, compared or converted.

The variant columns

Three columns handle variants: parent code, variant attribute, variant value.

A bracket in three lengths is three rows. All three carry the same parent code, the variant attribute is Size, and the values are 300mm, 400mm and 500mm. Each row still needs its own part number, its own barcode and its own cost, because each one is a separate thing that gets picked, packed and sold.

The failure is one row with all three sizes in a single cell. It saves the supplier two minutes and costs you a rebuild, usually discovered when somebody tries to list the range and finds there is only one barcode for three products.

One variant attribute per form keeps it usable. Products varying on two axes at once, size and colour, need a row per combination, and that is worth saying in the covering email rather than assuming.

Sending the new line form out

Delete the example row. Suppliers copy it.

Send it with a date and a consequence. "Please complete at your earliest convenience" returns a file in three weeks, half filled. "The range goes live on the 14th, anything without a barcode does not go live with it" returns a file on Friday. The second version is not aggressive, it is just specific.

Name one person to reply to. Forms sent from a shared mailbox come back to a shared mailbox and sit there.

Say what happens to the attachments. Suppliers hesitate to send a folder of PDFs if they think it will annoy you. Tell them it is the preferred answer and they will send it.

Validate at submission, not at import

The reason a new line form comes back incomplete is rarely that the supplier is being unhelpful. It is that nothing tells them it is incomplete until weeks later, by which time the person who filled it in has moved on and the file is somebody's third priority.

Checking the file the moment it arrives, and replying with the specific rows and columns that are missing, changes both the speed and the tone. You are pointing at row 47 rather than at the supplier, and they can fix row 47 in five minutes.

Doing that manually works while there are a handful of suppliers. It stops working at the point where forms arrive daily, in different states, from people who have never filled one in before. A supplier portal does the same check automatically at the point of upload, which is the difference between a three week loop and a same day one. Well designed portals see first submission completeness far above what a master spreadsheet returns, and the reason is timing rather than enforcement.

Cutting your own form down

If you already have a two hundred column form, the useful exercise is not adopting this one wholesale. It is going through your own, column by column, and asking a single question of each: can this only come from the supplier.

Category mapping cannot, because it is your taxonomy. Long descriptions cannot, because they are already written on their spec sheet. Channel specific attributes cannot, because the supplier does not know which channels you sell on. Those all come out.

What is left will be close to eighteen. Then run the short version alongside the long one for one range review and compare what comes back. That comparison tends to settle the argument faster than any amount of discussion about it, and it is the reason this template exists in the shape it does.

For the process around the form, see supplier onboarding software.