Mobile Sales Order and Van Sales App

Orders that arrive two days late, on paper

Field sales and van sales run on information the office already has and the rep cannot reach. A rep sits in front of a customer and cannot say whether the item is in stock, what the customer's last three orders were, whether they are over their credit limit, or what price they are actually entitled to under their discount group. So the order goes on a pad, gets photographed and sent to the office, and someone re-keys it into SAP Business One hours or days later — by which time the stock has been sold to someone else, the price has been keyed wrong, or the customer is on credit hold and nobody noticed until the invoice bounced.

Van sales is worse. Stock physically leaves the warehouse on a vehicle, gets sold and settled at the kerbside, and the ERP finds out at the end of the day, if the paperwork survives. Reconciling van stock becomes an accounting exercise instead of a warehouse fact.

And the reason most attempts at fixing this fail is connectivity. Basements, industrial estates, rural routes and border crossings do not have reliable signal, so an app that requires a live connection to SAP is an app the rep stops trusting.

What ECOSIRE builds

ECOSIRE builds a mobile application for iOS and Android, backed by a synchronisation service that talks to SAP Business One, designed offline-first so the rep can work with no signal at all.

Offline-first data model

The device holds a scoped local copy of what the rep needs: their assigned Business Partners with addresses and contacts, price lists and special prices applicable to those partners, item master data with images and units of measure, on-hand quantity per Warehouse as of the last sync, and open balances. Orders, quotations, activities and payments captured offline queue locally and post to SAP the moment connectivity returns. Sync is incremental and conflict-aware, not a nightly full download.

Order and quotation entry

The rep builds a Sales Order (ORDR) or Sales Quotation (OQUT) with the same document logic SAP applies — the correct price list for that Business Partner, special prices, quantity breaks, discounts, tax codes and unit-of-measure conversions. Documents are posted through the Service Layer under a per-user account, so the audit trail in SAP shows who actually created the document, not a shared integration user.

Customer visibility in the field

Before the rep walks in, they can see the Business Partner's open A/R Invoices, current balance against credit limit, ageing buckets, last order history and open deliveries. Where you want hard credit enforcement, we honour the SAP credit limit and deviation settings and block or warn at the same thresholds SAP would.

Van sales and settlement

For van operations the vehicle is modelled as a Warehouse. Loading the van is an Inventory Transfer out of the main warehouse; the rep sells from van stock, which decrements the on-device quantity in real time regardless of signal. Sales can settle as a Delivery plus A/R Invoice, and where you take cash or card at the kerbside, an Incoming Payment is created against the invoice. End-of-route reconciliation compares van stock on hand against expected quantity and generates the transfer or Inventory Posting needed to settle the difference — with variances visible rather than absorbed.

Activity capture and proof

Visits, calls, competitor notes and photographs are written to SAP Activities against the Business Partner, so the CRM record fills itself from the field. Signature capture and delivery photographs are stored against the document as proof.

Configuration and control

User-Defined Fields extend the mobile documents where your process needs extra data, and a User-Defined Object holds the route, van and territory configuration inside SAP so administration happens where your team already works. Where documents above a value or discount threshold need sign-off, we route them through SAP's approval procedures rather than building a parallel approval system.

Who it is for

Distributors, food and beverage wholesalers, building-materials suppliers, FMCG operators and any SAP Business One user with reps who take orders away from a desk. It suits businesses whose reps currently work from printed price lists and order pads, and van-sales operations that reconcile vehicle stock manually. It is genuinely useful only if your SAP master data — price lists, credit limits, warehouse quantities — is in reasonable shape, because the app makes that data visible rather than fixing it.

How delivery works

The app is built to order. There is nothing to download today and no trial build, because the version you receive is configured for your documents, your pricing rules and your route structure.

1. Scoping call. We map how your reps actually work: order-only or full van sales, which documents they create, whether they settle payments in the field, how many reps and vehicles, which device platforms, how your price lists and discount rules resolve, and how territories are assigned.

2. Fixed quote. You receive a written scope covering the document set, the offline behaviour, the van-sales flow if in scope, the UDF/UDO inventory, device platforms and store distribution, with a fixed price and timeline. Work starts only after you approve it.

3. Build. Typical lead time is two to four weeks from approval, extending if van sales, field payments and multiple device platforms are all in scope. We build against a copy of your company database structure so pricing and document behaviour match your live system.

4. Install in test. The sync service is installed against your test company and the app is distributed to a small pilot group. Your reps run real customer visits against test data — order, price, credit check, sync, van reconciliation — and you sign off before we go near production.

5. Install in production. We install the sync service against your production company with your Basis or hosting contact, distribute the app through your MDM or the app stores as agreed, migrate configuration, and support the first live route days.

6. Support. A support window from go-live covers defects, sync issues and configuration adjustments. Longer-term support and future device-OS compatibility work are available under a separate agreement.

Honest limits

Offline-first means the stock figure a rep sees is accurate as of their last sync, not as of this second — we make that explicit in the interface rather than pretending otherwise, and we can hard-check availability at posting time when there is signal. Devices, mobile data plans and any MDM tooling are yours to provide. We do not process payments ourselves; where field card payments are in scope we integrate the payment provider you already use.