Zest Platform FAQ and Feedback form

Feedback Form

Use this form to report issues, suggest improvements, or share ideas about the app.

Frequently Asked Question

  • Zest is a production analytics platform for food manufacturers. It connects to your existing operational data and shows you where efficiency losses and waste are occurring across your production process — and what to do about them. It's built for operations teams who need clear, actionable visibility into production performance, and for senior stakeholders who need a reliable picture of cost and efficiency at site level.

  • Accounts are set up by the Zest team as part of onboarding — there's no self-serve sign-up. We configure your account based on your site and data setup. Reach out via admin@zestsolution.io to get started.Answer

  • No special hardware is required. The platform runs in a modern web browser, so you just need a reliable internet connection and an up‑to‑date browser such as Chrome, Edge, or Safari. If you’re using it at a factory or site, we recommend devices with stable Wi‑Fi or ethernet.

  • Zest is an analytics layer — it reads from your existing production data rather than acting as a data entry tool. If something looks incorrect in the platform, contact your Zest point of contact or use the bug reporting process below.

  • We recommend desktop use. Zest is accessible via any web browser, but It's optimised for desktop use because some views involve a level of data detail that doesn't translate well to smaller screens.

  • Zest connects to your existing production and factory systems to ingest operational data such as run records, yields, waste volumes and process metrics. We use this data in our proprietary ingestion pipelines and analytics engine to turn siloed factory information into end‑to‑end visibility and actionable waste‑reduction insights inside your Zest workspace. Your underlying data remains your property and is not shared with third parties.

  • Use the feedback form on this page. We work closely with clients during rollout and actively incorporate operational feedback into how the platform develops.

  • Use the feedback form on this page. Include a brief description of what you were doing and what you expected to happen — a screenshot is helpful if you can include one.