How to build sequences in K Series to benefit with Opsimize recipes and GP

Effectively there are many different ways to build sequences in K Series to get the desired outputs from your online ordering platforms such as Deliverect or Arch2Order, this is commonplace and therefore it is vital that you understand how to build them in K Series to ensure accuracy within the cost which then provides to the penny GP

These condense down to 2 types of sequences within K Series and we will show you how to build these below inside K Series, where and when to apply the recipe inside Opsimize.

Sequence Type 1 - The Spirit Sequence

In this case the base item "Absolut" has a price of "£0" and is a "Master" item, it's used as a vehicle to drive choices with K Series such as the measurement "25ml" or "50ml" and what mixer the customer would like to choose. In this case, the sales price is derived from the sum of the item prices within K Series.

How we handle this in Opsimize,

Essentially "Recipe ID" 239, the "Master Item" Absolut MUST be marked as Non-Stock in Opsimize. This is because the GP and movements will be pushed via the "Child Item" it is vital your recipe is done on the "Child" items. In the example above "Recipe ID" 208 and 209, Absolut 25ml and 50ml respectively must be configured with the correct amount to deduct from stock on sale. This will create a "Cost" against the "Recipe". see example within Opsimize below;

Where it's used,

This is commonly used in Bars and Restaurants and due to the face it has a "0" price its very rare to find this within Arch or Deliverect

Sequence Type 2 - The Meal Deal or The Dish with Modifiers /Additions

In this variation, the base item has its own price, modifications and additions have their own SKU and thus amend the base price either with a "Reduction" or "Addition", this will then provide a "Menu" Price. An example of this would be the "Chciken, Bacon & Lettuce Sandwich" as displayed below.

How we handle this in Opsimize,

Essentially "Recipe ID" 362, the "Master Item" will have its own "Recipe" marked against it in Opsimize. This is because the GP and movements will be pushed against the "Master" item and the "Child Items". In the example above any additional modifications will have their "Own" unique "Stock Movements" we will calculate the attribute sales by a ratio derived by the sum of all costs. This means if I was to purchase the following; 

Chicken, Bacon and Lettuce Sandwich - £5.00 sales price with a cost of £1.50

Kettle Chips - £1.00 Sales Price with a cost of £0.30

Coke - £0.50 Sales Price with a cost of £0.20

Total Sales Price is £6.50

The Total Cost is £2.00

Attributed Sales = Recipe Line Cost / Total Recipe Cost x Sales Price

Therefore to work out the above Sales Attribution;

Chicken, Bacon and Lettuce Sandwich - 1.5 / 2 x 6.50 = 4.875

Kettle Chips - 0.30 / 2 x 6.50 = 0.975

Coke - 0.2 / 2 x 6.50 = 0.65

As you can see from the above the "Price" was forced by the "Grouping" which means that we will show and display a different Net and Gross price on the "menu items", this will be prevalent when looking at your "Recipe Profitability report"

Important Notes and Key takeaways

• It is vital that you understand how your recipe is built and where your item price is coming from. In some sequences, this could be from the "Child Item" however in other instances this could be "overwritten" by the Sequence/ Item Group, In Opsimize we will only display the "Item Price" as it is set within K Series
• If you want "Modifiers" with a bespoke price that does not fit in the above options, Ie. Extra Chicken is the same "Recipe" but has a different price in several sequences, we recommend either adding an additional group to your sequence or adding a new SKU with the correct price. This is the only way we can calculate the correct GP within Opsimize