Vendor code to first PO: what happens after yes

The agreement is signed and the buyer has said yes. Then four weeks pass and no order arrives. This gap is the least documented part of selling to an Indian retail chain, and it is where a large share of first listings quietly stall.

Nothing moves until the vendor code exists

A vendor code is your identity inside the retailer’s ERP. Purchase orders are raised against it, goods receipts are posted against it, and payments are released against it. Until that code is created and switched to active, the buyer can want your product badly and still be unable to order it. There is no informal route around this.

The code is usually created by a vendor master or shared services team that has never met you and does not report to the buyer. They work from a checklist: signed agreement, GST registration for the state you will dispatch from, PAN, bank proof, and often an MSME declaration and a cancelled cheque. The most common reason a file sits untouched for a fortnight is a name mismatch between the bank proof and the GST certificate. Nobody chases it, because the buyer assumes it is done and the vendor master team assumes you know it is pending.

Ask for two things by name: the code itself, and confirmation that it is extended to the specific legal entity and distribution centre you will supply. Several chains create separate codes per region or entity, and a code that works for one distribution centre will not raise a purchase order for another.

Master data is the real gate

The code lets a chain pay you. Article master data lets it order you. For each pack you need an article or retailer SKU code, a scannable EAN at both unit and case level, the case configuration, gross and net weight, carton dimensions, MRP, the net quantity declaration exactly as printed, shelf life in days, HSN and GST rate, and the ordering unit.

Mismatches here are expensive in a way paperwork errors are not, because they surface as rejected stock rather than as an email you can correct. A case configuration recorded as ten when you ship twelve means every receipt posts as an overage or a shortage. A barcode that will not scan at the gate holds the whole vehicle. An MRP printed on pack that differs from the declared MRP is a compliance issue, not a clerical one. Declared shelf life longer than you actually ship against means your first vehicle fails the chain’s freshness norm on arrival. Each of these turns into a debit note you will be arguing about months later.

Submit master data once, in the chain’s own template, checked by someone who has physically measured and weighed a carton. Do not fill it in from a spec sheet.

An approved vendor is not a live article

Approval sits at the chain level. Listing sits at the article level. Distribution sits at the store level, and it is granted in clusters rather than nationally. It is entirely normal to be an approved vendor with two of your four packs listed, live in one distribution centre, serving a few dozen stores in one region.

So the question to ask is not whether you are in. It is which articles are active, which distribution centres they are mapped to, how many stores are in the first phase, and when the next range review opens. Without those four answers you cannot plan production, and you cannot tell whether slow offtake is a demand problem or simply the absence of stores. Store coverage decays quietly from whatever number you start at, which is why you need the starting number written down.

The first PO is a test, not a forecast

First orders are small, cautious and usually to a single distribution centre. Read them as an operational test rather than a demand signal. The chain is finding out whether you can ship complete, ship on time and ship clean. Reading a first order as a run rate and producing against it is how brands end up holding stock nobody has asked for.

What matters is that the first three or four orders go out without a single exception. Confirm only against stock you physically hold, because your acceptance score starts counting from the first line, and book the inbound slot the moment the order lands, because the appointment is usually the binding constraint rather than your production.

Know which counterpart you are talking to

New suppliers route everything through the buyer, and it is the slowest possible path. In most chains there are four separate desks. The category buyer owns range, commercials and promotions. A replenishment or supply planner raises the actual purchase orders and owns your fill rate. Vendor master and accounts payable own your code, your master data and your money. The inbound team at each distribution centre owns appointments and gate decisions.

Get a name and a number for all four in your first month. Escalating a docking problem to the buyer costs a week and spends goodwill you will want later for a commercial conversation. The commercial conversation itself, including what you are actually being charged for, belongs to the buyer alone.

What goes wrong in the first ninety days

• The code is created but never extended to the distribution centre that was going to order, and nobody notices for three weeks.
• Case configuration in the master differs from the carton on the floor, so the first receipts all post short and set an early pattern of shortage notes.
• The brand ships against a verbal commitment before a purchase order exists, and the vehicle is turned away at the gate.
• Artwork changes between approval and production, the barcode changes with it, and the article stops scanning mid-launch.
• No one person is accountable for the account internally, so orders sit unread in a shared inbox over a weekend.

None of these are strategy failures. They are handover failures, and they are avoidable by treating the period between the yes and the first receipt as a project with an owner, a checklist and a date.