Pricing across D2C, Amazon, quick commerce and retail — without going to war with yourself

Why one-SKU-everywhere always ends in conflict

Put the identical 500g pack at the identical MRP on your site, on Amazon, on Blinkit and in a store, and the system starts eating itself. The marketplace discounts it during an event and your D2C conversion collapses. A distributor dumps stock online and undercuts everyone. Your best customers learn to buy wherever is cheapest this week — which is usually the shelf where you earn least. Meanwhile the buy box punishes you on Amazon if your own site is cheaper, and quick commerce demands margins the single-pack price cannot carry.

The root cause is structural: four channels with four fee stacks and four shopper missions cannot profitably share one SKU at one price. The answer is to stop trying.

The first rule: MRP parity on identical SKUs

Where the exact same pack does appear on multiple shelves, hold the same MRP and the same everyday selling price everywhere. This is non-negotiable hygiene: undercutting your own marketplace listing triggers buy-box suppression and platform friction; undercutting your own site trains customers away from your best-margin channel. Parity does not mean identical promotions forever — it means the *default* price never makes one of your shelves the sucker's shelf.

You do not solve channel conflict with discounts. You solve it by making sure no two shelves sell exactly the same thing.

The real fix: pack architecture by channel mission

Design packs for what each shelf is actually for:

• Quick commerce = impulse and trial. Small packs, single serves, ₹99–199 price points, thumbnail-readable design. Fast decisions need low-commitment sizes.
• Marketplaces = considered, planned purchase. Standard packs and value multi-packs; the shopper is comparing, so win on reviews and rating, not on being cheapest.
• Your D2C site = relationship and stock-up. Bundles, larger formats, subscribe-and-save, gift boxes, first-access drops — SKUs that literally cannot be price-compared because they exist nowhere else.
• Retail = visibility and habit. The hero SKU at the psychological price point the trade can carry.

Done properly, the shopper never sees a contradiction — they see the right pack for the moment. And each shelf carries a margin structure it can afford.

Worked example: a ₹399 hero SKU across four shelves

A staples brand with a hero 750g pack at ₹399: on quick commerce it fields a 200g trial at ₹129 (margin survives the platform take because the per-gram price is 20 percent higher — normal and accepted for convenience). On Amazon, the 750g at ₹399 plus a 2×750g at ₹749 for the value shopper. On the site, the 750g exists at parity — but the page pushes the 3-pack at ₹1,099 with free shipping and the subscription at ₹359/month, neither of which exists elsewhere. In store, the 750g at ₹399. Result: no two shelves compete head-on, every channel's economics close, and the D2C channel — where the brand keeps the customer — wins the heavy users. The deeper marketplace economics behind this are in D2C vs marketplaces.

Handling promotions without breaking the architecture

Events will pressure you — BFCM, Prime Day, quick-commerce flash sales. Rules that keep the system intact: promote channel-exclusive packs, not the shared hero (discount the Amazon twin-pack, the D2C bundle — never the parity SKU). Match event depth with an owned-audience offer on your site so your list never learns to wait for Amazon. Cap the calendar — a brand on permanent promotion somewhere is a brand teaching India its MRP is fiction, which is the discount treadmill we cover in the pricing-power piece. And police the grey channel: distributor dumping online is a contract conversation, not a pricing one.

Governance: who owns price

Channel conflict is usually an org-chart problem wearing a pricing costume. One person — founder or head of growth — must own the price-pack grid across all shelves, with a single sheet listing every SKU, every channel, its price, its margin after the channel's full fee stack, and its job. Review it monthly; update it before any new channel launch, not after. When a channel manager asks for a discount, the question is never "can we afford the discount" but "which architecture rule does this break, and is the event worth it".