IndiaCakes.com has been delivering birthdays, weddings, anniversaries, and midnight surprises across India since 2004. With over 1 million customers served across 5,000+ cities and 1,50,000+ pin codes, it’s one of the country’s most established online gifting platforms — running entirely on Magento 2 (Adobe Commerce). This Magento 2 case study covers how Ribog rebuilt it end-to-end.
The catalogue is anything but simple: 500+ cake variants spanning weight and type combinations, from classic Black Forest and Chocolate to trending Pinata, Pull-Me-Up, Fondant, and Labubu-themed creations. That scale demands serious Magento 2 configurable product architecture — not the fragile, vendor-patched setup the brand had inherited.
The scope of this custom Magento 2 development engagement was comprehensive: configurable product flows for weight and type selection, a custom storefront UX, a production-ready Hyvä Checkout with Razorpay integration and delivery date selection, pincode-driven delivery powered by Google Maps API, a “Message on Cake” feature, and a rebuilt product import pipeline — all deployed with zero downtime.
We’ve worked with Magento vendors for years, and this was the first time Ribog Digital fixed the foundation instead of patching over it. Razorpay, midnight delivery slots, pincode checks — everything our business actually runs on is finally on the website. And not one minute of downtime while they did it.
Years of unstructured vendor work had left IndiaCakes with a Magento 2 store that fought back at every step. Vendor-modified core files blocked configurable products. The storefront was Luma-based with default dropdowns and zero personalisation. The Hyvä Checkout had no delivery date picker, no flat shipping logic, and no Razorpay — on a business built around midnight deliveries and Indian payment habits. Five critical problems stood between the brand and a store worthy of its scale:
Previous vendor modifications to Magento core were preventing simple products from being replaced with configurable products. The default 2MB import limit blocked bulk catalogue uploads, and the custom "Upgrade Product" field couldn't be handled by Magento's default import or Amasty's extension — a triple blockade on catalogue operations.
A poorly built product name feature (Name + Weight + Type across cart, minicart, orders, and emails) recomputed data on every cart render — making the cart painfully slow and sometimes completely blank. On a high-volume checkout funnel, that's revenue vanishing in real time.
No button-style swatches, no auto-selection on load, no dynamic product name updates, no styled indicators. Customers were choosing cake weight and type from a plain Magento dropdown — the wrong UX for a gifting brand where the product is the visual.
Delivery across 5,000+ cities is governed entirely by pincode — yet there was no pincode lookup in the header or on product pages, no Google Maps API validation, and the city field wasn't even required at checkout, causing routing errors and failed deliveries.
The checkout lacked three non-negotiables: a delivery date picker (fatal for a midnight-delivery brand), flat free-shipping logic, and Razorpay integration — the way India actually pays. And with no "Message on Cake" field anywhere in the journey, personalisation data never reached the order, invoice, or bakery team.
The cart used to go blank and nobody could tell us why. Ribog didn't just fix it — they explained exactly what was wrong, rebuilt it the proper Magento way, and it hasn't failed once since. Every message on every cake now reaches our bakery team automatically. That alone changed how we operate.
Each module in this custom Magento 2 development engagement was independently scoped, built to Magento best practices — clean dependency injection, no ObjectManager in production logic — and tested on staging before every go-live. Here's how 12 weeks unfolded:
Vendor-modified core files blocking product type replacement were audited and safely resolved. Magento's import file size limit was raised via a targeted config override — not a risky server-wide PHP change. A custom Magento 2 import script was built for the Upgrade Product attribute, writing directly to EAV tables with full error handling and logging.
The Name + Weight + Type display was rebuilt on Magento's order item option pattern — computed once at add-to-cart, stored, and rendered across cart, minicart, checkout, confirmation, and every transactional email. Zero extra database queries on cart load. Zero blank pages since launch.
Default dropdowns replaced with tappable, brand-styled button swatches — a full Magento swatch customization. First available options auto-select on page load, out-of-stock combinations are visually disabled, and the product name updates live as customers pick weight and type: "Black Forest Cake" becomes "Black Forest Cake — 2kg — Eggless" in real time.
A header "Deliver to" widget, PDP delivery check, and Google Maps Geocoding API validation — with checkout shipping fields auto-populated from the saved pincode and the city field now required. Alongside it: a "Message on Cake" field flowing from PDP to order, invoice, and packing slip, plus Related Products, Upgrade Products, and Recently Viewed sections.
The Hyvä Checkout customization completed with three business-critical features: a delivery date picker (same-day, next-day, and midnight slots with admin-configurable rules), validated flat free shipping, and full Razorpay Magento 2 integration — UPI, cards, wallets, net banking — with webhook-based order status updates and graceful failure handling.
IndiaCakes.com runs on Magento Open Source with a fully customised Hyvä Theme and Checkout, purpose-built modules, and India-specific third-party integrations — combining lightweight frontend performance with the deep customisation a high-volume gifting platform demands.
IndiaCakes entered this engagement with a store that didn’t match its brand: vendor-hacked core files, a broken import pipeline, an incomplete Hyvä Checkout, a cart that went blank under load, and no delivery logic for a business that lives and dies by pincodes. Twenty years of customer trust deserved better infrastructure.
Twelve weeks later, the platform is unrecognisable: a clean configurable product import pipeline, a fast and stable cart with enriched product names, a mobile-first custom swatch UX, Google Maps-powered pincode delivery across 5,000+ cities, end-to-end cake personalisation, and a production-ready Hyvä Checkout with Delivery Date, Flat Shipping, and Razorpay at its heart.
Every module was built to Magento 2 development standards — clean code, proper dependency injection, no ObjectManager in production logic, thorough error handling, and zero downtime deployment. IndiaCakes now has the technical foundation to serve its next million customers.
"Razorpay is how India pays — without it on checkout, we were losing customers at the last step. Now the cart loads instantly, customers see exactly what they picked, and the delivery date picker finally lets us take midnight orders through the website, not just over the phone."
