[{"data":1,"prerenderedAt":270},["ShallowReactive",2],{"blog-article-en-fixer-prix-livraison-historique-ventes":3,"blog-locales-fixer-prix-livraison-historique-ventes":254,"blog-related-en-fixer-prix-livraison-historique-ventes":263},{"id":4,"title":5,"body":6,"category":242,"categoryColor":243,"date":244,"description":245,"extension":246,"meta":247,"navigation":248,"path":249,"readTime":250,"seo":251,"stem":252,"__hash__":253},"blog\u002Fblog\u002Fen\u002Ffixer-prix-livraison-historique-ventes.md","Setting delivery prices using your sales history, events and time slots",{"type":7,"value":8,"toc":231},"minimark",[9,18,23,26,42,49,53,56,80,83,87,94,114,118,125,132,136,139,166,175,179,185,193,197],[10,11,12,13,17],"p",{},"Raising delivery prices is scary: you fear losing orders. Yet not raising them is costly, between rising ingredient costs and platform commissions. The right answer is neither \"raise everything\" nor \"change nothing\": it's ",[14,15,16],"strong",{},"adjusting dish by dish, at the right time",", based on your own data.",[19,20,22],"h2",{"id":21},"what-your-history-already-knows","What your history already knows",[10,24,25],{},"Every recorded order is a piece of information: which dish, which price, which day, which time, which platform. Over several months, this history answers precise questions:",[27,28,29,33,36,39],"ul",{},[30,31,32],"li",{},"When did I change this dish's price, and what happened to sales afterwards?",[30,34,35],{},"In which time slots does this dish sell best?",[30,37,38],{},"Did my sales move during an event (match, holidays, local festival, weather)?",[30,40,41],{},"At what point in the week am I really profitable?",[10,43,44,45,48],{},"The history still needs to be ",[14,46,47],{},"centralised",": if your sales are scattered across several tablets, several statements and the POS, the analysis becomes a headache.",[19,50,52],{"id":51},"step-1-know-each-dishs-margin-by-channel","Step 1: know each dish's margin, by channel",[10,54,55],{},"A price is judged against the margin. For each dish:",[57,58,59,66,73],"ol",{},[30,60,61,62,65],{},"calculate its ",[14,63,64],{},"cost price"," (ingredients, packaging);",[30,67,68,69,72],{},"subtract the ",[14,70,71],{},"commission"," of the platform concerned;",[30,74,75,76,79],{},"compare the resulting margin ",[14,77,78],{},"by channel",": dine-in, takeaway, each platform, direct sales.",[10,81,82],{},"A dish that's profitable in the dining room can be much less so in delivery. That's often where the first adjustments are hiding.",[19,84,86],{"id":85},"step-2-review-your-past-price-changes","Step 2: review your past price changes",[10,88,89,90,93],{},"Go back over the latest price changes and compare sales ",[14,91,92],{},"before and after",", over comparable periods (same days of the week, outside holidays). Three cases come up:",[27,95,96,102,108],{},[30,97,98,101],{},[14,99,100],{},"sales hold",": the dish could take the increase;",[30,103,104,107],{},[14,105,106],{},"sales dip slightly but total margin rises",": the increase is still a win;",[30,109,110,113],{},[14,111,112],{},"sales plummet",": the price crossed a psychological threshold, you need to roll back or rework the offer.",[19,115,117],{"id":116},"step-3-take-events-and-time-slots-into-account","Step 3: take events and time slots into account",[10,119,120,121,124],{},"A drop in sales isn't always about price. Before drawing conclusions, check the context: school holidays, a big match, heatwaves, roadworks in the area. Also cross-check your sales by ",[14,122,123],{},"time slot",": a dish can be in high demand at lunch and barely profitable in the evening, or the other way round.",[10,126,127,128,131],{},"This time-slot reading answers a key question: ",[14,129,130],{},"when is my restaurant profitable, and when isn't it?"," It guides prices as much as opening hours on the platforms.",[19,133,135],{"id":134},"step-4-adjust-in-small-steps","Step 4: adjust in small steps",[10,137,138],{},"A few proven principles:",[27,140,141,147,153,159],{},[30,142,143,146],{},[14,144,145],{},"one adjustment at a time",", so you can measure its effect;",[30,148,149,152],{},[14,150,151],{},"moderate increases"," on the most popular dishes rather than a general increase;",[30,154,155,158],{},[14,156,157],{},"consistent prices across platforms",", with a deliberate gap if commissions differ;",[30,160,161,162,165],{},"a ",[14,163,164],{},"single menu"," to apply the change everywhere at once, without forgetting a platform.",[10,167,168,169,174],{},"For building the menu itself, see also ",[170,171,173],"a",{"href":172},"\u002Fen\u002Fblog\u002Fmenu-engineering-livraison-rentabilite","menu engineering for delivery",".",[19,176,178],{"id":177},"what-ai-changes","What AI changes",[10,180,181,182,174],{},"Doing this work by hand takes time and rigour. An AI agent connected to your data can do it continuously: track each dish's price history, spot when an increase or decrease had an effect, cross-check with events and time slots, then ",[14,183,184],{},"suggest adjustments",[10,186,187,188,192],{},"That's the role of the ",[170,189,191],{"href":190},"\u002Fen\u002Ffonctionnalites\u002Fagent-ia","Pepprio AI agent",". Connected via MCP to your tablet, your POS, your platforms and your history, it analyses your menus, orders and prices and suggests improvements — the final decision stays yours. It only accesses your restaurant's data, in line with the GDPR.",[19,194,196],{"id":195},"in-short","In short",[57,198,199,205,211,217,224],{},[30,200,201,202,174],{},"Centralise your sales to have a ",[14,203,204],{},"reliable history",[30,206,207,208,174],{},"Think in terms of ",[14,209,210],{},"margin per dish and per channel",[30,212,213,214,174],{},"Review the effect of your ",[14,215,216],{},"past price changes",[30,218,219,220,223],{},"Take ",[14,221,222],{},"events and time slots"," into account before drawing conclusions.",[30,225,226,227,230],{},"Adjust ",[14,228,229],{},"in small steps"," and apply them everywhere via a single menu.",{"title":232,"searchDepth":233,"depth":233,"links":234},"",2,[235,236,237,238,239,240,241],{"id":21,"depth":233,"text":22},{"id":51,"depth":233,"text":52},{"id":85,"depth":233,"text":86},{"id":116,"depth":233,"text":117},{"id":134,"depth":233,"text":135},{"id":177,"depth":233,"text":178},{"id":195,"depth":233,"text":196},"Analytics","is-success","2026-09-27","When to raise a price, on which dish, at what moment? A method to adjust delivery prices from your sales history, events and time slots, and what AI adds.","md",{},true,"\u002Fblog\u002Fen\u002Ffixer-prix-livraison-historique-ventes","7 min",{"title":5,"description":245},"blog\u002Fen\u002Ffixer-prix-livraison-historique-ventes","8JhvqoDVUvou-qJM_LaSlFgxX1lDeJJVonKvvtoHZuA",[255,256,257,258,259,260,261,262],"ar","ca","de","en","es","fr","it","pt",[264],{"path":265,"title":266,"description":267,"category":242,"categoryColor":243,"date":268,"readTime":269},"\u002Fblog\u002Fen\u002Fanalytics-restaurant-decisions-data","Analytics restaurant : 7 questions auxquelles vos données doivent répondre","Your sales data is worth its weight in gold… if you know how to leverage it. Here are the 7 key questions and how to answer them with an appropriate dashboard.","2025-07-12","6 min",1790617959367]