Dynamics 365 for restaurant, catering and hotel groups

Restaurant and Hospitality from register to kitchen in one system

An order taken at the table reaches the kitchen screen, its ingredients come off inventory, and the sale posts to accounting at day end, all as one record. At Pargesoft, we build this on Microsoft Dynamics 365 and fit it to the way each of your branches works.

  • Track every plate's real cost from its recipe
  • See each branch's profit without waiting for month end
  • Move to Dynamics 365 without replacing your POS
During dinner service in an open-kitchen restaurant, a server checks an order on a tablet while a chef plates dishes under the order screen

Brands we work with

  • D.ream
  • DO&CO
  • The Marmara Group

One system

One order, four stops, one record

Branch registers run on Dynamics 365 Commerce, inventory and purchasing on Dynamics 365 Supply Chain Management, and accounting on Dynamics 365 Finance, and all four use the same record. Here is how one table of four's dinner order passes through the four stops.

  1. 7:42 p.m.

    The order is taken

    • Table 7 · 4 guests
    • Cheeseburger 2
    • Margherita pizza 2
    • Lemonade 4
    • Note 1 burger extra cheese

    The server enters the order on a tablet by table number: no paper check, and the order never loses its table.

  2. 7:42 p.m.

    The kitchen cooks

    • Table 7 · Station screens
    • Grill 2 cheeseburgers
    • Oven 2 pizzas
    • Bar 4 lemonades

    Burgers land on the grill's screen, pizzas on the oven's and lemonades on the bar's, all at once.

  3. 7:43 p.m.

    Stock updates itself

    • Table 7 · Off inventory
    • Ground beef −360 g
    • Burger buns −2
    • Cheddar −3 slices
    • Pizza dough −2
    • Mozzarella −250 g
    • Lemons −8

    The ingredients in each dish's recipe come off the branch's stock automatically, extra cheese included.

  4. 8:31 p.m.

    The bill closes

    • Table 7 · The bill
    • Split 4 ways
    • Card 3 guests
    • Cash 1 guest
    • Card terminal 3 payments
    • Fiscal receipts 4
    • Accounting posted

    The bill splits per guest: three pay by card, one in cash. Card payments go through the bank terminal, receipts through the fiscal register, and the sale posts to accounting at day end.

No piece of this order was typed twice: what the server entered at the table reached the kitchen, inventory and accounting exactly as it was.

Problems and our solutions

Four problems we see most often in restaurant chains

When the register, kitchen, inventory and accounting run in separate programs, every team lives with its own piece of the problem.

At a restaurant chain's head office, an operations manager on the phone looks over branch reports spread across the desk
Management and branch operations

Head office loses control of operations as branches grow

When every branch runs its own program, you only learn which branch made money at the end of the month, and even then it's an estimate. Checking a branch's stock takes a phone call, and a single menu price change has to be keyed in at each branch.

We bring every branch and brand into one system

Each branch's sales, inventory and costs are recorded in the same system, so you can track profit and loss by branch or restaurant from head office, down to the ingredients in a recipe. Menus and prices are set centrally and reach every branch at once. If you run more than one brand or company, each keeps its own menu and prices in the same system, and every user sees only the records their role needs.

At closing time, an accountant in a restaurant's back office checks a register receipt roll and slips against a calculator and laptop
Finance and accounting

End-of-day reconciliation is done by hand

Matching the register, card terminals and accounting takes hours every evening. Receipts from the branches are keyed in one by one, and card fees are picked out of bank statements at month end. A void or a discount at the register gets questioned only if someone happens to notice it.

We close each day by cashier, on the record

The fiscal cash register (ÖKC) and card terminals connect to the register, and every sale posts directly to accounting. Fiscal receipts, e-invoices and e-archive invoices are issued from the same system. At shift and day end, the register closes with a separate reconciliation for each cashier, and card fees are calculated per bank and matched to collections. Voids, discounts and returns are monitored against audit rules you define, so unusual activity shows up the same day.

In a central kitchen's storeroom, a cook weighs a sack of flour while a purchasing staff member records the count
Kitchen, production and purchasing

No one knows what a plate really costs

Waste, complimentary items and staff meals never come off inventory, so the count comes up short and no one can say why. The cost of a sauce or dough made in the central kitchen never reaches the plate at the branch, which makes it hard to price the menu on cost.

We tie recipes to inventory, and cost to price

Every item sold deducts the ingredients in its recipe from inventory. Because waste, complimentary items and staff meals are recorded separately, the reason behind a count difference becomes visible. Production in the central kitchen and in the branches is modeled separately, and items sent to a branch are tracked in stock. Recipes provide allergen information and an estimated plate cost, and the system suggests a selling price from that cost. Purchasing runs centrally or by branch depending on the supply category.

During a busy dinner service, a server takes an order on a tablet at a table of four
Branch and floor teams

Order and check tracking breaks down at peak hours

Orders go to the kitchen on paper, the same ticket travels between the grill and the bar, and tables get mixed up. Bills can't be split by guest, and delivery orders live somewhere else. When the internet goes down, the register can't make a sale.

We put the dining room, kitchen and delivery on the same screen

Servers enter orders on the branch's floor plan, where table status and reservations are visible too. Each order is split by the station that prepares it, so the grill, the cold kitchen and the bar see only their own work on their own screen or printer. Delivery orders are taken at the register and reach the kitchen as the same record, and bills split by guest or by item. When the internet goes down, the register keeps selling and sends its records to head office once the connection is back.

What we build

Six solutions Pargesoft developed for restaurants on Dynamics 365

We extend the register and store foundation of Dynamics 365 Commerce with what restaurant operations need. All six solutions share the same item, recipe and guest records.

Dining room and register

We set up the register screens around each branch's floor plan and service flow. Checks, reservations, delivery orders and split bills are handled on the same screen, and the register keeps selling offline and works with a range of hardware.

Recipes and kitchen

Every item's recipe, ingredients and allergen information are defined in the system. Orders are routed to kitchen stations by screen or printer, and the estimated cost from each recipe gives you a basis for menu prices.

Inventory, production and purchasing

Inventory is tracked separately for each branch and warehouse and updates with every sale. Production in the central kitchen or in the branch is modeled separately, and purchasing runs centrally or by branch depending on the supply category.

End of day and audit

Shift and day end close with a reconciliation for each cashier. The fiscal cash register, card terminals and card fees are matched to accounting, and risky transactions such as voids and discounts are monitored against audit rules.

Guests and quality

A guest's orders, loyalty points and complaints sit in one record. Each complaint is followed through to its resolution, and branches run hygiene audits from defined checklists.

Your existing POS

If you'd rather keep your POS system, your terminals stay where they are. We connected Micros registers to Microsoft Dynamics for D.ream and The Marmara Group, and today we do the same job with our adapter on Microsoft Marketplace.

Our references

What Pargesoft built for restaurant, catering and hotel groups

A restaurant and entertainment group, a caterer whose operations in Türkiye, Austria and the US we brought together and a group running hotels and residences. In all three, inventory, purchasing, finance and the registers ran in separate systems. We brought that work together on Microsoft Dynamics, and we use what we learned there in every restaurant system we build today.

Restaurants and entertainment

D.ream

Part of Doğuş Group, D.ream was founded in March 2012 to bring corporate standards to Türkiye's food and beverage industry. Today it serves guests at more than 190 locations in 20 countries under 49 brands, including Zuma, Roka, Coya, Nusr-Et, Günaydın and Da Mario.

The need

As the restaurant portfolio grew, bringing inventory, purchasing and product management for every group company into one system had become a priority. Keeping product definitions consistent across the companies added a further operational burden.

What we built

We set up central production and distribution, shared inventory and shared purchasing on Microsoft Dynamics 365. We moved intercompany transactions and financial management onto the same system and integrated the branches' Micros registers and banking systems with it.

  • Central production
  • Shared purchasing
  • Intercompany transactions
  • Micros integration

Airline and event catering

DO&CO

Headquartered in Vienna, DO&CO runs 32 gourmet kitchens in 12 countries on 3 continents for airline, rail and event catering, alongside restaurants, business lounges and hotels. In Türkiye, Turkish DO&CO serves nine major airports.

The need

Processes specific to airline catering had to be managed in the same system as restaurant, business lounge, hotel and event catering. The solution also had to be ready to roll out to operations abroad, adapted to each country's local requirements.

What we built

We implemented an integrated ERP platform with airline catering functionality and connected it to Turkish Airlines' reservation and flight management systems. We put advanced warehouse management and demand forecasting in place for food processes and distribution. Today the operations in Türkiye, Austria and the US run on the same platform.

  • Airline catering
  • Turkish Airlines integration
  • Warehouse management
  • Demand forecasting

Hotels, residences and events

The Marmara Group

In tourism since 1978, The Marmara Group operates hotels in Istanbul, Bodrum and Antalya, along with residences, historic event venues, restaurants and the Maison Marmara catering brand.

The need

Hotels operating under distinct concepts had to be run from one central system. Continuous integration with the register and front office systems, and bringing Türkiye's e-document processes into the same system, were also core requirements.

What we built

We unified the hotels' shared inventory and purchasing with their distribution, finance and human resources processes on Microsoft Dynamics, and integrated the Micros registers, Fidelio front office systems and banking systems into the same setup.

  • Shared inventory and purchasing
  • Micros integration
  • Fidelio integration
  • Banking integration

Project process and support

We start with a pilot branch and keep our support line open after go-live

We complete the setup in one pilot branch and validate it with real sales, then open it to every branch.

  1. Process analysis

    We review the dining room, kitchen, inventory and accounting flow on site, with your staff.

  2. Tailoring

    We prepare the register screens, recipes and payment methods for your business.

  3. Testing and sign-off

    We test the register, kitchen screen and fiscal register connections and get each team's sign-off.

  4. Pilot branch

    We go live in one branch and validate the system with real sales.

  5. Rollout to every branch

    Once the pilot is complete, we open the system to the other branches one by one.

Frequently asked questions

What restaurant managers ask us most often

Can we keep our existing restaurant POS system?

Yes. Pargesoft External POS Integration Adapter connects existing POS systems to Dynamics 365 Commerce and Finance. Your terminals stay in place, and all sales data still comes together in one system. The adapter is published on Microsoft Marketplace.

Do the branch registers keep working when the internet goes down?

Yes. In Dynamics 365 Commerce, the register can be set up to keep selling when the connection drops, and its records reach head office once the connection is back. We choose this setup for branches where the connection often fails.

How does it work with Türkiye's fiscal cash registers and e-invoicing?

Our register connects to the fiscal cash register (ÖKC) in each branch. Fiscal receipts, e-invoices and e-archive invoices are issued from the same system, and sales post directly to accounting.

We run several brands and companies. Can we manage them in one system?

Yes. In Dynamics 365 Commerce, each brand and company is set up in the same system with its own menu, prices and register settings. Head office runs shared purchasing and inventory while still seeing each brand's results separately.

Can hotels use it?

Yes, in the restaurants, bars and cafes inside a hotel, which work like a restaurant in terms of the register, kitchen and inventory. For The Marmara Group, we brought the hotels' shared inventory and purchasing into the same setup.

We run a single location. Is this solution right for us?

We build this solution for multi-branch chains and businesses with a central kitchen. For single-location or small businesses, our cloud-based restaurant POS, Olimposs, may be a better fit.

Visit the Olimposs website

Ready to run every branch, from register to kitchen, in one system?

Replace separate register, inventory and accounting programs and run all your branches on Microsoft Dynamics 365. Talk to Pargesoft consultants to map out the setup path and project plan that fit your business.

Schedule a Discovery Meeting