Pack Architecture for Quick Commerce: Why Your MRP SKU Will Not Work

Most FMCG brands arrive at quick commerce carrying the pack they already sell everywhere else. The 200ml bottle, the family-size pouch, the MRP that was set for a general trade shelf and a once-a-month shop. It feels efficient. One SKU, one barcode, one production run, listed across every channel. It is also the single most expensive assumption a brand can bring into this channel, because the quick commerce buyer is not shopping the way your retail pack was designed for. The pack that anchors your distribution is frequently the pack that quietly suppresses your conversion and erodes your margin at the same time.

This is not a listing problem you fix with better images. It is a product decision. Quick commerce rewards purpose-built pack architecture, and treating it as just another distribution point for your existing range is how brands end up with thin sell-through and a contribution line that never recovers. The largest FMCG houses in India have already figured this out, and the way they have responded tells you exactly where the channel is heading.

The quick commerce buyer is solving a different problem

A general trade shelf serves the planned shop. The buyer is stocking the house, comparing unit prices, and optimising for the month. Your large pack and your value MRP are perfectly tuned to that moment. The quick commerce buyer is in a completely different headspace. They are solving an immediate, narrow need. Ran out of something. Friends arriving in an hour. A craving at eleven at night. The decision happens in seconds, on a small screen, against a price point they will accept without much thought.

That difference reshapes everything about the pack. The right size is often smaller, because the buyer wants enough for now, not a month of supply. The right price point is one that clears an impulse threshold rather than one that wins a unit-economics comparison nobody is running. And the right configuration is sometimes a bundle or a multipack that fits the occasion, not the pantry. Importing your retail SKU means answering a question the buyer is not asking.

The retail pack is engineered for the planned monthly shop. The quick commerce order is an unplanned, single-need impulse. Same product, opposite buying logic.

Why your MRP SKU suppresses conversion

Start with the price point, because it does the most damage. A large retail pack carries a large absolute MRP. On a general trade shelf that is fine, the buyer has already decided to stock up. Inside a quick commerce app, that same number sits above the threshold at which an impulse purchase happens without friction. The buyer pauses. The pause kills the order. Your product was never uncompetitive. It was simply priced for a different decision.

Pack size compounds this. A buyer reaching for a single-use or single-evening quantity does not want, and will not pay for, a month of supply delivered in ten minutes. The mismatch reads as poor value even when the unit economics are excellent, because the buyer is judging the pack against the occasion, not against a price-per-gram chart. The result is a listing that gets impressions and views but stalls at the add-to-cart step, and most brands misread that as a demand problem when it is a pack problem.

Why it also breaks your margin

The cruel part is that the same wrong pack that suppresses conversion also damages margin, so you cannot even buy your way to volume. Quick commerce loads a stack of fees on every order, much of it fixed per unit rather than scaled to your price. We have laid this out in detail in the quick commerce margin reality check, and the core lesson applies directly to pack design. Fixed per-order and per-unit charges become a brutal share of a low-ticket SKU and a manageable share of a higher-ticket one.

That fee load is rising, not falling. Through 2025 and into 2026 the platforms steadily monetised the consumer side, with Blinkit adding handling charges of roughly Rs 4 to Rs 11 and Instamart layering platform fees of Rs 2 to Rs 10 on top of delivery, even as Zepto moved the other way and scrapped its handling and surge fees, per Storyboard18. Those charges sit on the buyer, but they raise the effective price of every basket and push the impulse threshold lower, which is exactly the wall a fat retail MRP runs into.

This is where pack architecture becomes a margin tool, not just a conversion tool. The job is to engineer a pack and a price point that clear the impulse threshold while still carrying the fee stack and a real ad rate. Sometimes that means a slightly premium single-serve at a clean price point. Sometimes it means a curated multipack that lifts the ticket enough to absorb the fixed fees without scaring the buyer. What it almost never means is shipping the exact pack and exact MRP you list on a marketplace or in general trade.

A separate SKU is not optional

The instinct to keep one universal SKU across every channel is understandable. It is also the thing that quietly prevents you from optimising any of them. A shared pack and MRP means your quick commerce pricing is hostage to your general trade pricing, your promotions collide, and channel conflict becomes a recurring fire. The brands that win this channel run a distinct quick commerce SKU with its own grammage, its own MRP, and its own promotional calendar.

That separation is what lets you price for the impulse threshold without disrupting the shelf price your distributors depend on. It is also what makes the channel legible. When the quick commerce pack has its own barcode, you can actually read its contribution, test its price point, and adjust without dragging the rest of your distribution into the experiment. This is foundational to a real quick-commerce-first FMCG launch, where the pack is designed for the channel from the start rather than retrofitted after the numbers disappoint.

Pack architecture is an assortment decision too

Pack design does not stop at one hero SKU. The platforms decide which of your products each dark store carries, and the shelf is deliberately narrow. That means your pack architecture and your assortment strategy are the same conversation. The pack that survives in a high-density metro store may be the wrong one for a smaller catchment, and the price point that clears in one location stalls in another. Pruning the slow movers and assorting deliberately is the unglamorous core of the work, and we go deeper on it in pruning slow movers from your quick commerce range. It depends entirely on having purpose-built packs to assort in the first place. You cannot assort intelligently if every store is offered the same retail SKU.

The platform you choose shapes the architecture as well. A grocery-led basket behaves differently from an impulse-led one, and the right pack and price point shift accordingly. If you are still deciding where to lead, the trade-offs in BigBasket versus Instamart for grocery and FMCG brands feed directly into how you design the pack, because the dominant buying mode on each platform changes which quantity and which price point clears.

What changed recently

This is no longer a contrarian operator opinion. India’s largest FMCG houses have moved, and they have moved exactly toward purpose-built packs. As Business Standard reported, Hindustan Unilever, ITC, Parle and Adani Wilmar are now building separate sizes and price points for quick commerce rather than recycling their general trade range.

  • Parle has launched quick-commerce-exclusive packs in the Rs 50 to Rs 100 band for Parle-G, Hide & Seek, Krack Jack and Monaco, while keeping smaller packs priced up to about Rs 30 reserved for kiranas and larger Rs 120 to Rs 150 packs for big retail. Parle’s own reasoning, per the same report, was that quick commerce had been bundling small kirana packs and creating conflict, so it carved out a distinct channel pack to stop it.
  • Adani Wilmar said it is building a separate brand for quick commerce, deliberately priced a notch higher than its kirana range, on the read that quick commerce shoppers run a higher value basket.
  • ITC rolled out quick-commerce-specific packs across Engage, Savlon handwash and Mangaldeep, treating the channel as its own product line rather than a shelf for existing SKUs.

Read those moves together and the message is blunt. The biggest players are doing exactly what we have argued a small brand must do: separate the barcode, engineer the price point to the channel’s buying mode, and let the kirana shelf and the app run different packs. They are also doing it partly to protect the kirana, which is the other half of the story. If the giants need a distinct pack to make quick commerce work and to keep their distributors whole, a smaller brand shipping its single universal MRP is not being efficient. It is being out-operated.

The fee side reinforces the same conclusion. With platforms raising consumer charges and brands facing per-SKU listing costs reported around Rs 25,000 plus heavy ad-wallet minimums, as Storyboard18 detailed, the only pack that survives is one whose ticket and grammage were designed to carry that load. A retail MRP was never designed to.

What to build before you list

The work is narrow and it is decisive. Before you list a single SKU, decide the price point your category buyer will clear on impulse, build the pack and grammage backward from that number to protect contribution after the full fee stack, give it a distinct barcode and MRP, and design the artwork to sell its use case at thumbnail size. Then assort those purpose-built packs by store rather than blanketing the network with your retail range.

  • Right-size the quantity. Match the immediate-need occasion, not the monthly pantry. Smaller and single-use beats family-size in most quick commerce categories.
  • Engineer the price point, not the pack. Decide the number the buyer will accept on impulse first, then build the pack and grammage backward to protect contribution.
  • Use bundles to lift the ticket. A purpose-built multipack or combo can raise the order value enough to swallow fixed fees while still feeling like an occasion buy.
  • Separate the barcode. Give the quick commerce pack its own SKU and MRP so its economics, pricing, and promotions never get tangled with your retail line, exactly as Parle and ITC have now done.
  • Design for the small screen. The pack has to communicate its use case in one glance at thumbnail size, because that is the entire shelf you get.

This is exactly the build our Quick Commerce Onboarding work starts with, alongside D2C & Marketplace Strategy Consulting to set the price architecture and Profitability & Unit Economics to prove each pack carries its own weight. The brands that struggle in quick commerce are rarely beaten on product. They are beaten on pack. They shipped the SKU built for a kirana shelf into a channel that buys on impulse, in seconds, against a price point their pack was never designed to clear. Fix the pack first, and the rest of the channel becomes a question you can actually answer.

Book a meeting