Instead of mSalesApp
Outgrow mSalesApp. Own your order and route records.
Enterprise DNA builds your version around your price groups, your promotions and the way your reps work their routes, brings your mSalesApp customers and history across, and runs it for you.
mSalesApp lists AU$299 a month, or AU$2,189 a year. Letting your own customers order through mOrderApp is extra: 0.90 per order, at least $99 a month.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
Where the subscription goes
The fee is fair for an app. The question is who holds the history.
mSalesApp prices one plan for the whole team, which is simpler than paying per rep. What it rents you is the screen your reps tap and the cloud behind it. The customers, prices and orders underneath came from your business and your accounts system.
An Android app for the road
Order taking, returns and payment collection happen in a phone app. That is the part of the fee a rep actually feels.
A sync with Xero, MYOB or QuickBooks
Customers and products are pulled in from Xero through a Data Sync screen. The records started in your books, not in the app.
A separate charge when customers order themselves
mOrderApp is not in the plans. It is charged per order your customers place, with a monthly minimum, so the bill rises as that channel grows.
Order history you view and print
The help centre shows orders filtered by date or customer, opened one at a time and printed as a PDF. Asking a new question across a year of orders is harder.
Reps who cannot add a customer
In the mobile app a rep edits the customers allocated to them and cannot create a new one. The office keeps the list, the app follows it.
Anything custom goes to a quote
Other ERP links, compliance needs and larger teams go to the Enterprise tier, which is priced by conversation.
What you get instead
Stores, routes, orders and promotions you can question directly
Customers
Every store with its price group and its trend
Each customer holds its rep, its visit rhythm, the price group it buys on and ninety days of orders. The office and the road read the same record.
- check Customers whose orders have dropped off
- check Products that similar stores buy and this one never has, with the gap in dollars
- check The price list each customer buys on, kept on the customer
Routes
A route plan managers can check without calling the rep
Each store sits on its own visit cycle. See who is due today, who is overdue and what each overdue store is worth.
- check Calls made, orders won and average order per rep, against the target you set
- check Try moving stores between two reps and see both workloads before anyone is told
- check Visit notes kept in full on the customer, not cut short on a small screen
- check A weekly summary of last week's calls and orders, written from the records
Promotions
Promotions judged by what they sold
Setting up a deal is the easy part. Knowing whether it worked, store by store, is what the records are for.
- check Display, ticket and shelf price checked per promotion and per store
- check Stores nobody has checked while a deal is running, listed before it ends
- check Which deals lifted orders
- check The deal price applied to the order line without the rep typing it
Returns and books
Returns, credits and the handover to your accounts
Returns cannot skip approval, batch coded lines cannot skip the batch, and every order is marked when it reaches your books.
- check Orders written out for Xero, MYOB or QuickBooks in one step and marked sent
- check Orders that never reached the accounts system, flagged the next morning
- check Every credited batch listed with stores and dates the day a recall lands
- check Order confirmations and rep reports printed under your own name and logo
Make it yours
Design your own mSalesApp replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from mSalesApp. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your mSalesApp data across and run it for you.
Switching
How to switch from mSalesApp
Moving over usually means pulling what records mSalesApp will give you, adding your order history from the accounting system it feeds, and running a test load before anything is saved for real.
- 1
Export what mSalesApp will give you
Export your customers and products from mSalesApp if your account allows it, and check the options with mSalesApp support. mSalesApp does not document a spreadsheet export for order history, so the more reliable source for orders is the accounting system it already feeds, Xero, MYOB or QuickBooks, which holds a record of every invoice it sent.
- 2
Run a test load first
Load the exported files in as a test run before anything is saved. This shows you what customers, products and orders would be created, without touching your real records yet. Your mSalesApp columns will not match the new system's own format exactly, so this step is also where that mapping gets checked before it goes live.
- 3
Check what the import flags
Look through what the test run flagged: records it could not match, fields it left blank, orders it could not tie to a customer or product. Decide, item by item, whether to fix the source file, adjust how a field maps, or leave it and move on. This is the step that decides how clean the new records end up.
- 4
Run both side by side for a while
Once the real load is done, keep mSalesApp running alongside the new system for a short stretch. Enter orders and check outlets in both, and compare what each one shows for the same customer or the same week. This is how you catch a mapping mistake before it becomes the only record you have.
- 5
Switch off mSalesApp
Once the numbers agree and your team is working from the new system without reaching for mSalesApp, cancel the mSalesApp subscription. Keep a final export or a PDF copy of anything mSalesApp does not carry across, in case you need it later.
Where the real effort goes
The real work is not moving the data, it is deciding how your own fields, price rules and call cycles should map into the new system, and how much order history is worth bringing across versus leaving in the accounting system. That mapping work is what takes judgement. Enterprise DNA does this for you when you have them install and run it.
Not ready for a call?
Get your mSalesApp switch plan by email
We will send you the step-by-step plan for moving your business off mSalesApp, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your mSalesApp switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways in
Try the free version, or have Enterprise DNA build and run yours
Open source
Try it yourself
Free
- 1 Download the free version from GitHub
- 2 Load the sample stores and open the folder in Claude Code
- 3 Ask which customers are overdue for a visit
- 4 Export your customers and invoices from Xero, MYOB or QuickBooks and ask Claude Code to map the columns
Omni by Enterprise DNA
Have Enterprise DNA build it for you
One setup fee, then a monthly retainer
- check We bring your mSalesApp customers, price groups, promotions and order history across and check the totals
- check A phone screen for reps that saves orders without signal, if your team orders in the aisle
- check We connect Xero, MYOB or QuickBooks so orders go in and prices come back
- check It runs inside Omni, our managed Command Center, with the rest of your business
Questions
Instead of mSalesApp, answered
mSalesApp is not expensive. Why would I move? expand_more
For a small team the fee is reasonable, and if the app does everything you need, stay. Owners move when they want answers the app does not give: which stores are slipping, which deals paid off, what a route change would do. They also move when they want the history in records they control, or when the business needs rules and paperwork of its own. That is what the free version and the built version are for.
How do I get my order history out of mSalesApp? expand_more
mSalesApp's help centre shows orders viewed on screen and printed to PDF, and customers and products coming in from Xero. It does not document a spreadsheet export of orders. The simplest source is usually your accounts system, which already holds every invoice the app sent it. Those columns differ from the free version's own import format, so they are mapped on the way in. Enterprise DNA does that mapping, and a test run shows what would be created before anything is saved.
My reps work offline on Android phones. What do they use? expand_more
The free version has no phone app. Reps using it today work from a laptop between calls. If your team takes orders in store without signal, Enterprise DNA builds your version a phone screen that holds the order and sends it when signal comes back. Some businesses keep mSalesApp for the road for a few months and move reporting and promotions first.
Our customers order through mOrderApp. What happens to that? expand_more
The free version has no ordering site for customers. If your stores order online today, Enterprise DNA can scope one as part of building your version.
Does it work with Xero, MYOB and QuickBooks? expand_more
Yes. The free version writes submitted orders to a file your accounts system can take in, and marks them sent, so nothing is posted twice. The built version connects directly, so orders flow in and prices flow back without anyone moving a file.
Keep the reps selling. Keep the records yourself.
30 minutes with Sam. We look at how your reps use mSalesApp today, what you wish the reports told you, and what your own version would look like. If it is a fit, we build it and run it. If not, the free version is yours to try.
Field Sales for Claude Code is free and open source, published by Enterprise DNA.
Done paying for mSalesApp?
Get your version built