Anyone who has waited tables at a busy restaurant knows the quiet chaos of course management. The kitchen needs to know what to fire first, the server needs to keep track of which table is on starters and which has moved to mains, and the POS system — in theory — should be the single source of truth that keeps everyone synchronized. In practice, most POS setups treat course allocation as a manual step that servers handle when they remember and skip when they’re slammed.
Odoo just addressed this with two features that work together to make restaurant order management significantly less error-prone: automatic course allocation based on product categories, and a Break Combo option that lets staff deconstruct combo meals into individual items without voiding and re-entering the order.
Automatic Course Allocation: Set It Once, Forget It Forever
The concept is straightforward. Every product in the POS belongs to a category — Appetizers, Burgers, Steaks, Desserts, Drinks, and so on. With the new automatic course allocation feature, each of those categories gets a course assignment. Appetizers and Salads map to the Starter course. Burgers and Steaks map to Main. Desserts map to the Dessert course. Once that mapping exists, the system handles the rest.
When a server adds items to an order, Odoo automatically sorts them into the correct course based on their category. A Caesar Salad lands in the Starter course. A Ribeye goes to Main. A Tiramisu goes to Dessert. There’s no manual course button to press, no drag-and-drop to rearrange, and — critically — no opportunity to forget. The kitchen sees a properly structured order with courses clearly separated, every time.
The configuration lives in the POS settings under the Preparation section. Toggle on Automatic course allocation, then go to POS Product Categories and assign a course to each category. One course can apply to multiple categories, and there’s no limit on the number of courses you can define. A fine-dining restaurant with seven-course tasting menus can set up just as easily as a casual bistro with three.
Why This Matters More Than It Sounds
The manual alternative — which is what Odoo offered before — required servers to click a Course button in the POS interface to start a new course, add the items for that course, then click Course again for the next one. During a lunch rush with six tables ordering simultaneously, that extra interaction adds up. Some servers would skip it entirely and dump everything into a single course, which meant the kitchen had to sort out the firing order themselves. Others would use it inconsistently, creating orders where the steak was in Course 1 and the salad was in Course 2.
Automatic allocation removes the variability. Every order follows the same structure regardless of which server enters it, how busy the floor is, or whether someone forgets to press the Course button. For kitchen staff, this consistency is worth more than any individual feature improvement. They can trust the order of items on their preparation display without second-guessing whether the server actually intended the soup to fire before the steak.
Fire and Transfer: Controlling the Kitchen Flow
Automatic sorting is only half the equation. The other half is controlling when each course actually gets sent to the kitchen. Odoo handles this with the existing Fire Coursemechanism, which now works seamlessly with auto-allocated orders.
When an order comes in with three courses, only the first course fires immediately. The Main and Dessert courses sit in a waiting state on the kitchen display until the server explicitly fires them. This matches the real-world rhythm of table service — you don’t want the kitchen plating the main while guests are still finishing their appetizers.
The Transfer feature complements this by letting staff move individual items between courses after the order has been placed. If a table decides they want their side salad served with the main course instead of as a starter, the server can drag it between courses directly in the POS interface. The kitchen display updates immediately, and the billing stays consistent.
Break Combo: When the Meal Deal Needs to Come Apart
The second new feature addresses a different restaurant scenario entirely: what happens when a customer orders a combo meal and then wants to modify it in ways the combo structure doesn’t support.
Combo meals in Odoo POS bundle products together at a discounted price. A $18.99 lunch special might include a burger, fries, and a drink. That’s great until the customer decides they want to upgrade the drink, swap the fries for a salad, or split the combo across two checks at the end of the meal. In previous versions, handling this required voiding the combo and re-entering each item individually — a process that slowed down service and created opportunities for pricing errors.
The new Break Combo option sits in the vertical ellipsis menu on any combo item in the order. Select it, and Odoo splits the combo into its individual component products, each priced at its standard sales price. The burger goes back to $12.99, the fries to $6.00, and the drink to whatever its standalone price is. From there, the server can modify, remove, or reassign any individual item without touching the others.
The price adjustment is the important detail here. When a combo breaks apart, each item reverts to its individual list price, not a proportional share of the combo price. This is intentional — it means the restaurant doesn’t accidentally sell items below cost, and the math on the final check is straightforward. If the customer questions why their broken-combo total is higher than the original combo price, the answer is simple: the combo was a deal.
The Bigger Picture for Restaurant POS
These two features work at different levels of the restaurant workflow, but they share a common design philosophy: reduce the number of manual decisions that servers have to make during service. Auto course allocation handles the structural organization of an order. Break Combo handles the exception cases when a preset configuration needs to flex.
For restaurant operators evaluating POS systems, the question has always been whether the system can keep up with the pace and unpredictability of table service. A POS that requires too many taps, too many decisions, or too many workarounds during a rush will eventually get bypassed — servers will write orders on notepads, shout to the kitchen, and reconcile later. Features like automatic course allocation and Break Combo don’t just add functionality; they remove friction points that cause staff to work around the system instead of through it.