At 11 a.m., the warehouse receives a photo of a notebook page. The shop’s name is abbreviated, a quantity has been crossed out, and nobody knows whether “8” means eight cases or eight units. The pre-sales representative is already visiting the next customer. If you are looking for pre-sales software, start by sorting out the handover between taking an order in the shop and preparing it at the warehouse.
Here is how to organise that transition for a distributor in Algeria. This article is published by FULLLOYAL.

Pre-sales software needs a clear order process
In pre-sales, the representative takes orders without carrying goods. The warehouse then organises picking and delivery. Giving the representative a phone is therefore only part of the job: the back-office, warehouse keeper and delivery driver need to know which information to work from.
Before choosing an app, describe your working day on a sheet of paper. By what time must orders reach the office? Who checks availability? Who confirms a changed quantity with the customer? Who assigns delivery notes to drivers?
Set a rule for orders that arrive after the cut-off time. Representatives need to know when they can promise a delivery, rather than committing to a visit the warehouse has not planned.
Prepare customer records, products and sales units
Start with the products you actually sell and the shops in the pilot area. The same grocery shop should not appear three times under different names. Each product must be identifiable without relying on a nickname that only one representative uses.
For each product, clarify:
- Its code and description.
- Its packaging: individual unit, case or another pack you use.
- The number of units in that pack.
- Its price and the commercial rules that apply.
Every quantity needs an explicit unit. If the catalogue uses individual units and the customer orders cases, define how the team converts between them. Ask the software provider to demonstrate this situation in the app before you adopt it.
A cleaned-up Excel file can help you prepare this data. Check the process for bringing it into the software with the publisher; having a mobile app does not establish how data migration works.
Divide the work between the representative, warehouse and driver
Clarify responsibilities before the first trial. Here is one possible arrangement to adapt to your team:
| Role | Work to organise |
|---|---|
| Pre-sales representative | Identify the customer, enter the products and check the quantities together. |
| Back-office | Check received orders and resolve points that need clarification. |
| Warehouse keeper | Check available quantities and prepare the agreed goods. |
| Delivery driver | Deliver against the assigned delivery note and report discrepancies. |
Taking an order does not, by itself, guarantee that the goods are available. If the warehouse must reduce a quantity, designate the person who informs the customer and confirms their agreement.
Keep separate rules for orders, returns and payments. A request for goods does not mean they have been delivered or paid for.
Fictional example: three pre-sales representatives and two drivers
Consider a food distributor with three pre-sales representatives, two delivery drivers, one warehouse keeper and one back-office employee. This organisation and the following figures are entirely fictional.
For the pilot, only one representative uses the new app in their area. A shop orders eight cases of a product, with six units per case. The requested quantity therefore represents 48 units.
The warehouse has only six cases of this product available, or 36 units. The back-office contacts the customer, who accepts the six cases. The remaining two cases represent twelve units; they must not be recorded as delivered.
| Checkpoint | Quantity in this example |
|---|---|
| Initial order | 8 cases, or 48 units |
| Quantity accepted after checking | 6 cases, or 36 units |
| Quantity not delivered | 2 cases, or 12 units |
If the customer then calls the office, find the original order before entering another record. Use the call to clarify that request without creating a second, identical order.
At the end of the trial, reconcile the initial request, the agreed quantity and the delivery note. This check helps establish whether the new process remains understandable to everyone on the team.
Test offline order taking on an actual sales route
Do more than test on the office Wi-Fi. Using the phone intended for field work, try entering an order without a connection, then reconnect.
In the back-office, check that the correct customer, products and quantities have arrived. Also check how a modification is handled and what to do if an operation has not appeared yet.
Check the first entry before asking for a second one. An order saved on a phone may not have reached the office yet.
Also test an order for a product that becomes unavailable during the route. Offline operation does not remove the need to check availability before preparing the goods and confirming with the customer.
Start without multiplying versions of the same order
Choose a reference source for orders in the pilot area. If the notebook and app remain two independent lists, the office will still need to decide which one to trust.
Prepare a fallback procedure for incidents: who takes the request, who enters it afterwards, and who checks that it appears only once? Keep this procedure simple and make sure everyone knows it.
After the first routes, review concrete problems: a customer who is difficult to find, unclear packaging, an order not received or a changed quantity. Resolve these issues before equipping the other two representatives. Let these checks guide the rollout schedule.
Where FULLLOYAL fits into this organisation
FULLLOYAL combines an Android field app with a web back-office. Its pre-sales representative profile supports order taking without carrying stock. Driver mode provides access to the delivery notes assigned to each driver.
The solution includes routes, visits, stock per warehouse and offline work with synchronisation when the connection returns. It also provides reports on sales, stock and field activity.
For your demonstration, use the eight-case order and the offline scenario. Ask how packaging, quantity changes and synchronisation incidents are handled for your organisation. These are points to verify rather than automatic behaviour to assume.
FAQ
What is the difference between a pre-sales app and van sales?
A pre-sales representative takes an order for later delivery. In direct sales, the representative sells and delivers from the stock carried in their van. Choose the process that matches your activity.
Can we start with just one pre-sales representative?
Yes, for an operational pilot. Involve the back-office, warehouse keeper and a driver so that you test the whole chain. Check the software publisher’s commercial terms separately.
Does every customer location need internet to use FULLLOYAL?
FULLLOYAL supports offline work and synchronisation when the connection returns. During the trial, verify that operations have reached the back-office before starting their processing at the warehouse.
Do we need to stop using Excel on the first day?
You can use it to prepare your data and check the pilot. For orders in the trial area, however, choose a single reference source and a clear recovery procedure after an incident.