ONDC Onboarding: What to Fix Before You Join

ONDC onboarding is a data problem before it is a sales channel

A marketplace you already know sends you a spreadsheet and tells you what to paste. A network is different. Your catalogue, price and stock are published as structured records that other applications read on your behalf, with no account manager correcting a mistake before a buyer sees it. If a field is empty, the buyer does not see an incomplete listing; the item may simply not be discoverable in that context.

That reframes ONDC onboarding. It is not primarily a marketing decision and not a discount you negotiate. It is the work of making your own product data accurate, complete and consistent enough that a machine can pass it to a stranger who will judge it without speaking to you.

The failure mode is predictable and cheap to avoid. Businesses that struggle after joining are usually not short of demand. They are short of clean data: one product name across three channels, a price that differs between the shop floor and the site, a stock count nobody updates, a returns policy that exists only in conversation.

Fix your own catalogue before anything else

Start with the catalogue, because every later step inherits its errors. Export whatever list you already keep, whether that is a spreadsheet, a billing system or a marketplace seller panel, and treat it as the draft it is.

Then work through the fields that a stranger needs in order to buy without asking you a question. Do not aim for a perfect catalogue; aim for a consistent one, where the same product is described the same way everywhere it appears.

This is also the point at which most retailers discover a genuine problem rather than a paperwork one: they cannot say what a product costs without checking with someone, or two of their own systems disagree about stock. Finding that on a spreadsheet is far cheaper than finding it in a live order.

• One product name and one description per item, reused unchanged across every channel.
• A unit of sale that is unambiguous: each, pack of six, per kilogram, per litre.
• A price with tax treatment stated, and a clear rule for who absorbs a discount.
• Category and attributes filled in from the network's own list rather than invented.
• At least one usable image per item, correctly oriented and not a phone snap of a screen.

Stock, pricing and returns are where it breaks

Three fields cause most of the damage after joining, and all three are operational rather than technical.

Stock is first. If your published count is wrong, a buyer pays for something you do not have, and the cost is not one refund; it is a failed order on a network that other sellers are also being judged against. Pick a stock number you can actually keep true, and update it on a schedule you will genuinely follow.

Pricing is second. A network exposes your price to comparison in a way a shop counter does not. Decide your floor before you publish, including what delivery costs you, because an order that is profitable at the counter can be loss-making once packing and shipping are counted.

Returns is third, and it is the one most often left implicit. Write down the window, what is excluded, who pays return shipping, and how a customer starts a return. A policy that exists only in your head becomes an argument the first time it is tested.

What your own website still has to do

A common mistake is to treat the network as a replacement for a website. It is not. The network is a channel, and channels change their rules, fees and priorities without asking you. The website is the asset you control, and it is where the trust that converts a first-time buyer is actually built.

Three things belong on your own site even after you join a network. First, the full catalogue, so a buyer who wants to check you out finds more than one listing. Second, the policies — shipping, returns, contact, who you are — in plain language on a real page, because that is what a cautious buyer reads before paying a stranger. Third, a way to reach you that you answer, since the enquiries that arrive direct carry no platform cost.

This is ordinary website work, and it is worth doing properly rather than quickly. A catalogue that is accurate on your own site is the same catalogue you publish to a network; the two efforts should not be separate.

A sensible order of work

Sequence matters more than speed. Trying to join a network while simultaneously rebuilding a website usually produces both badly. The order below keeps the shop trading throughout, and each step is useful even if you decide not to join yet.

Notice that the network signup is fifth, not first. Everything before it is work you would want done anyway, which is the test of a good order of operations: if you stop halfway, you have still improved the business.

• Export and reconcile the catalogue into one list with one name, one price and one unit per item.
• Decide the pricing floor including fulfilment cost, and write it down.
• Publish shipping and returns policies as pages on your own site, not as a paragraph in chat.
• Confirm your own site lists the catalogue accurately and takes enquiries you actually read.
• Join the network, publish a deliberately small first set of items, and watch the first ten orders closely.
• Fix what those orders expose before expanding the range.

ONDC onboarding checklist

Use this as a gate before publishing to any network. Any item you cannot answer is a field a buyer will eventually see as missing, wrong, or a reason to buy elsewhere.

• Every published item has one name, one unit of sale, one price and a stated tax treatment.
• Published stock is a number you can keep true, with a named owner and an update routine.
• Product images exist, are correctly oriented and show the actual item.
• Shipping and returns policies are written, published on your own site and consistent with what you tell buyers.
• You know your true cost per order, including packing and delivery, before you set a price.
• Your website catalogue matches what you publish to the network, item for item.
• Someone is responsible for answering network and website enquiries, with a stated response time.