Skip to main navigation Skip to main content Skip to page footer

Version Easilys 0.655

🚀 Functional Enhancements

  1. Automatic update of finished products
    Overview:
    Since the previous version, it is possible to indicate in the Price Lists whether it is necessary to automatically update the prices and characteristics of the finished products. This choice is taken into account.
    Why is it important?
    When using the concept of storable recipe and finished products, it is necessary that the values of the finished products are accurate and up-to-date. Depending on the case, it may be preferable that the characteristics and prices of the finished products be entered manually or that this be automatic based on the characteristics of the corresponding storable recipes. The fact that this information can be automatically updated prevents oversights and makes the process safer.
    Benefits:
    ✅ Reduced manual errors.
    ✅ Consistency of nutritional data and characteristics.
    ✅ Reduced update tasks.

  2. Inventory blocking if receipts are in progress
    Overview:
    When creating an inventory, a warning message is displayed if receipts are still pending for the chosen inventory date or for an earlier date. In addition, a new option available in the site page allows you to activate an automatic block of inventory creation in this case.
    Why is it important?
    Avoids inventory errors due to premature inventory opening.
    Benefits:
    ✅ Securing stock.
    ✅ Fewer inventory errors.
    ✅ More robust process.

  3. Mapal internal control and alert on the integration of cash turnover
    Overview:
    We now take into account the 'Automatic D-x Days Revenue Integration Check' option added during the previous sprint on the site settings page. By checking this option (only visible to Mapal administrators) and entering the desired number of days, Mapal teams will be alerted if no sales is integrated for this site X days after the sale date.
    Why is it important?
    Enables the early detection of possible malfunctions in the integration of POS system data into Easilys.
    Benefits:
    ✅ Increased confidence in the data reported.
    ✅ Increased responsiveness.
    ✅ Proactive technical support.

  4. Manual Production Shift (Production Plan V2 BETA)
    Overview:
    We're making progress on the creation of the future ‘production plan V2’ screen. It is now possible to move part of a production batch using drag & drop, with an interactive choice window. Development will continue over the coming weeks.
    Why is it important?
    The recipe production date is normally determined automatically from the configured offset rules. However, in reality, constraints such as the availability of equipment, the presence of staff or the logic of production organization can lead the production manager to modify these dates. It is therefore essential to be able to manually adjust production dates directly in the schedule.
    Benefits:
    ✅ Better control of the production schedule.
    ✅ Intuitive interface.
    ✅ Faster adjustments.
    ✅ Adaptation to operational hazards.

  5. Improved duplication of menu frames
    Overview:
    Users are now allowed to duplicate a menu frame on frames that already have a parent menu frame.
    Why is it important?
    This allows menus from a parent site to be copied to a child site, and the child site itself to be able to make duplicable changes to its own child sites. Thus, for example, a national headquarters can suggest menus to all the descendants of sites, then an intermediate regional site can adapt the menu and easily update the menus of the sites within its perimeter.
    Benefits:
    ✅ Save time in creating menus.
    ✅ Reduction of manual errors.
    ✅ Better menu coordination.
    ✅ Better adaptation to local specificities.

  6. Taking into account "pinned" recipes when impacting menus
    Overview:
    Recipes pinned to a menu plan (Menu Predesign) will now be taken into account when impacting the menu.
    Why is it important?
    Exceptionally, during festive meals for example, we may want, in collective catering, to impose a single recipe and not a choice of recipe in a menu frame. In these cases, the recipe in question is ‘pinned’ and when the menus are impacted, this recipe must be the only one positioned for this meal element. Taking pinned recipes into account when impacting menus means that menu, cost and order forecasts are correct, limiting the need for manual actions.
    Benefits:
    ✅ Better forecasting of menus, costs, and orders.
    ✅ Easier menu management.
    ✅ Simplification of the process.

🐞 Bug Fixes

  • Period selection: Removal of the 30-day limit in the calendar.
  • Visibility of obsolete pages in profiles management: Deletion of sections linked to the old “POS Record” screen in the settings for actions authorised to profiles.
  • Deletion of label images is once again possible.
  • Deleting suppliers: securing when using the ‘supplier/site link’ import.
  • Supplier imports with multiple identifiers: correctly taken into account in v2 imports.
  • Valued recipes: duplicates linked to control dishes removed.
  • Nutritional calculations: Non-food ingredients are now excluded.
  • Menu pre-design and Smart Particulars: UI adjustments (alignments, borders, labels).
  • Supplier invoice status: It is now possible to change the status of supplier invoices from ‘validated’ to ‘balanced’.
  • Supplier filter in equipment: improved search function.
  • CA integration check: now only visible to Mapal teams.
  • Secure Price Lists import logs: more detailed server-side traces, hidden from the user.

See detailed Release