{"slug": "catering-in-50000-cities-live-in-8-weeks", "title": "Catering in 50,000+ cities, live in 8 weeks", "summary": "Rigby, a Medusa Expert partner, built an event catering platform for Polish meal-box caterer Kuchnia Vikinga in 8 weeks — 2 weeks ahead of schedule — using AI coding agents to draft specifications, data models and architecture before human sign-off. The Party Box storefront runs on Medusa with a Next.js frontend and custom delivery modules covering more than 50,000 Polish cities, 92% of the population, with a minimum two-day lead time and a coverage list refreshed roughly every two weeks. Kuchnia Vikinga, which produces nearly 300,000 meals a day with 2,000+ employees and grew revenue at a 96% compound annual rate since 2021 to more than 160 million EUR in 2025, chose Medusa partly to avoid transaction fees or a share of GMV as it launches further business lines on the same foundation.", "body_md": "[Blog](https://medusajs.com/blog)\n\nNovember 18, 2026·User stories\n\n# Catering in 50,000+ cities, live in 8 weeks\n\nNicklas Gellner\n\nNicklas Gellner\n\nLearn how one of Europe's largest meal box caterers launched an event catering platform in 8 weeks with AI agents building the Medusa backend, serving 50,000 cities.\n\n[Kuchnia Vikinga](https://kuchniavikinga.pl) is the leader of Poland's box-diet catering market and one of the fastest-growing food companies in the country. Nearly 300,000 meals a day come out of its kitchens, carried by 2,000+ employees and delivered to over 50,000 Polish cities. Its revenue has grown at a 96% compound annual rate since 2021, reaching 160 million+ EUR in 2025.\n\nThe company is opening a series of new consumer business lines beyond the core diet subscription, each with its own brand and economics, and it wanted all of them on one commerce engine. The first line due was [Party Box](https://partybox.panviking.pl): large trays of ready-made event food, ordered to a home or an office.\n\nKuchnia Vikinga worked with [Rigby](https://www.rigbyjs.com), a Medusa Expert partner, who used Medusa's agent primitives to speed up development and delivered it in 8 weeks, 2 weeks ahead of schedule. Here is how they approached the project.\n\nWorking together feels like having a true partner on your side, not just a software house. Rigby builds and implements, we cook, and customers can simply sit back and enjoy the experience. That's exactly how a good partnership should work.\nKamila Wysocka\n\n·\n\nGrowth Manager, Kuchnia Vikinga\n\n## Selling a Product Nobody Had Sold Nationwide\n\nEvent catering boxes existed in Poland, but only locally, from providers serving one city or a handful. No one sold them nationwide, so there was no benchmark to follow and no established pattern for how the category should be bought.\n\nThe harder constraint was operational. Every Party Box order enters a production plan and a route plan at a company already making 300,000 meals a day.\n\n- **Lead time:** every order needs at least two days' notice. The exact cut-off depends on the weekday and the destination, with separate rules for weekends and days the kitchen is closed.\n- **Coverage:** courier delivery reaches more than 50,000 cities, 92% of the Polish population, and that list is refreshed roughly every two weeks as routes change.\n\nThe storefront could not be allowed to sell a date or a town the production plan could not serve.\n\n## Custom Delivery Logic on a Shared Commerce Foundation\n\nRigby started from a clickable prototype that carried no production code, data model, or delivery logic. They designed the whole business logic, data model, and architecture, then built all of it on Medusa with a [Next.js storefront](https://docs.medusajs.com/resources/nextjs-starter).\n\nMedusa runs the commerce core: catalogue, product pages, cart, checkout, customer accounts, order history, promotions, and the admin panel. Everything specific to how Kuchnia Vikinga sells and delivers was built as custom modules on top of it, which is what made the single-engine requirement workable.\n\nThe next business line starts from the same foundation: a catalog, checkout, and admin. Cost and time to market are why Kuchnia Vikinga chose Medusa. They do not pay for transactions or a share of their GMV, and it launches in a fraction of the time the first one took.\n\n## How Coding Agents Built Party Box in 8 Weeks\n\nThe speed came from the order of the work and from how much of it AI agents could take on. Rigby applied its AI-native delivery approach, [Canso](https://www.rigbyjs.com/canso), in three steps:\n\n1. **Specify before building.** AI drafted a written specification for every feature from the client's own materials, together with the data model and the architecture. Anything ambiguous went back to Kuchnia Vikinga for an answer before work started, and nothing was built against a specification a person had not signed off.\n2. **Settle the frontend first.** The whole storefront was built against mock data and approved by the client on a live staging URL. The design was frozen before any backend existed, so there was no rework once the logic landed.\n3. **Let agents build the backend.** AI agents implemented the backend against the approved specifications, one module at a time, and developers reviewed every merge.\n\n[Medusa's agentic primitives](https://medusajs.com/cloud#agents) supported this approach. A specification such as \"a cut-off engine configured per weekday, re-validated at checkout\" maps onto one module with a clear boundary, so an agent can build it without touching the commerce core underneath. Cart, checkout, orders, and the admin panel were already there, which left the agents to build only what was specific to Kuchnia Vikinga: the delivery cut-off engine, delivery-area validation, and courier and pickup fulfillment, while connecting it with the rest of the modules in Medusa.\n\n## Implementation Highlights\n\n### A Cut-Off Engine the Kitchen Controls\n\nParty Box needed delivery dates derived from a production calendar that operations staff change without a developer. Rigby built a cut-off engine as a custom Medusa module, configured per weekday from the admin panel along with the days the kitchen is closed.\n\nValidating once is not enough. A customer can put a valid delivery date in the cart, spend twenty minutes choosing boxes, and try to pay after that date's window has closed. The engine re-validates at checkout, immediately before payment.\n\nDelivery area works the same way. The list of served towns lives as a dataset the client refreshes by uploading a CSV in the Medusa admin. Address entry runs as a searchable autocomplete over that live list, and coverage is checked again against the current version during checkout.\n\n### Courier and Pickup in One Checkout\n\nParty Box ships two ways: nationwide courier delivery and pickup at one of 20+ Viking Point locations. Both run through a single checkout.\n\nThe routes have different availability rules, different cut-offs, and different required fields. Courier drop-off is left at the door without a signature, so the customer supplies an intercom or entry code. Pickup routes them through location selection instead. One selector handles both, and each route applies its own availability rules, so the dates shown always match the route picked.\n\n### The Stack Around the Commerce Layer\n\nSolutions included in the implementation\n\n- **Payments:** ING Pay is the payment gateway, covering BLIK, card payments, and PayPo deferred payment.\n- **Finance:** the team keeps working in Enova, the accounting system the company already runs.\n- **Business customers:** the GUS API, the Polish company registry, fills in a legal name and registered address from a NIP tax number.\n- **Monitoring:** Sentry handles error monitoring.\n- **Infrastructure:** Hosted on[Medusa Cloud](https://medusajs.com/cloud) .\n\n## A New Business Line Without Disrupting Operations\n\nParty Box now sells to more than 50,000 Polish cities and is the first service of its kind available nationwide. It launched on a platform the company had never run before.\n\nNone of the core operations stopped for it. The company kept producing nearly 300,000 meals a day while the new consumer channel was built alongside the existing business.\n\nThe shared Medusa backend is what turns that into a repeatable path. Every new line starts from the catalogue, checkout, and delivery engine Party Box already runs, so the company's next brand reaches the market in a fraction of the time this one took.\n\n## You may also like\n\nOctober 29, 2026·User stories\n\n### PortAventura: +63% revenue with Medusa for hotel and ticket bookings\n\nNicklas Gellner\n\nSeptember 29, 2026·User stories\n\n### Healthletic: 30% Checkout Lift After Shopify Plus Migration\n\nNicklas Gellner\n\nAugust 27, 2026·User stories\n\n### 6,000+ Products Matched to Every Vehicle Type\n\nCarla Böddeker", "url": "https://wpnews.pro/news/catering-in-50000-cities-live-in-8-weeks", "canonical_source": "https://medusajs.com/blog/kuschnia-vikinga", "published_at": "2026-11-17 20:11:53.604944+00:00", "updated_at": "2026-11-17 20:11:55.796515+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools"], "entities": ["Kuchnia Vikinga", "Rigby", "Medusa", "Party Box", "Next.js", "Canso", "Kamila Wysocka", "Nicklas Gellner"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/catering-in-50000-cities-live-in-8-weeks", "markdown": "https://wpnews.pro/news/catering-in-50000-cities-live-in-8-weeks.md", "text": "https://wpnews.pro/news/catering-in-50000-cities-live-in-8-weeks.txt", "jsonld": "https://wpnews.pro/news/catering-in-50000-cities-live-in-8-weeks.jsonld"}}