Software for quick service restaurants and franchises: Saturday’s rush, forecast from Monday.

Quick service management software forecasts each restaurant’s footfall and derives supplier orders, team rotas and food cost from it. With Enskel, the rush is forecast quarter-hour by quarter-hour, site by site; each manager prepares their week, and head office follows the whole group, franchised or company-owned.

Each restaurant sees its day; head office sees all of them, on the same data: forecasts, purchasing, overdue checks, margins. On Monday, the group review; every morning, the alerts; at month end, food cost site by site. Our guide explains how to run several restaurants and which indicators to track.

Head office sees what the franchise agreement says will be shared, to compare sites and help them. The franchisee runs their restaurant: their forecast, their purchasing, their food cost, against their own theoretical cost. Your figures stay yours: each site reads its own.

Yes. You start with a pilot site: three months free, on all modules except HACCP, with a before-and-after measurement. Enskel is up and running there one week after the POS is connected; the group’s other restaurants then follow, at the pace you set.

Yes: the same recipe card everywhere, costed at each site’s purchase prices. A shared recipe card gives the same dish, to the gram, in every restaurant. An amended recipe card does not rewrite the past: each version keeps its period. The recipe costing and food cost module gives the details.

Popina is already connected. Your POS isn’t Popina? Tell us which one: we look at the connection with you, before the pilot; the timing depends on its vendor. You don’t change POS: Enskel reads your sales, and your POS stays yours.

Yes, if they go through the POS: the forecast starts from every sale it records, with the product, quantity, time and site. Their sales therefore feed into the rush forecast, then into the rota and supplier orders.