A barcode-scanning mobile app for SAP Business One that posts Inventory Counting, Stock Transfers, Goods Receipts and Goods Issues in real time. Built to order for your company database after a scoping call and fixed quote. Built to order by ECOSIRE for SAP Business One (build-to-order) — indicative price from $699.00 USD; request a quote for a scoped proposal.
A barcode-scanning mobile app for SAP Business One that posts Inventory Counting, Stock Transfers, Goods Receipts and Goods Issues in real time. Built to order for your company database after a scoping call and fixed quote.
Built to order
Most SAP Business One sites still count stock on paper or in a spreadsheet. A storeman walks the aisles with a printed list, writes quantities in a column, hands the sheet to an accounts clerk, and someone keys the numbers into the Inventory Counting window hours or days later. By the time the count posts, the warehouse has moved again. Transfers between warehouses get written on a scrap of paper and entered late — or never. Goods arriving against a Purchase Order sit on the receiving dock until someone has time to open SAP and key the Goods Receipt PO line by line.
The result is familiar: negative stock warnings, sales orders committed against quantities that do not exist, month-end variances nobody can explain, and a physical count that takes the whole weekend because every discrepancy has to be traced by hand.
SAP Business One already holds the correct data model for all of this. What it does not give you is a fast, offline-tolerant scanning interface that a warehouse operator can use with gloves on. That is what this app is.
We build a mobile scanning application — Android and iOS handhelds, or rugged Windows scanners where you already own them — that talks to your SAP Business One company database through the Service Layer REST interface, with the DI API used server-side where a document type or add-on dependency requires it. Nothing is stored in a parallel database that later has to be reconciled: every scan becomes a real SAP B1 document.
Operators open a count assignment, scan a bin or warehouse location, then scan each item barcode and key or scan the quantity. The app builds an Inventory Counting document (and the follow-on Inventory Posting for approved variances) against the correct warehouse. Counts can be full or cycle-based, filtered by item group, warehouse, bin location, or an ABC classification held in a UDF. Recounts are triggered automatically when a line variance exceeds a tolerance you define — by percentage, by value, or both.
The same handheld handles the other three high-volume transactions:
The app reads your existing item barcodes from the SAP B1 barcode table, and we can add GS1-128 parsing so a single scan of a supplier label populates item, batch, expiry and quantity in one action. Where an item is batch- or serial-managed, the app collects the required allocation at the point of scan rather than leaving the document incomplete for a clerk to finish later.
Warehouses have dead zones. The app queues transactions locally when the Service Layer is unreachable and posts them in order when the connection returns, with a visible queue the operator can inspect. Conflicts — a line already counted, a PO closed in the meantime — are surfaced for resolution rather than silently dropped.
Count assignments, tolerance rules and device registrations are stored in User-Defined Tables and exposed as User-Defined Objects so they are backed up, authorised and audited by SAP itself. Additional data you need on a line — a reason code, a pallet ID, an inspector initial — is carried in UDFs on the marketing or inventory document so it flows into your existing Crystal Reports without a separate reporting stack.
SAP Business One sites running one to a handful of warehouses that want accuracy now and are not ready to buy, configure and staff a full warehouse management system. Distributors, light manufacturers, food and beverage wholesalers, spare-parts operations, and any company whose auditors have started asking hard questions about the stock figure on the balance sheet.
If you already run a full WMS with wave picking, task interleaving and slotting optimisation, this is not a replacement for it. If you are counting on paper, this is the shortest path to a warehouse number you can defend.
Built for SAP Business One 10.0 on both Microsoft SQL Server and SAP HANA, on-premise or cloud-hosted. Authentication uses Service Layer sessions against real SAP users, so every posted document carries the correct user in its audit trail and obeys the authorisations, posting periods and approval procedures you have already configured. Where your licensing gives operators indirect access, we scope the named-user model with you before quoting — we do not guess at your licence position.
1. Scoping call. We walk your current count and receipt process, list the document types in play, confirm your SAP B1 version, database platform, hosting and handheld hardware, and agree what is in scope. 2. Fixed quote. You receive a written scope with a fixed price and a delivery date. Nothing starts until you approve it. 3. Build. We develop against a copy of your data structure, not a generic demo database, so item masters, warehouses, bin setup and UDFs match your reality. 4. Install in test. The add-on is installed into your test company database first. You count a real aisle with real people and real scanners, and we adjust before anything touches live. 5. Install in production. Once you sign off on the test run, we install into the production company database and support the first live count or receipt session. 6. Support window. A defect-fix support period runs from go-live, with an optional extension afterwards.
Lead time is typically two to four weeks from approved quote, depending on how many document types and how much barcode label rework is in scope. This app is built for you on order — it is not a pre-packaged download, and there is no trial binary, because until we have scoped your warehouse there is nothing to trial.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
Runs counts on paper and spends the days afterwards chasing variances that nobody can explain because the count sheet and the posting happened hours apart. Scanning directly into Inventory Counting removes the transcription step entirely, and the recount tolerance flags a suspect line while the operator is still standing in the aisle.
Has to sign off an inventory value at period end and currently relies on a count whose accuracy is asserted rather than evidenced. Every movement becoming a real SAP B1 document with the correct user, timestamp and Journal Entry gives an audit trail that stands up to questioning, and cycle counts spread the work across the year instead of one chaotic weekend.
Is asked for warehouse accuracy but does not want a second database that drifts out of sync with SAP or a black-box add-on nobody can support. Because everything posts through the Service Layer into standard documents and all custom data lives in UDTs and UDFs inside the company database, backup, authorisations and upgrades stay under SAP's control.
| Criterion | ECOSIRE | Custom Build | Competitor |
|---|---|---|---|
| Barcode scanning posts directly into SAP B1 documents | Included | Included | Included |
| Offline queue with ordered replay and conflict surfacing | Included |
From $699.00
Starting point — quoted to your scope
| Partial support |
| Automatic recount trigger on value or percentage variance tolerance | Included | Partial support | Partial support |
|---|
| Batch and serial allocation captured at the point of scan | Included | Partial support | Included |
|---|
| Custom data held in UDTs/UDFs inside the company database, not a side system | Included | Partial support | Partial support |
|---|
| Fixed price agreed before any development begins | Included | Not included | Included |
|---|
| Installed and piloted in your test company database before production | Included | Partial support | Partial support |
|---|
| Source-level changes to scanning rules after go-live without vendor roadmap dependency | Included | Included | Not included |
|---|
A build-to-order SAP Business One integration with your 3PL: order release, shipment and tracking confirmation, receipts and stock adjustments posted automatically, built to your provider's spec.
A SAP Business One add-on that syncs Amazon Seller Central orders, FBA inventory, settlements and returns into Sales Orders and A/R Invoices. Built to order for your company database after a scoping call.
A build-to-order B2B portal on top of SAP Business One letting wholesale customers reorder at their own contract pricing, check availability, track Deliveries and download A/R Invoices. Built for your catalogue and pricing after a scoped quotation.
One-click forward and backward genealogy across batches and serials in SAP Business One, with FEFO allocation, expiry control and recall reporting. Built to order for your company database after a scoping call and fixed quote.