In a bright office, a woman operations analyst builds a simple app on a laptop while a colleague tests it on a tablet
Fynd ERP

The screens only your business needs, built on your ERP

Compose apps from widgets, bind them to ERP data or your own tables and publish them to the people who need them.

A builder that lives inside the ERP

No separate platform to secure. Apps use the same data and permissions as everything else.

Visual builder

Lay out pages with widgets on a grid or in a flow, and bind each one to data with expressions.

ERP data, ready to use

Read and change ERP records such as work orders and products from inside your app.

Your own tables

Create tables with text, number, date, true or false, JSON and reference columns, relations and views.

Outside systems

Call REST APIs and run automations from an app, with credentials kept on the server.

Actions and logic

Run queries, show messages and chain steps on clicks and changes, with your own logic in a sandbox.

Versions and approvals

Edit a draft, submit it, approve it and publish. Published versions never change in place.

Permissions

Give users, roles or teams edit, view or admin access to each app.

Run logs

Every run records the actions and changes it made, how long it took and whether it worked.

Import and export

Bring rows into your tables and take them out again in bulk.

Who it's for

The people who build apps and the people who use them work on the same data and permissions.

Operations and business teams

  • Build pages by placing widgets on a grid
  • Bind widgets to ERP data with expressions
  • Your own tables without a database project

Developers

  • Your own logic in a sandbox
  • REST calls with credentials kept on the server
  • Run logs for every action

IT and admins

  • Edit, view or admin access per app
  • Draft, approve and publish before changes go live
  • Published versions that never change in place

App users

  • Screens shaped to the way their team works
  • The same records the standard screens use
  • Apps that open inside the mobile app

See the screens your team will use

Real screens from Fynd ERP, shown with demo data for a fictional manufacturer.

See every app in the organisation, its status and its published version.

  • Draft and published status
  • Owners and access
  • Open, edit or embed

A day building a custom app

Follow one app from an idea to daily use. Each step happens in Fynd ERP, so there is no separate platform to run.

  1. Custom Apps and Tables

    A need comes up

    The plant wants a simple screen to track canteen coupons issued per shift.

  2. Custom Apps and Tables

    A table is created

    The builder adds a coupons table with date, shift and count columns.

  3. Custom Apps and Tables

    The page is laid out

    Widgets are placed on a grid and bound to the table and ERP records with expressions.

  4. Workflow and Automation

    An automation is added

    A button on the page runs an automation when a supervisor saves the day's count.

  5. Custom Apps and Tables

    It is approved and published

    The draft is submitted, approved and published as a version that never changes in place.

  6. Mobile App

    It is used on the floor

    Supervisors open the app inside the mobile app, already signed in.

Custom apps features in detail

The parts of a low-code app builder teams ask about most.

Low-code app builder

Lay out pages with widgets on a grid or in a flow, and bind each one to data with expressions. Run queries, show messages and chain steps on clicks and changes.

  • Grid and flow layouts
  • Widgets bound with expressions
  • Actions on clicks and changes

Custom tables

Create your own tables with text, number, date, true or false, JSON and reference columns. Add relations and views, and import or export rows in bulk.

  • Typed columns and references
  • Relations and views
  • Bulk import and export

App versioning and approvals

Edit a draft, submit it, approve it and publish it. A published version never changes in place, so you can always see what ran.

  • Draft, submit, approve and publish
  • Published versions kept as they were
  • Edit, view or admin access per app

Connect outside systems

Call REST APIs and run automations from an app. Queries run on the server, so the browser never receives the credentials.

  • REST calls from an app
  • Credentials kept on the server
  • Run logs with timing and result

Apps sit on top of every module

Your apps read and change the same records the standard screens use.

Manufacturing

Build station screens and checks on top of work orders and routings.

Inventory

Show stock and lots in the layout each team prefers.

Workflow and Automation

Run automations from an app and react to its changes in workflows.

Custom APIs

Expose your app's data and logic to outside systems through your own endpoints.

Reporting

Combine your tables with ERP data in the views your team needs.

Integrations and Connectors

Bring data from outside systems into your tables and apps.

Frequently asked questions

No. Most apps are built by placing widgets and binding them to data. You can add your own logic in code when you need it.

Yes, within the permissions of the person using the app. Every run is logged.

On the server. Queries run server side and the browser never receives the credentials.

You edit a draft, submit it, get it approved and publish it. A published version is never changed in place, so you can always see what ran.

Yes. A custom table belongs to the organisation and its rows can be used by every plant in it.