Run Your Own B2B Ordering Portal for Retailers

Most Indian brands take trade orders on WhatsApp. A retailer sends a voice note, a sales rep types it into a spreadsheet, someone in accounts raises the invoice, and stock leaves the warehouse. It works until it does not, and the failure point usually sits between the thirtieth and the eightieth active account.

What WhatsApp actually costs you

The cost is not the tool. It is everything the tool cannot enforce.

• Price is whatever the rep said. Two retailers in the same town discover they are paying different rates, and one of them stops ordering.
• Nobody can see stock. Orders get taken for SKUs you do not have, then part shipped, then argued about for a month.
• Credit is checked from memory. An account 60 days overdue places another order and the rep pushes it through because the month is closing.
• Order to invoice takes a day or more, so dispatch cutoffs slip and the retailer blames you for the delay.
• When the rep leaves, the relationship and the order history leave with him.

A portal does not make you friendlier to trade. It makes price, credit and stock non-negotiable at the point of order. That is the entire business case.

Tiered price lists are the hard part

Trade pricing in India is a ladder, not a number. A typical structure runs super stockist at 3 to 5 percent, distributor at 5 to 8 percent and retailer at 8 to 15 percent off the level above. Modern trade, ecommerce distributors and institutional buyers each sit on their own rate.

Build price lists that attach to accounts, not to products. Each account maps to exactly one list. Above that you need scheme handling, because Indian trade runs on schemes: quantity slabs, free goods such as one case free with ten, festive schemes with start and end dates, and launch pricing on new SKUs. Decide up front whether a scheme is an invoice level price reduction or free goods added as a line, because the GST treatment and the credit note trail differ.

Keep one rule absolute. If a price does not exist on the account list, the order cannot be placed. Exceptions go through an approval, never through an editable price field.

Credit limits, terms and the block

Set three fields per account and enforce them in code. Credit limit in rupees. Credit days, usually 21 to 45 for retailers and 30 to 60 for distributors. Security in the form of a deposit, post dated cheques, or a bank guarantee for the larger partners.

Then decide what happens at the limit. A hard block is the honest answer and the one that gets argued about. A workable middle path is to block automatically at the limit or at overdue past terms, allow a sales head to release one order with a reason code, and expire that release in 48 hours. Show the retailer his own outstanding, ageing and available limit on the order screen. Half your collection calls disappear once the partner can see his own number.

MOQ, case packs and minimum order value

These are two different constraints and brands routinely confuse them. Case pack forces quantities in multiples of the shipper, so nobody orders 7 units of a 12 pack. Minimum order value sets the rupee floor at which you will dispatch directly, often 15,000 to 25,000 rupees for a retailer and considerably higher for a direct distributor drop. Below that floor, route the account to its distributor instead of shipping a loss making consignment.

Show the shortfall live in the cart. A line saying add 3,200 rupees to reach the free freight slab moves more incremental volume than most trade schemes you will run this quarter.

GST, e-invoicing and e-way bills at bulk

Trade orders are where compliance stops being a background task.

• E-invoicing applies once aggregate annual turnover crosses 5 crore rupees. Every B2B invoice needs an IRN before dispatch, and businesses at 10 crore rupees and above must report invoices within 30 days of the invoice date.
• An e-way bill is required above 50,000 rupees of consignment value in most states. Maharashtra holds intra state at 1,00,000 rupees and other states vary, so keep the threshold as a state level setting rather than a hardcoded constant.
• E-way bill validity is one day per 200 km. On long hauls east and north east, plan the extension before the vehicle is already late.
• Ship to and bill to are different GSTINs when a distributor buys and asks you to deliver to a retailer. Capture both at order time, not at invoice time.

Your portal does not have to do all of this itself. It has to carry the fields cleanly into whatever raises the invoice, so nobody is retyping a GSTIN at nine in the evening.

The approval flow, in order

• Retailer places the order against his own price list.
• System checks credit limit, ageing, case pack and minimum order value. Failures surface immediately, not by phone the next morning.
• Stock is soft allocated so two accounts cannot be promised the same batch.
• Any price or scheme exception routes to the area sales manager with a reason code and a timestamp.
• Order releases to the warehouse. Invoice and e-way bill generate, and dispatch details go back to the retailer inside the portal.

Build or buy

Below roughly 100 trade accounts, a B2B mode on your existing storefront is enough. Shopify B2B features, or a WooCommerce setup with customer group pricing, will hold price lists, MOQs and net terms. Expect a few lakh in setup and a working portal in six to ten weeks.

Above that, or if you run a field sales team, look at a distributor management system with an ordering front end. Tools in that category already carry schemes, claims and secondary sales reporting. Budget an annual licence and a genuine data migration, not a weekend.

Whichever route you take, the launch sequence is the same. Pick twenty accounts that already order weekly. Load their real price lists and real outstandings, not test data. Run two weeks in parallel with WhatsApp still open. Then close WhatsApp ordering for that cohort and hold the line. Portals fail because the brand keeps accepting the voice note, not because the software was wrong.