What to look at when choosing a pre-sales and order-taking app
Updated:
When choosing a pre-sales app, look at five things: whether it works offline, where prices and stock come from, what happens to the ERP, how access is controlled and who authorizes orders. CoreDLS fits when the company has a field team and wants to work with the ERP it already uses, or needs a native ERP.
A pre-sales app is used every day, often where coverage is poor. So the decision is not about the feature list but about how it handles a few criteria. This guide lists them and explains how CoreDLS answers each one.
The five criteria
| Criterion | What to ask | How CoreDLS answers |
|---|---|---|
| Works offline | Can an order be taken in a shop with no coverage? What happens to what was entered? | Data lives on the phone. What is entered without signal is queued and goes out by itself when the connection returns, and sync is by differences. |
| Prices and stock | Where do they come from? Do they have to be loaded separately? | They come from the company ERP (or the CoreDLS native ERP): real prices, stock, customers and customer accounts, with no retyping. |
| Relation to the ERP | Is data migrated? Does it write to my tables? Do ports have to be opened? | It does not migrate data, does not write to the ERP tables and does not open ports: a service on the customer network only makes outbound connections. |
| Access | How does each person log in? What if they lose the phone? | The phone is bound to the person; access is by fingerprint, face or PIN. An administrator revokes the device and the session is closed. Each person sees only their modules. |
| Authorizations | Who approves a large order or one with a discount? | Rules by amount, discount and credit limit, defined as data: they warn or block, and the order waits for whoever is defined. |
Beyond orders
- Collections: receipts against the customer account, with the real balance.
- Hands-free voice entry of orders, receipts and visits.
When CoreDLS fits
- The company already has an ERP and its field team (salespeople, pre-sellers, collectors, delivery staff) needs orders and collections from the phone without changing systems. It works with any ERP in any country; if the system runs on SQL Server it can most likely be connected, and if not, the connector is developed.
- It is an Argentine small or mid-sized company with no system, or with spreadsheets, that needs an ERP with ARCA electronic invoicing, purchasing, inventory, treasury and accounting.
When it does not fit
- As an ERP with fiscal invoicing outside Argentina: fiscal invoicing is for Argentina only and no fiscal compliance for other countries is claimed.
- Companies with no field team whose current ERP already meets their needs.
- When the company system does not run on SQL Server: it is not a blocker, but the connector has to be developed, and that is assessed in a technical call before deciding.
Frequently asked questions
- Which criterion matters most when choosing a pre-sales app?
- It depends on the company, but offline operation and the source of prices and stock usually decide whether the app is used in the field or abandoned.
- Does CoreDLS replace the ERP?
- If the company already has an ERP, no: it extends it to the phone and that system remains the one in charge. If it has none, CoreDLS also works as a complete native ERP.
- Do prices and stock have to be loaded again in the app?
- No. They are read from the company system and synced to the phone by differences.
- Who authorizes orders that exceed credit or discount?
- Whoever is defined as data in the administration: the order waits for their approval or is blocked, depending on the rule.
- Can it be tried before deciding?
- You can request a half-hour demo: the app is shown with test data and technical questions are answered on the same call.
You can request a half-hour demo: the app is shown with test data and technical questions are answered on the same call.