Your POS, connected.

Enskel is compatible with the Popina POS, already connected. Your POS isn’t Popina? Tell us which one: we’ll look at the connection with you; the timing depends on its provider. Whatever the POS, Enskel uses the same sales data. See the details of the connection between Popina and Enskel.

Sales: for each sale, the site, the product, the date and time, the quantity and cancellations. They are used for forecasting and profitability; kiosks, drive-thru and delivery count if they go through the POS. Enskel itself adds local weather and events near each site.

No. Enskel reads your sales; your POS remains yours. You authorise access to your sales data, then we check the depth and quality of the history, site by site. Your teams take payments as before, and their sales feed the forecast, the orders and the food cost.

No. The POS is enough to start forecasting; the rest is connected afterwards. Recipe cards, stock and purchasing, teams and HACCP checks are added with the modules you choose, on the same sales data. You can start with Forecasting and Stock, or with Recipe costing and Profitability.

The first forecasts arrive one week after access to your POS data. Before that, we scope your sites, your tools and the decisions to prepare with you, then check access to the POS and the depth and quality of the history. For a POS other than Popina, the connection is looked at with you before the pilot.

In Paris: accounts and users with Supabase; large volumes, such as sales, forecasts and calculations, with Scaleway. Some Supabase processing, such as billing or support at your request, may take place elsewhere, under standard contractual clauses. The list of sub-processors and their hosting regions is published.