> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to build a mobile sales order app connected to the ERP
- URL: https://blog.jestor.com/mobile-sales-order-app-erp/
- Published: 2026-09-16T18:49:24.000Z
- Updated: 2026-09-16T18:49:24.000Z
- Author: Bruno Bannach

A **mobile sales order app** lets a field rep create an order on a phone using the product, client and seller data that already exists in the **ERP**. In **Jestor**, a ready made template mirrors that registry from **Omie** and handles commission alongside the order.

## Why field sales still runs on paper and messages

Reps are rarely at a desk. When the ordering system only works on a computer, the order gets written on paper or sent as a message, and someone else types it in later.

That delay is where the wrong price, the outdated product and the forgotten commission come from.

What a connected mobile flow solves:

- Orders taken with prices that are no longer current
- Products sold that are not in the catalog
- Commission calculated manually at month end
- Delay between closing the sale and registering it
- Reps unable to check a client record on the spot

## What mirrors from the ERP into the app

| Registry   | Where it is created | What the app shows                     |
| ---------- | ------------------- | -------------------------------------- |
| Products   | Omie                | Name, base price and ERP code          |
| Clients    | Omie                | Client record available for selection  |
| Sellers    | Omie                | Rep linked to the order for commission |
| Order      | Jestor              | Items, quantities and total            |
| Commission | Jestor              | Calculated against the closed order    |

## Step by step to put it in the field

1. **Install the sales order template**, built with a mobile first layout that also works on desktop.
2. **Create or review your products in Omie**, including base price and code.
3. **Register clients and sellers in the ERP**, since both mirror into the app.
4. **Wait for the sync**, after which new products appear in the app's product list.
5. **Train the reps on the order flow**: select client, add products, confirm quantities.
6. **Configure the commission rule** so it is calculated from the closed order.

## Why mirroring beats maintaining two catalogs

Keeping a second product list in the sales tool guarantees they will drift apart. Mirroring means the ERP stays the single registry and the app is a window onto it.

- **One catalog:** products created in Omie show up in the app automatically
- **Price at the source:** the rep sees the base price registered in the ERP
- **Mobile layout:** built for use in the field, not adapted from a desktop screen
- **Commission tied to the order:** no separate spreadsheet at month end

## Frequently Asked Questions

### Does the rep need to register products in the app?

No. Products, clients and sellers created in Omie mirror into the app. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Does the template work on a computer too?

Yes. The layout is mobile first, but it works on desktop as well.

### Is commission calculated automatically?

Yes, from the closed order, using the rule you configure for each seller.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.