BigBasket-style Online Grocery — Custom-Built for Your Market

A pantry refill is only complete when every basket line is accounted for

A household orders rice, detergent, milk and vegetables for the week. During picking, the requested rice pack is missing and one vegetable arrives damaged. The shopper still needs the rest of the basket in the chosen window, a clear replacement decision and an explanation of the amount returned. That ordinary order is a better starting brief than a catalog homepage: it connects shopping, warehouse work, delivery and support in one transaction.

A BigBasket-style build serves broad household grocery baskets, pantry lists and planned replenishment across warehouse or store fulfillment. BigBasket is a category reference for an independently branded product; affiliation, its catalog data, supplier relationships and operating network are not included. Scope one complete basket journey before adding categories or loyalty features. A launch agreement should identify what is configured, what needs custom work and which operating responsibilities belong to the buyer.

Choose the large-basket operating model before the storefront

Start with who supplies the basket and where it can be assembled. A regional warehouse may carry pantry goods while a partner store supplies fresh produce. Decide whether one site must fulfill the whole order or whether separate deliveries are permitted. Split fulfillment changes slot selection, minimum baskets, delivery fees, invoices and support ownership; it should never appear unexpectedly after payment. Name the seller and fulfillment owner for each line.

Compare the Amazon Fresh-style owned-inventory channel when a retail group controls the stock and fulfillment sites. This brief focuses on a broad household basket with warehouse or partner-store responsibilities. A rapid essentials model has different basket sizes, picking deadlines and dispatch assumptions; copying its speed promise does not settle the economics or handling of a pantry refill.

Make pack size, selling unit and quantity separate facts

Two packs of one kilogram of rice are different from one two-kilogram pack, even when the total weight matches. Show the product variant, pack size, selling unit and number of packs together in search results, the basket, pick tasks and the receipt. Household cleaners also need volume and pack count, while produce may need a clearly disclosed estimated weight. Define which identifiers distinguish variants and which barcode the picker should confirm.

A catalog import must validate unit mappings, prices and required product information before publication. Keep supplier feed changes reviewable so a renamed pack cannot silently replace a saved-list item. Where variable-weight fulfillment is included, agree the tolerance, price basis, final weighing and payment adjustment process. Do not describe a quantity selector as sufficient support for weighted goods. Review food labeling and category information with the responsible team for the actual launch market.

Rebuild repeat orders instead of replaying old checkout totals

A pantry list records what the household likes to buy; an earlier receipt records what it actually bought. Let customers choose lines, edit pack counts and remove goods they still have. Keep unavailable items visible with a reason and an optional alternative rather than dropping them silently. Reordering must use current location-specific availability and prices, with changes shown before confirmation. An old discount or delivery entitlement should not survive by accident.

Separate a customer-approved replacement from a permanent list change. Someone may accept another rice brand for one delivery without wanting it every week. Restrict household purchase-history access and agree retention and export permissions. Recurring orders require an additional agreement about timing, current prices, skipped deliveries and payment authority. For the first release, reviewed repeat baskets can provide replenishment value without introducing unattended purchases that support cannot explain.

Reserve delivery slots against warehouse and route capacity

A selectable window needs more than an open calendar. Connect serviceability, basket handling, picking capacity, staging space and route load to the site offering that window. A large ambient basket and a chilled order may consume different capacity. Define how long checkout holds a slot and what releases it after abandonment or payment failure. Recheck the reservation when the address, basket or fulfillment site changes.

The BigBasket delivery-slot reference lists windows by location and delivery type and notes that they can change under special circumstances. Use it as a planning example, not a promised schedule for your product. Your operator needs its own capacity rules, cutoffs and customer communication when a booked window can no longer be met.

Keep reservation authority and late stock changes visible

A warehouse feed saying available does not mean stock is reserved for this order. Agree which system owns sellable quantity, reservation and release. Keep damaged, expired or quarantined stock out of customer availability. Record when inventory was observed and what happens if a partner-store feed becomes stale. Orders waiting for a future slot need a defined reservation policy so the storefront and picker do not make conflicting promises.

Trace a shortage back to its order line, site and stock state. An operator should be able to distinguish an unavailable product from a failed stock synchronization or a picking discrepancy. Prevent repeated order events from taking the same reservation twice, and reconcile uncertain acknowledgements before allocating again. Let support see the customer impact without giving every support agent authority to alter inventory. The launch walkthrough should include a stock change between basket creation and checkout.

Batch picking must preserve each household’s order

A picking wave can group similar work across several household orders, but every item must still reach the correct tote and customer line. Assign a wave, site, picker and identifiable containers; confirm the requested variant and count at the appropriate step. Keep ambient, chilled and frozen work distinct according to the operator’s handling plan. A barcode match should not conceal a wrong pack count or damaged item.

Define how a picker pauses a line, reports a shortage and hands an exception to a supervisor. Packing should reconcile picked lines with substitutions, omissions and the final manifest before dispatch. If a device loses connectivity, establish which confirmed work can continue and how duplicate updates are resolved when it reconnects. Buyers should see a deliberate wrong-tote and wrong-pack attempt rejected or routed for review, not just a clean picking animation.

Substitutions need consent, price limits and an expiry

Offer replacement preferences at the line level: no replacement, an approved alternative, or a request for confirmation. A similar product name is not enough when allergens, diet preferences, brand choice or pack size matter. Define who proposes a substitute, what price difference is allowed and when customer approval expires. A picker should see the actual consent state rather than infer acceptance from an unanswered notification.

Show the replacement pack, quantity and revised amount before acceptance. If the shopper declines or does not respond before the agreed cutoff, apply the stated omission policy and update the basket record. Preserve the requested item alongside the supplied item so support can explain what changed. Keep any payment adjustment within the provider’s supported and agreed workflow. Do not promise automatic substitution intelligence as a substitute for customer preferences and accountable human review.

Cold-chain handling extends beyond a temperature label

Milk waiting beside detergent in a staging area reveals a handling problem that a product badge cannot solve. Define temperature-zone storage, packing, staging and vehicle requirements with the operator’s food-safety team. Record the handoff evidence and measurements that its approved process requires. Separate cleaning chemicals and food appropriately, and give teams a route to quarantine goods when packaging or handling checks fail.

A delayed route or failed doorstep handoff needs a category-specific decision about redelivery, return or disposal. The software should record the decision, responsible operator and customer resolution; it cannot certify that physical handling was safe. Supplier documentation, equipment, trained staff and market-specific review remain operational prerequisites. Include a simulated staging breach in acceptance, and inspect whether the affected lines are blocked from dispatch and remain traceable through support and refund decisions.

Partial refunds and delivery charges need a line-level ledger

When the shopper keeps the rice and detergent but rejects damaged vegetables, the receipt and support record must account for each outcome. Preserve ordered, picked, delivered and refunded quantities with the amounts used for discounts, tax and charges. Define whether a shortage changes a basket threshold or delivery fee and show the agreed rule before payment. A full-order delivered status should not prevent investigation of a missing line.

The BigBasket order, payment and refund FAQs direct customers to check delivered goods against the invoice, describe reporting a missing product through My Orders and explain refund destinations. They also say delivery and handling charges can vary with location and basket value. Use these as examples of decisions to specify for your own product; set your own reporting windows, refund routes and fee rules, then verify that support and provider reconciliation can represent them.

Retain the provider refund identifier and distinguish requested, acknowledged, failed and unresolved outcomes. A timeout should trigger reconciliation before another refund attempt. Give manual credits and adjustments named permissions and recorded reasons. The customer-facing explanation should state which lines were affected and where the refund is going under the agreed policy.

Make the walkthrough prove an incomplete basket can recover

Illustrative grocery screens explain navigation; they do not establish warehouse integration, live stock, supplier access or cold-chain execution. Ask for a connected demonstration using clearly identified sample goods and sandbox payments. Walk a repeat pantry list through changed pack size, a last-slot race, batch picking, a declined substitute and delivery with a missing line. Inspect customer messages and operator records at each boundary rather than treating a final success screen as evidence.

Buyer acceptance should force duplicate order events, a stale inventory feed, a wrong tote, an unanswered replacement request and an ambiguous partial-refund response. Verify that reservations and refunds are not repeated, unresolved work has an owner and restricted roles cannot edit prices or issue arbitrary credits. Agree what evidence will be retained, how records are recovered and which systems are simulated. Production capacity and physical food handling require separate operational checks against the buyer’s sites and teams.

Bring one household basket and its exception rules to scoping

Bring a redacted pantry list, representative product variants, warehouse or partner-store stock examples and one service zone. Include a planned delivery window, a weighted item if relevant, a permitted substitute and a damaged-item refund. Name the catalog owner, fulfillment supervisor, delivery coordinator and support decision-maker. Those inputs reveal whether the first release needs split fulfillment, dynamic payment amounts or only a simpler single-site basket.

Use a household grocery scope discussion to agree the release boundary, provider access, acceptance cases and operating responsibilities. Confirm deployment access, source ownership, third-party licences, record recovery and support coverage before fixing delivery commitments.

Review the delivery process for checkpoints around catalog preparation, fulfillment rehearsal, exception evidence and operator handover. A useful first release is a basket that the customer and operations team can both account for, including the lines that did not arrive.