Submitted Ideas

We should have the option to change product views from ML to TOT or Bottle per category instead of having to do each line item seperately.

When entering an invoice on the system, could we perhaps have a feature where we select if tax is included / excluded and the % thereof. I am suggesting this as some supplier invoices are including tax while others are excluding. If the invoice is including we have to go item by item and calculate the excluding tax value which takes up quite a bit of time. If we could select if tax is included or excluded it would streamline the entering of invoices and leave less room for errors on the cost prices.

An embedded support bot which is trained specifically on Sculpture Hospitality's Knowledge Center, Support work flows, and reported field operations. The purpose of this support bot is to provide users a quick/easy support solution, while expanding our A.I. integrations across the organization. ref: v1.0 - UUPC in Application v1.1 - UUPC extended / expanded v2.0 - Dynamic Support Bot v3.0 - Item Database / Cross Database Brand Similarities v4.0 - Interactive Report Agent v5.0 - Interactive Report Generation & AI Driven Suggestions

What is Just-in-Time Reporting? This feature is a near clone and defeature of the current EoM Estimates Report. The feature’s purpose is to provide our users with a clear & concise means to provide a client an estimated on-hand inventory at any point given the following: The outcome of this is a single, exportable report, that could be provided to a client to have an estimated on-hand, based off the Previous On-Hand Inventory (from audit), Current Purchases {invoices are timestamped} (+) and Current Sales (-). What Problem are we solving? Users often face the challenge of providing clients with accurate, real-time information about product availability (on-hand inventory) based on the available product. This approach answers the main two questions that a perpetual users needs to know, “What do I have on hand right now?” and “What do I need to order today?”. This development aims to solve this problem, with a focus on providing 3 solutions Estimated On-Hand Inventory - by brand, by DateEstimated Order - by bottle size, by DateEstimated End-of-Month - by brand

Shelf count should be bolded and a larger font Currently, the Shelf number is bolded and a larger count, while the shelf count is a smaller font and not bolded. They are very close to each other and easy to mix up. Just reverse the bolding and font size as the shelf count is more important than the shelf number. My opinion....

If you predominately swipe to count on the app, the sound of the swipe is an important factor. Currently, it is easy to inadvertently select one of the other presets on either the left or especially the right of the screen. Unless looking at the screen each time (which really eliminates the advantage of swiping), you end up entering a different multiple than was intended with the swipe. To eliminate errors, the solution would be to have different sounds for each of these presets, so the user would know which one they are on based on sound or at least be alerted that the preset was changed to another multiple.

When we audit several venues of same client, they use to move preps between them. When this happens we have to manually do the maths to be able to receive or send that preps to other places with their quantities and items. Having this option we directly put the preps in or out at the purchase tab and system do the calculation itself. This will also help when we want to compare if this information was taken in account in the report and compare with information sent by client.

In the variance tab of the dashboard the Class ´s name that appears are not my customized classes, are default ones.

Problem we are solving: A user should be able to switch between the use of the weight (mass) units of measure and volume, or count when building recipes, prep items, capturing inventory, or any other feature where solids and liquids need to be interchangeable. Example: Flour is purchased by the pound (lb) or gram (g), but in almost every recipe it will be identified as a cup. Onions are purchased by the bag, or each, and used within recipes as a “cup” and “diced cup”. The benefits of this enhancement for the client and franchisee are : Recipes align with the same definition and ingredient quantities as provided by the chef Recipes are easier to understand and teach. Creating less steps Reduces the need for work arounds with prep-items. Consider how we would set up something such as soup, I want 4 cups of onions 2 cups of jalapenos 1 cup of rice 8 cups of beans The Solution: The feature is broken down into two main components: Standard Conversions: Should be used to convert a Solid to a Liquid, Liquid to a Solid, OR any situation where an object is purchased in a liquid/solid but used in the opposite form. NOTE: This is a massive shift and defines a density for an item, at the ITEM level. Custom Conversions: This is a means to define things like a Cup of Sugar, packed or unpacked. Or create custom units. This is Client specific, and much less intrusive as Standard Conversions. To get started, you must assign a conversion at the ITEM level, via Item setup. please use this link here: https://beta.food.sculpturehospitality.com/itemSL/https://beta.food.sculpturehospitality.com/slConversions/

When weighing, we should add the ability to swipe up to change to the counting screen and add a bottle.

We don't usually count beer by the case so if we uncheck the case box, this should stay unchecked for each client until checked again. We would all benefit because once this count feature is unchecked, no more having to uncheck it again for every single audit.

There are several items with redundancies. Instead of choosing 1 out of the 6 that will continuously populate. If I could add the remainder to a personal blacklist (on my device only), I would save time by removing items I don't use. some examples: Corona 24p case KEG Elysian Space Dust KEG Budweiser Bud Lt 24p case Being able to remove redundancies in my app only would maintain the presence in the server, but remove them for me to save time.