Custom order app development
An ordering app is built for the customer who needs the same fifty items every week, not for the visitor who browses once. Appfront builds custom ordering apps for wholesalers, manufacturers and suppliers: ordering from the shop floor, with the right customer price, the right stock level and an order that lands directly in your ERP.
What is an ordering app?
An ordering app is a mobile application that lets business customers order directly from you, usually from the place where they see that something is running low: the warehouse, the cold store, the building site or the shelf. The difference from a webshop lies in user behaviour. They don't search, they repeat. They already know the item, want to know if it's in stock and want to be done in a few steps.
That is why the search bar is rarely the most important part of a good ordering app. More often it is the previous order, the customer's own item list and the barcode scanner. If you work with GS1 article numbers, the phone's camera can serve as a scanner: the GTIN on the packaging points straight to the right item, even if the customer doesn't know your internal item code. For deliveries to multiple locations, the same principle works with GLN location codes.
This page is about the app. If you want customers to order via the browser, see building an ordering portal or the B2B e-commerce portal. If you're concerned with processing after the order is placed, a custom order management system is the right starting point.
Repeating instead of searching
The app opens on the customer's previous order and their own item list. Copying and adjusting a standing order takes a few steps, instead of the buyer having to search for the same items all over again every week.
The price this customer pays
Customer-specific prices, volume tiers, contract terms and promotions come from your ERP and apply identically in every channel. Buyers see straight away how a larger order affects the unit price, without phoning or digging out a price list.
Even without a good connection
In a cold store, a warehouse or on a building site, the connection drops. The app builds the order locally and sends it as soon as the network is back, so a half-finished order doesn't get lost.
How we build your ordering app
An ordering app stands or falls on how well it connects to your product range, your pricing agreements and your order processing. So we start with the data you already have and with how your customers actually order.
We map out your product range, pricing structure and order flow: how products are structured, which volume tiers and customer agreements apply, and what happens to an order once it comes in. We also look at who orders and under what conditions.
We design the ordering flow around repeat orders and speed, and the data model around product, customer, price and stock. In doing so, we define which data comes live from the ERP and which the app keeps available locally.
We build in short iterations and test with real customers, because reality on the shop floor almost always differs from what was devised in the office. We build integrations early, so the order flow works from end to end.
A controlled rollout to a first group of customers, followed by a wider rollout, monitoring for failed orders and ongoing development as your product range and agreements change.
What an ordering app actually does
The structure differs by industry, but these components appear in almost every ordering app we build for business customers.
Scan and order
The camera reads the barcode on a package or shelf and adds the product straight to the order. With GS1 article numbers, this also works on your suppliers' packaging, so customers don't need to know your internal coding.
Order lists per customer
Fixed lists per branch, department or buyer, with the customer's own naming alongside your product description. This saves searching and prevents the wrong variant from being ordered by accident.
Prices and volume tiers from the ERP
Customer prices, volume discounts, contract prices and promotions come directly from Exact Online, AFAS, Microsoft Dynamics 365 Business Central, SAP or whichever package you use. That way, the price in the app is the same as on the invoice.
Stock and lead time
Current stock levels and expected delivery date per product, plus alternatives if something isn't available. Buyers see what is arriving and when before they complete the order, instead of having to phone to find out.
Order confirmation and delivery tracking
The order goes to your order processing and the status comes back to the app: confirmed, picked, on its way. If you work with EDI, the confirmation (ORDRSP) and the dispatch advice (DESADV) can feed those statuses automatically.
Ordering on behalf of the customer
Your sales rep or driver orders on the spot on behalf of the customer, with the same prices and agreements and a record of who placed the order. Handy for customers who would rather have someone order for them than open an app themselves.
Who we build ordering apps for
Repeat ordering looks different in each sector. These are the types of organisation we come across most often.
Wholesalers and distributors
Organisations with a broad product range, customer-specific pricing agreements and customers who order at regular intervals. See also custom wholesale software development and the specific approach for fruit and vegetable wholesalers.
Manufacturers with their own sales
Producers who supply directly to dealers, installers or processors and want to move ordering away from the phone and the inbox, without abandoning their existing agreements.
Hospitality and food suppliers
Suppliers whose customers order several times a week based on what is in the chiller. Speed, stock visibility and a reliable cut-off time matter more here than an elaborate product showcase.
Technical and construction suppliers
Suppliers who receive orders from the building site or the service van, where connectivity comes and goes and gloves dictate how the app is operated. For the related B2B context, see also building a B2B app.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
The app is nothing without the integration underneath it. Items, customer prices, stock and order status come from your ERP, and the order must land back there without manual intervention. If you work with supply chain partners who exchange data via EDI, we connect to the messages that go with it: ORDERS for the purchase order, ORDRSP for the confirmation, DESADV for the dispatch advice and INVOIC for the invoice, exchanged via AS2, SFTP or a VAN provider. For invoices to the public sector and a growing number of business customers, this runs via Peppol. See also building an EDI integration.
If you supply ships and want orders to be signed off on board, take a look at our order handling app for ship supply.
Payment works differently in an ordering app than many clients expect. Because it involves physical goods delivered outside the app, Apple's App Store Review Guidelines (section 3.1.5) actually require you to use a payment method other than in-app purchases. In practice, that means payment on account, direct debit or iDEAL, exactly as you do today. More about our approach: building an app and building software.
Why choose Appfront for your ordering app?
Appfront builds custom software with smart technology and considered design, working in design and development sprints. For an ordering app, that means we start with your pricing structure and order flow, not with the screen. A beautiful app that shows the wrong price will cost you more than it delivers.
Standard B2B web shop platforms often get stuck on precisely the things your customers deal with every day: tiered pricing that differs per customer and per product group, packaging units that are not the same as the order unit, or a range that varies per branch. Custom software lets you follow that logic rather than work around it.
The process starts with a no-obligation introductory meeting, followed by planning, development and maintenance. Because the app relies on your ERP, we involve your application manager or ERP partner early in the process.
Also take a look at our wider services: building an app, building software and building point-of-sale software. Do you have questions? Get in touch.
- Custom apps for iOS, Android and web
- Ordering flow designed around repeat orders and speed
- Customer prices, tiered pricing and contract terms from your ERP
- Barcode scanning with GS1 item numbers
- Order offline and synchronise as soon as there is a network
- Integrations with Exact Online, AFAS, Dynamics and SAP
- EDI messages and Peppol for supply chain data exchange
- Order status fed back into the app for the customer placing the order
- Ordering on behalf of the customer by sales rep or driver
- Ongoing management, monitoring and further development
Security and reliability of an ordering app
An ordering app carries commercially sensitive information: your agreed prices per customer. Authorisation is therefore never an afterthought. Each user sees only the product range, prices and delivery addresses of their own organisation, and within a single customer you can distinguish between who may order and who may only view or must approve.
Reliability is the other half of the story. An order that quietly disappears in the integration with your ERP costs more than an outage that is visible. That is why we build order flows with confirmation and recovery: failed messages go into a queue, are resubmitted, and, if errors persist, go to a member of staff rather than to a log file nobody reads. We process the personal data of people placing orders in accordance with the GDPR.
More about our approach to security: information security policy and coordinated vulnerability disclosure policy. Discuss your situation without obligation via our contact form.
- Prices and product range strictly separated per customer
- Roles for ordering, viewing and approving
- Encryption in transit (TLS 1.2+) and at rest
- GDPR-compliant processing of user data
- Order flows with confirmation, queueing and recovery
- Alerts for failed or stuck orders
- Audit logging of orders and price changes
- Monitoring and alerting on the ERP integration
Frequently asked questions about an ordering app
Answers to the questions we get asked most often about custom ordering apps for business customers.
An ordering app is a mobile application that lets business customers order directly from you, usually from the place where the item is running low. Usage differs from a webshop: the customer is not searching for products but repeating an order they already know. The app is therefore built around previous orders, standing order lists and scanning, with the right customer price and current stock alongside.
An ordering portal runs in the browser and is strong when someone at a desk puts together a large order or needs documents and history at hand. An app is strong on the shop floor: scanning, quick repeat orders and carrying on working when the connection drops. Many organisations combine both on the same data. See also our page on building an ordering portal.
Yes, and that is usually the most important part of the project. We integrate with packages such as Exact Online, AFAS, Microsoft Dynamics 365 Business Central and SAP, and with custom systems via an API. Products, customer prices, tiered pricing and stock come from there, and the order lands back in it without a manual step in between. Which data is retrieved live and which the app keeps locally for a while is decided in the design.
Yes. If you work with customers or chain partners who exchange data via EDI, we connect to the usual EDIFACT messages: ORDERS for the purchase order, ORDRSP for the order confirmation, DESADV for the dispatch advice and INVOIC for the invoice, via AS2, SFTP or a VAN provider. For e-invoicing to the public sector and a growing number of business customers, we use Peppol.
For physical goods delivered outside the app, Apple's guideline 3.1.5 of the App Store Review Guidelines requires that you do not use in-app purchases but a regular payment method instead. In B2B this almost always means delivery on account with existing payment terms, optionally supplemented by direct debit or iDEAL for customers without a credit limit.
Largely, yes, if we design for it. The product range, customer prices and order lists can remain available locally, so the person ordering can simply carry on working in a cold store, warehouse or cellar. The order is built locally and sent as soon as there is a connection again. There is one caveat for stock levels: they are only up to date when there is a connection, and we make that visible in the interface.
Yes. We model the customer organisation explicitly, with branches, departments and buyers beneath it. At each level you can set up separate order lists, delivery addresses and permissions, and, if you wish, add an approval step above a certain order value. That way a branch employee can place orders while head office keeps control over what is purchased.
We build custom software. For B2B ordering, standard platforms often get stuck on price tiers that differ per customer and product group, packaging units that differ from the order unit, or ranges that vary per branch. Custom software lets the app follow your logic rather than the other way round, and it can grow along when your range or agreements change.
Ready to build your ordering app?
Tell us how your customers currently order: by phone, by email, with a spreadsheet or in a portal that doesn't fit how things work on the shop floor. We're happy to think along on the ordering flow, the integration with your ERP and how you keep price agreements consistent across every channel. The first conversation is free of obligation.