In B2B, field sales are often the most valuable connection to the customer - and at the same time the one most poorly connected to the shop. While the online store draws on Shopware and the ERP, knows customer-specific prices and sees stock levels almost in real time, the sales team on site still frequently works with a printed catalog, a notepad and a paper order form. That costs time, produces transcription errors and leaves revenue on the table. Around 75 percent (Sana Commerce) of B2B buyers now consider switching to a supplier with a better digital buying experience, and 33 percent (Sana Commerce) of B2B orders captured online recently contained errors. At the same time 43 percent (Bitkom) of companies in Germany still fax frequently, and only 40 percent (Bitkom) work predominantly paperless. An offline-capable field sales app on the same Shopware and ERP data base closes exactly this gap: it brings customer prices, stock levels and order capture directly to the point of sale - even when there is no signal there. This article shows how field sales become the extended arm of the B2B shop and its services and replace paper forms on site.
Key takeaways
- Field sales still work with paper on site while the shop has long known customer prices and stock levels. Around 75 percent (Sana Commerce) of B2B buyers consider switching to a supplier with a better digital buying experience.
- The most expensive media break is the re-keying in the sales desk: 33 percent (Sana Commerce) of B2B orders captured online recently contained errors, and 43 percent (Bitkom) of companies in Germany still fax frequently.
- The app has to run on the same data base as the shop - customer-specific prices, tiers and stock from Shopware and the ERP - so that the same price and the same availability apply on site and online.
- Offline-first means customer, item and price data sit locally on the device, orders are captured completely without a signal and transferred automatically once a connection returns - with a visible status per order.
- So that a retry after a dropped connection does not create a second document, every order needs a unique identifier. Roles, limits and approvals are adopted from the shop instead of forming a separate island.
Why Field Sales Become the Extended Arm of the B2B Shop
In B2B a large part of the purchasing decision is made in the personal conversation. The sales rep sits with the customer, discusses the need, checks samples and takes the order. In exactly this moment, however, they often lack what the online store has long had: the correct customer-specific price, current availability and a way to capture the order directly and bindingly. Instead things are noted on paper, typed into the system later at the office, and the customer has to wait for confirmation. Every one of these intermediate steps is a break point where time is lost and errors arise. A field sales app moves the capabilities of the shop to where selling happens and turns the sales force into the extended arm of the digital channel - not its competitor.
Customer expectations amplify this pressure. Already 73 percent (Sana Commerce) of B2B buyers prefer to order online, and 85 percent (Sana Commerce) report friction that leads to abandoned purchases. Anyone who still works with paper in field sales looks unprofessional next to a well-made shop. At the same time online trade in B2B is no longer a niche channel: via online shops and marketplaces, manufacturers and wholesalers in Germany recently generated around 509 billion euros (IFH Cologne), a plus of 7 percent (IFH Cologne) over the previous year. Field sales must draw on the same data quality as this channel, otherwise contradictory prices and information arise. Linking sales and shop is therefore not a technical detail but a matter of credibility toward the customer. How to digitize sales processes in general is explored in our article on digital sales processes in B2B.
Customer Visit
During the on-site visit, sales capture the need with correct customer prices and record the order directly, instead of re-entering it later at the office.
Construction Site
On the site with thick concrete and poor reception, the order is captured offline and transmitted automatically as soon as there is signal again.
Trade Fair and Promotion
At the fair stand many orders arise in a short time; the app captures them in a structured way, even when the on-site Wi-Fi is overloaded.
Branch Visit
While walking through the customer branch, sales check stock and add the reorder directly at the shelf.
Plant and Warehouse
In the customer hall, where mobile coverage is rarely reliable, order capture remains usable at all times thanks to offline mode.
Region Without Signal
In rural areas with dead zones the app keeps working and synchronizes the orders as soon as the next connection is available.
Paper Form, Phone Call and Fax: Where the Break Happens Today
The classic field sales workflow is full of media breaks. Sales note the order on a form, call it in to the office or send a fax, someone types it into the ERP, and only then does a binding order arise. That this route is still widespread shows in the figures: 43 percent (Bitkom) of companies in Germany still fax frequently, and 53 percent (Bitkom) report problems coping with digitalization. Every manual transcription step costs time and is a source of error. In the worst case a wrong part number, a wrong quantity or an outdated price is carried over - and the error only surfaces when the goods are already on their way.
The follow-on costs are considerable. Because around 33 percent (Sana Commerce) of B2B orders captured online contained errors, 68 percent (Sana Commerce) of buyers say an error-prone order process keeps them from using digital channels. This applies all the more to the handwritten paper order: it passes through more manual stations and is additionally typed out. An app that captures the order once cleanly with checked data and transmits it to the ERP without further intervention removes exactly these break points. The customer gets an immediate order confirmation, and the sales desk no longer has to decipher notes.
The Most Expensive Media Break Is the Second One
One Data Base: Customer Prices, Stock and Order in One App
The real value of a field sales app lies not in a pretty form but in the fact that it works on the same data base as the online store. Customer-specific prices, tiers and framework conditions live in the ERP and in Shopware; the app shows them for the right customer without looking up. That is decisive, because wrong prices are a common frustration: 29 percent (Sana Commerce) of buyers complain about inaccuracies in prices. How customer-specific pricing logic is mapped cleanly in the shop is shown in our article on price lists and tier pricing in Shopware; the same logic must apply in field sales so that the same price is quoted on site and online.
Stock levels are just as important. When sales promise a quantity to the customer that is not actually available, trouble arises. 28 percent (Sana Commerce) of buyers name inaccurate stock information as a problem, 31 percent (Sana Commerce) complain about inconsistent delivery times. The app should therefore show the last synchronized availability and make clear how current this value is - in the offline case, for example, with a timestamp. How to reliably bring stock and delivery times into the shop is covered in our article on real-time availability and delivery times in the B2B shop. The basis for all of this is a clean connection of the ERP system, as described in our article on ERP integration in B2B e-commerce.
When prices, stock and customer data come from one source, the captured order is automatically consistent. Sales need not reconstruct conditions from memory or search a price list in a folder. The order arises with the same rules that apply in the shop and, after synchronization, lands as a regular document in the ERP. This turns two separate worlds - online store and field sales - into one continuous sales channel on a shared data base.
Offline-First: Order Capture Without a Signal
The decisive difference between a mobile shop view and a real field sales app is offline capability. In the field a stable connection is not a given: thick walls in warehouses and plant halls, dead zones in rural regions, overloaded Wi-Fi at trade fairs. An app that shows only an error message in these moments is useless exactly when it is needed. Offline-first means the app keeps the necessary data - customers, articles, prices, last stock levels - locally on the device, and sales can work fully without a connection. The order is stored locally and held in a queue until there is signal again.
Technically this can be implemented with modern web technologies, without having to install an app from a store. A Progressive Web App stores data in the device browser, works without a connection and synchronizes on its own as soon as there is reception again. That significantly lowers the entry barrier for sales, because no separate installation and approval process is needed. This is complemented by a clear display of the synchronization status, so the employee always sees which orders are already transmitted and which are still in the queue.
- Customer, article and price data live locally on the device and are usable without a signal
- Orders are captured fully offline and held in a queue
- Automatic synchronization as soon as a connection is available again
- Visible status per order: stored locally, transmitting, arrived in the ERP
- A timestamp on the stock level makes clear how current the displayed value is
- No data loss on app restart or interrupted connection
What the App Must Be Able to Do at the Customer
A good field sales app maps the real course of a customer visit rather than rebuilding the entire shop for mobile. Sales choose the customer, see their conditions and history, capture line items with correct prices and availability and complete the order or a quote. In addition, quick capture via part number and barcode scan helps, as it makes sense in the mobile order flow too - details in our article on B2B procurement by smartphone and tablet. The following building blocks form the core of such an app.
Customer Selection
Sales pick the customer from the locally stored list and immediately see conditions, addresses and the most recent orders - even without a signal.
Customer Prices
For every article the individual price including tier appears, exactly as in the shop, without the employee having to look up conditions manually.
Stock Level
The last synchronized availability is shown with a timestamp, so that no quantity is promised on site that cannot be delivered.
Order and Quote
Line items are captured with quantity and packaging unit and saved either as a binding order or as a quote for later approval.
Document and Signature
The customer can confirm the order on site, for example by signing on the tablet, and receives a traceable summary.
Sync Status
A clear status shows per order whether it is stored locally, transmitting or already arrived as a document in the ERP.
Synchronization and Conflict Resolution with Shopware and ERP
The trickiest part of an offline-capable app is synchronization. As soon as several employees capture orders offline and transmit them later, data can overlap: a price was changed centrally, a stock level is now tight, or the same customer was edited from two sides. The app must therefore clearly govern which data the device only reads and which it writes. Master data such as prices, articles and stock flow from the ERP to the app; orders flow from the app to the ERP. Separating this direction cleanly prevents most conflicts from the outset.
For the remaining cases, clear rules are needed. Every order gets a unique identifier, so that a duplicate transmission does not lead to a duplicate document. If the locally displayed price deviates from the current ERP price, the system should report the difference instead of silently adopting one value or the other. And if a promised stock is no longer available at transmission, the sales desk must receive a visible task instead of the order quietly failing. A robust synchronization is thus above all a question of clear responsibilities and a clean integration architecture, as described in our article on interface architecture in B2B.
Pitfall: Duplicate Orders
Paper Order or Field Sales App in Comparison
The difference between the classic paper route and an offline-capable app shows in every single step of the customer visit. The following comparison sums up the key points.
| Attribute | Paper Order | Field Sales App (offline) |
|---|---|---|
| Price finding | Price list in a folder, searched manually | Customer-specific price automatically from ERP and Shopware |
| Availability | Estimate or callback to the office | Last synchronized stock with a timestamp |
| Capture | Handwriting, typed out later | Structured on site, captured once |
| Signal needed | No, but many follow-on steps | No, order is stored locally |
| Transfer to ERP | Manual typing at the sales desk | Automatic synchronization without re-typing |
| Confirmation for the customer | Only after processing at the office | Immediately on site, including a summary |
Adopt Roles, Prices and Approvals from the Shop
So that the app does not become yet another isolated island, it should adopt the rules of the B2B shop. Shopware knows customer groups, roles and rights that control who sees which prices and assortments. This logic can be carried over to field sales: the sales rep sees the conditions the respective customer is entitled to, and no more. Dynamic prices oriented on margin and demand can also be integrated - how to protect margins in the B2B shop with data-driven pricing is shown in our article on dynamic pricing in the B2B shop. It is decisive that the same pricing logic applies on site and online, so that no customer hears two different prices for the same article.
Approvals and limits are just as important. If field sales capture a quote with an unusual discount or an order exceeds a limit, it should run into an approval process instead of becoming binding immediately. This keeps sales able to act without losing commercial control. Besides prices and stock, product-accompanying mandatory details can also be adopted from the shop - such as packaging and material information, as described in our article on implementing the PPWR in the B2B shop. Field sales thus become not a special solution but a consistent part of digital sales that complements shop self-service rather than contradicting it; how both routes interact is shown in our article on digitizing sales alongside self-service.
An order arises where the customer agrees - in the conversation, in the warehouse, on the construction site. Whoever can capture it cleanly and offline in that moment turns every customer conversation into a binding document, without the detour via paper.
Implementation in Shopware: From Idea to Productive App
The path to the field sales app begins not with technology but with the real course of a customer visit. Whoever understands which information sales actually need on site and which steps they really take can focus the app on the essentials rather than rebuilding the whole shop for mobile. Shopware Open Source and a cleanly connected ERP provide the shared data base; the app is built on top as an offline-capable Progressive Web App. A step-by-step approach makes sense that delivers real value early and then grows based on practice.
- Analyze the customer visit: which data, prices and steps sales really need on site
- Clarify the data base: reliably provide customer prices, stock and master data from Shopware and ERP
- Build the offline core: make customer selection, price display and order capture usable without a signal
- Secure synchronization: implement a unique order identifier, conflict rules and a visible sync status
- Adopt roles and approvals: carry over customer groups, limits and approval paths from the shop
- Test and refine in the field: check on real devices, with poor signal and with real customer visits
Whoever thinks of the field sales app from the start as an extension of the B2B shop - on one data base, offline-capable and with the same rules - gains a cleanly captured order at every customer visit, without paper and without re-typing. Sales become faster and more reliable, the sales desk is relieved, and the customer experiences the same data quality on site as in the shop. Which routes make sense for your assortment and processes is shown by comparable project approaches; the concrete implementation and connection to Shopware and ERP we are glad to discuss as part of our interface and integration services.